Website
The release succeeds when the intended visitor can understand the proposition and take the right next step.
See its process →Auteur product playbooks
The same method. A different build reality.
A marketing site, SaaS product, mobile app, and internal automation all pass through Frame, Direct, Deliver, Verify, and Learn. What changes is the decision being made, the shape of a useful slice, and the evidence required before release.
Choose a build path
Start with how the product creates value.
Choose by operating model, not technology alone. A PWA that runs a subscription workflow is closer to the SaaS playbook; a staff dashboard that triggers consequential actions is closer to the internal-tool playbook.
01 · Marketing websiteTrust + action
Help the right visitor understand, trust, and act.
For service sites, product marketing, portfolios, launches, and conversion journeys.
- Core object
- The visitor decision
- Useful slice
- One complete message-to-action path
- Primary proof
- Comprehension, credibility, accessibility, conversion path
02 · SaaS / web appWorkflow + state
Turn a capability into a dependable product workflow.
For authenticated web products, subscription software, AI applications, and operational platforms.
- Core object
- The stateful user workflow
- Useful slice
- One valuable journey across UI, API, service, and data
- Primary proof
- Correctness, trust, recovery, authorization, retention signal
03 · Mobile appDevice + interruption
Make the workflow dependable in the conditions people actually use it.
For responsive PWAs and Expo-based iOS and Android products that depend on device behavior.
- Core object
- The interruptible device task
- Useful slice
- One capture, review, correction, and sync journey
- Primary proof
- Permissions, offline behavior, recovery, device QA, accessibility
04 · Internal toolEfficiency + control
Automate repetition without automating accountability.
For staff software, workflow automation, agent systems, admin tools, and operational decision support.
- Core object
- The governed operational decision
- Useful slice
- One suggestion, approval, action, and audit trail
- Primary proof
- Permissions, explainability, escalation, auditability, time saved
Assurance overlayFor every high-consequence build
Prove the whole system—not merely the visible feature.
Apply this overlay when the product spans repositories, agents, integrations, migrations, regulated data, money, or operational authority.
- Trace
- Intent through every required layer
- Verify
- Components, seams, failures, and recovery
- Gate
- Implemented, integrated, deployable, and safe to activate
When the category overlaps
Follow the highest-consequence behavior.
A product can use more than one playbook. Use the primary playbook for the complete value path, then borrow the stricter checks from any secondary reality.
SaaS
The release succeeds when a user can complete and recover one valuable authenticated workflow.
See its process →Mobile
The release succeeds when a task survives real permissions, networks, interruptions, and device states.
See its process →Internal tool
The release succeeds when assistance improves work while approval, escalation, and accountability remain clear.
See its process →Before the build process
Open the direction brief →Write the direction that all five stages will protect.
The printable brief captures the outcome, evidence, boundaries, risks, acceptance checks, and decision owner before implementation begins.