Writing Specs & Designs

Scope

Covers

• Producing a Spec & Design Doc Pack that helps product, design, and engineering quickly reach shared clarity
• Converting “insights” into concrete artifacts: a low‑fidelity diagram, flows/states, prototype plan, and testable acceptance criteria
• Mobile-specific tap economy (when relevant): explicitly optimizing taps and interaction cost

When to use

• “Write a spec / feature spec / technical spec for this feature.”
• “Turn these notes into a design doc that engineering can build from.”
• “Create a shaping-style doc with a diagram of the moving pieces.”
• “We need a prototype plan to evaluate the feel of this interaction.”

When NOT to use

• You’re still validating what problem to solve (do discovery / problem definition first).
• You need a high-level strategy/vision document (do product vision / north star work first).
• You need a deep engineering architecture design (APIs, schemas, scaling, reliability) rather than product interaction clarity.