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 4 of 6
Containing technical debt: Deprecation tracking
Retirements and end-of-support notices need the same visibility as new features. This retrospective daily note considers how to prevent a short-term compromise from becoming permanent architecture.
Read daily noteContaining technical debt: 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 prevent a short-term compromise from becoming permanent architecture.
Read daily noteContaining technical debt: 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 prevent a short-term compromise from becoming permanent architecture.
Read daily noteContaining technical debt: 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 prevent a short-term compromise from becoming permanent architecture.
Read daily noteContaining technical debt: 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 prevent a short-term compromise from becoming permanent architecture.
Read daily noteContaining technical debt: Seasonal regression testing
Regression testing should concentrate on high-impact journeys, custom automation and integration boundaries. This retrospective daily note considers how to prevent a short-term compromise from becoming permanent architecture.
Read daily noteContaining technical debt: Sandbox preview planning
Preview sandboxes provide a controlled window to evaluate upcoming platform behaviour before production changes. This retrospective daily note considers how to prevent a short-term compromise from becoming permanent architecture.
Read daily noteContaining technical debt: 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 prevent a short-term compromise from becoming permanent architecture.
Read daily noteMeasuring what matters: Deprecation tracking
Retirements and end-of-support notices need the same visibility as new features. This retrospective daily note considers the operational evidence that shows whether the design is creating value.
Read daily noteMeasuring what matters: 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 operational evidence that shows whether the design is creating value.
Read daily noteMeasuring what matters: 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 operational evidence that shows whether the design is creating value.
Read daily noteMeasuring what matters: 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 operational evidence that shows whether the design is creating value.
Read daily noteMeasuring what matters: Critical update review
Critical updates can change security or runtime behaviour and deserve ownership before enforcement dates arrive. This retrospective daily note considers the operational evidence that shows whether the design is creating value.
Read daily noteMeasuring what matters: Seasonal regression testing
Regression testing should concentrate on high-impact journeys, custom automation and integration boundaries. This retrospective daily note considers the operational evidence that shows whether the design is creating value.
Read daily noteMeasuring what matters: Sandbox preview planning
Preview sandboxes provide a controlled window to evaluate upcoming platform behaviour before production changes. This retrospective daily note considers the operational evidence that shows whether the design is creating value.
Read daily noteMeasuring what matters: 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 operational evidence that shows whether the design is creating value.
Read daily noteRecognising the anti-pattern: Deprecation tracking
Retirements and end-of-support notices need the same visibility as new features. This retrospective daily note considers the early signs that a convenient implementation is becoming long-term risk.
Read daily noteRecognising the anti-pattern: 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 early signs that a convenient implementation is becoming long-term risk.
Read daily noteRecognising the anti-pattern: 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 early signs that a convenient implementation is becoming long-term risk.
Read daily noteRecognising the anti-pattern: 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 early signs that a convenient implementation is becoming long-term risk.
Read daily noteRecognising the anti-pattern: Critical update review
Critical updates can change security or runtime behaviour and deserve ownership before enforcement dates arrive. This retrospective daily note considers the early signs that a convenient implementation is becoming long-term risk.
Read daily noteRecognising the anti-pattern: Seasonal regression testing
Regression testing should concentrate on high-impact journeys, custom automation and integration boundaries. This retrospective daily note considers the early signs that a convenient implementation is becoming long-term risk.
Read daily noteRecognising the anti-pattern: Sandbox preview planning
Preview sandboxes provide a controlled window to evaluate upcoming platform behaviour before production changes. This retrospective daily note considers the early signs that a convenient implementation is becoming long-term risk.
Read daily noteRecognising the anti-pattern: 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 early signs that a convenient implementation is becoming long-term risk.
Read daily note