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 36 archive entries
Page 2 of 2
Planning the migration: Backup and recovery
Data protection requires tested recovery objectives, not only confidence that a backup exists. This retrospective daily note considers how to move from the current state without losing service or trusted information.
Read daily notePlanning the migration: Deployment observability
Delivery metrics should show whether change is becoming safer and faster, not merely count deployments. This retrospective daily note considers how to move from the current state without losing service or trusted information.
Read daily notePlanning the migration: Environment strategy
Each Salesforce environment should have a clear purpose, data posture and refresh rhythm. This retrospective daily note considers how to move from the current state without losing service or trusted information.
Read daily notePlanning the migration: 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 move from the current state without losing service or trusted information.
Read daily notePlanning the migration: Flow governance
Flow makes automation accessible, which increases the need for shared design and lifecycle standards. This retrospective daily note considers how to move from the current state without losing service or trusted information.
Read daily notePlanning the migration: Permission-set strategy
A scalable access model grants capability through composable permission sets rather than profile sprawl. This retrospective daily note considers how to move from the current state without losing service or trusted information.
Read daily noteAdoption is architecture: Backup and recovery
Data protection requires tested recovery objectives, not only confidence that a backup exists. This retrospective daily note considers how the user experience and operating model determine whether the capability is used.
Read daily noteAdoption is architecture: Deployment observability
Delivery metrics should show whether change is becoming safer and faster, not merely count deployments. This retrospective daily note considers how the user experience and operating model determine whether the capability is used.
Read daily noteAdoption is architecture: Environment strategy
Each Salesforce environment should have a clear purpose, data posture and refresh rhythm. This retrospective daily note considers how the user experience and operating model determine whether the capability is used.
Read daily noteAdoption is architecture: 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 user experience and operating model determine whether the capability is used.
Read daily noteAdoption is architecture: Flow governance
Flow makes automation accessible, which increases the need for shared design and lifecycle standards. This retrospective daily note considers how the user experience and operating model determine whether the capability is used.
Read daily noteAdoption is architecture: Permission-set strategy
A scalable access model grants capability through composable permission sets rather than profile sprawl. This retrospective daily note considers how the user experience and operating model determine whether the capability is used.
Read daily note