David McLeod
26.3K posts

David McLeod
@Mucx
Built & led the Design Team at Twitch (7+ years) and similarly at Discord. Taking a break now to get married & Travel!. Also: https://t.co/jqvhWxpFu7
San Francisco Katılım Mart 2008
392 Takip Edilen1.3K Takipçiler
David McLeod retweetledi
David McLeod retweetledi

This looks like a fun old-school like side scrolling beat em up. I’m down… store.steampowered.com/app/3749580/He…
English
David McLeod retweetledi
David McLeod retweetledi

Most PMs write documentation backwards.
They start with 10-page PRDs that nobody reads. Then wonder why engineers ignore them.
Elite PMs do it differently. They use three document types, each with a specific purpose.
Start with 1-pagers. They're decision documents, not specifications.
Your goal: Get stakeholders to say yes or no.
Cover these essentials:
- Problem statement (who feels pain, how often)
- One metric that defines success
- Three possible approaches (not detailed specs)
- Cost estimate (time, people, dependencies)
- Open questions that need answers
That's it. No user stories. No wireframes. No implementation details.
Why this works: You haven't validated anything yet. Building a full spec now wastes hours on ideas that might get killed in five minutes.
You'll write 10 one-pagers. Maybe three get approved to continue.
Those three become 3-pagers. Now you're validating and aligning.
Add to your 1-pager:
- User research findings (actual quotes, not summaries)
- Success metrics with baseline numbers
- High-level solution approach (what changes, what stays)
- Key risks and mitigation plans
- Dependencies mapped out
Engineers should read this in 10 minutes and understand what you're trying to accomplish.
It's still scannable. Still focused on outcomes. But now it has enough meat for engineers to poke holes in your logic.
Most 3-pagers never become 5-pagers. That's good. You learned something was harder than expected. Or stakeholders couldn't agree on metrics. Or engineering found a simpler path.
Only the validated ideas become 5-pagers for execution.
Now you add the details:
- User stories with acceptance criteria
- Wireframes or prototypes
- System design overview
- Instrumentation plan (what metrics, where to track)
- Launch checklist (rollout plan, communication, monitoring)
This is the document engineers build from.
But notice what happened: You only wrote detailed specs for ideas that survived two rounds of validation. Everything else got killed early when it was cheap to kill.
The hard part isn't writing these documents. It's stopping yourself from jumping straight to the 5-pager.
Your brain wants certainty. It wants to "figure everything out" before talking to stakeholders.
Resist that urge. Write the 1-pager. Get feedback. Let it die or grow based on reality, not your assumptions.
Most weeks, you're writing 1-pagers. Some weeks, you're refining 3-pagers. Rarely, you're finishing 5-pagers.
That ratio is correct. That's how product work actually flows.
Documentation should match your confidence level, not your anxiety level.
English

About time. Wonder what they will do with the weirdness left-over from iTunes on iOS and MacOS?
MacRumors.com@MacRumors
Apple Removes iTunes Movies and TV Shows Apps in tvOS 26.4 macrumors.com/2026/02/17/tvo…
English
David McLeod retweetledi
David McLeod retweetledi
David McLeod retweetledi
David McLeod retweetledi
David McLeod retweetledi


Seeing people buy into this, and then get stuck in their own echo chamber frothing each other into a frenzy has been a real eye-opener. 2026 has started with the “stupid” button turned on across a lot of areas huh?
DiscussingFilm@DiscussingFilm
A secret 9th episode of ‘STRANGER THINGS’ Season 5 is not happening (Source: @Variety)
English

@chriswallace Nice! Thanks. There’s tons of tools out there from my limited poking around so far. This one looks decent.
English
David McLeod retweetledi

Nearly spat out my coffee… then I re-read this…
DiscussingFilm@DiscussingFilm
Samuel L Jackson now has 4 skins in Fortnite
English











