How to ask for feedback when you're new to the team

Three weeks into the new job, you ask the question that feels natural: "How am I doing so far?" And you get the answer everyone gets: "Honestly, really well. Great energy." It sounds like feedback. It contains nothing. The person who said it wasn't lying — they answered a different question than the one you asked. Not how is this person doing, but what does a decent colleague say to someone who's been here three weeks.

This is the newcomer's paradox. You will never need calibration more than in your first months — you don't know the norms, you can't read the silences, you have no idea which of your defaults land differently here. And you will never get less of it. The feedback supply is at its thinnest exactly when the need peaks. Meanwhile, the one asset you genuinely hold — a license to ask questions that would look strange coming from anyone else — starts expiring the day you arrive.

Why newcomers get the least honest feedback

Three mechanics, and none of them is about you.

Honesty is priced in relationship, and you have no account yet. Real feedback is a small risk: the giver bets that you'll take it well, that it won't come back to bite them, that the relationship can absorb the discomfort. Colleagues who've worked together for years have collateral for that bet. With you they have none, so they default to the zero-risk option — encouragement. (This mechanism never fully disappears either; most people don't volunteer honest feedback to anyone. It just becomes extractable once there's trust to draw on.)

Nobody has your baseline. The most useful feedback sentences start with "you've started to..." or "you're usually X, but lately...". Nobody can say them to you — they don't know your usually. All they can compare you to is the person you replaced, the job description, or whatever they imagined when they heard you were coming. So instead of observations you get impressions, and impressions of newcomers skew polite.

Judgments form anyway — they're just not shared. Your new colleagues are calibrating you from day one: how you run a meeting, how you take pushback, whether your questions are sharp or performative. By week six, a fairly detailed picture of you is in circulation. Almost none of it reaches you, because nothing about a new relationship makes sharing it natural. The picture exists. The pipe doesn't.

The license you're sitting on — and its expiry date

Here's what you get instead of a baseline: a window where asking is free. Questions that would read as insecure in year two — "what does good actually look like here?" — read as diligence in week two. You're expected not to know. There is no status cost.

Most people barely use the window, for one reason: they're afraid that asking makes them look incompetent, precisely while everyone is forming that first impression. The research says the fear points the wrong way. In a series of studies at Harvard Business School, people who asked for advice were rated as more competent than those who didn't — and the effect was strongest when the task was difficult and the person asked was an expert. Asking your most experienced colleague a real question about a hard problem isn't damage to your image. It's about the best PR available in week three.

The mistake newcomers actually make is quieter. Sue Ashford's research on feedback-seeking — the closest thing this field has to a canon — maps how people weigh the image cost of asking against the value of knowing, and newcomers consistently resolve the trade-off the "safe" way: they stop asking and start watching. Monitoring instead of inquiry. Reading the room, decoding tone in Slack, guessing from what nobody said in the meeting. Watching isn't useless, but it returns ambient information — how the team works — not information about you. And it quietly burns through the exact weeks when asking directly was free.

Because the window does close. Somewhere around month three, "still figuring things out" flips to "should know this by now." Same question, same person, different read. The license isn't revoked in any meeting; it expires while you're busy trying to look like you don't need it.

What to ask, and when

The window has phases, and the right ask changes as your visibility grows.

Weeks 1–2: calibrate the terrain, not yourself. You haven't done anything visible yet, so questions about your performance can only produce politeness. Ask about the territory instead: "What does 'good' look like on this team — what earns someone respect here?" "What took you longest to figure out after you joined?" "What would you tell someone in their first week that isn't written down anywhere?" These aren't feedback yet. They're channel-building: every person who gives you a real answer to an easy question becomes someone who can later give you a real answer to a hard one.

Weeks 3–6: first behavior asks, anchored to moments. Once you've done things people actually saw — run a meeting, shipped a doc, made a call — ask about those, one moment at a time. "In Tuesday's planning I pushed back on the timeline. Too hard for how things work here?" You're not asking am I good; you're asking for a norms-read on one behavior. That's the thing you structurally cannot see from the inside: whether defaults you calibrated on your last team land the same way on this one.

One targeting note for the early weeks: the most underrated source is the second-newest person on the team. They still remember what was invisible at the start — which unwritten rules bit them, which impressions they accidentally mis-set — and they have the least invested in the team's self-image. Longer-tenured colleagues know more; the recently-new remember more of what you actually need to hear.

Months 2–3: pattern asks. By now people have data on you. Cash it in: "What's one thing I do that someone who's been here two years wouldn't do?" — the outsider-tells question, and the single highest-yield ask of the whole window. Or: "If I keep operating exactly the way I have been, what will be annoying people six months from now?" Beyond the answers themselves, questions like these establish that you're a person who can be told things — which, more than anything else, determines whether people keep telling you things after the newcomer window closes.

Three ways to waste the window

Asking "how am I doing?" It's the question every newcomer reaches for, and it's a politeness pump — so broad that the honest answer would be an essay, so you get a compliment instead. Every ask needs a moment and a behavior attached to it. (The phrasing mechanics — and how to receive the answer without flinching — are the same for newcomers as for everyone else: how to ask for honest feedback without it feeling weird.)

Asking only your boss. Your manager sees outcomes and trajectory — and is also the person most invested in your onboarding being a success story. Peers see the thing you actually need read: your behavior in rooms. Spread the asks across different colleagues and different contexts, because each person watches a surface of you the others never see.

Waiting until you know enough. The instinct is to hold your questions until you can ask smart ones. But that trades the free-asking window for a stack of observations about everything except yourself. Ask before you feel ready. Feeling ready is usually the sign the window is already closing.

When single questions stop being enough

One-at-a-time asks are the right tool for the first two months. Around day 60 to 90 they hit a ceiling: you've collected anecdotes, and what you need is a pattern — whether the transition itself is working, seen from the different seats watching it.

That's the moment to swap anecdotes for structure: the same calibrated questions to four or six people — new peers, your boss, longer-tenured colleagues — answered by you about yourself first, then read side by side. Mirorly's first 90 days in a new role template is built for exactly this checkpoint: how your arrival actually reads from the outside — decision pace, communication defaults, where the team is quietly compensating for you — while your license to ask is still warm.

And if your "new" is a promotion inside a team you already know, the problem is inverted — too much history instead of none, and channels that closed for a different reason. That case has its own playbook.

The one-line summary

Your first ninety days pair the emptiest feedback with the cheapest asking rights you'll ever hold — so ask early, anchor every question to a specific moment, spread the asks beyond your boss, and run one structured check on the whole transition before the license expires.