first-90-days
The First 90 Days
A structured framework for accelerating leadership transitions. Based on Michael D. Watkins' "The First 90 Days" — the definitive playbook for anyone starting a new role, whether it's a promotion, a lateral move, or joining a new company. The first 90 days set the trajectory for everything that follows.
Core Principle
Transitions are the most critical — and most dangerous — times in a leader's career. What you do in the first 90 days will largely determine whether you succeed or fail. The actions you take during your transition establish your reputation, shape how people perceive you, and build (or destroy) momentum. There is no "figuring it out as you go" — you need a plan.
The fundamental challenge: you are simultaneously learning (absorbing massive amounts of new information) and being judged (people form opinions about you quickly and update them slowly). This dual pressure is what makes transitions so hard and so consequential.
Scoring
Goal: 10/10. When evaluating a transition plan, rate 0-10:
| Score | Description |
|---|---|
| 0-2 | No plan. Winging it. No structured learning or relationship building. |
| 3-4 | Basic plan exists but doesn't account for the business situation (STARS). Key conversations are unplanned. |
| 5-6 | Reasonable plan with learning goals and stakeholder mapping, but missing early wins or cultural adaptation strategy. |
More from tomaszstaniak/pm-ai-skills
continuous-discovery-habits
Product discovery framework based on Teresa Torres'' "Continuous Discovery Habits". Use when you need to: (1) build an opportunity solution tree from desired outcomes, (2) identify and prioritize customer opportunities, (3) design assumption tests for product ideas, (4) structure customer interview snapshots, (5) map assumptions to experiments, (6) move from output-driven to outcome-driven product development, (7) map current-state customer experiences, (8) build a weekly discovery habit.
13good-strategy
Strategy evaluation and design framework based on Richard Rumelt''s "Good Strategy Bad Strategy" and Michael Porter''s "What Is Strategy?". Use when you need to: (1) evaluate whether a strategy is good or bad, (2) diagnose the core challenge before proposing solutions, (3) build a coherent strategy kernel (diagnosis + guiding policy + coherent actions), (4) stress-test strategic plans with pre-mortem analysis, (5) distinguish strategy from goals, ambitions, or wish lists.
10working-backwards
Amazon''s Working Backwards product development method based on Colin Bryar and Bill Carr''s "Working Backwards". Use when you need to: (1) write a PR/FAQ document for a new product or feature, (2) validate an idea by defining the customer experience first, (3) stress-test a proposal with pre-mortem analysis, (4) align stakeholders around a product vision, (5) decide whether an idea is worth building before writing code.
9positioning-and-pitch
Framework based on April Dunford''s "Obviously Awesome" and "Sales Pitch". Use when you need to: (1) define or evaluate product positioning using the five-component framework, (2) translate positioning into a compelling pitch for stakeholders or buyers, (3) choose a market category strategy that shapes what you build and how you compete, (4) develop differentiated value claims that connect product decisions to market reality, (5) structure a pitch for exec reviews, board updates, or partner conversations, (6) diagnose why your product story isn''t landing with customers or internal stakeholders, (7) align cross-functional teams around a shared positioning narrative, (8) connect positioning decisions to roadmap priorities and feature trade-offs
6escaping-build-trap
Product management framework based on Melissa Perri''s "Escaping the Build Trap". Use when you need to: (1) diagnose whether a team is stuck in the build trap (shipping features without outcomes), (2) shift from output-driven to outcome-driven product development, (3) evaluate product manager archetypes and team maturity, (4) design a product strategy that connects company vision to team-level decisions, (5) run a pre-mortem on a product roadmap to detect build-trap patterns.
5para-method
Personal knowledge management framework based on Tiago Forte''s "The PARA Method" and "Building a Second Brain". Use when you need to: (1) organize digital information into Projects, Areas, Resources, and Archives, (2) build a Second Brain for capturing and retrieving knowledge, (3) apply CODE methodology (Capture, Organize, Distill, Express), (4) design progressive summarization layers, (5) create actionable knowledge management systems, (6) connect knowledge to current projects, (7) reduce information overload through systematic organization.
2