First 90 Days Novels & Stories

Stepping into those first 90 days can feel like booting up a brand-new game on hard mode — there’s excitement, uncertainty, and a dozen systems to learn. I treat it like a mission: first, scope the map. Spend the early weeks listening more than speaking. I make a deliberate effort to talk with a cross-section of people — direct reports, peers, stakeholders — to map out who has influence, who’s carrying hidden knowledge, and where the landmines are. That listening phase isn’t passive; I take notes, sketch org charts, and start forming hypotheses that I’ll test.

Next, I hunt for achievable wins that align with bigger goals. That might be fixing a broken process, clarifying a confusing priority, or helping a teammate unblock a project. Those small victories build credibility and momentum faster than grand plans on day one. I also focus on cadence: weekly check-ins, a public roadmap, and rituals that signal stability. That consistency helps people feel safe enough to take risks.

Finally, I read 'The First 90 Days' and then intentionally ignore the parts that don’t fit my context. Frameworks are useful, but culture is the real game mechanic. I try to be honest about my blind spots, ask for feedback, and adjust. By the end of the third month I aim to have a few validated wins, a clearer strategy, and stronger relationships — and usually a renewed buzz about what we can build together.

Right off the bat I expect the first 90 days to feel like a sprint-meets-mapping exercise. In the first 30 days I’m mostly absorbing: meeting people, learning jargon, and spotting low-hanging fruit. Those early wins aren’t usually seismic, but they matter — fixing a small process hiccup, clarifying a miscommunicated goal, or delivering a quick demo that proves momentum. Those feel-good moments show others I pay attention and can move things.



By day 60 I want to turn learning into leverage. That means measurable progress on at least one meaningful metric, a roadmap that people trust, and a handful of relationships that have moved from polite to productive. I’m watching for changes in behavior — are teammates asking for my input? Is a stalled project starting to unstick? I’m also careful to communicate trade-offs: deeper structural fixes take longer than a single sprint.



At day 90 I expect to have laid claim to a clear strand of responsibility. Not a finished empire, but a visible trajectory: an increase in performance, clearer processes, and documented next steps. I always keep expectations realistic: some systems or culture shifts take many more 90-day cycles. Reading 'The First 90 Days' helped me shape expectations, but real life is messier. Overall, I like seeing a mix of quick wins, trust built, and a solid plan — that combination feels like progress to me.

The book 'The First 90 Days' by Michael D. Watkins is all about making a smooth transition into a new leadership role. The first few months are critical, and the author breaks down strategies to accelerate your learning curve, build credibility, and secure early wins. It's not just about surviving but thriving in those initial days. Watkins emphasizes the importance of diagnosing the situation—understanding whether you're stepping into a startup, turnaround, realignment, or sustaining success scenario. Each demands a different approach, and misreading the context can set you back.

One of the standout ideas is the 'STARS' model (Startup, Turnaround, Accelerated growth, Realignment, Sustaining success), which helps tailor your strategy. The book also dives into building alliances, managing expectations, and avoiding common traps like the 'action imperative' (feeling pressured to act before fully understanding the landscape). Personally, I found the section on cultural assimilation super practical—learning the unwritten rules of an organization can make or break your success. It's a must-read for anyone stepping into a new role, whether you're a fresh grad or a seasoned exec.