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 5 of 6
Making team hand-offs work: Deprecation tracking
Retirements and end-of-support notices need the same visibility as new features. This retrospective daily note considers the ownership and information needed when work crosses team boundaries.
Read daily noteMaking team hand-offs work: 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 ownership and information needed when work crosses team boundaries.
Read daily noteMaking team hand-offs work: 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 ownership and information needed when work crosses team boundaries.
Read daily noteMaking team hand-offs work: 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 ownership and information needed when work crosses team boundaries.
Read daily noteMaking team hand-offs work: Critical update review
Critical updates can change security or runtime behaviour and deserve ownership before enforcement dates arrive. This retrospective daily note considers the ownership and information needed when work crosses team boundaries.
Read daily noteMaking team hand-offs work: Seasonal regression testing
Regression testing should concentrate on high-impact journeys, custom automation and integration boundaries. This retrospective daily note considers the ownership and information needed when work crosses team boundaries.
Read daily noteMaking team hand-offs work: Sandbox preview planning
Preview sandboxes provide a controlled window to evaluate upcoming platform behaviour before production changes. This retrospective daily note considers the ownership and information needed when work crosses team boundaries.
Read daily noteMaking team hand-offs work: 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 ownership and information needed when work crosses team boundaries.
Read daily noteGovernance without gridlock: Deprecation tracking
Retirements and end-of-support notices need the same visibility as new features. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: 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 create control without slowing every useful change.
Read daily noteGovernance without gridlock: 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 create control without slowing every useful change.
Read daily noteGovernance without gridlock: 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 create control without slowing every useful change.
Read daily noteGovernance without gridlock: 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 create control without slowing every useful change.
Read daily noteGovernance without gridlock: Seasonal regression testing
Regression testing should concentrate on high-impact journeys, custom automation and integration boundaries. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Sandbox preview planning
Preview sandboxes provide a controlled window to evaluate upcoming platform behaviour before production changes. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: 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 create control without slowing every useful change.
Read daily noteFailure-first thinking: Deprecation tracking
Retirements and end-of-support notices need the same visibility as new features. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily noteFailure-first thinking: 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 what happens when dependencies, data or assumptions fail.
Read daily noteFailure-first thinking: Post-release validation
A successful deployment does not prove that every business journey works under production data and integrations. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily noteFailure-first thinking: 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 what happens when dependencies, data or assumptions fail.
Read daily noteFailure-first thinking: Critical update review
Critical updates can change security or runtime behaviour and deserve ownership before enforcement dates arrive. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily noteFailure-first thinking: Seasonal regression testing
Regression testing should concentrate on high-impact journeys, custom automation and integration boundaries. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily noteFailure-first thinking: Sandbox preview planning
Preview sandboxes provide a controlled window to evaluate upcoming platform behaviour before production changes. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily noteFailure-first thinking: Release readiness
Each seasonal Salesforce release is a change programme, even when most features are enabled automatically and safely. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily note