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 5 of 5
The decision before the tool: Backup and recovery
Data protection requires tested recovery objectives, not only confidence that a backup exists. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: Deployment observability
Delivery metrics should show whether change is becoming safer and faster, not merely count deployments. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: Environment strategy
Each Salesforce environment should have a clear purpose, data posture and refresh rhythm. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: 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 business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: Flow governance
Flow makes automation accessible, which increases the need for shared design and lifecycle standards. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteThe decision before the tool: Permission-set strategy
A scalable access model grants capability through composable permission sets rather than profile sprawl. This retrospective daily note considers the business decision that must be clear before choosing a Salesforce feature.
Read daily noteDesigning for scale: Backup and recovery
Data protection requires tested recovery objectives, not only confidence that a backup exists. This retrospective daily note considers how the decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: Deployment observability
Delivery metrics should show whether change is becoming safer and faster, not merely count deployments. This retrospective daily note considers how the decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: Environment strategy
Each Salesforce environment should have a clear purpose, data posture and refresh rhythm. This retrospective daily note considers how the decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: 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 decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: Flow governance
Flow makes automation accessible, which increases the need for shared design and lifecycle standards. This retrospective daily note considers how the decision behaves when volume, users and connected systems grow.
Read daily noteDesigning for scale: Permission-set strategy
A scalable access model grants capability through composable permission sets rather than profile sprawl. This retrospective daily note considers how the decision behaves when volume, users and connected systems grow.
Read daily note