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 2 of 2
Observability before production: Deprecation tracking
Retirements and end-of-support notices need the same visibility as new features. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily noteObservability before production: 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 the signals and context required to support the capability once it is live.
Read daily noteObservability before production: Post-release validation
A successful deployment does not prove that every business journey works under production data and integrations. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily noteObservability before production: 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 the signals and context required to support the capability once it is live.
Read daily noteObservability before production: Critical update review
Critical updates can change security or runtime behaviour and deserve ownership before enforcement dates arrive. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily noteObservability before production: Seasonal regression testing
Regression testing should concentrate on high-impact journeys, custom automation and integration boundaries. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily noteObservability before production: Sandbox preview planning
Preview sandboxes provide a controlled window to evaluate upcoming platform behaviour before production changes. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily noteObservability before production: Release readiness
Each seasonal Salesforce release is a change programme, even when most features are enabled automatically and safely. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily notePlanning the migration: Deprecation tracking
Retirements and end-of-support notices need the same visibility as new features. This retrospective daily note considers how to move from the current state without losing service or trusted information.
Read daily notePlanning the migration: 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 to move from the current state without losing service or trusted information.
Read daily notePlanning the migration: 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 to move from the current state without losing service or trusted information.
Read daily notePlanning the migration: 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 to move from the current state without losing service or trusted information.
Read daily notePlanning the migration: Critical update review
Critical updates can change security or runtime behaviour and deserve ownership before enforcement dates arrive. This retrospective daily note considers how to move from the current state without losing service or trusted information.
Read daily notePlanning the migration: Seasonal regression testing
Regression testing should concentrate on high-impact journeys, custom automation and integration boundaries. This retrospective daily note considers how to move from the current state without losing service or trusted information.
Read daily notePlanning the migration: Sandbox preview planning
Preview sandboxes provide a controlled window to evaluate upcoming platform behaviour before production changes. This retrospective daily note considers how to move from the current state without losing service or trusted information.
Read daily notePlanning the migration: 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 to move from the current state without losing service or trusted information.
Read daily noteAdoption is architecture: Deprecation tracking
Retirements and end-of-support notices need the same visibility as new features. This retrospective daily note considers how the user experience and operating model determine whether the capability is used.
Read daily noteAdoption is architecture: 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 user experience and operating model determine whether the capability is used.
Read daily noteAdoption is architecture: 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 user experience and operating model determine whether the capability is used.
Read daily noteAdoption is architecture: 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 user experience and operating model determine whether the capability is used.
Read daily noteAdoption is architecture: 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 user experience and operating model determine whether the capability is used.
Read daily noteAdoption is architecture: Seasonal regression testing
Regression testing should concentrate on high-impact journeys, custom automation and integration boundaries. This retrospective daily note considers how the user experience and operating model determine whether the capability is used.
Read daily noteAdoption is architecture: Sandbox preview planning
Preview sandboxes provide a controlled window to evaluate upcoming platform behaviour before production changes. This retrospective daily note considers how the user experience and operating model determine whether the capability is used.
Read daily noteAdoption is architecture: 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 user experience and operating model determine whether the capability is used.
Read daily note