Quick tips
- Map who decides, who influences, who is told last.
- Write down everything that confuses you in week one.
- Pick one visible win you can finish by week eight.
The offer is signed, the laptop arrives Friday, and you have been lying awake planning how to prove in week one that hiring you was the right call. Good. That energy is an asset and nobody here will talk you out of it. The only question is where to spend it.
A new job hands you one thing you will never have again, which is a clean view. For about four weeks you can see everything that is odd about this place. Then you stop seeing it, because you have become one of the people who work here. Nearly every advantage of these twelve weeks comes from using that view before it closes.
Here is the shape. Weeks one to four buy information. Weeks five to eight buy one small, visible win. Weeks nine to twelve set the standard you want to be held to. Go hard the whole time. Composure is what aims it at the part that counts.
What should I actually do in my first week?
Map who decides what, and write down everything that confuses you. Those two things are only available now, and both get harder every week you stay.
The map is not an org chart. Draw three columns: who decides, who influences the decider, and who finds out last. Fill it in by asking people directly, because in week one you are allowed to ask anything and nobody thinks less of you for it. That permission expires around week five. Ask each person you meet what they are working on, what is in their way, and who they go to when something is stuck. The third answer is the one that tells you how the place really runs.
The confusion list is the other half. Every time something makes no sense, write one line. Why do two teams own this? Why does the deploy take an hour? Why does nobody use the tool we pay for? The confusion you feel in week one is the most valuable thing you own, and it has a shelf life of about a month.
One practical thing, and then back to the job. Put your training in the calendar in week one, before the new role takes the empty slots. The person still going hard in week twelve is the one whose week has a floor under it, and the body is the equipment ambition runs on, not a reward for surviving the quarter.
How do I prove myself without shipping something half-baked?
Spend the first month asking better questions than anybody expects, and the second month finishing one real thing. Speed on the wrong problem in week two reads as inexperience, and it costs more to undo than the wait would have cost.
New hires get this backwards because the anxiety is loudest at the start. You feel a debt to justify the salary, so you look for something to fix in the first fortnight, and you usually pick the thing that is broken for a reason you have not learned yet. Everybody in the building has already tried the obvious fix. The question that earns you standing is not "why don't we just" but "what did you try, and what happened?"
Meanwhile, your questions are the output. A new person who asks precise questions in week two is already visible, already useful, and already teaching the room something about how they think. That is a much better first impression than a rushed pull request.
When should I make my first visible move?
Pick the win in week five and finish it by week eight. It should be small enough that nothing can stop you, and useful enough that somebody outside your own team notices it is done.
Choose from the confusion list, because that list is a catalog of things everybody has stopped seeing. The best candidates are unglamorous and finishable: the report that three people rebuild by hand each month, the setup step that costs every new hire a day, the dashboard that nobody trusts. Announce nothing at the start. Finish it, then say one sentence about it in the place where your team talks, naming what changed rather than how hard it was.
The day you finish it, write the row down: what you did, what changed, who saw it. You will not remember the details in eleven months, and eleven months from now is when somebody will ask.
What do I do with all the notes I took in week one?
Turn them into the onboarding document nobody at this company ever wrote, and hand it to the next person who starts. It costs you an hour, it makes you learn the system twice, and it is the fastest honest way to be known before you have enough output to be known for.
Do it in weeks nine to twelve, while your notes are still readable and the answers are fresh. Take the confusion list, write the answer you eventually found next to each line, cut the complaints, and keep the parts a stranger would need. Send it to the next new starter with their name on it, and copy your manager, not as a performance but because they will otherwise never know it exists.
Two things make this worth an hour of a busy quarter. The first is that teaching is the fastest route to actually owning what you know. Explaining the deploy process out loud shows you exactly which parts you were faking, and you will fix them that afternoon. The second is what it does to how you are read. Gallup has found that only about 12% of employees strongly agree that their organization does a great job of onboarding new people, which means the gap you just closed is a gap almost every company has and almost nobody fills. The person who fills it becomes the person others come to, and that happens months before their own work has had time to speak.
Keep it modest and specific. This is not a manifesto about how the company should change. It is a page that saves the next person a week.
How do I set the standard I want to be held to?
In weeks nine to twelve, say out loud how you intend to work, then work that way in front of people. Norms you set in the first quarter get read as who you are. The same norms introduced in month nine get read as a change of behavior, and changes of behavior invite questions.
Say the small things plainly. When you need two days for a review, say so and deliver in two days. When you will not answer messages after nine at night, do not announce a policy, simply do not answer, consistently, from the start. When you commit to a date, hit it or renegotiate it early. Reliability is boring and it compounds faster than brilliance, because everything anybody says about you for the next three years is a summary of whether you did what you said.
This is also the quarter to open the first real conversation about where you are heading. Not an ask, just a heading: what does strong look like at the next level here, and what would you want to see from me over the next six months. Managers answer that question well when it is asked early and badly when it is asked in a panic.
Week thirteen is the one that counts
The plan above is not a slower start. It is a start aimed properly. You are still working at full intensity, still ambitious, still intending to be the best hire they made this year. The difference is that at week thirteen you have a map, one finished thing with your name on it, a document other people use, a standard you set on purpose, and a manager who knows what you are aiming at.
Compare that to the version where you sprinted at whatever appeared first. That person is also exhausted at week thirteen, and cannot point at anything a stranger would recognize.
Pick the first version. Then keep going, because the twelve weeks were never the goal. They were the setup for the three years.