FREE FIELD GUIDE / V1 Synapedia BUILD
The AI Platform Blueprint
Thirteen practical artifacts from an observed problem to a measured release. Each step ends with one concrete artifact so your project accumulates decisions—not just code.
Idea Filter
Reject attractive distractions before they consume a repository.
Is this a repeated problem with observable evidence, a reachable audience and a credible path to value?
Checklist
- Write the user, painful moment and current workaround in one sentence.
- Collect five evidence points from conversations, searches, support threads or behavior.
- Score urgency, frequency, access to users and willingness to change.
- Reject ideas whose main proof is that the technology looks impressive.
Problem Definition
Describe the problem precisely enough that a solution can be tested.
Can a real user recognize the situation without hearing your proposed feature?
Checklist
- Name the trigger, failed outcome and consequence.
- Separate facts, assumptions and unknowns.
- Quantify the cost in time, money, risk or missed progress where possible.
- Write explicit evidence that would disprove the problem.
Audience Definition
Choose the first group whose context is specific enough to design for.
Could you find and interview ten of these people this week?
Checklist
- Define role, context, skill level and constraints—not vague demographics.
- Name the first-use trigger and the language people use for it.
- List where this audience already learns, searches and asks for help.
- Document who the first version is deliberately not for.
Jobs To Be Done
Translate the problem into progress the user is trying to make.
Does the job describe a desired change rather than your interface?
Checklist
- Complete: When ___, help me ___, so I can ___.
- Identify functional, emotional and social dimensions only when evidenced.
- Name the switching forces: push, pull, habit and anxiety.
- Choose one job for the first product loop.
Product Boundary
Make the product promise clear by deciding what it will not become.
Can a visitor understand the promised change without reading a feature inventory?
Checklist
- Write one promise, one primary user and one activation moment.
- Separate the core product from services, community and future platform ideas.
- List irreversible, regulated or trust-sensitive actions.
- Create non-goals for every attractive adjacent feature.
MVP Cut
Ship the smallest coherent loop that produces a real user result.
Can one user enter, complete the core action and receive a useful outcome?
Checklist
- Map entry, core action, result and next step.
- Keep validation, empty, loading, failure and retry states on the core path.
- Defer dashboards, automation and roles that do not unlock the first result.
- Test with realistic content rather than generic placeholders.
Architecture Brief
Choose boundaries that make the first version safe to change.
Do you know where identity, durable data, external services and irreversible actions live?
Checklist
- Draw the path from browser to server, storage and each external provider.
- Separate public, authenticated and administrative surfaces.
- Name the source of truth, fallback behavior and retention rule for critical data.
- Record security boundaries, assumptions and the simplest rollback path.
AI Agent Brief
Give coding agents enough context and constraints to produce reviewable work.
Could another engineer explain what changed, why and how it was verified?
Checklist
- State the outcome, current architecture and files in scope.
- List invariants, prohibited actions and exact acceptance checks.
- Require inspection before editing and facts to be separated from assumptions.
- Keep the task bounded enough to review without trusting an opaque diff.
Definition of Done
Turn quality from a feeling into evidence collected before release.
Would two reviewers reach the same ship/no-ship decision?
Checklist
- Define functional, content, accessibility, privacy and security acceptance criteria.
- Require type, test, build and critical journey evidence appropriate to the stack.
- Include mobile widths, error recovery and keyboard behavior.
- Name the remaining limitations and the owner of each follow-up.
Launch Checklist
Release a bounded promise with controls that make failure recoverable.
Can you explain what changed, what was verified and how you will respond if it breaks?
Checklist
- Verify permissions, secrets, routes, forms, metadata, robots and sitemap.
- Test incognito access, production persistence and the full user-visible handoff.
- Prepare release notes, monitoring signals and a rollback decision.
- Launch to a specific audience with one primary call to action.
Distribution Map
Connect relevant attention to a useful next action before launch day.
Do you know where the first fifty relevant visitors can realistically come from?
Checklist
- Choose one primary acquisition channel and one durable secondary channel.
- Map audience questions and search intent to pages, content and next actions.
- Give each indexable page a distinct intent, canonical URL and useful internal links.
- Attach stable campaign and creative identifiers before publishing links.
Feedback Loop
Combine behavior and conversation so numbers retain their meaning.
Can each event or question change a product or growth decision?
Checklist
- Define landing, activation, lead, checkout and verified purchase events.
- Keep personal data out of analytics payloads and record consent separately.
- Ask a small set of repeatable questions after meaningful product moments.
- Review qualitative feedback beside the funnel, not in a separate archive.
Iteration Scorecard
Improve the bottleneck that matters instead of adding whatever feels productive.
What single constraint is preventing more users from reaching value?
Checklist
- Record the baseline and choose one leading indicator.
- Write a falsifiable hypothesis and decision threshold before changing the product.
- Change one meaningful variable and define the evaluation window.
- Keep, kill or revise the change, then document what was learned.
WORKBENCH Your next 60 minutes
Do not complete all thirteen steps at once.
Choose one idea. Create these three artifacts, then decide whether it deserves code.
- 20 minProblem brief
User, trigger, workaround, evidence, unknowns.
- 20 minMinimum loop
Entry, core action, useful result, non-goals.
- 20 minBoundary map
Public, private, durable, external and irreversible.
NEXT From method to workspace
You have the method. BUILD Starter System helps you run it.
Save one project, work through ten connected systems, copy the AI Brief and export the complete operating file.
Build my product