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 54 archive entries
Page 1 of 3
Designing for maintainability: Backup and recovery
Data protection requires tested recovery objectives, not only confidence that a backup exists. This retrospective daily note considers how another team will understand, support and safely change the solution.
Read daily noteDesigning for maintainability: Deployment observability
Delivery metrics should show whether change is becoming safer and faster, not merely count deployments. This retrospective daily note considers how another team will understand, support and safely change the solution.
Read daily noteDesigning for maintainability: Environment strategy
Each Salesforce environment should have a clear purpose, data posture and refresh rhythm. This retrospective daily note considers how another team will understand, support and safely change the solution.
Read daily noteDesigning for maintainability: 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 another team will understand, support and safely change the solution.
Read daily noteDesigning for maintainability: Flow governance
Flow makes automation accessible, which increases the need for shared design and lifecycle standards. This retrospective daily note considers how another team will understand, support and safely change the solution.
Read daily noteDesigning for maintainability: Permission-set strategy
A scalable access model grants capability through composable permission sets rather than profile sprawl. This retrospective daily note considers how another team will understand, support and safely change the solution.
Read daily noteThe cost of complexity: Backup and recovery
Data protection requires tested recovery objectives, not only confidence that a backup exists. This retrospective daily note considers where unnecessary components and customisation create recurring operating cost.
Read daily noteThe cost of complexity: Deployment observability
Delivery metrics should show whether change is becoming safer and faster, not merely count deployments. This retrospective daily note considers where unnecessary components and customisation create recurring operating cost.
Read daily noteThe cost of complexity: Environment strategy
Each Salesforce environment should have a clear purpose, data posture and refresh rhythm. This retrospective daily note considers where unnecessary components and customisation create recurring operating cost.
Read daily noteThe cost of complexity: 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 where unnecessary components and customisation create recurring operating cost.
Read daily noteThe cost of complexity: Flow governance
Flow makes automation accessible, which increases the need for shared design and lifecycle standards. This retrospective daily note considers where unnecessary components and customisation create recurring operating cost.
Read daily noteThe cost of complexity: Permission-set strategy
A scalable access model grants capability through composable permission sets rather than profile sprawl. This retrospective daily note considers where unnecessary components and customisation create recurring operating cost.
Read daily noteSecurity by design: Backup and recovery
Data protection requires tested recovery objectives, not only confidence that a backup exists. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Deployment observability
Delivery metrics should show whether change is becoming safer and faster, not merely count deployments. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Environment strategy
Each Salesforce environment should have a clear purpose, data posture and refresh rhythm. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: 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 access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Flow governance
Flow makes automation accessible, which increases the need for shared design and lifecycle standards. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteSecurity by design: Permission-set strategy
A scalable access model grants capability through composable permission sets rather than profile sprawl. This retrospective daily note considers how access, data exposure and accountability shape the implementation.
Read daily noteContaining technical debt: Backup and recovery
Data protection requires tested recovery objectives, not only confidence that a backup exists. This retrospective daily note considers how to prevent a short-term compromise from becoming permanent architecture.
Read daily noteContaining technical debt: Deployment observability
Delivery metrics should show whether change is becoming safer and faster, not merely count deployments. This retrospective daily note considers how to prevent a short-term compromise from becoming permanent architecture.
Read daily noteContaining technical debt: Environment strategy
Each Salesforce environment should have a clear purpose, data posture and refresh rhythm. This retrospective daily note considers how to prevent a short-term compromise from becoming permanent architecture.
Read daily noteContaining technical debt: 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 to prevent a short-term compromise from becoming permanent architecture.
Read daily noteContaining technical debt: Flow governance
Flow makes automation accessible, which increases the need for shared design and lifecycle standards. This retrospective daily note considers how to prevent a short-term compromise from becoming permanent architecture.
Read daily noteContaining technical debt: Permission-set strategy
A scalable access model grants capability through composable permission sets rather than profile sprawl. This retrospective daily note considers how to prevent a short-term compromise from becoming permanent architecture.
Read daily note