ProductSnap Studio
Chapter 02 · where the ideas start

Everything here started as a pencil sketch.

I think on paper first. Messy boxes, margin notes, arrows that argue with each other. Before there were screens, there were rough sketches trying to answer the same question: does this actually make sense?

Here is where most of those questions started — paper first, product second.

the app · one card at a time

From paper to the flashcard

The same wireframes that explain the app on its own page sit here in a different frame — not as instructions, but as the loops the thinking went through before any of it had a screen.

ProductSnap · the flashcard, both sides v0.5 wireframe · one card flips · what it is, why it matters, a real example — nothing else front · the question 12:25 wifi · 64% ☰ Today's card 1 of 1 · flip to reveal FRAMEWORKS & MODELS Is a PM the CEO of the product? A line you'll hear in every PM interview. Is it actually true? Tap to flip ‹ prev next › flip back · the answer 12:25 wifi · 64% ☰ The short answer flip back any time WHAT Not really. A PM has the vision but not the authority — you lead by influence, not command. WHY IT MATTERS Acting like a CEO of the product is how new PMs lose engineering's trust. The job is alignment, not orders. A REAL EXAMPLE A PM wants to cut a feature to hit a date. A CEO could just decide. A PM has to bring eng, design, and sales to the same conclusion — with evidence. The trade-off only sticks if the team owns it too. influence > authority ★ save › next card three blocks, no fourth what / why / example. there is no "watch out for" box — the real app doesn't have one, so this can't either. the card fits. everything sits on one face. you flip — you never scroll inside it. ProductSnap · early wireframe iteration · sketch fidelity sketch · card 01
the flashcard, both sides — one question, then what / why / a real example. nothing else on the card.
ProductSnap · Product Gym (one rep) v0.4 wireframe · one question, four options, then why — not a wall of categories 12:25 wifi · 64% ‹ 🏋 Product Gym Frameworks & Models · rep 2 of 5 no timer · no leaderboard THE QUESTION Jobs to Be Done says customers "hire" a product to get a job done. What does that change about how you size up the competition? A Only other JTBD apps count as rivals. ✓ Anything the customer could "hire" instead — even a spreadsheet. C Competition only matters at the pricing stage. D JTBD says to ignore competitors entirely. 💡 STUDY CONCEPT – JTBD widens the field. If a customer "hires" your product for a job, your real rivals are whatever else could do that job — a rival app, a workaround, or doing nothing at all. tap the – to collapse · swipe for the next rep one question, not a list of categories the old sketch showed five category boxes. a rep is one question you actually answer. answer first, then the why. the concept only opens after you commit — so you're learning, not guessing. collapsible expand to study, collapse to keep moving. no internal scroll inside the card. ProductSnap · early wireframe iteration · sketch fidelity sketch · gym 01
a gym rep, drawn honestly — one question, four options, then the why. answer first, study after.

↳ below: the six original screen sketches, in the order the thinking happened.

Hand-drawn wireframe of the flashcard home screen with margin notes about one card at a time
where the flashcard idea first showed up — one card, nothing else on the page.
Hand-drawn wireframe of the flashcard answer side, with What, Why It Matters, and a real-world example blocked out
the back of the card — what / why / example, before it had names.
Hand-drawn wireframe of the bookmarks screen
bookmarks — the argument was whether saving things even belonged in v1.
Hand-drawn wireframe of the product gym quiz screen
the gym — reps, not lessons. This one took three sketches to get honest.
Hand-drawn wireframe of the product stories screen
stories — a card felt wrong, so this one wanted to read like a memo.
Hand-drawn wireframe of the future PM trends screen
future PM — the section I kept redrawing because I wasn't sure it earned a spot.

↳ the same screens, explained module-by-module, live on the app page. Here they're just the thinking, in order.

pulse · from terminal to one question

How Pulse stopped being a dashboard

Pulse very nearly became a Bloomberg-style terminal — every signal, every chart, all at once. This is the sketch where that idea got crossed out and replaced with one question per signal.

Pulse started as a dashboard. Then I deleted the dashboard. v0.1 sketch · the detour that almost shipped the rejected idea MARKETS TERMINAL live · 14:32:07 CPI 3.4 ▲ SENT 61 ▼ API -38% ▼ RATE 5.5 AI cost hiring 3.4% headline inflation -12 pts SYMLASTCHGVOL CPI3.40+0.31.2M SENT61.2-4.1880K API0.62-38%4.0M RATE5.500.00— JOBS216K+9K2.1M PCE2.80+0.1760K too much. nobody needs another terminal. so I cut it the idea that stuck the connection, in one line Signal what the world just did Meaning why it matters to us Product question what should we do about it? one signal. one question. that's the whole idea. Pulse · early sketch · from terminal to one question sketch · pulse 01
the detour, in pencil: a dense dashboard, crossed out — then signal → meaning → one product question. The version that shipped.
Pulse · from signal to product question v0.3 wireframe · the real section layout — boxes, pills, the explorer card, the chain THE CHAIN · ONE SIGNAL AT A TIME From signal to product question one section lead line — what this part of the page is for Category [ all signals ] [ category ] [ category ] [ category ] Signal [ signal ] [ signal ] [ signal ] [ signal ] ··· [ CATEGORY ] [ signal name ] [ one-line plain-English summary of the signal — what it is, in a sentence ] [ status ] [ confidence ] [ value ] [ unit ] 12-month trend 01 SIGNAL [ what moved, named — not the raw number ] ＋ 02 MEANING [ the same move, in plain words ] ＋ 03 PRODUCT IMPACT [ where this touches a product team ] ＋ 04 EXAMPLE [ a concrete, Monday-morning situation ] ＋ 05 PM QUESTION [ the one question this signal asks you to sit with ] — pre-opened · the others say “＋ tap to expand” ▸ Why I think this evidence · counter-signal · product takeaway source · tier · last updated — [ structural footnote ] pick a signal read on the left, numbers right summary one side, data the other. it ends on a question. the last step is already open — a question, not a verdict. ProductSnap · early wireframe iteration · sketch fidelity sketch · pulse 03
the real section, in pencil: pick a signal, read it on the left, the data on the right, and the five-step chain that ends on a product question.

↳ the question that survived: not "what's the number?" but "what should a product team do about it?"