Roles and Responsibilities
Meera's first week as ReShelf's PM: forty chat messages answered, six meetings, one document written. On Friday evening she could not say what she had actually moved forward. A PM's calendar fills itself. Knowing the core responsibilities is how you decide what deserves your time.
The rule
Discover, decide, align, deliver, learn — then go round again.
- Discover. Understand users, the market and the data. Meera talks to students, reads support messages and watches the sales numbers.
- Decide. Choose which problems to tackle and, just as important, which to leave. Set the scope and the success measure. "Not now" is a real answer.
- Align. Get the people involved (engineering, design, marketing, the founder, student ambassadors) to understand and back the plan. Roadmaps and clear updates live here.
- Deliver. Stay close while the team builds: write clear requirements, answer questions quickly, remove blockers, and make small scope calls when surprises appear.
- Learn. After release, measure what changed and feed it back into discovery.
What the role is not matters as much. A PM usually has nobody reporting to them. ReShelf's engineers report to Arjun, who handles hiring and performance reviews. That is why the popular line "the PM is the CEO of the product" misleads: a PM carries responsibility for results without the authority to give orders. Their influence comes from evidence, clarity and trust.
Titles vary (associate PM, senior PM, group PM, and specialists such as growth PMs or technical PMs), but they all run this same loop at different scales.
The shortcut
When a week feels chaotic, ask: "Which step of the loop is weakest right now?" Spend your time there first.
Learn
The dashboard shows completed sales down 30% on last week. The loop starts here.
The trap is living in one step. A PM who only discovers never ships. One who only delivers becomes a ticket-taker for whoever shouts loudest. One who never learns repeats last year's mistakes with more confidence.
Drills
Answer fast — trust the rule.
Mid-build, an engineer asks what should happen when a book has no edition number. Meera answers within the hour so work can continue. Which step is this?
Which of these is usually NOT a product manager's responsibility?
Why is "the PM is the CEO of the product" misleading?
After a release, Meera finds that listings with edition tags sell twice as fast. Where does this finding go next?
Remember
- Discover, decide, align, deliver, learn, then go round again.
- When the week is chaotic, find the weakest step of the loop and start there.
- Trap: believing you can command the team. A PM has responsibility without authority.