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 4 of 5
Making team hand-offs work: Backup and recovery
Data protection requires tested recovery objectives, not only confidence that a backup exists. This retrospective daily note considers the ownership and information needed when work crosses team boundaries.
Read daily noteMaking team hand-offs work: Deployment observability
Delivery metrics should show whether change is becoming safer and faster, not merely count deployments. This retrospective daily note considers the ownership and information needed when work crosses team boundaries.
Read daily noteMaking team hand-offs work: Environment strategy
Each Salesforce environment should have a clear purpose, data posture and refresh rhythm. This retrospective daily note considers the ownership and information needed when work crosses team boundaries.
Read daily noteMaking team hand-offs work: 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 ownership and information needed when work crosses team boundaries.
Read daily noteMaking team hand-offs work: Flow governance
Flow makes automation accessible, which increases the need for shared design and lifecycle standards. This retrospective daily note considers the ownership and information needed when work crosses team boundaries.
Read daily noteMaking team hand-offs work: Permission-set strategy
A scalable access model grants capability through composable permission sets rather than profile sprawl. This retrospective daily note considers the ownership and information needed when work crosses team boundaries.
Read daily noteGovernance without gridlock: Backup and recovery
Data protection requires tested recovery objectives, not only confidence that a backup exists. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Deployment observability
Delivery metrics should show whether change is becoming safer and faster, not merely count deployments. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Environment strategy
Each Salesforce environment should have a clear purpose, data posture and refresh rhythm. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: 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 create control without slowing every useful change.
Read daily noteGovernance without gridlock: Flow governance
Flow makes automation accessible, which increases the need for shared design and lifecycle standards. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Permission-set strategy
A scalable access model grants capability through composable permission sets rather than profile sprawl. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteFailure-first thinking: Backup and recovery
Data protection requires tested recovery objectives, not only confidence that a backup exists. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily noteFailure-first thinking: Deployment observability
Delivery metrics should show whether change is becoming safer and faster, not merely count deployments. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily noteFailure-first thinking: Environment strategy
Each Salesforce environment should have a clear purpose, data posture and refresh rhythm. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily noteFailure-first thinking: 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 what happens when dependencies, data or assumptions fail.
Read daily noteFailure-first thinking: Flow governance
Flow makes automation accessible, which increases the need for shared design and lifecycle standards. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily noteFailure-first thinking: Permission-set strategy
A scalable access model grants capability through composable permission sets rather than profile sprawl. This retrospective daily note considers what happens when dependencies, data or assumptions fail.
Read daily noteA practical architecture review: Backup and recovery
Data protection requires tested recovery objectives, not only confidence that a backup exists. This retrospective daily note considers the questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: Deployment observability
Delivery metrics should show whether change is becoming safer and faster, not merely count deployments. This retrospective daily note considers the questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: Environment strategy
Each Salesforce environment should have a clear purpose, data posture and refresh rhythm. This retrospective daily note considers the questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: 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 questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: Flow governance
Flow makes automation accessible, which increases the need for shared design and lifecycle standards. This retrospective daily note considers the questions an architecture review should ask before approving the design.
Read daily noteA practical architecture review: Permission-set strategy
A scalable access model grants capability through composable permission sets rather than profile sprawl. This retrospective daily note considers the questions an architecture review should ask before approving the design.
Read daily note