Capstone: Your 90-Day Plan
Synthesize everything from this course into a concrete, written 90-day plan for a new role, covering communication, feedback, and influence milestones.
The Job Doesn’t Start on Day 90
Most new hires treat their first three months as a probation period to survive quietly — learn the codebase, don’t ruffle feathers, wait until you “know enough” to actually contribute an opinion. That instinct is understandable and almost always wrong. The first 90 days are the highest-leverage window you’ll ever have in a role, because it’s the only period where you have permission to ask basic questions, where people’s first impressions of you are still forming, and where you can observe the team’s actual habits before you’ve absorbed them as invisible defaults.
This capstone asks you to write an actual plan, not read about one. Every module in this course maps onto a specific piece of it — this is where the pieces get assembled.
The Three-Phase Shape
A 90-day plan works best broken into three deliberately different phases, because what’s useful to do changes as you move from having zero context to having enough context to act on:
Days 1–30: Learn and Listen. Your job is to build an accurate map of how the team actually works — not how the onboarding doc says it works. Meet everyone you’ll work with regularly, one-on-one if possible. Ask more questions than you think you need to. Resist the urge to propose changes yet, even ones you’re fairly confident about — you don’t yet know which of your observations are genuine problems versus just unfamiliar-to-you norms that work fine.
Days 31–60: Contribute and Calibrate. Start shipping real work, and start testing your read on the team against reality. This is where you give your first pieces of feedback (Module 2), where you might raise your first idea for a change (Module 3) — small-scale, well-cased, not a sweeping proposal on day 35.
Days 61–90: Own Something. By now you should have at least one area where you’re not just executing, but genuinely driving — a project, a process improvement, a piece of the codebase. This is where influence-without-authority (Module 3) becomes real rather than theoretical, and where the writing and explaining skills from Module 1 get used on something with actual stakes.
Building Your Plan: Communication
From Module 1, your plan should specify how you’ll communicate in the new role, not just what you’ll work on — because the habits you establish in the first month are the ones that stick.
Concretely, decide now, before day 1:
- Your status update format. Will you default to the inverted pyramid — bottom line first — in your first standup updates, or will you fall back into narrating what you did chronologically because it’s more comfortable? Write the template you’ll actually use.
- How you’ll explain your work to non-technical stakeholders, if your role touches any. If you’ll be in cross-functional meetings in week one, draft what a “so what”-tested explanation of your first project sounds like before you’re asked for it live.
- One thing you’ll write down, even if nobody asks — a doc explaining a decision, a clear README for something undocumented you had to reverse-engineer. This is a low-risk, high-visibility way to demonstrate the writing skills from Lesson 2 early.
Building Your Plan: Feedback and Team Habits
From Module 2, decide how you’ll handle both directions of feedback before you’re in a moment that requires improvising it:
- Receiving it. In your first 30 days, you’ll get onboarding feedback almost constantly — plan to actually use the “separate hearing from responding” technique rather than defaulting to explaining yourself. Write down one thing you’ll say when you get feedback that stings: a scripted “thanks, can you say more about what that looked like” buys you the pause you’ll need in the actual moment.
- Giving it. Decide roughly when you’ll give your first piece of feedback to a peer — not too early (you don’t have enough context yet to be confident it’s SBI-accurate) and not so late that you’ve absorbed “don’t rock the boat” as a permanent habit. Days 45–60 is a reasonable target for most roles.
- Code review or equivalent. If your role includes reviewing others’ work, decide your default tone for your first few review comments — this is where the “question, not verdict” phrasing from Lesson 2 either becomes a habit or doesn’t, and first impressions here are sticky.
Building Your Plan: Influence
From Module 3, name — specifically — what you’re aiming to influence by day 90, and through which lever:
Weaker plan: “By day 30, I’ll have identified what’s broken about our deploy process and proposed a fix in a team meeting.”
This repeats the exact failure from Module 3’s opening story — a case made too early, to a room, before any alliances were built and before enough context exists to know whether the “problem” is actually a problem or just unfamiliar. Being new and being loud about a sweeping change in the same month is the fastest way to burn credibility you haven’t earned yet.
Better plan: “By day 30, I’ll have a list of things that seem off, but I’ll hold off proposing fixes. By day 45, I’ll pick the single most well-evidenced one, talk to the person most likely to be skeptical one-on-one first, and only then bring a cased proposal to the team — probably around day 60.”
The better version doesn’t abandon influence, it sequences it correctly: observation first, case-building second, one-on-one alliance-building third, public pitch last — exactly the order Module 3 laid out, now with actual dates attached.
Building Your Plan: A Template
Use this structure to draft your own plan. Fill in specifics — not “communicate well,” but the actual template, the actual name of the person you’ll talk to first, the actual project you’re aiming to own by day 90.
| Phase | Communication | Feedback | Influence / Ownership |
|---|---|---|---|
| Days 1–30 | [Your status update template; who you’ll meet 1:1] | [How you’ll receive feedback; script for the sting] | [What you’re observing, not yet acting on] |
| Days 31–60 | [First “so what”-tested stakeholder explanation] | [First piece of feedback you’ll give, and to whom] | [The one idea you’ll case up and pitch privately first] |
| Days 61–90 | [One thing you’ll write down for others] | [How review/feedback habits have shifted] | [The thing you now own] |
Try This
Fill in the template above with real specifics for an actual role — your current one if you’re recently started, or a target role you’re interviewing for. For each cell, write one concrete sentence, not a category. “Talk to more people” is not a plan; “meet with my manager and the two engineers on the payments team 1:1 in week one, and ask each what’s the thing that’s hardest to get right here” is a plan.
When you’re done, read the whole thing back and check it against the Pitfall above: does days 1–30 include anything that jumps straight to proposing a change? If so, move it to phase two, and replace it with an observation goal instead.
You're 25 days into a new role. You've noticed the team's PR review turnaround is slow — sometimes three or four days — and you're fairly sure a lightweight SLA (like 'first response within one business day') would fix it. Per this course, what should you do in the next two weeks?
Reveal Answer & Explanation
Keep observing rather than proposing yet — you’re still inside the Days 1–30 ‘learn and listen’ phase, and you don’t yet have the standing, the case, or the allies to pitch a team-wide process change. Use the next two weeks to gather the actual evidence (how often does slow review really block someone, is there already a known reason it’s slow) and identify who to talk to first, privately, once you’re past day 30.
This is the exact pattern the capstone and Module 3 both warn against: a plausible, probably-correct observation, proposed too early, to the group, before any case or alliance-building has happened. Being right isn’t the risk — being right at the wrong moment, in the wrong order, is. The better use of the next two weeks is exactly what Days 1–30 are for: confirm the observation is real (track a few PRs, see if the pattern holds), and identify the person on the team most likely to have an opinion about it, so that whenever you do raise it — probably day 40 or 45 — you’re doing it with a case and a one-on-one conversation already behind you, not cold, in a meeting, on day 25.
Course Wrap-Up
That’s the whole course. You started with translating technical work into language anyone could act on, built up through feedback and disagreement, into leading without a title, into landing the next role — and this capstone is where all of it gets used at once, in the highest-leverage window any new role gives you. The plan you just drafted isn’t a class exercise to file away; it’s the actual plan. Pull it out on day 1.