Someone walks into a new job full of energy and ideas. They've been hired to lead a team and improve processes, convinced they see exactly what needs to change in the first hour. By day two, they've pitched three different improvements. They think they're showing initiative. What they're actually doing is telling the team that they don't trust their judgment and that they haven't bothered to understand why things were built this way.
Six months later, a peer tells this person the damage: "People liked you, but everyone decided you were the kind of manager who changes things without understanding them first." That story sticks around long enough that even good work done later gets filtered through it.
This pattern shows up repeatedly. The mistake isn't unique to one person or one industry. It's what happens when people focus on proving competence instead of proving they're paying attention.
The Trap: Proving vs. Paying Attention
When someone is new, there's a gap between what they can contribute and what they actually understand. The temptation is to close that gap by demonstrating capability. "Look, I can do this. Look, I see a better way." The thinking goes that faster contribution proves you belong.
But the people who have been in the room already made those decisions. The processes that look broken aren't broken because nobody thought of the fix. They exist because someone learned something that an outside perspective hasn't reached yet.
People watching on day one aren't asking, "Is this person smart?" They're asking, "Is this person going to listen to us, or are they going to start reorganizing before they even know how coffee orders work?" The second question determines whether they trust you. The first one is almost irrelevant.
What Everyone Is Actually Assessing
Your first week, people notice four things, usually not the things you think.
They notice whether you ask questions. Specifically, whether questions suggest genuine curiosity about how things work or whether they're performative. "How did you end up choosing this tool?" is different from "Why not use a better tool?" One says you're curious. The other says you've already decided.
They notice what gets written down. Someone new asks a question about a system, gets an explanation, doesn't write anything, and asks the exact same question to a different person the next day. By day three, people have stopped bothering to answer. Taking notes signals that what people are telling you matters enough to remember.
They notice when someone says, "I don't know." Saying it early and without defensiveness is a signal of strength. It means you're comfortable enough to be curious instead of pretending. Most new hires either oversell what they know or undersell it. The people who say "I don't understand that yet, walk me through it" are the ones who people actually want to help.
They notice whether you respect the decisions people made before you arrived. If you immediately critique how something was done, you're criticizing the person who did it. Even if you're right, even if there's a genuinely better way, that conversation doesn't happen on day one. It happens after enough credibility is built that people trust you're not just being critical.
The Week That Sets the Pattern
Stories about new hires travel fast. One person's first week can become the lens through which everyone views them for years.
Someone gets hired into a new role and spends the first week mostly in meetings and conversations, taking detailed notes, asking about decisions. Nothing flashy. No big ideas pitched. By the end of the week, people are already saying, "I think we're going to like working with this person." Six months later, when that person does propose changes, the team listens instead of getting defensive.
Someone else gets hired and spends their first week suggesting three new processes, two restructured workflows, and one new tool. The person means well. But the story that sticks is not "great ideas" but "doesn't respect how we do things." When that person later finds a genuine problem to solve, the team is skeptical from the start.
Your first week writes a story about you that's stickier than your actual work. That's unfair but true. The story is also not fixed. But it's much harder to rewrite than to write correctly the first time.
The First Conversation That Matters
Usually, someone reaches out in the first few days and asks how you're settling in. This is the moment that matters most.
If you use it to ask about the team, the pressures they face, what they're proud of, what keeps them up at night, you learn something genuine. If you use it to demonstrate knowledge or pitch ideas, you miss the whole point.
The strongest new hires ask real questions: "What's the biggest challenge the team faces?" "What would you do differently if you could?" "What did the last person who had this role miss?" These questions do two things at once. They get actual information. And they signal that you're not here to prove something, you're here to learn something.
This connects to how Page 12: The Second Mouse Gets the Cheese works: observation and learning before action separates people who move smart from people who move fast and wrong.
Closing Thoughts
You were hired because someone thinks you can do the job. You don't have to prove that on day one. What you have to prove is that you're willing to learn how this specific job actually works, in this specific place, with these specific people.
That takes patience. But patience in your first week buys you credibility for years.