Most 30-60-90 day plans fail for one reason: they list activities instead of outcomes. "Meet the team" is not a plan. "Know who owns each decision on my project by day 30" is.
Days 1 to 30: Learn
Name what you will understand, not just who you will meet: the product, the customers, how decisions get made, and the one metric your team is judged on. End the phase with a short written summary of what you learned and what surprised you.
Days 31 to 60: Contribute
Pick one small, visible win that fits what you learned and ship it. A first fix, a clearer process, a report nobody had time to write. The point is proof that you can deliver inside this team's real constraints.
Days 61 to 90: Lead
Propose the bigger bet. Show the problem, the options, your recommendation and how you will measure it. Managers remember the person who arrived with a plan and then followed it.
Three habits that make it stick
- Write each phase as outcomes with a measure.
- Share a draft with your manager in week one and ask what they would change.
- Review it every Friday for ten minutes and log what moved.
If you are interviewing
The same structure works as a six-slide presentation: the role, what you would learn, what you would contribute, how you would lead, how you would measure it, and the risks you see. Practice the tough questions out loud, especially "what if the plan changes?"
A ready-made kit
I put together the 30-60-90 Day Plan Kit: an editable Word template, five role examples (engineer, product manager, marketing, sales, new manager), an interview presentation script with twelve answer frames, a first-90-days tracker and a 12-page playbook. It is $12: https://logi2.gumroad.com/l/voskbb
If you want one practical template or guide each week, subscribe to the newsletter: https://aifounderweekly.substack.com
Top comments (0)