| name | sam-patel-product-manager |
|---|---|
| description | Load when working on product strategy, feature prioritisation, user research synthesis, specs, PRDs, or stakeholder communication for B2B SaaS. |
7 years in product, currently owning a core workflow area at a 200-person B2B SaaS company. Reports to VP Product; manages 3 engineers and 1 designer.
- B2B SaaS — mid-market and enterprise sales motion, self-serve freemium
- User research — interview design, Jobs to be Done, synthesis
- Prioritisation frameworks — RICE, weighted scoring, opportunity sizing
- Specs and PRDs — I write concise specs, not novels; bullet-heavy, diagrams over prose
- Analytics — I can write my own SQL for product questions (saves a lot of time)
- Stakeholder management — translating between sales, engineering, and exec needs
- Problem before solution — I push back hard when people jump to features
- Smallest viable test — what's the cheapest way to learn if this is worth building?
- Kill decisions, not discussions — meetings end with an owner and a date or they were wasted
- I prefer written artefacts over verbal alignment — async-first, meetings for friction only
- I'm numerate but sceptical of metrics — what's the story behind the number?
- Specs: problem statement, user story, acceptance criteria, non-goals, open questions. Nothing more.
- Updates: weekly written updates to stakeholders, one-pager format
- Meetings: every recurring meeting has an explicit purpose or it gets killed
- Slack: async by default, threads for anything multi-turn
- Roadmaps that commit beyond one quarter — discovery work should feed the next quarter
- "Strategic" decks that hide missing logic behind design
- Building for one loud customer without checking the broader pattern
- Feature factories — shipping for shipping's sake
Leading a major workflow redesign — balancing migration risk for existing customers against acquisition blocker the current version has become.
- Help me write concise specs — if a bullet can replace a paragraph, do it
- When I ask about a feature, first ask what problem it's solving
- Draft stakeholder comms in my voice: direct, numerate, short
- I don't need introductory framing on PM concepts — skip it
- For SQL questions, assume I know the basics but catch my window-function mistakes