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 730 archive entries
Page 11 of 31
Adoption is architecture: Data virtualisation
External data can sometimes remain in its source while Salesforce presents it at the point of work. This retrospective daily note considers how the user experience and operating model determine whether the capability is used.
Read daily noteAdoption is architecture: Transaction boundaries
Cross-system work cannot rely on one database transaction to guarantee an all-or-nothing outcome. This retrospective daily note considers how the user experience and operating model determine whether the capability is used.
Read daily noteAdoption is architecture: Idempotent integrations
A request may be delivered more than once; a dependable receiver must make repetition safe. This retrospective daily note considers how the user experience and operating model determine whether the capability is used.
Read daily noteAdoption is architecture: Error recovery
Failure handling is part of the business process, not a technical appendix added after the happy path. This retrospective daily note considers how the user experience and operating model determine whether the capability is used.
Read daily noteAdoption is architecture: API boundaries
An API should expose a stable business capability rather than mirror a database or a single user interface. This retrospective daily note considers how the user experience and operating model determine whether the capability is used.
Read daily noteAdoption is architecture: Customer identity across systems
Identity resolution is the foundation of a coherent customer view across Salesforce and connected platforms. This retrospective daily note considers how the user experience and operating model determine whether the capability is used.
Read daily noteAdoption is architecture: Master data decisions
A connected estate needs a clear answer to which system is authoritative for each important business fact. This retrospective daily note considers how the user experience and operating model determine whether the capability is used.
Read daily noteAdoption is architecture: Event-driven Salesforce
Events allow systems to announce meaningful change without controlling every downstream reaction. This retrospective daily note considers how the user experience and operating model determine whether the capability is used.
Read daily noteAdoption is architecture: Synchronous or asynchronous
Timing is an architectural decision: a process should wait only when the immediate response genuinely changes the next action. This retrospective daily note considers how the user experience and operating model determine whether the capability is used.
Read daily noteAdoption is architecture: Integration ownership
Every integration needs an explicit owner for its business contract, data meaning and operational health. This retrospective daily note considers how the user experience and operating model determine whether the capability is used.
Read daily noteDesigning 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 noteDesigning for maintainability: Deprecation tracking
Retirements and end-of-support notices need the same visibility as new features. This retrospective daily note considers how another team will understand, support and safely change the solution.
Read daily noteDesigning for maintainability: Feature adoption decisions
New platform capability creates value only when it solves a prioritised business need and has an accountable owner. This retrospective daily note considers how another team will understand, support and safely change the solution.
Read daily noteDesigning for maintainability: Post-release validation
A successful deployment does not prove that every business journey works under production data and integrations. This retrospective daily note considers how another team will understand, support and safely change the solution.
Read daily noteDesigning for maintainability: Release communication
Users need to understand the few changes that affect their work, not receive a copy of the complete release notes. This retrospective daily note considers how another team will understand, support and safely change the solution.
Read daily noteDesigning for maintainability: Critical update review
Critical updates can change security or runtime behaviour and deserve ownership before enforcement dates arrive. This retrospective daily note considers how another team will understand, support and safely change the solution.
Read daily noteDesigning for maintainability: Seasonal regression testing
Regression testing should concentrate on high-impact journeys, custom automation and integration boundaries. This retrospective daily note considers how another team will understand, support and safely change the solution.
Read daily noteDesigning for maintainability: Sandbox preview planning
Preview sandboxes provide a controlled window to evaluate upcoming platform behaviour before production changes. This retrospective daily note considers how another team will understand, support and safely change the solution.
Read daily noteDesigning for maintainability: Release readiness
Each seasonal Salesforce release is a change programme, even when most features are enabled automatically and safely. This retrospective daily note considers how another team will understand, support and safely change the solution.
Read daily note