Week 1 Checklist: how to look competent in your first seven days

Your first week isn’t about proving you’re smart. It’s about eliminating uncertainty.

Most workplace confusion isn’t about effort. It’s about expectations: who decides, what “done” means, what the deadline really is, what happens if it slips, where the landmines are. Your first five days are when you find that out — without making your manager spell it out.

Three principles

1. Be useful quickly. Not heroic. Useful.
2. Ask good questions early. Confusion compounds.
3. Write things down. Your brain is not a CRM.

You don’t need to be perfect. You need to be clear.

Day 0 — The night before

Thirty minutes of setup. Worth it.

• Confirm start time, location, any setup instructions
• Open a doc called Week 1 — Onboarding with sections: People · Glossary · Links · Questions · Wins

That’s it. The rest is real time.

Day 1 — Reset your defaults

Day 1 is about signal, not output.

Show up early, even on Zoom. Punctuality is the cheapest signal you can buy.

Ask for: org chart, team goals, glossary of acronyms (or start one), links to docs, dashboards, ticketing, repos. Confirm logistics: how your manager prefers updates (Slack vs. email), when your 1:1 will be, what “urgent” looks like.

Then ask the two questions most new hires forget:

“To make sure I ramp fast, what are the top three things you’d recommend I read first?”

“Quick style question: do you prefer updates in Slack, email, or in the project doc? And how often is normal here?”

Write down your manager’s top three priorities. Write down their stated update preferences. Don’t trust your memory.

Day 2 — Map the people

A lot of work is really “who knows what.”

Ask your manager: “Who should I meet with to understand how this actually works?” Schedule three to five short intros (15–25 minutes — never an hour, that’s an imposition).

In every intro, ask the same three questions:

1. What are your team’s goals right now?
2. What does a great partner look like?
3. What’s the fastest way I could accidentally make your life harder?

Question three is the one nobody asks. People answer it generously because they have specific answers and rarely get to give them.

For each person, capture: their role, what they own, what they care about (metrics, deadlines, customers), their preferences (Slack vs. email, async vs. meetings). One line per person. This becomes your map.

Day 3 — Define “good”

One of the best career hacks is boring: calibrate expectations early.

Pick the main project you were given. Write a one-page “definition of done.” Confirm it.

# Definition of Done — [Project]

## Outcome
What problem are we solving, and for whom?

## Scope
In:
Out:

## Deliverable
Format:
Where it lives:

## Quality bar
What does "great" look like?
What does "good enough" look like?

## Stakeholders
Decider:
Approvers:
Informed:

## Timeline
Milestone 1:
Milestone 2:
Final:

## Risks
-

Send to your manager:

“I drafted a quick definition of done so I don’t miss the target. Can I send it for a fast thumbs-up?”

You will look extremely organized. Most of your peers won’t have done this.

Day 4 — Pick a small win

One thing you can ship in Week 1. Not a moonshot. Visible to your manager or team, low risk, finishable in a day or two.

Examples: fix a small bug. Improve a template. Document a confusing process. Close a straightforward ticket. Clean up a report.

Tell your manager:

“For Week 1, I’m going to ship ___. Small but useful. I can finish by ___. If there’s a better first win you’d prefer, tell me and I’ll adjust.”

Shows initiative AND alignment. Hard to do both at once.

Day 5 — Lock in your weekly rhythm

Week 1 isn’t done until you have a cadence. Avoid the “I’m busy but nobody knows what I’m doing” trap.

• Schedule a recurring 1:1 with your manager
• Identify your recurring meetings and what each one is actually for
• Set up a running work log + a parking-lot question list
• Send a Friday recap

Friday recap:

• Wins:
• What I learned:
• Open questions:
• Next week:
• Any early feedback for me — anything you want me to do differently?

That last line is gold. Most managers are dying to give micro-feedback but won’t volunteer it. Ask once, get it forever.

The “do not do this” list

• Don’t pretend to understand when you don’t
• Don’t wait a week to ask how priorities work
• Don’t schedule 60-minute intro meetings
• Don’t complain about processes before you understand why they exist
• Don’t try to solve everything in Week 1

Be curious. Be useful. Be steady.

—

I walked into my first job at a big tech company in a brand-new suit my parents had convinced me I’d need. Everyone else was in t-shirts. I spent the day hyper-aware of every signal — how people greeted each other, how they asked questions, what “normal” looked like. That’s the texture of Week 1. You’re learning the job AND the hidden rules at the same time, and the only sane move is to write the hidden rules down as you spot them.

For a one-page alignment doc to pair with this checklist, use the 30/60/90 plan template.