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 108 archive entries
Page 1 of 5
Testing the business outcome: Backup and recovery
Data protection requires tested recovery objectives, not only confidence that a backup exists. This retrospective daily note considers how tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: Deployment observability
Delivery metrics should show whether change is becoming safer and faster, not merely count deployments. This retrospective daily note considers how tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: Environment strategy
Each Salesforce environment should have a clear purpose, data posture and refresh rhythm. This retrospective daily note considers how tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: Data-quality ownership
Data quality is an operating responsibility supported by technology, not a cleanup project owned only by administrators. This retrospective daily note considers how tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: Flow governance
Flow makes automation accessible, which increases the need for shared design and lifecycle standards. This retrospective daily note considers how tests can prove user and operational behaviour rather than implementation detail.
Read daily noteTesting the business outcome: Permission-set strategy
A scalable access model grants capability through composable permission sets rather than profile sprawl. This retrospective daily note considers how tests can prove user and operational behaviour rather than implementation detail.
Read daily noteRelease-ready engineering: Backup and recovery
Data protection requires tested recovery objectives, not only confidence that a backup exists. This retrospective daily note considers how the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: Deployment observability
Delivery metrics should show whether change is becoming safer and faster, not merely count deployments. This retrospective daily note considers how the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: Environment strategy
Each Salesforce environment should have a clear purpose, data posture and refresh rhythm. This retrospective daily note considers how the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: Data-quality ownership
Data quality is an operating responsibility supported by technology, not a cleanup project owned only by administrators. This retrospective daily note considers how the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: Flow governance
Flow makes automation accessible, which increases the need for shared design and lifecycle standards. This retrospective daily note considers how the capability will be tested against seasonal platform change.
Read daily noteRelease-ready engineering: Permission-set strategy
A scalable access model grants capability through composable permission sets rather than profile sprawl. This retrospective daily note considers how the capability will be tested against seasonal platform change.
Read daily noteProtecting the data contract: Backup and recovery
Data protection requires tested recovery objectives, not only confidence that a backup exists. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Deployment observability
Delivery metrics should show whether change is becoming safer and faster, not merely count deployments. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Environment strategy
Each Salesforce environment should have a clear purpose, data posture and refresh rhythm. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Data-quality ownership
Data quality is an operating responsibility supported by technology, not a cleanup project owned only by administrators. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Flow governance
Flow makes automation accessible, which increases the need for shared design and lifecycle standards. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Permission-set strategy
A scalable access model grants capability through composable permission sets rather than profile sprawl. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteObservability before production: Backup and recovery
Data protection requires tested recovery objectives, not only confidence that a backup exists. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily noteObservability before production: Deployment observability
Delivery metrics should show whether change is becoming safer and faster, not merely count deployments. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily noteObservability before production: Environment strategy
Each Salesforce environment should have a clear purpose, data posture and refresh rhythm. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily noteObservability before production: Data-quality ownership
Data quality is an operating responsibility supported by technology, not a cleanup project owned only by administrators. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily noteObservability before production: Flow governance
Flow makes automation accessible, which increases the need for shared design and lifecycle standards. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily noteObservability before production: Permission-set strategy
A scalable access model grants capability through composable permission sets rather than profile sprawl. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily note