From Formal Authority to Organizational Legitimacy

There is a management story making the rounds. The company and the person can’t be independently verified, so treat it as a management scenario, not a replicable success case.

A VP who had spent his career at headquarters in France was sent to Asia to take over a mature team. He didn’t know the local market, didn’t speak Chinese, and had never managed these people. Everyone knew headquarters had sent him.

The usual script: the new leader arrives, listens to a round of briefings, finds problems, replaces people, resets strategy, then announces “we’re going to make some changes.”

This VP didn’t start that way.

For the first stretch he kept talking to managers and frontline employees — asking not “do you support my strategy,” but:

What are you most proud of about this team?
Which process wastes the most time?
If you had a small budget, what would you fix first?
What problem has been raised many times and never actually solved?

Months later he shared a five-page deck: what he’d heard, what this team should be proud of, what was grinding people down, what he planned to fix in the next 90 days, and what he needed from the team.

The message: he wouldn’t clone French headquarters here; the local market would teach him, and he would own the problems outside the organization.

The comments immediately asked: which company really gives a VP three months to do nothing?

That question pulls the story back to reality. An appointed leader obviously can’t spend three months interviewing. When key customers are churning, cash flow is at risk, or compliance problems are growing, “let me understand first” can’t become delay.

And the point worth discussing isn’t “don’t move for the first three months.”

The story illustrates the migration every appointment requires: from the formal authority the company grants with the title, to the organizational legitimacy a team grants through working together.

The appointment only solves the first kind of legitimacy

Formal authority exists on day one. The org chart carries your name, the budget is yours, people report to you. You can change goals, reallocate resources, make evaluations, and if necessary reorganize and replace people.

There is another legitimacy the company can’t grant at the same time.

Whether the team believes you understand the real problems and can separate symptoms from root causes; whether your judgments have a basis and your commitments get honored; whether following your decisions makes things clearer and the organization more capable.

I call this organizational legitimacy. It’s a management-practice frame for this article, not a replacement for an existing academic concept.

Formal authority lets you demand that the team act. Organizational legitimacy makes the team willing to hand you bad news, real disagreement and unfinished judgments.

The second isn’t “make everyone like you.” A leader with organizational legitimacy still kills projects, makes trade-offs, restructures and changes people. The difference: the team understands the basis, believes in the process, and has seen commitments honored.

A meta-analysis of trust in leadership covering 106 independent samples found that trust in one’s direct leader relates to a range of work attitudes and behaviors — and that the direct leader is a particularly important target of trust. Dirks & Ferrin: Trust in Leadership

Trust is not atmosphere. It affects whether people still share information, take on commitments and stay.

Why the first 90 days go wrong

A new leader faces three pressures at once. The boss wants results; the team wants rules; and the leader wants to prove why the company needed them.

The easiest response is to prove value with change: redraw the org chart, replace managers, change processes, launch a new strategy, even deliberately negate what the predecessor left.

The actions are fast. The context is minimal.

You see the formal org chart, not the real collaboration network; you see outcome metrics, not which decision months ago produced them; you hear that someone “can’t execute,” without knowing whether it’s capability, goals, resources or interfaces; you see a convoluted process, without knowing whether it exists to prevent a past accident.

The team also interprets a new leader’s behavior through status. Sauer’s two experiments with newly appointed team leaders found that identical participative or directive behavior was evaluated differently under different status conditions, and affected team performance. Sauer: Taking the Reins

The experiments don’t hand real companies a universal prescription. They remind us: what the newcomer does is one layer; how the team explains “why does this person get to do that” is another.

The more urgently you prove yourself, the easier it is to substitute positional power for factual understanding.

Run two tracks at once: stabilize and diagnose

More practical than “observe for three months” is Stabilize + Diagnose: stop the bleeding while you build understanding.

Risks that are expanding and have clear costs get handled immediately — safety, compliance, cash flow and major customer problems don’t wait for a full study. For hard-to-reverse decisions, raise the evidence bar.

