On my first day at a marketing agency years ago, I spent eleven minutes trying to figure out how to print a single document. The printer needed a code. The code was on a sticky note. The sticky note was on someone else's monitor. I was too embarrassed to ask, so I just stood there pretending to read something important on my phone.
Nobody warns you that the hardest part of a new job is not the work. It is the not-knowing. Where things are, who decides what, whether your questions sound dumb, and whether anyone has noticed you exist yet.
Your first ninety days are not about being brilliant. They are about being steady, curious, and easy to trust. Here is the plan I give every nervous new hire I coach, broken into the order you should actually do things.
Treat Your First Week as Listening, Not Performing
New hires often arrive ready to prove themselves. They fire off ideas in the first meeting, volunteer for everything, and try to fix processes they barely understand. It almost always lands badly.
Your first week has one job: build a map. Who does what, how decisions move, and what "good" looks like on your team. You cannot improve a system you have not seen run yet.
Keep a running notes doc you never share. Jot down names, roles, acronyms, where files live, and who answers which kind of question. By Friday you will have a personal handbook nobody handed you.
Ask one good question per meeting instead of five rushed ones. "Can you walk me through how this normally works?" makes you look engaged. Rapid-fire opinions before you understand the context make you look like you are auditioning.
Nail the Boring Reliability Stuff Early
Here is a quiet truth I wish someone had told me sooner. In your first months, reliability beats brilliance. Showing up on time, replying to messages, and doing exactly what you said you would do builds more trust than any clever idea.
If a manager asks for something by Thursday, deliver it Wednesday afternoon. If you are running late on a task, say so before the deadline, not after. People remember who they could count on long before they remember who was the smartest person in the room.
Small promises kept, repeated over weeks, equal a reputation. Nobody hands you credibility on day one. You earn it in ten-minute increments by being someone whose word matches their work.
Set up the basics so reliability is easy. Learn the calendar tools, turn on notifications for the channels that matter, and block focus time so deadlines do not sneak up on you.
Ask Better Questions (and Stop Apologizing for Them)
The fear of looking incompetent makes new hires either ask nothing or apologize for everything. Both are mistakes. The goal is to ask in a way that shows you thought first.
Compare two versions. "How do I do this?" puts all the work on the other person. "I tried X and Y, I think the next step is Z, am I on the right track?" shows initiative and gets you a faster answer.
The 15-minute rule
When you are stuck, try solving it yourself for about fifteen minutes first. Check the docs, search old messages, look for a similar example. If you are still stuck after that, ask. This protects your time without making you a person who burns through other people's afternoons.
Saving up questions for a weekly check-in so you do not "bother" anyone. You end up blocked for days on something a two-minute message would have solved. Ask in the moment, just ask well.
Learn the Unwritten Rules of Your Workplace
Every team has a culture that nobody documents. When meetings really start. Whether direct messages or email get faster replies. How people disagree without it getting tense. These unwritten rules matter as much as the official handbook.
Watch the people who are clearly respected and clearly happy. How do they communicate? When do they speak up in meetings? What do they never do? You are not copying them, you are reading the room so you can be yourself without stepping on landmines.
If your role involves a mix of office and home days, pay attention to how your team handles that rhythm. The differences are real, and our breakdown of how remote and hybrid setups actually compare can help you figure out where you do your best work and how to flag it without sounding demanding.
Build Real Relationships, One Coffee at a Time
You do not need to befriend the whole company. You need a handful of people who know your name, trust your work, and would vouch for you. That web of small relationships is what carries you through the hard months later.
In your first few weeks, ask two or three people for a short coffee or a quick call. Not to network in some cynical way, just to understand their work and let them understand yours. "I am new and trying to learn how the team fits together, can I get fifteen minutes?" almost never gets a no.
| Timeframe | Main focus | What success looks like |
|---|---|---|
| Days 1-30 | Observe and absorb | You understand who does what and how work flows |
| Days 31-60 | Contribute reliably | You finish assigned work on time and ask sharp questions |
| Days 61-90 | Add visible value | You take ownership of something small and start suggesting improvements |
Remember that relationships go both ways. Offer help when you can, even tiny things like sharing a useful link or covering a small task. Generosity early is remembered long after.
Find One Thing to Own by Day Sixty
Around the two-month mark, the listening phase should turn into doing. Look for one project, process, or recurring task you can quietly become the reliable person for. It does not need to be glamorous. A clean weekly report, a tidied-up document, a small fix everyone kept ignoring.
Ownership is how you stop being "the new person" and become "the person who handles that." It gives your manager a clear answer when someone asks what you have been contributing.
When you finish that owned task, send a short, plain update. "Cleaned up the onboarding doc, here is the new version." No bragging needed. Quiet, consistent updates make your work easy to notice without you ever fishing for praise.
Set Up Your First Real Check-In
Do not wait for your ninety-day review to find out how you are doing. Around week four or five, ask your manager a direct question. "What is one thing I am doing well and one thing I could improve?" It signals maturity and gives you time to course-correct.
Write down the feedback and act on it visibly. If they say you could communicate progress more often, start sending short status updates the next week. Acting on feedback fast is one of the most underrated career moves there is.
This early habit pays off far beyond your first job. The same skill of inviting feedback and tracking your wins is exactly what you will lean on later when you decide it is time to make the case for a raise with evidence instead of nerves.
The new hires who thrive are rarely the loudest. They are the ones who listen first, deliver what they promised, and quietly become indispensable.
What if I make a real mistake in my first month?
Own it quickly, explain what happened in one sentence, and say how you will prevent it next time. Most managers judge new hires by how they handle errors, not by whether they make them. Hiding a mistake does far more damage than the mistake itself.
How do I look competent when I genuinely do not know much yet?
Competence early looks like good questions, reliable follow-through, and visible effort, not perfect answers. Show your thinking when you ask for help, and finish what you start. That reads as capable far more than pretending to know things you do not.
Should I be polishing my resume during my first ninety days?
Not for a job hunt, but yes for your own records. Keep a running list of what you accomplish each month while it is fresh. When you eventually update things and study how to write a resume that lands interviews, those notes turn vague memories into concrete, specific wins.
None of this requires you to be the most talented person on the team. It requires you to be present, reliable, and genuinely curious about how things work. Do that for ninety days and you will not just survive your first job, you will earn the kind of trust that makes everything after it easier. You have got this, and the printer code will eventually make sense too.
