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 3 of 5
Security 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 noteMeasuring what matters: Backup and recovery
Data protection requires tested recovery objectives, not only confidence that a backup exists. This retrospective daily note considers the operational evidence that shows whether the design is creating value.
Read daily noteMeasuring what matters: Deployment observability
Delivery metrics should show whether change is becoming safer and faster, not merely count deployments. This retrospective daily note considers the operational evidence that shows whether the design is creating value.
Read daily noteMeasuring what matters: Environment strategy
Each Salesforce environment should have a clear purpose, data posture and refresh rhythm. This retrospective daily note considers the operational evidence that shows whether the design is creating value.
Read daily noteMeasuring what matters: 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 operational evidence that shows whether the design is creating value.
Read daily noteMeasuring what matters: Flow governance
Flow makes automation accessible, which increases the need for shared design and lifecycle standards. This retrospective daily note considers the operational evidence that shows whether the design is creating value.
Read daily noteMeasuring what matters: Permission-set strategy
A scalable access model grants capability through composable permission sets rather than profile sprawl. This retrospective daily note considers the operational evidence that shows whether the design is creating value.
Read daily noteRecognising the anti-pattern: Backup and recovery
Data protection requires tested recovery objectives, not only confidence that a backup exists. This retrospective daily note considers the early signs that a convenient implementation is becoming long-term risk.
Read daily noteRecognising the anti-pattern: Deployment observability
Delivery metrics should show whether change is becoming safer and faster, not merely count deployments. This retrospective daily note considers the early signs that a convenient implementation is becoming long-term risk.
Read daily noteRecognising the anti-pattern: Environment strategy
Each Salesforce environment should have a clear purpose, data posture and refresh rhythm. This retrospective daily note considers the early signs that a convenient implementation is becoming long-term risk.
Read daily noteRecognising the anti-pattern: 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 early signs that a convenient implementation is becoming long-term risk.
Read daily noteRecognising the anti-pattern: Flow governance
Flow makes automation accessible, which increases the need for shared design and lifecycle standards. This retrospective daily note considers the early signs that a convenient implementation is becoming long-term risk.
Read daily noteRecognising the anti-pattern: Permission-set strategy
A scalable access model grants capability through composable permission sets rather than profile sprawl. This retrospective daily note considers the early signs that a convenient implementation is becoming long-term risk.
Read daily note