Two questions set the pace:

If this keeps running unchecked, does the loss grow fast?
After deciding now, can we still reverse it cheaply?

Low-risk, reversible actions can happen early. High-risk, irreversible restructuring, replacements and strategic pivots need more evidence.

A better 90-day plan looks like three stage gates.

Stage	Main task	Must leave behind	Condition to advance
Days 0–30: Understand	Stop the bleeding; see product, users, business, technology, delivery and organizational relationships	Problem map, conflict explanations, urgent-risk list	The team can form basic consensus on key problems and unknowns
Days 31–60: Co-evidence	Pick one important but controllable early battle	Shared evidence, decision log, reusable interfaces	The team has seen the new way of working improve outcomes
Days 61–90: Change	Institutionalize goals, decisions, reviews and commitments; handle necessary structure and people issues	New interfaces, clear roles, change rationale, review time	Change no longer depends on the new leader personally firefighting

The days are reference points, not law. A business crisis can compress the stages; a complex organization can need longer. Order matters more than days: understand first, co-evidence second, then change.

Draw six maps first

The most valuable output of the first 30 days is usually a problem map the team can correct — not a rushed new strategy.

Look at the organization from six sides.

Product. What role does each line play — exploring, delivering, or merely surviving on sunk costs?

Users. Who chooses, who uses, who pays; where is the real churn and usage evidence; which voices are only internal retellings.

Business. What drives revenue, cost, channel, renewal, service and cash flow; is growth mixed with subsidies, customization or one-off deals.

Technology. Do bottlenecks come from foundational capability, system coupling, quality debt, or planning and coordination.

Delivery. How goals become requirements, baselines and commitments; who decides changes; how risk escalates.

Organizational relationships. Beyond the formal chart, where do information and trust actually flow; who has low title but moves cross-team problems; who bears outcomes without decision rights.

Each map should mark: facts already known, conflicting explanations, missing evidence, and how to validate next.

The newcomer’s classic mistake is dismantling infrastructure that was never drawn on the org chart.

Choose one small, important battle

Understanding alone doesn’t produce organizational legitimacy. The team still has to see things get better.

Days 31–60 need an early battle. Not so small that it’s fixing the meeting-room projector, and not a bet on the company’s hardest strategic problem. The right target usually has four features: everyone knows it matters; it has been bothering the team for a while; its boundaries are controllable; it needs cross-team cooperation and can show evidence within weeks.

A key release that keeps slipping. A customer problem chain nobody owns. A review interface that makes multiple teams rework endlessly.

An early battle has two outcomes.

One is solving the problem. The other is the team collectively experiencing a reusable way of working: bad news surfaces early, disagreements are recorded, commitments have owners, decisions get review time.

If the win comes entirely from the new leader personally firefighting, it proves individual capability. Only when the working method survives — the team does better without you later — does it convert into organizational legitimacy.

Teams need to trust your judgment, not agree with every conclusion

What a leader most needs to build is judgment trust, not “everyone likes me.”

The team won’t agree with every trade-off, but it should know how conclusions formed. Important decisions deserve five things written down: what the basis is, what isn’t known yet, what was traded for what, when it will be reviewed, and the formal path by which dissenters can bring evidence.

This doesn’t slow every decision down. Reversible small moves can be tried fast. Cross-team, high-risk, hard-to-reverse decisions get the fuller record.

Organizational-justice research distinguishes outcome, procedure, interpersonal treatment and information explanation. Colquitt’s scale study supported the four dimensions; the procedural dimension includes consistency, accurate basis, opportunity for correction and representativeness. Colquitt: On the Dimensionality of Organizational Justice

Teams don’t have to like the outcome. They judge whether the process used reasonably consistent standards, allowed meaningful input, and explained reasons.

A decision log isn’t administrative burden. It’s the public record of a leader’s judgment quality.

Fix the interfaces before you redraw the org chart

A lot of “the people are the problem” is actually unclear interfaces.

