Run product management end to end, with evidence your team can see
A complete operating system for product managers in small and growing software teams: strategy on a page, weekly discovery, open prioritisation, a now-next-later roadmap, launches, metrics, experiments and AI features done responsibly.
- A 26-sheet Product Manager's Operating System Workbook: an 18-practice maturity self-assessment with gap-to-action plan, strategy on a page, interview log, opportunity tree, assumption tests, RICE and cost of delay side by side, roadmap, delivery, launches, metrics, cohorts, experiments, stakeholders, decision log, AI features register and a six-chart dashboard
- A 8-sheet Product Business Case and Experiment Calculator: low, mid and high business case, a feature case that derives cost of delay, A/B test sample sizes and a capacity check
- Five fillable forms and eight Word documents, including a PRD template, a strategy and roadmap template, an operating policy, a sign-off memo, 36 stakeholder messages and 28 AI prompts
- A 57-event 90-day calendar, a 38-task board, a 45-minute team briefing and a 14-question LMS-ready knowledge check
The Product Manager's Operating System · Bodhih Pro Kits · 335 by Bodhih Training, trainers to 2,000+ companies since 2008.
What should a product manager do in the first 90 days?
In the first 30 days, listen: meet every lead, score your practices, start weekly customer interviews and agree one outcome. In days 31 to 60, focus: build an opportunity tree and prioritise in the open. By day 90, deliver a signed-off roadmap, a first experiment and a re-score. The Product Manager's Operating System from Bodhih Training has the tools.
Want the full free guide first? Read How to Prioritise Product Features with RICE and Cost of Delay.
You already feel the problem. Here is what it is costing you.
Everyone has a list
Sales, the CEO and support each send a list of features, and each list is the most important. Without an agreed outcome, there is no way to compare them except by who argues last.
Discovery in bursts
Customers are interviewed once a year, or when a big launch looms. Decisions happen every week, so most of them are made on opinion.
A roadmap of broken dates
A Gantt chart of features runs two years out. Half the dates have passed, sales still sends it to prospects, and customers ask about features that were never started.
Launches customers discover by accident
A good feature ships on Tuesday morning and support finds out from the tickets. The help article describes the old flow and nobody knows whether the change moved anything.
Picture the next few weeks with the kit open beside you.
Picture next Monday at 8:45. The north star post goes out: hires ready on day one this week, the completion rate and the biggest mover. Two customer interviews are in the calendar, with consent sheets already sent. The dashboard shows two red lights, and you know what you will do about each before your coffee is finished.
On Thursday, a request arrives from sales with a deal attached. You score it on RICE and cost of delay, see that the two ranks disagree, and scope the smallest version that meets the deadline. As you send the answer, with the reason and a date, you notice that nobody is arguing. The scores are on the sheet where everyone can see them.
At the end of the quarter, the roadmap goes to your CEO on one page: now, next and later, each item with its bet, its metric and a confidence level. The sign-off memo puts the recommendation first. The board hears what customers taught you, what shipped and what it moved, including the number that is still red.
Open the Start-here map tonight and give yourself one hour. Whether you start with the maturity self-assessment or the strategy on a page, you will finish the hour with a first score, a draft outcome and your first two interviews booked.
23 files that do the work for you
The e-book shows you how. The tools make it happen. Here is exactly what you download.
The Product Manager's Operating System (e-book, PDF)
The guide: methods, worked examples, scripts and exercises
Start here: the product manager's operating system map
The whole job in thirteen steps with the file to open at each, your first hour, your first week, the 30/60/90-day plan and the weekly rhythm.
Product Manager's Operating System Workbook
26 sheets: Settings, an 18-practice maturity self-assessment with gap-to-action plan, strategy on a page, interview log, opportunity tree, assumption tests, RICE and cost of delay, now-next-later roadmap, delivery, launches, metrics, cohorts, experiments with sample sizes, stakeholders, decision log, AI features register, RACI, 90-day plan, crosswalk, official sources, What changed, glossary and a six-chart dashboard with traffic lights.
Product Business Case and Experiment Calculator
Eight-sheet calculator: inputs, a low, mid and high business case for the product operating system (cost of doing nothing vs doing it), a case summary, a one-feature business case that derives cost of delay, an A/B test sample-size calculator, a capacity check and a dashboard with three charts.
Customer interview guide and snapshot
Three pages: plan and consent (recruiting brief, consent steps and the exact words), a story-based interview guide with 17 prompts, and a one-page interview snapshot that feeds the Interview log and the opportunity tree.
Assumption test and experiment card
Three pages: an assumption test card (belief, risk type, cheapest test, success criterion written first), an A/B experiment brief with sample size, duration and stopping rule, and a readout with the decision.
Feature request and trade-off intake
Two pages: a request intake that captures the problem behind the ask (who, evidence, deadline, money at stake) and a trade-off record with RICE, cost of delay, what moves out and the answer sent back within five working days.
Launch readiness and go/no-go checklist
Three pages: pick the launch tier and work through the 22-item readiness checklist (14 for Tier 2, 8 for Tier 3), run the go/no-go with a rollback plan, and review the launch at two and six weeks.
AI feature risk review
Three pages for any feature that uses AI: what it does and for whom, 16 scored risk questions (harm, fairness, privacy, transparency, security, reliance), an evaluation plan with a pass mark and a human fallback, and a sign-off.
Product strategy on a page and now-next-later roadmap template
A ten-box product strategy on a page with a filled SAMPLE, a now-next-later roadmap template with the rules that keep it honest, and a 60-minute quarterly product review agenda with a one-page board summary.
PRD template: one-pager and full version
A one-page product requirements document for most work and a full version for Tier 1 and high-risk changes (requirements, acceptance criteria, accessibility, privacy, AI, analytics, rollout), with a filled SAMPLE.
Product operating policy and procedures
A ten-section policy starter to adopt: decision rights, request intake, prioritisation and roadmap rules, customer research consent, experiments, release and launch, accessibility, AI features, metrics and review.
Product decision and sign-off memo
A two-page leadership decision memo (recommendation first, evidence, options, capacity, risks, reversibility, checks, how we will know, signature) with a filled SAMPLE for a quarterly roadmap sign-off.
Product stakeholder message library
36 ready-to-edit emails, chat messages, release notes and on-screen wording for research consent, saying no, roadmap updates, delivery, launches, experiments, AI features and a new PM's first 90 days.
Worked example pack: Mesquite Labs
The kit's main files filled in for one fictional company: maturity baseline and day 90, strategy on a page, an interview snapshot, the opportunity tree, an assumption test, RICE and CD3 side by side, an experiment readout, a go/no-go record, an AI risk review, a monthly product update and the day-90 review.
AI prompt pack for product managers
28 tool-agnostic prompts across nine steps (strategy, discovery, prioritisation, PRD and delivery, roadmap and stakeholders, launch, metrics and experiments, AI features, first 90 days), each with what to paste in and what to check, plus five human-review rules.
Team briefing session plan and answer key
A 45-minute session plan with timings, facilitator notes, a prioritisation exercise with request cards and the printable answer key for the 14-question knowledge check.
Numbers that matter: the product metrics card
Twelve numbers with plain-words definitions, exact formulas, where each lives in the workbook and what to do when it moves, with the origins of each method credited.
Product decision cards and mistakes to avoid
Eleven if-you-see-this decision cards, a pre-ship check and twelve mistakes to avoid.
Product rules by country (November 2026)
The dated sheet: research, analytics, interface design, accessibility, AI and hiring rules in the US, Canada, the UK, the EU, Australia and New Zealand, verified on official sites.
90-day new PM and product rhythm calendar
57 events over 13 weeks: day-1 baseline, north star and strategy, weekly interviews and north star posts, six two-week cycles, opportunity tree, prioritisation, monthly update and metrics reviews, roadmap sign-off, re-score, team briefing, day-90 review, quarterly product review and source checks.
Product OS task board (CSV import)
38 tasks for the first 90 days and the running rhythm, with phase, owner, week, the kit file to use and a 'done when' test. Imports into Trello, Asana, Notion, Planner or Jira.
Knowledge check (LMS-ready CSV)
14 scenario questions for the team briefing, in a seven-column CSV that imports into Bodhih LMS or any LMS (question, four options, correct letter, explanation).
Chapter by chapter
Each chapter opens with a real situation, gives you a method and ends with something to do today, using the tools in your kit.
- Format
- PDF e-book + XLSX + fillable PDF + DOCX + PDF cheat sheets + ICS + CSV
- Files
- 23 files plus a one-click ZIP
- E-book
- 72 pages
- Works with
- Excel, Google Sheets, Apple Numbers, LibreOffice, Word, Google Docs, Acrobat Reader, Google Calendar, Outlook, Apple Calendar, Trello, Asana, Notion, Planner, Jira, any LMS that imports CSV
- Best for
- Product managers and founders in software and digital product teams of roughly 10 to 150 people
What a Product Manager Is For: Outcomes, the Maturity Score and the First 90 Days
What the job is for, an 18-practice maturity score with a gap-to-action plan, an honest business case and the shape of a new PM's first 90 days.
Product Strategy on a Page
Ten boxes on one page: outcome, north star, non-goals and three bets, written with your CEO and reviewed every quarter.
Customer Interviews Every Week
A weekly interview habit with proper consent, story-based questions and a same-day snapshot that feeds the log.
Opportunity Trees and Assumption Tests
An opportunity solution tree built from what customers said, and risk-scored assumption tests run before engineering starts.
Prioritisation: RICE, Cost of Delay and Saying No
RICE and cost of delay side by side, a feature business case, capacity checks and how to say no with evidence.
The PRD and Delivery with Engineering and Design
A one-page PRD that starts with the problem, the product trio, two-week cycles and five working agreements.
Roadmaps and Stakeholders: Now, Next, Later
Now, next and later instead of dates, a stakeholder map with cadences, the monthly update and the quarterly review.
Launch: Tiers, Readiness and the Go/No-Go
Launch tiers with 22, 14 or 8 checklist items, a go/no-go, reviews at two and six weeks, and how rules differ by market.
Metrics and Experiments: North Star, Activation, Retention and A/B Tests
A north star that counts customer value, activation and retention by cohort, and A/B tests sized before they start.
AI Features Done Responsibly, and the Product Rhythm
Four gates for AI features, AI as the PM's assistant, the weekly to quarterly rhythm and the Monday dashboard.
Not just reading. Tools you will actually open again.
Start here
- 00-Start-Here-Product-OS-Map.pdf: the whole job in thirteen steps with the file for each, your first hour, your first week, the 30/60/90-day plan, the weekly rhythm and the 'Brand it in five minutes' box
Workbooks
- Product-Manager-Operating-System-Workbook.xlsx: 26 sheets including Settings, Self-assessment (0-4), Top gaps, Action plan, Strategy on a page, Interview log, Opportunities, Assumptions, Prioritisation, Roadmap, Delivery, Launches, Metrics, Cohorts, Experiments, Stakeholders, Decision log, AI features, RACI, 90-day plan, Crosswalk, Official sources, What changed, Glossary and a dashboard with six charts and traffic lights
- Product-Business-Case-and-Experiment-Calculator.xlsx: 8 sheets with inputs, a low, mid and high business case, a case summary, a feature case that derives cost of delay, an A/B sample-size calculator, a capacity check and a three-chart dashboard
Fillable forms
- Customer-Interview-Guide-and-Snapshot.pdf
- Assumption-Test-and-Experiment-Card.pdf
- Feature-Request-and-Trade-Off-Intake.pdf
- Launch-Readiness-and-Go-No-Go-Checklist.pdf
- AI-Feature-Risk-Review.pdf
Word templates
- Product-Strategy-and-Roadmap-Template.docx (strategy on a page, now-next-later roadmap, quarterly product review)
- PRD-Template-One-Pager-and-Full.docx
- Product-Operating-Policy-and-Procedures.docx
- Product-Decision-and-Sign-Off-Memo.docx
- Product-Stakeholder-Message-Library.docx (36 messages)
- Worked-Example-Pack-Mesquite-Labs.docx
- AI-Prompt-Pack-for-Product-Managers.docx (28 prompts with human-review rules)
- Team-Briefing-Session-Plan-and-Answer-Key.docx
Cheat sheets
- Numbers-That-Matter-Product-Metrics-Card.pdf
- Product-Decision-Cards-and-Mistakes.pdf
- Product-Rules-by-Country-November-2026.pdf (the dated sheet)
Calendar, import and training
- 90-Day-New-PM-and-Product-Rhythm-Calendar.ics (57 events)
- Product-OS-Task-Board.csv (38 tasks for Trello, Asana, Notion, Planner or Jira)
- Product-Management-Knowledge-Check.csv (14 scenario questions for any LMS)
When you have worked through it, you will be able to…
Every outcome is practised with a worked example and a tool, not just described.
- Write a product strategy on one page with an outcome, a north star and three bets
- Run a customer interview every week with proper consent and a same-day snapshot
- Build an opportunity solution tree and test the riskiest assumptions before build
- Prioritise in the open with RICE and cost of delay, and say no with evidence
- Write one-page PRDs with your design and engineering leads
- Keep a now-next-later roadmap and a stakeholder cadence that prevents surprises
- Launch by tier with a go/no-go and review the result at two and six weeks
- Size an A/B test before it starts, and register and review every AI feature
Know your starting point. Prove your progress.
People who measure before and after improve faster and can show it. AssessAll, our sister assessment platform, has AI-graded assessments that pair with this kit. Take one now, work through the kit, then re-take it.
Product Management Judgment
Take the assessment →AssessAll assessmentBusiness Intelligence Dashboard Design Work Sample for Analysts and Management Information Teams
Take the assessment →AssessAll assessmentStakeholder Management & Influence
Take the assessment →JobularyIf-then plans that make habits stick (Jobulary)
Make it a growth plan →A taste of Chapter 1
Here is the sentence we use: a product manager is accountable for what the team builds and why, and measured by whether it changes customer behaviour and business results. Three things follow from it. First, the unit of success is an outcome, not an output. An output is a feature shipped. An outcome is a change in what customers do, with a baseline, a target and a date: "raise the share of new hires ready on day one from 46% to 60% by 31 March 2027". Features are bets on outcomes. Some bets lose. Second, the PM decides through evidence, not authority. You rarely manage the engineers or designers; you earn the decision by knowing most about customers, data and trade-offs, and making that knowledge visible. Third, the PM owns the system, not every decision. Many decisions belong to the design lead, the engineering lead or the CEO. Your job is that they get made well, on time, with the right evidence, and leave a record.
The honest comparison
| Free templates and typical advice | This kit | |
|---|---|---|
| Prioritisation | A RICE spreadsheet on its own | RICE and cost of delay side by side, a feature case that shows where cost of delay comes from, a capacity check and messages for saying no |
| Discovery | A list of interview questions | Consent steps and exact words, a story-based guide, a snapshot form, an interview log that builds the opportunity tree by formula, and risk-scored assumption tests |
| Roadmap | A slide template with dates | A now-next-later roadmap with bets, metrics and confidence, rules for what sales may share, and a sign-off memo |
| Measurement | A list of metric names | A north star with input metrics, activation and retention by cohort, an experiment log with sample sizes and a dashboard with traffic lights |
| Compared with hiring a consultant or coach | Expert advice for your situation, paid by the day or month | The method and tools a good coach would set up, for you and your team to run; use it alongside an adviser where you need one, especially for legal questions |
| Compared with product management software | A tool to store ideas, roadmaps and feedback | The method, decision rules, policy, templates and training that software does not provide; works in a spreadsheet or alongside any tool |
Made for you if…
- The first product manager at a start-up or scale-up with roughly 10 to 150 people
- Founders and CEOs doing the product job themselves, or about to hire a first PM
- Engineers and designers who have been handed product responsibility
- PMs moving from a large company to a small one, who need the scaffolding back
- Heads of product setting a common way of working for a small team of PMs
- Teams in the US, Canada, the UK, the EU, Australia and New Zealand, and other English-speaking markets
Probably not for you if…
- Anyone looking for a promise of retention, growth, a promotion or a successful launch: the kit makes decisions visible and evidence explicit, it does not guarantee outcomes
- Legal advice: research consent, privacy, consumer, accessibility, AI and employment rules need your adviser; the kit names them and dates the specifics
- Large product organisations that need portfolio governance across many teams: this kit runs one product team well
- Full go-to-market launches with pricing, campaigns and events: see The Product Launch Command Centre
Built by trainers, tested in real rooms.
Bodhih Training has designed and delivered corporate programmes since 2008. Bodhih Pro Kits package what works in those workshops into a guide plus the exact tools we use, so you can apply it the same day without a facilitator in the room.
From here to using it in three steps
- STEP 1
Tap Get the kit
Name, email and country. UPI, card or netbanking in India; international cards everywhere else. No account to create.
- STEP 2
Download instantly
Your download page opens at once, with every file and a one-click ZIP. A permanent link lands in your inbox too.
- STEP 3
Open the first tool
Start with the quick-start chapter, then the main spreadsheet or planner. Most buyers use something from the kit the same day.
One outcome, decisions in the open, starting this week
Open the Start-here map tonight and give yourself one hour with the workbook. Whether you begin with the self-assessment or the strategy on a page, you will finish the hour with a first score, a draft outcome and your first interviews booked.
Personal licence for the buyer's own use, including use within your own company with your team and leadership. Please don't share or resell the files. Team, multi-team and company licences: solutions@bodhih.com.
What buyers say
No ratings yet. Only people who have bought this kit can rate it - every buyer gets a one-click rating link a couple of days after their purchase.
The Bodhih family, when you are ready for more
The Compensation and Salary Band Builder
Build a fair, market-based pay structure for a company of 20-1,000 people.
The Succession Planning and Talent Review Kit
Run succession planning and talent reviews.
The Skills Matrix and Skills-Based Hiring Kit
Move a team or company to skills-based talent practices.
AssessAll
250+ AI-graded assessments to measure skills and earn verified credentials.
Jobulary
Individual development plans that start from evidence and stay yours.
Bodhih Training
Run this topic as a live workshop for your team, in person or online.
Pewple
Book a vetted coach for career, leadership or communication. Pay per session.
Bodhih.org pathways
Certification pathways in Applied AI, Workplace English and management.
The Product Manager's Operating System: FAQs
Read the free guideAlready bought? Resend my linkWhat is in The Product Manager's Operating System?
An e-book with ten chapters, a 26-sheet workbook, a 8-sheet business case and experiment calculator, five fillable forms, eight Word documents (strategy and roadmap template, PRD template, operating policy, sign-off memo, 36 messages, a worked example, 28 AI prompts and a briefing plan), three cheat sheets, a start-here map, a 57-event calendar, a task board and a 14-question knowledge check.
What should a new product manager do in the first 90 days?
Listen for the first 30 days (one-to-ones, a baseline score, weekly interviews, one agreed outcome), focus in the next 30 (opportunity tree, open prioritisation, stakeholder map, a first launch with a checklist) and deliver by day 90 (a signed-off roadmap, a first experiment, a re-score). The kit's 90-day plan sheet and calendar hold the milestones.
Is RICE or cost of delay better for prioritising features?
Use both. RICE (reach x impact x confidence / effort) orders a long backlog by impact per unit of effort. Cost of delay divided by duration (CD3) captures deadlines, deals and risk that RICE misses. When the two ranks disagree by a lot, that is a conversation to have, not a number to average.
What goes in a PRD?
For most work, one page: the problem in the customer's words with evidence, the outcome and metric with a guardrail, the opportunity and bet it serves, a short solution, the riskiest assumptions and tests, scope and non-goals, the launch tier and open questions. The full version adds requirements, acceptance criteria, accessibility, privacy, AI, analytics and rollout.
How do I say no to feature requests without damaging relationships?
Answer every request within a few days, give the reason as evidence and a trade-off rather than an opinion, and offer a next step: a workaround, a date to revisit or a question that would change the answer. The kit has an intake form, a five-day answer rule and six messages for these moments.
How many users do I need for an A/B test?
A common rule of thumb for about 80% power at 5% significance is 16 x p x (1 - p) / d squared per variant, where p is the baseline rate and d the smallest change worth detecting. For a 46% baseline and a 4-point change, that is about 2,485 per variant. The calculator does the sum and flags tests that would take too long.
Can I use this with my team?
Yes, within your own company under the personal licence: share the outputs with your team and leadership, and run the briefing session and knowledge check with your staff. Company-wide and multi-team licences are available through solutions@bodhih.com.
Does it work in my country?
The method works anywhere. The Crosswalk sheet and the dated sheet cover the US, Canada, the UK, the EU, Australia and New Zealand: research consent and privacy, analytics and cookies, interface and subscription rules, accessibility, AI features and hiring. Laws differ by country and state and change often, so check locally with your adviser.
Do I need product management software to use it?
No. Everything runs in Excel or Google Sheets and Word or Google Docs. If you already use a product tool, the workbook's method, decision rules and templates work alongside it, and the task board imports into Trello, Asana, Notion, Planner or Jira.
Is this legal advice, or a guarantee of results?
Neither. It is educational content and templates. It does not make a feature compliant, and it does not promise retention, growth or a successful launch. It names the rules that touch product work and dates the specifics, so you know what to check with your adviser.
How can I measure my starting point as a product manager?
The kit's 18-practice self-assessment scores your team's practice. If you also want to test your own judgement, AssessAll offers Product Management Judgment, a Business Intelligence Dashboard Design Work Sample and Stakeholder Management and Influence at assessall.com.
How do I make the new habits stick after day 90?
Put the rhythm in the calendar (the kit's calendar file does this) and write an if-then plan for the moments habits slip, such as 'if an interview is cancelled, I rebook it before I close the email'. Jobulary's guide to if-then plans at work explains why this works and how to write them.
How much does The Product Manager's Operating System cost?
₹1,499 including 18% GST for buyers in India, or $39 for buyers outside India. One-time payment, no subscription, with an automatic invoice.
How do I get the files after paying?
Instantly. Your download page opens the moment payment succeeds, and a permanent download link is emailed to you. Download each file separately or everything in one ZIP.
What software do I need?
Any of the usual tools: Excel or Google Sheets for spreadsheets, Word or Google Docs for templates, Adobe Acrobat Reader, Preview, Xodo or GoodNotes for the fillable PDFs, and Google, Outlook or Apple Calendar for the calendar plan.
Can I get a refund?
Because it is a digital download, kits are not refundable once downloaded. We always refund a duplicate charge or a failed delivery, and if a file is corrupted and we cannot fix it within 3 working days. Full terms: bodhih.org/refunds.
Can my company buy this for a team?
Yes. Team and company licences, and workshops on this topic run by Bodhih Training, are available. Write to solutions@bodhih.com or call +91 99000 11601.
