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 48 archive entries
Page 1 of 2
Testing the business outcome: Deprecation tracking
Retirements and end-of-support notices need the same visibility as new features. This retrospective daily note considers how tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: 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 tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: 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 tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: 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 tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: Critical update review
Critical updates can change security or runtime behaviour and deserve ownership before enforcement dates arrive. This retrospective daily note considers how tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: Seasonal regression testing
Regression testing should concentrate on high-impact journeys, custom automation and integration boundaries. This retrospective daily note considers how tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: Sandbox preview planning
Preview sandboxes provide a controlled window to evaluate upcoming platform behaviour before production changes. This retrospective daily note considers how tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: 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 tests can prove user and operational behaviour rather than implementation detail.
Read daily noteRelease-ready engineering: Deprecation tracking
Retirements and end-of-support notices need the same visibility as new features. This retrospective daily note considers how the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: 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 the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: 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 the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: 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 the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: Critical update review
Critical updates can change security or runtime behaviour and deserve ownership before enforcement dates arrive. This retrospective daily note considers how the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: Seasonal regression testing
Regression testing should concentrate on high-impact journeys, custom automation and integration boundaries. This retrospective daily note considers how the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: Sandbox preview planning
Preview sandboxes provide a controlled window to evaluate upcoming platform behaviour before production changes. This retrospective daily note considers how the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: 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 the capability will be tested against seasonal platform change.
Read daily noteProtecting the data contract: Deprecation tracking
Retirements and end-of-support notices need the same visibility as new features. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: 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 meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: 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 meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: 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 meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Critical update review
Critical updates can change security or runtime behaviour and deserve ownership before enforcement dates arrive. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Seasonal regression testing
Regression testing should concentrate on high-impact journeys, custom automation and integration boundaries. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Sandbox preview planning
Preview sandboxes provide a controlled window to evaluate upcoming platform behaviour before production changes. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: 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 meaning, validation and change control keep producers and consumers aligned.
Read daily note