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 365 archive entries
Page 13 of 16
Governance 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 noteGovernance without gridlock: Deprecation tracking
Retirements and end-of-support notices need the same visibility as new features. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: 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 to create control without slowing every useful change.
Read daily noteGovernance without gridlock: 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 to create control without slowing every useful change.
Read daily noteGovernance without gridlock: 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 to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Critical update review
Critical updates can change security or runtime behaviour and deserve ownership before enforcement dates arrive. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Seasonal regression testing
Regression testing should concentrate on high-impact journeys, custom automation and integration boundaries. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Sandbox preview planning
Preview sandboxes provide a controlled window to evaluate upcoming platform behaviour before production changes. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: 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 to create control without slowing every useful change.
Read daily noteGovernance without gridlock: API version discipline
API versions influence behaviour and should move through the estate as a managed engineering decision. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Flow and Apex boundaries
Declarative and programmatic automation are complementary when their responsibilities are explicit. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Salesforce code review
Code review is an architectural control as well as a defect check. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Application logging
Logs should describe business context and decision points, not produce an unstructured stream of debug statements. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Custom metadata as configuration
Custom metadata can move controlled business variation out of code and into deployable configuration. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Security enforcement in Apex
Apex can execute with privileges that require developers to enforce the intended access model deliberately. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Test data design
Good test data communicates the business scenario and remains independent of org state. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Meaningful Apex tests
Tests should protect business behaviour and failure handling, not merely raise coverage percentage. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Bulk-safe code
Salesforce transactions may process many records even when the original change appears singular. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Selective SOQL
Query design must reflect data distribution and access paths, not only functional correctness. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Lightning component boundaries
A Lightning Web Component should own a coherent interaction rather than accumulate an entire business process. This retrospective daily note considers how to create control without slowing every useful change.
Read daily noteGovernance without gridlock: Asynchronous Apex
Queueable, batch and scheduled work solve different execution and scale requirements. This retrospective daily note considers how to create control without slowing every useful change.
Read daily note