The First 90 Days OS: your Week 1 boot sequence

Nobody judges you for what you know in Week 1. They judge you for your defaults.

• Do you communicate clearly?
• Do you follow through?
• Do you ask good questions without creating extra work?
• Do you seem like someone your manager can trust with the next thing?

That’s what a “boot sequence” is: the small habits you set up in the first five days so the rest of the ramp doesn’t feel like a loop.

The loop most new hires get stuck in

Week 1 is a blur. New systems, new acronyms, new people, a lot of “where do we keep the latest version of ___?”

Without a system, you end up in the same cycle every day:

1. You’re confused.
2. You ask a question.
3. You get an answer.
4. You forget it.
5. You ask it again.

Not a smarts problem. A system problem.

The five moves

1. Get a real definition of “good”

Most new hires guess what matters, optimize for the wrong thing, and get hit with “why did you do that?”

Three questions will save you weeks. Ask all of them in your first 1:1:

• What does success look like by Day 30?
• What should I not work on yet?
• How do you want updates — Slack or email, cadence, format?

Script:

“To make sure I’m aiming at the right target — what would you want to be able to say about me thirty days from now? And are there traps you’ve seen new hires fall into that I should avoid?”

That second sentence does the heavy lifting. Managers love the question because they have actual traps in mind and rarely get the chance to name them.

2. Install your note system

Your memory is not a system.

Create one doc called My Job: Notes + Decisions + Glossary. Sections:

• People and what they own — names, responsibilities, preferences
• Decisions — what we decided, and why
• Recurring rules — “we always do X before Y”
• Glossary — internal acronyms (yes, this matters)
• My open questions — batch them, don’t drip them

This is how you look sharp without trying hard. You stop repeating yourself, and the people answering you stop noticing they’ve answered you twice.

3. Make your manager’s life easier

In Week 1, being brilliant is optional. Being low-friction is not.

Send a short end-of-week note Friday afternoon:

Week 1 quick update

Wins: … In progress: … Blocked on: … (here’s what I tried) Next up: … One question: …

That last line matters. One question. Not twelve. The point of the note isn’t your wins — it’s signaling that you’re tracking yourself.

4. Ship one small thing

Pick something low-risk, small, visible, and actually useful. Update a doc everyone complains is outdated. Fix a tiny bug. Turn a meeting into a clean action-item list. Write a “how to run this process” checklist.

The point isn’t impact. The point is a signal: I close loops.

5. Build a tiny relationship map

Your org chart is not the power chart. In Week 1, identify three people:

• one person who reviews your work
• one person who unblocks you
• one person who gets mad if you surprise them

Then ask your manager:

“Who should I be aligned with early so I don’t accidentally create extra work for someone?”

That question alone is worth more than the relationship map.

The thing nobody tells you about Week 1

Looking smart is the wrong target. Looking reliable is the right one. Smart you can fake for an afternoon. Reliable takes ninety days to demonstrate, and once it’s there, your manager will hand you the next thing on their plate without thinking.

—

I’ve onboarded into roles where the first week was a structured boot camp and roles where it was a Slack channel and a prayer. The structured ones were easier. The unstructured ones were higher-leverage — because the system you build in week one in the absence of an official one becomes the version everyone else copies six months later. Either way, the doc, the Friday note, and the small win are how you turn week one into the foundation for the rest of it.

For the full copy/paste version, use the Week 1 Checklist. When you’re ready to pair this with a one-page alignment doc, use the 30/60/90 plan template.