Name the result
Write the observable finished state and the business decision the project must support.
Field Guide 006 · $49
Give the builder a result they can build and you can review.
Five professional brief systems for a website, iOS app, lead magnet, email funnel, and product research.
The result
You finish with a reusable Master Build Brief and five scenario-specific operating contracts that make inputs, boundaries, acceptance, evidence, handoff, and recovery visible before work starts.
Good fit
For a woman directing Claude, Codex, a freelancer, or a future teammate who wants work to survive handoff and review without becoming a developer herself.
Inside the download
A working kit, not a long explanation.
- 01
The complete 34-page Field Guide in PDF, plus an editable DOCX edition.
- 02
A reusable Master Build Brief for defining outcome, inputs, authority, constraints, acceptance, QA, handoff, and recovery.
- 03
A small-website brief covering routes, responsive states, forms, accessibility, metadata, preview, deployment, and rollback.
- 04
An iOS-app brief covering flow, data, permissions, offline and error states, VoiceOver, tests, privacy, signing, and handoff.
- 05
Lead-magnet and email-funnel briefs covering claims, delivery, consent, suppression, rendering, test sends, and activation boundaries.
- 06
A product-research brief with source, freshness, contradiction, claim-ledger, confidence, and limitations rules.
- 07
Five filled fictional examples plus review, change-control, handoff, and recovery tools.
The method
Small decisions you can inspect.
Supply authority
List the source files, owners, permissions, decisions, and facts the builder may rely on.
Make acceptance visible
Replace words such as simple, clean, and user-friendly with observable criteria and required evidence.
Control the handoff
Define review, external-action boundaries, change control, rollback, and recovery before the work leaves draft state.
Tested before release
Built from the same files you receive.
All five brief systems were completed against the same fictional studio while using different risk models. Website, iOS, lead-magnet, email, and research work were checked with scenario-specific acceptance criteria rather than one generic prompt or QA list.
Clear boundary
This self-serve library does not create the project, supply missing business decisions, establish legal or regulatory compliance, guarantee accessibility conformance, App Store acceptance, email deliverability, conversion, saved time, reduced cost, revenue, or a successful build.
Field Guide 006