The first ninety days are an information problem

A coach gets hired into a leadership team for a three-month engagement. By week six they’re starting to feel they actually know the team. Two weeks later the engagement is two-thirds gone. The most useful work happens in the last few weeks, when there’s barely any time left.

A new VP joins a company. They have ninety days, give or take, before people start drawing conclusions about whether the hire was right. They spend the first thirty figuring out who actually makes decisions versus who has the title. By day sixty they’re starting to see the real dynamics between their direct reports. By day ninety they finally understand what they walked into. By then, the impressions of them are mostly formed.

This is the timing problem at the center of team work. Most of the tools that claim to help with it don’t actually compress the timeline. They just add information to a discovery process that still takes months.

What you actually have to figure out

When people say “understand a team,” they usually mean the surface layer. Who’s smart, who’s reliable, who’s a culture fit. That part is fast. A week of meetings, maybe two, and the broad shape is clear.

The part that takes months is everything below that:

Who actually drives decisions

The CTO might be the person other engineers call when the spec is unclear, even if the VP of Engineering runs the meeting.

Which pairs have hidden tension

Two people who never argue in front of you may have stopped expecting anything productive from each other a year ago. The silence reads like alignment. It isn’t.

Which pairs have unusual trust

The person from product and the person from sales who shouldn’t get along often do, because of something specific between them you can’t see from the outside. That trust is doing structural work for the team. If you don’t know it’s there, you’ll accidentally damage it.

How conflict actually happens, or doesn’t

Some teams disagree out loud and resolve it. Some teams disagree privately and never resolve it. Some teams have someone whose job has quietly become “absorb the disagreement so nothing has to be resolved.” Until you know which pattern you’re in, your interventions are mostly guessing.

Who needs what kind of feedback to receive it

The same sentence delivered the same way will land for one person and bounce off another. This is rarely about defensiveness. It’s about how each person processes input, and the team has probably never made it explicit.

Who steps forward when stakes rise, and who steps back

Crisis behavior is different from normal behavior, and you can’t see it until a crisis happens. Sometimes the person you’d bet on disappears. Sometimes the quiet one carries the room.

None of that is on the org chart. Most of it isn’t in the assessments people have on file. All of it has to be figured out, mostly by watching, mostly slowly.

Why it takes months

The information you need to read a team is mostly relational, not individual. Relational information doesn’t accumulate from observation the way individual information does.

You can read a person in a single one-hour conversation if you’re good at it. The signal is dense. They’re sitting in front of you. You can read a relationship by watching one meeting only if the relationship happens to do something legible in that meeting, which most relationships don’t most of the time. Most pairs in a team mostly don’t interact in front of you. You’re inferring the relationship from fragments: the way Sarah glanced at Marcus when Priya brought up the budget, the email thread you got cc’d on at 11pm, the side conversation that happened in the hallway before the meeting started. Each fragment is low-signal. You need a lot of them to triangulate.

That’s the structural reason it takes months, and why every coach and every new leader feels behind for the first chunk of the engagement no matter how experienced they are. The gap isn’t a skill problem. It’s an information problem.

Why the tools haven’t fixed it

Plenty of tools have promised to compress the timeline. Most of them haven’t.

Tool	What it gives you	What it misses
Individual personality assessments	Per-person descriptions, fast	Relationship information
Type-based tools (DISC, Myers-Briggs)	A memorable shorthand	The specific dynamics; produces confident wrong predictions
360 surveys	Structured perception data	The layer underneath; weeks to administer
Direct observation	High-quality behavioral signal	Speed; meetings are partly performative
Interviews	The real version of the story	Trust to be useful; trust takes weeks

The trouble with type-based tools is more than imprecision. They produce confident-sounding predictions that interfere with observation. “John is a High D, so expect direct and confrontational” is useful right up until John, in this specific team with these specific people, actually defers to Marcus and locks horns with Priya. The type told you a generic story; the team has a specific one; the generic story sits in your head and quietly competes with what you’re actually seeing.

Reading seven individual reports gives you seven individual descriptions, not twenty-one relationship descriptions. The synthesis from one to the other is the slow part of the work, and none of these tools help with it.

What it costs

The cost of the timeline gap is mostly invisible, because nobody does the counterfactual. It’s still real.

The coach who needs eight weeks to understand the team has eight weeks of partial-information work in the can before the real coaching can start. Some of that work is fine. Some of it is in directions that look reasonable on incomplete information and turn out to be off-target once the full picture is clear. Engagements get extended for this reason more often than anyone admits.

The new leader pays the cost more directly. Decisions made in the first sixty days carry weight. Decisions made on incomplete reads of the team are worse decisions. The leader who promotes the wrong person, or restructures around the wrong center of gravity, or reassigns work to the wrong pair, often does so because they didn’t yet know what they were looking at. By the time they would know, the decision is in the rear view.

Once a team has decided you don’t see them clearly, getting that perception back is its own project.

What would actually compress the timeline

A useful tool here would do something specific. Give the coach or leader a working map of the relationships on day one, not a stack of individual descriptions. Not a final answer. A starting hypothesis, structured by pair, accurate enough that observation refines it instead of building it from scratch.

Three things have to be true for that to work.

If those three things are true, the timeline shortens from months to days. Not because the tool is smarter than the coach. Because the coach is no longer building the map from raw observation. They’re starting with a structured hypothesis and using their judgment on what matters and what to do.

This is what we’ve built Kyuria to do. Per-pair guides, asymmetric, grounded in personality data the team can produce in twenty minutes per person. The coach still does the coaching. The leader still does the leading. They just stop spending the first half of the engagement figuring out what they walked into.

The information problem doesn’t go away. The timeline does.