Release notes — the blog
Practical notes on Salesforce delivery.
Short, operational writing on UAT, release governance, and delivery stability. The same material as the monthly newsletter, in the open.
- Read the note →: UAT is a governance problem, not a testing problem
UAT is a governance problem, not a testing problem
Why Salesforce UAT fails before a single test runs — and how named owners, agreed acceptance criteria, and a sign-off gate fix user acceptance testing for good.
- Read the note →: What a release log is for (and who it protects)
What a release log is for (and who it protects)
A plain-language Salesforce release log is the cheapest support-ticket reduction program available. What to include, when to publish, and who it protects.
- Read the note →: The go/no-go meeting that takes ten minutes
The go/no-go meeting that takes ten minutes
How to run a Salesforce release go/no-go gate with written criteria — a release readiness review that nobody argues with and that takes ten minutes.
- Read the note →: Requirements are not tickets
Requirements are not tickets
When Salesforce requirements arrive as tickets, the backlog sets your strategy. How senior business analysis turns requests into decisions.
- Read the note →: The hidden cost of unreviewed licenses
The hidden cost of unreviewed licenses
Salesforce license waste hides in plain sight because nobody owns the review. How a structured license audit pays for itself in the first hour.
- Read the note →: Why release weekends feel risky (and how to fix it)
Why release weekends feel risky (and how to fix it)
Salesforce release risk is not a feeling — it is unscored change. How scoring blast radius and rollback difficulty turns go-live dread into a checklist.