Bruce Tuckman described four stages every new team goes through: forming, storming, norming, performing. He published this in 1965. It still describes most teams accurately because most teams handle it the same way they did then.
Forming is polite. Storming is where it breaks down. Norming is when the team develops informal rules. Performing is when the work gets fast.
Most early-stage teams spend six months in storming. Some never leave.
Why it takes so long
The differences driving friction are invisible.
When two people disagree repeatedly about how much information they need before making a call, they don't experience it as a measurable gap in risk tolerance. They experience it as one person being reckless and the other being indecisive. When someone shuts down after direct feedback, the person who gave it doesn't know they triggered a social threat response. They see someone defensive.
These things show up clearly in psychometric data. They don't show up clearly through six months of observation.
Which gaps do the most damage
Some dimensions are weighted more heavily than others when the engine scores a pair, because a gap on them is more consequential; which they are, and by how much, is part of the scoring model and is not published.
Trust & Challenge is whether someone reads criticism as information offered in good faith or as an attack. Volatility Vector is risk appetite and tolerance for downside exposure. Influence Style is how directive someone is, which collides when both are or when neither is. Bonding Index is relational investment, where a gap leaves one person carrying the relationship. This weighting is a design decision grounded in the constructs, not a validated ranking against outcome data.
Two people far apart on any one of these will produce conflict in exactly that domain, repeatedly, until they have an explicit shared model of why. A high-drive, high-risk founder paired with a high-diligence, low-risk co-founder will hit execution paralysis on timeline decisions. This is predictable from their profiles. It keeps happening until they name it.
A shared map
Kalibr's team cohesion report gives both people that map before the friction starts. Both take the assessment. Pairwise compatibility runs across all 10 dimensions. The output is a Team Cohesion Score (0 to 100) and a working agreement: specific protocols for how this pair communicates, makes decisions, and handles the moments their profiles predict conflict.
The working agreement doesn't resolve the differences. It names them. That turns invisible friction into a problem both people can talk about. Whether that makes the storming phase shorter is not something Kalibr has measured, and it does not claim it.
This only works when both people take it and both read the same report. There is no version where one person runs a profile on somebody who did not participate, and Kalibr is not a hiring decision tool.
The point
The model is 60 years old. It still describes most teams accurately because most teams still rely on accumulated observation to understand each other. That takes months.
Teams that enter storming with an explicit shared model of their profiles don't skip the conflict. They skip the part where the conflict is mysterious.