Product, engineering, sales and delivery each optimize local goals while nobody owns the complete result. Requirements change daily with no formal baseline. A project manager is told to chase the schedule but has no power to escalate risk. Three leaders can all voice opinions and no one makes the final call.

Replace people and the interfaces stay; the problems come back.

So in days 61–90, check four kinds of interfaces first:

Do goals point at one result, not locally optimized metrics;
Who proposes a decision, who advises, who is finally accountable;
Do reviews expose risk, or perform progress;
Do cross-team commitments have explicit content, timing, quality and change rules.

Once interfaces are clear, structural problems become recognizable: genuinely duplicated roles, key capabilities with no owner, unreasonable spans of control, or a role no longer fit for the next stage.

Then restructuring has a purpose — instead of a new chart proving a new leader arrived.

Some structure and people problems can’t wait

“Understanding first” can also become another form of avoidance.

Clear safety, compliance and integrity issues get handled immediately. A key role that chronically fails its basic duties, a leader who persistently destroys collaboration, or a role whose requirements have fundamentally changed — none of these wait indefinitely for politeness.

The line to hold: don’t mistake your unfamiliarity for their incompetence.

Before any people decision, separate four things: is the role’s goal clear, is resourcing sufficient, are interfaces reasonable, and does the person have capability and willingness. Evidence and procedural fairness don’t block timely decisions; they stop systemic problems from landing on one person.

Delaying an obvious mismatch makes the team compensate for it indefinitely. Replacing people fast without evidence teaches everyone to hide problems.

Three outcomes: right, late, wrong

Three scenarios merged from common management situations; they don’t correspond to specific companies, people or times.

Right. A new leader finds product-engineering reviews chronically inefficient, doesn’t reorganize immediately, first unifies decision standards and cuts redundant reviews, and validates with one key release. Only after delivery smooths out do they adjust roles — by which point the team has seen the shared evidence behind the change.

Late. To observe long enough, the manager leaves a core leader who has lost the team’s trust for months. When the replacement finally comes, the decision itself is defensible — but what the team learned is: the problem was always there; the leader just wouldn’t take responsibility.

Wrong. After arriving, the manager sees projects slipping and replaces the lead immediately. Months later the root cause surfaces: sales commitments, product scope and engineering resources had been mismatched for a long time. The person changed; the interfaces didn’t; the projects kept slipping.

The difference between the three isn’t just the decision. It’s whether the timing and the evidence matched the judgment.

Organizational legitimacy leaves behavioral signals

It isn’t a satisfaction survey, and it isn’t everyone nodding in the meeting.

The more reliable signals:

Bad news arrives earlier, not only when it can’t be hidden;
Objections move from after-meeting complaints to in-meeting challenges with evidence;
Cross-team commitments are clearer; changes stop relying on private coordination;
Fewer things need to escalate to the top leader;
Middle managers start making judgment calls instead of waiting for instructions;
When the leader is absent, the team still uses the same decision logic;
Necessary people decisions happen on time and fairly.

Edmondson’s study of 51 work teams found psychological safety associated with team learning behavior. Edmondson: Psychological Safety and Learning Behavior in Work Teams

A team willing to say “I don’t know,” admit errors and raise counterexamples isn’t a sign of management chaos. It usually means members believe that bringing real problems to the table won’t be punished.

One of the strongest signals: the team starts letting you see reality.

Back to the opening story.

What’s worth borrowing from that VP isn’t “three months of doing nothing,” or a five-page deck.

It’s that he didn’t mistake a headquarters appointment for the team’s endorsement. He handled what had to be handled, had the team co-explain reality, and used checkable decisions to turn a title into a work record.

So for the first 90 days of an appointment, remember three words:

Understand. Co-evidence. Change.

When you finally move something important — a structure, a project, a person — the team shouldn’t just see “the new boss is changing things.”

They should know: why now, what the evidence is, what it costs, and how we return if the judgment was wrong.

That’s when formal authority starts to become organizational legitimacy.