Go-to-Market · core
Positioning
Naming the problem, the audience, and the alternative you beat.
Mental model
Positioning answers two questions: "for whom" and "compared to what alternative." If your statement could just as well describe three of your competitors, you have a description — not positioning.
How to study Positioning
Begin by restating the mental model in your own words, then connect it to a concrete system you have built or operated. Name the mechanism, the constraint it addresses, and the trade-off it introduces. Use April Dunford — Everything You Know About Positioning Is Wrong to check details, but close the source before writing your explanation. Retrieval is the learning step; rereading is only preparation.
Next, compare Positioning with Landing Pages. Ask what changes in correctness, latency, resource use, operability, and failure recovery. Complete Draft a product positioning statement and preserve the command, input, output, and one failed attempt as evidence. Finish by explaining the idea without jargon to someone who has not studied the track.
Proof of understanding
- Explain the mechanism from first principles and identify the state it reads or changes.
- Give one situation where the concept is the right choice and one where it is not.
- Predict a realistic failure mode before running the drill, then compare the prediction with evidence.
- Connect the result to a roadmap or build artifact instead of treating the concept as isolated trivia.
Learn from primary sources
Practice and explain it back
Draft a product positioning statement
Write a 2-sentence positioning statement for a product you use, using the form: "For [target] who [need], [product] is the [category] that [unique benefit]. Unlike [competitor], it [differentiator]." Then write a worse version and explain why yours is sharper.
Expected evidence: Two positioning statements (good + worse) + a one-line critique of the worse one.
Open the interactive drill →Review prompts
- Your positioning statement is completely true. Why might it still be worthless?
Build evidence
Synthesize: Application Engineering
Turn backend, client, UX, real-time, interactive, analytics, and distribution skills into one complete product. Produce one working system, benchmark, or evidence-backed design that integrates the path.
- Implements or precisely models the core mechanisms from all three milestones
- Includes at least one injected failure or adversarial case and demonstrates recovery
- Reports quality, latency, resource, reliability, or usability measurements relevant to the domain
- Ships a concise architecture note explaining decisions, trade-offs, and remaining risks
Prerequisites
None assigned yet.