Salesforce daily archive
730 days of practical thinking.
One retrospective note for every day from 2 September 2024 to 1 September 2026.
Archive dates organise the subject history. They do not claim the notes were originally published on those dates.
Showing 144 archive entries
Page 3 of 6
Designing for maintainability: Deprecation tracking
Retirements and end-of-support notices need the same visibility as new features. This retrospective daily note considers how another team will understand, support and safely change the solution.
Read daily noteDesigning for maintainability: Feature adoption decisions
New platform capability creates value only when it solves a prioritised business need and has an accountable owner. This retrospective daily note considers how another team will understand, support and safely change the solution.
Read daily noteDesigning for maintainability: Post-release validation
A successful deployment does not prove that every business journey works under production data and integrations. This retrospective daily note considers how another team will understand, support and safely change the solution.
Read daily noteDesigning for maintainability: Release communication
Users need to understand the few changes that affect their work, not receive a copy of the complete release notes. This retrospective daily note considers how another team will understand, support and safely change the solution.
Read daily noteDesigning for maintainability: Critical update review
Critical updates can change security or runtime behaviour and deserve ownership before enforcement dates arrive. This retrospective daily note considers how another team will understand, support and safely change the solution.
Read daily noteDesigning for maintainability: Seasonal regression testing
Regression testing should concentrate on high-impact journeys, custom automation and integration boundaries. This retrospective daily note considers how another team will understand, support and safely change the solution.
Read daily noteDesigning for maintainability: Sandbox preview planning
Preview sandboxes provide a controlled window to evaluate upcoming platform behaviour before production changes. This retrospective daily note considers how another team will understand, support and safely change the solution.
Read daily noteDesigning for maintainability: Release readiness
Each seasonal Salesforce release is a change programme, even when most features are enabled automatically and safely. This retrospective daily note considers how another team will understand, support and safely change the solution.
Read daily noteThe cost of complexity: Deprecation tracking
Retirements and end-of-support notices need the same visibility as new features. This retrospective daily note considers where unnecessary components and customisation create recurring operating cost.
Read daily noteThe cost of complexity: Feature adoption decisions
New platform capability creates value only when it solves a prioritised business need and has an accountable owner. This retrospective daily note considers where unnecessary components and customisation create recurring operating cost.
Read daily noteThe cost of complexity: Post-release validation
A successful deployment does not prove that every business journey works under production data and integrations. This retrospective daily note considers where unnecessary components and customisation create recurring operating cost.
Read daily noteThe cost of complexity: Release communication
Users need to understand the few changes that affect their work, not receive a copy of the complete release notes. This retrospective daily note considers where unnecessary components and customisation create recurring operating cost.
Read daily noteThe cost of complexity: Critical update review
Critical updates can change security or runtime behaviour and deserve ownership before enforcement dates arrive. This retrospective daily note considers where unnecessary components and customisation create recurring operating cost.
Read daily noteThe cost of complexity: Seasonal regression testing
Regression testing should concentrate on high-impact journeys, custom automation and integration boundaries. This retrospective daily note considers where unnecessary components and customisation create recurring operating cost.
Read daily noteThe cost of complexity: Sandbox preview planning
Preview sandboxes provide a controlled window to evaluate upcoming platform behaviour before production changes. This retrospective daily note considers where unnecessary components and customisation create recurring operating cost.
Read daily noteThe cost of complexity: Release readiness
Each seasonal Salesforce release is a change programme, even when most features are enabled automatically and safely. This retrospective daily note considers where unnecessary components and customisation create recurring operating cost.
Read daily noteSecurity by design: Deprecation tracking
Retirements and end-of-support notices need the same visibility as new features. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Feature adoption decisions
New platform capability creates value only when it solves a prioritised business need and has an accountable owner. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Post-release validation
A successful deployment does not prove that every business journey works under production data and integrations. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Release communication
Users need to understand the few changes that affect their work, not receive a copy of the complete release notes. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Critical update review
Critical updates can change security or runtime behaviour and deserve ownership before enforcement dates arrive. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Seasonal regression testing
Regression testing should concentrate on high-impact journeys, custom automation and integration boundaries. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Sandbox preview planning
Preview sandboxes provide a controlled window to evaluate upcoming platform behaviour before production changes. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Release readiness
Each seasonal Salesforce release is a change programme, even when most features are enabled automatically and safely. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily note