How to Plan Your First Two Weeks in a New Job Calmly
Day one of my last role went like this. Nineteen browser tabs of onboarding documents, six tool invitations, a laptop that would not authenticate until the afternoon, and a manager who said the genuinely kind words "take your time, there...

Day one of my last role went like this. Nineteen browser tabs of onboarding documents, six tool invitations, a laptop that would not authenticate until the afternoon, and a manager who said the genuinely kind words "take your time, there is no rush." By the Friday I had absorbed almost nothing I could repeat back, and I had also said yes to two pieces of work that nobody had asked me to own.
That second part is the expensive one. Information you miss in week one you can pick up in week four. Commitments you accept in week one follow you for a year, because they get written into other people's plans before you understand what you agreed to. The whole point of planning the first ten working days is to protect your capacity to say no later, while you still have no idea what you are looking at.
The real constraint is not knowledge
New starters plan their first fortnight as a learning problem. Read the handbook, shadow a colleague, work through the documentation. That framing is comfortable and mostly wrong.
Two things are genuinely scarce in a new job, and neither is reading time. The first is other people's willingness to explain things, which is high in weeks one and two and falls off a cliff around week four, because by then you are expected to know. The second is your own ignorance, which sounds odd until you notice it is the only period where you can ask why something is done this way without appearing to criticise anyone.
Both expire. Plan around the perishable goods, not the handbook, which will still be there in March.
There is a third constraint worth naming. Your calendar in week one is empty, which means it fills with whatever other people put in it. Within eight working days most new starters are at four or five meetings a day with no unscheduled blocks, and nobody decided that on purpose.
Against the quick win doctrine
The received wisdom is to find a visible quick win inside the first 30 days. Every onboarding guide repeats it. I have watched it do more harm than good often enough to argue against it.
The trouble is that a quick win, by definition, is something you can do without understanding the context. That selects for exactly the wrong kind of work: a tidy up nobody asked for, a dashboard that duplicates one that exists, a process fix that solves the symptom a previous team chose to live with for a good reason. I rebuilt a reporting pipeline in my first month once and discovered in month three that the ugly manual version existed because a regulator wanted a human signature at a specific step.
It also sets a precedent about what you are for. Deliver a flashy small thing in week three and you have advertised availability for flashy small things. The colleague I most admired in that job spent her first six weeks appearing to do very little and then rewrote the team's whole intake process, which held for years.
The honest version of the advice is narrower: in the first month, finish something small that you were explicitly asked to finish. That demonstrates reliability without claiming judgement you have not earned yet.
Two documents, opened on day one
Everything I now do fits in two files, and keeping them separate is what makes the system work rather than becoming one long undifferentiated note.
The first is a question log. Every time something does not make sense, it goes in, with the date and the person most likely to know. Mine runs to 40 or 50 lines by the end of week two. The value is partly in asking them, and partly in rereading the list in month two and noticing which questions stopped mattering, which tells you a lot about what the organisation actually cares about.
The second is a decision log, and it records choices made around you rather than by you: who approved what, what got rejected, which option was considered and dropped. Three lines per entry. This is the document that stops you proposing in week nine something the team killed in week two, which is the fastest way a new person loses credibility.
Keep both in plain text somewhere you can search. The specific tool matters far less than whether you will still open it on a Tuesday afternoon when you are tired, which is the test any system has to pass.
Booking the conversations before the calendar fills
This is the part that needs to happen on day one or day two, while your calendar is still yours. The target is eight to twelve people in ten working days, and the sequencing matters more than the total.
- Day one: ask your manager for a list of the people you should talk to, ordered. Ask specifically who you will frustrate if you get something wrong, because that list is different from the org chart and more useful.
- Day one, same afternoon: send all the invitations at once, 25 minutes each, spread across days three to ten. Sending them in a batch is the whole trick, since doing it one at a time means the last four never get booked.
- Cap it at three conversations a day and block two unscheduled hours every afternoon before anyone else can claim them. Those blocks are where the notes get written, and notes not written within a few hours are mostly lost.
- Open each conversation with the same two questions: what does your week actually look like, and what do you wish the person in my role would do differently. The second one gets you more in four minutes than a week of documentation.
- Day eight or nine: draft one page on what you think your job is, in your own words, and the three things you believe matter most this quarter.
- Day ten: put that page in front of your manager and ask where it is wrong. Expect it to be wrong in at least one significant way, which is the reason to do it early rather than at the end of the quarter.
That final step is the same move as working out a plan from its endpoint rather than from today, which I have written about in planning a project backwards from the deadline day. Starting from where you are supposed to arrive makes the gaps visible much faster.
Closing out week two
Spend 25 minutes on the Friday of week two doing a short review, and run it in the same format you intend to use permanently so the habit starts attached to something real. What did I learn that changed my mind. What did I agree to, and did I mean to. Who do I still owe a reply. What goes in next week's two protected blocks.
The reason to do it now rather than in month two is momentum. A review habit that starts in a quiet fortnight survives the busy ones, and one you try to install during a crisis does not. The mechanics of making it stick are in building a weekly planning routine that actually sticks, and more on the planning side generally sits under planning.
One caveat. All of this assumes a role with some discretion over your own time. If you have started on a rota, a support queue or a factory line, the conversation plan still works but the protected blocks will not, and I would compress the whole thing into the first three days instead.
FAQ
How many people should I meet in my first two weeks?
Eight to twelve is enough for most roles. Past that the conversations blur together and you stop retaining them, which defeats the purpose of having them early.
Should I say yes to everything at first to seem helpful?
No. Say yes to anything that takes under an hour, and for larger requests say you want to understand the context first and will come back on a specific day. Almost nobody objects to that.
What if my manager gives me no structure at all?
Write the structure yourself and send it to them as a proposal. A one page plan for your first fortnight is far easier to react to than an open question, and managers who seem vague are often just busy.
When should I start suggesting changes?
Once you can explain why the current approach exists. If you cannot describe the reasoning behind a process, you do not yet know enough to improve it, and that threshold usually lands somewhere in the second month.
More in Planning
Planning
How to Replan Mid-Week When Monday Falls Apart
Monday was supposed to carry the week. Instead a server outage ate the morning, a colleague resigned at 14:00 and the two hours...
Planning
Buffer Time in Your Schedule and How Much to Leave
Your plan for the day looked perfect at 8:30, and by 11:00 it was already wrong.
Planning
Monthly Planning Routine That Keeps Each Week Realistic
Your weekly plans look reasonable on Sunday night, yet by the third week of the month you are behind on the big things and...