The first 90 days with a team you didn't build
You inherited this team. You're responsible for it. But you don't understand it yet — and the clock is running.
The third one-on-one
I remember the exact moment I realized I was getting managed.
Third week leading a team I hadn't built. Back-to-back one-on-ones, asking open questions, taking notes. And the third person I spoke to that day told me, almost word for word, the same thing the first two had said. Different roles, different projects, same script: things are going well, some resource constraints, the previous manager had a different style but it was fine.
Three people. Same answer. That's not alignment. That's a performance.
They weren't lying. They were doing what every rational person does when someone new takes over: managing the relationship before revealing the reality. Which meant everything I'd "learned" in three weeks was, at best, a curated version of what was actually happening.
After a few transitions like that, I stopped trusting the standard playbook — the "listen first, don't change anything, build relationships" advice that sounds wise but tells you nothing about what to actually do. Here's what I wish someone had given me instead.
Your first round of one-on-ones tells you what people want you to believe. The structural picture is underneath — and it doesn't surface in conversation.
The silent priorities exercise (Week 1)
This is the single most useful thing I've done in a new role.
In your first all-hands or team meeting, don't present your vision. Don't give a speech. Instead, hand everyone a piece of paper — or a Slack DM, or an anonymous form — and ask one question: "What are the team's top three priorities right now? Write them down. Don't discuss."
Collect the answers. Read them privately.
If the team is structurally aligned, you'll see roughly the same three things from everyone. If they're not — and in my experience, they usually aren't — you'll see five, eight, twelve different answers. Some people will name projects. Others will name problems. A few won't know what to write.
This exercise does two things at once. First, it gives you a real picture of whether the team has shared direction — without relying on what anyone tells you in a one-on-one. Second, it shows the team you're paying attention to the right things. You didn't ask "how are you feeling?" You asked "are we pointed at the same target?" That signals structural thinking, and the team notices.
Hackman's research on team effectiveness consistently found that clarity of direction is the single most important enabling condition for team performance. This exercise tests for it directly, in ten minutes, with no politics involved.
If six people give you six different answers about what the team's priorities are, you've found your first structural problem — and you didn't need a single one-on-one to see it.
Map the workarounds (Weeks 2–3)
Every team has unofficial processes — the things people actually do to get work done, as opposed to what the org chart says they should do. In established teams, these workarounds become invisible. People stop noticing them. But as the new person, you can see them — and this window closes fast.
Here's the specific move: in your second and third week, every time someone explains how something gets done, listen for the phrase "what we actually do is..." or "the way it really works is..." or "I usually just go directly to..."
Write those down. Every single one.
Each workaround is a signal. It tells you where an official system or process has failed, and the team has routed around it. Maybe approvals go through a back channel because the formal chain takes two weeks. Maybe someone keeps a personal spreadsheet because the project management tool doesn't reflect reality. Maybe two people coordinate directly because the cross-team handoff is broken. A team's workarounds reveal its actual operating structure more accurately than any process document or org chart ever will.
New team? Get the structural picture before you start making changes.
The Destuck diagnostic maps twelve structural dimensions — giving you a baseline you can act on in your first week.
Take the diagnosticAsk the "magic authority" question (Weeks 2–4)
This one's simple and surprisingly powerful. In your one-on-ones — after the initial polite round — ask each person: "If you had my authority for one day and could change one thing about how this team works, what would you change?"
Not "what's wrong." Not "what would you improve." The framing matters. "If you had my authority" gives them permission to name structural issues they'd normally consider above their pay grade. And "one thing" forces prioritization — you won't get a laundry list.
Some people will name a process. Others will name a meeting they think is pointless. A few will name a dynamic between people. One or two will say "nothing" — which is also data.
The real value is in the patterns. When three out of seven people independently name the same thing, you've found a constraint the team has been living with — and you found it without guessing. Amy Edmondson's research on psychological safety suggests why the framing is critical: people share honest structural observations only when they feel it's safe and sanctioned. "If you had my authority" explicitly sanctions it.
The "magic authority" question surfaces what the team has been living with but never had permission to name. Three people naming the same thing is a structural finding, not an opinion.
Watch the meeting after the meeting (Weeks 3–4)
Pay attention to what happens in the five minutes after a team meeting ends. Who clusters together to talk? Who immediately messages someone? Who leaves looking frustrated? Who checks in with whom?
The meeting after the meeting is where the real reactions live. It tells you who actually trusts whom, which decisions are going to stick, and which ones the team is already working around.
You can't engineer this observation. You just have to notice it. But the patterns become clear quickly: if the same two people always debrief privately, there's a communication gap in the formal structure. If someone consistently checks with a peer before acting on a decision, the decision-making process doesn't have full buy-in. If people leave quickly and quietly, the meeting isn't generating alignment — it's generating compliance. This is the kind of structural signal that never appears in a one-on-one. No one will tell you "I don't actually trust the decisions we make as a team." But their behavior in those five minutes will.
The move that actually builds trust
All of this builds toward one moment — usually somewhere around week four or five — where you can do the thing that actually earns trust.
Name a structural condition the team has been living with. Not as blame. Not as a complaint. As an observation.
Something like: "I've noticed that most of our work slows down at the approval stage. That looks structural to me, not a people issue. I want to look at how we can change that."
When a new manager says that in the first month, the room shifts. Because the team has been routing around that bottleneck for months, maybe years. And someone just named it — clearly, without drama, and with the intent to fix the structure rather than blame a person. That's the moment the team starts to believe you might actually understand what's happening.
Trust doesn't come from listening. It comes from naming the structural condition the team has been living with — out loud, without blame, with intent to act.
The Destuck diagnostic maps twelve structural dimensions of how your team actually works. For managers inheriting a team, it gives you a structural baseline in the first week — before politics, impressions, and curated conversations start shaping what you think you know.
Take the diagnosticNot sure what to write? Grab a ready-to-use post.
