For product managers who hold it all together
You're the connective tissue between the team, the roadmap, and everyone who wants an update. Here's the kit for turning fuzzy specs into aligned ones, making calls that stick, and keeping every stakeholder on the same page.
By RECT · 4 templates
Being a PM is mostly holding a dozen threads together at once — the spec engineering is arguing about, the decision design is waiting on, the exec who wants a one-liner by Friday, the roadmap that shifted twice this week. You don't own the code or the designs; what you own is alignment, and alignment leaks constantly. A decision made in standup gets remembered four different ways. A deck goes out with a number that contradicts last week's. The loudest voice in the thread wins by default. This kit is built around the PM's actual job — get everyone reading from the same doc, make the call in a way that survives contact with next month, and communicate it so cleanly that nobody has to ask "wait, what did we decide?"
Turn a fuzzy spec into an aligned one
Every product starts as a doc that half the team reads differently. A Draft Annotator is where you close that gap: people and agents drop anchored comments right on the line they're reacting to, replies thread underneath, and every open question gets resolved instead of scrolling off into oblivion. It's Google Docs comments with a spine — closer to the discipline of an Amazon six-pager review than a free-for-all, so by the time the PRD is "done," engineering, design, and you are actually picturing the same thing.
Get the stakeholder deck right — internal or external
Sooner or later it all becomes a presentation: the sprint demo, the exec review, the QBR, the customer-facing pitch. And nothing undercuts a good plan like a typo on the "strategy" slide or a metric that doesn't match the one three slides back. Run it through a PowerPoint Proofreader first — it checks spelling, grammar, and terminology slide by slide, catches the numbers that don't line up, and tightens the wording so the story lands the same whether you're presenting to your team or to a room of execs. It's the polish pass a good chief-of-staff would do, on demand.
Make the call — and make it stick
Half of a PM's job is deciding the open questions everyone's blocked on: which segment to build for, which feature to cut, whether to ship the smaller thing now. A Decision Room turns that from a Slack blur into a real record — lay out the options, pull in input from eng and design, keep the dissent instead of pretending everyone agreed, and publish the call with an owner and a date. It's the RFC or decision log the best teams keep, minus the ceremony — so when the tradeoff resurfaces in two months, the reasoning is right there instead of relitigated from scratch.
Distill the chaos into your own day
Half the schedules you deal with aren't yours to begin with — the three-track conference agenda, the exec's packed week you're trying to slot a review into, the shared team plan with forty entries where only six involve you. You don't need the whole thing, you need your slice of it. My Schedule takes a shared calendar, a conference agenda, or the schedules of the people you report to and distills it into one clean day-by-day view of what, when, and where — just the sessions worth showing up to, just the windows your stakeholders are actually free. It's the difference between screenshotting a Sched agenda or someone's Google Calendar and actually having a plan for it.