Run a 30-60-90 day plan for a new PM role

The 30-60-90 That Builds Trust Instead of Showing Off

The worst 30-60-90 plans propose changes on day 1; the best ones listen first, validate second, and lead third. Silicon Valley Product Group's writing on PM onboarding and First Round Review's writing on new-role strategy both document the same pattern: PMs who listen in the first 30 days earn the credibility to propose changes in the next 60. Proposing on day 1 marks you as someone who hasn't yet understood the context.

How the Run a 30-60-90 day plan for a new PM role Prompt Works

The prompt sequences the three phases (listen, validate, lead) with deliverables per phase. The "one thing I should NOT do in the first 30 days" output is the discipline: the usual temptation is to propose fixes, and resisting it is the highest-leverage new-role move.

When to Use It

• You just started a new PM role (or start in <4 weeks).
• Your manager asked for a 30-60-90.
• A role change to a different product area requires a new plan.
• An acquisition onboarded you into a new org.
• A senior-level hire needs a plan that matches their scope.

Common Pitfalls

• Proposing changes on day 1. Marks you as someone who hasn't yet understood. Listen first.
• No deliverables per phase. Undocumented phases decay into ambiguity. Each phase needs a written artifact.
• Skipping the feedback step at 90 days. Without explicit 90-day feedback, the pattern of the first 90 days repeats.

Sources

• The Product Manager — Silicon Valley Product Group
• Good Product Team / Bad Product Team — Silicon Valley Product Group
• First Round Review — First Round
• Begin with Trust — Harvard Business Review