Case type: Critique a product

1CRITIQUE SPINE23  1. PICK WELL     product you use; clear primary job; enough depth4  2. USER + JOB    who it is for; what progress it offers5  3. LIKE          1–2 specific strengths (mechanism, not adjectives)6  4. TRADE-OFFS    what the product deliberately chose to lose7  5. DISLIKE       underserved segment or broken job step — structural8  6. FIX           one sharp change; why not five; success metric9  7. REFUSE        what you would not change (protects the wedge)10  8. BUSINESS      how the fix helps retention/revenue/cost — not vibes only1112  Anti-pattern: 'clean UI, great UX, I'd add AI' with no metric or user.

1CHARITY → CRITIQUE → FIX (one breath)23  Charity:  'They optimized for X under constraint Y…'4  Critique: 'That leaves segment Z failing job step W…'5  Fix:      'I'd ship N that completes W without destroying X…'67  If you skip charity, you sound like a drive-by reviewer.8  If you skip the refuse list, you sound like you would redesign everything.

1LIKES (specific mechanisms)23  1) Performance as product: keyboard-first, optimistic UI, snappy navigation.4     Mechanism: speed reduces "process tax," so teams actually update issues.5     Business link: higher issue hygiene → better planning reliability.67  2) Opinionated workflow defaults (cycles, project structure) without8     enterprise customization sprawl.9     Trade-off (charity): they chose coherence over "any workflow imaginable."10     That loses some enterprise process buyers — deliberately.1112  3) Design polish that signals respect for craft — attracts the ICP13     (teams that care about software quality).

1DISLIKE + WHO IS UNDERSERVED23  Structural gap: cross-functional roadmap communication to non-Linear4  stakeholders (execs, GTM) is weaker than the core issue experience.5  PMs often export-to-slides or maintain a second source of truth.67  Underserved: PM/exec consumers of status who will not live in keyboard8  issue workflows — they need narrative progress, risks, and decisions,9  not just issue states.1011  Why it exists (charity): team optimized for the builder ICP first; narrative12  layers risk becoming "enterprise bloat" if done wrong.1314  NOT the critique: 'the logo could be nicer' or 'add AI everywhere.'

1FIX → METRICS → REFUSE23  Success (user): % of projects with a brief opened by a non-member viewer4                  at least once per cycle5  Success (biz):  expansion revenue from viewer/stakeholder seats OR reduced6                  churn reason "execs can't see status" in exit surveys7  Guardrail:     issue update rate by eng must not fall (briefs must not8                  become the place work is tracked)910  REFUSE TO CHANGE:11  · Core keyboard-speed issue UX — that is the wedge12  · Infinite workflow customization (would recreate Jira gravity)1314  Sequencing: manual brief template + share link first; AI draft second15  once structure is used weekly (eval later if AI — see L6 patterns).

1WEAK2  'I love Instagram. Clean UI, addictive, great for sharing. I'd add better3   filters, less ads, and an AI caption writer. Success = more time spent.'4  (Generic, no trade-off charity, metric may harm user trust.)56STRONG7  Named ICP + job · specific mechanism likes · deliberate trade-offs ·8  structural dislike with underserved user · one fix · user+biz metric ·9  guardrail · sacred cows protected.

18-MINUTE SPOKEN OUTLINE2  0:00–0:40  product, ICP, JTBD3  0:40–2:30  two likes with mechanisms4  2:30–4:00  trade-offs + structural dislike + underserved5  4:00–6:30  one fix + metrics + refuse list6  6:30–8:00  business implication + risk if you ship the fix badly

