PRODUCT NOTES
What a Fractional PM Should Deliver in the First 30 Days
A week-by-week view of what you should expect from a fractional product manager in the first month, plus a checklist of deliverables and warning signs.
When you bring in a fractional product manager, the first month sets the tone. Here is a reasonable picture of what a good first 30 days looks like. Use it as a yardstick for any provider, including me.
Week 1: Listen and map
The goal is understanding, not opinions.
- Conversations with the founder, developers, and whoever talks to customers.
- A review of the current backlog, support requests, analytics and recent releases.
- A map of how work moves today, from idea to release.
Output: a short written summary of what is happening now, including where decisions get stuck.
Week 2: Define the problem and the decisions
- A written problem statement: what the team is trying to achieve in the next 4 to 8 weeks.
- A list of open decisions, who owns each, and what information is missing.
- A first pass at what to stop, delay or cut.
Output: one agreed goal and a decision log.
Week 3: Put a light process in place
- A single, ordered backlog that replaces scattered notes and chat messages.
- A simple weekly rhythm: planning, a midweek check, and a short review.
- A standard format for specs, so developers know what "ready to build" means.
Output: the team runs one planning cycle using the new rhythm.
Week 4: Ship something through the new process
- One real piece of work moves from spec to release using the new approach.
- A short review of what worked and what did not.
- A plan for the next 60 days, with what is in scope and what is not.
Output: a released piece of work, a retrospective, and the next-60-days plan.
Deliverables checklist
By day 30 you should be able to point to:
- A written current-state summary.
- One goal for the next period.
- A prioritized backlog.
- A decision log.
- At least one spec in the agreed format.
- A weekly rhythm the team actually follows.
- A short plan for the following two months.
Warning signs
- The month ends with a slide deck and no change in how the team works.
- Developers cannot say what changed for them.
- You are still the only person who knows the priorities.
- There is no written output you could hand to someone new.
What this depends on
A first month goes well when the PM has access to the team and to the people who know the customers, and when decisions get made on time. If those are missing, say so early. It is better to adjust scope in week one than to discover the problem in week four.