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 24 archive entries
Page 1 of 1
A practical architecture review: Deprecation tracking
Retirements and end-of-support notices need the same visibility as new features. This retrospective daily note considers the questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: 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 questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: 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 questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: 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 questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: Critical update review
Critical updates can change security or runtime behaviour and deserve ownership before enforcement dates arrive. This retrospective daily note considers the questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: Seasonal regression testing
Regression testing should concentrate on high-impact journeys, custom automation and integration boundaries. This retrospective daily note considers the questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: Sandbox preview planning
Preview sandboxes provide a controlled window to evaluate upcoming platform behaviour before production changes. This retrospective daily note considers the questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: 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 questions an architecture review should ask before approving the design.
Read daily noteThe decision before the tool: Deprecation tracking
Retirements and end-of-support notices need the same visibility as new features. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: 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 business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: 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 business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: 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 business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: Critical update review
Critical updates can change security or runtime behaviour and deserve ownership before enforcement dates arrive. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: Seasonal regression testing
Regression testing should concentrate on high-impact journeys, custom automation and integration boundaries. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: Sandbox preview planning
Preview sandboxes provide a controlled window to evaluate upcoming platform behaviour before production changes. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: 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 business decision that must be clear before choosing a Salesforce feature.
Read daily noteDesigning for scale: Deprecation tracking
Retirements and end-of-support notices need the same visibility as new features. This retrospective daily note considers how the decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: 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 decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: 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 decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: 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 decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: 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 decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: Seasonal regression testing
Regression testing should concentrate on high-impact journeys, custom automation and integration boundaries. This retrospective daily note considers how the decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: Sandbox preview planning
Preview sandboxes provide a controlled window to evaluate upcoming platform behaviour before production changes. This retrospective daily note considers how the decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: 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 decision behaves when volume, users and connected systems grow.
Read daily note