1SPOKEN SENIOR ANSWER — Favorite product: Linear (~12 min)23  [0:00–1:20 PICK + JOB]4  "Favorite product: Linear. I use it weekly on eng-led product teams. Primary5  user: teams of about ten to one hundred fifty who want issue tracking that6  stays fast as volume grows. Job: when work is chaotic across eng, design, and7  PM, I want a high-signal system of record for what is in progress so we ship8  without Jira-weight ceremony. I pick Linear over Notion-as-tracker or Jira9  because the wedge is speed and opinionation, not infinite configuration."1011  [1:20–4:00 LIKES WITH MECHANISMS]12  "Like one: performance as product — keyboard-first, optimistic UI, snappy13  navigation. Mechanism: when updating an issue is cheaper than avoiding the14  tool, issue hygiene rises, and planning reliability follows. Business link:15  teams that trust the board cancel fewer commits. Like two: opinionated16  workflow defaults — cycles, projects — without enterprise customization17  sprawl. Charity: they chose coherence over any-workflow-imaginable, knowing18  they would lose some process-heavy buyers. Like three: craft signal attracts19  the ICP that cares about software quality — distribution through taste."2021  [4:00–7:00 TRADE-OFFS + DISLIKE]22  "Deliberate trade-offs: speed and opinionation over admin configuration;23  product-led growth over heavy services; builder aesthetic over PM-gantt24  everything. Structural gap: cross-functional roadmap communication to non-25  Linear stakeholders — execs and GTM — is weaker than the core issue26  experience. PMs export to slides or maintain a second source of truth.27  Underserved: PM and exec consumers of status who will not live in keyboard28  issue workflows; they need narrative progress, risks, and decisions. Charity:29  the team optimized for builder ICP first; narrative layers risk enterprise30  bloat if done wrong. Not my critique: nicer logo or add AI everywhere."3132  [7:00–10:30 ONE FIX + METRICS + REFUSE]33  "One sharp fix: Stakeholder Briefs — a first-class, read-mostly surface auto-34  drafted from projects and cycles with scope, risks, decisions, ship dates, a35  PM-editable narrative layer, and a share link that does not require full36  workspace seats for exec viewers. Not a second Jira. Not AI novels from37  issues as the pitch — AI may draft; human owns narrative. Success user: share38  of projects with a brief opened by a non-member viewer at least once per39  cycle. Success biz: expansion from viewer seats or reduced churn reason execs40  can't see status. Guardrail: eng issue-update rate must not fall — briefs41  must not become where work is tracked. Refuse to change: keyboard-speed issue42  UX, and infinite workflow customization. Sequence: manual template and share43  link first; AI draft second once weekly use is proven."4445  [10:30–12:00 CLOSE]46  "Linear wins because it protects a wedge. My fix serves an underserved job47  without destroying that wedge. If the fix made eng live in slides again, I48  would kill it. That refuse list is half the critique."

1PRESSURE Q → SENIOR REPLY23  Q: "Everyone says Linear — pick something else."4  A: Backup ready: [your product]. Same spine — ICP, mechanisms, trade-offs,5     one fix, refuse list. Depth beats trend.67  Q: "Isn't your fix just Roadmap features competitors already have?"8  A: Maybe on a feature matrix. Differentiation is read-mostly share without9     forcing execs into issue chrome, while guarding eng update rates.1011  Q: "What would you not change even if users complain?"12  A: Keyboard-speed core and opinionated defaults — complaints from process-13     heavy buyers are the price of the wedge.1415  Q: "Add AI that writes the brief automatically."16  A: After structure is used weekly. Uncalibrated AI narrative becomes fiction17     that execs stop trusting — worse than no brief.1819  Q: "How is this different from a favorite-app gush?"20  A: Mechanisms, charity, underserved segment, one fix, business tether,21     refuse list — not adjectives.2223  Q: "Critique a product you dislike."24  A: Same spine. Name the job it claims, the trade-off that hurts users, one25     fix that does not require burning the company down.

1BACKUP CRITIQUE SKETCH — WhatsApp (4 min version)23  Job: reliable private messaging with low friction across networks.4  Like: default encryption + universal reach; status/calls as adjacent jobs5  without forcing a feed identity.6  Trade-off charity: simplicity over power-user organization (muted chaos).7  Structural dislike: work/personal context collapse for users who cannot8  carry two devices — group noise and boundary failure.9  Fix: first-class 'Spaces' or work profiles with separate notification10  defaults — not a full Slack clone.11  Metric: reduction in mute-all rate for multi-group power users; guardrail12  must not raise message send friction for pure social users.13  Refuse: turning WhatsApp into a public content network as the core bet.

1CRITIQUE SELF-SCORE (after every practice run)23  [ ] Named ICP and JTBD in first 40 seconds4  [ ] Two likes with mechanisms (not adjectives)5  [ ] Charity: why the pain exists under a smart trade-off6  [ ] One structural dislike + underserved segment7  [ ] One fix with user metric + business metric + wedge guardrail8  [ ] Refuse list protecting the product's reason to exist9  [ ] Could survive 'pick something else' with a backup product1011  Fail any two boxes → rewrite only those sections, do not polish the rest.