How to handle old loyalists when you return as CEO

Map the work dependencies beneath competing loyalties and apply the same evidence standard to everyone. Protect useful historical knowledge while closing private routes around current accountability.

Loyalist faction management is the use of common contribution and decision standards across groups attached to different leadership eras. This article uses the term as an applied working label. Its research reference is Weiner’s 2009 theory of organizational readiness, especially shared commitment to a change and belief in the capacity to implement it. The proposed method below is advisory guidance rather than a tested psychological scale.

Recognize the decision behind the pressure

Composite recognition scene: At a weekend gathering, an old colleague tells you who stayed loyal during your absence. You realize that you are hearing a history of allegiance before seeing the current performance record. This is an invented illustration of a leadership pattern, not a client story or evidence about a particular person. Use the scene to identify the work choice that needs attention, without drawing conclusions about anyone’s psychological condition.

Choose a disputed proposal or handoff where allegiance appears to be replacing work evidence. Map who needs information and who controls the relevant decision. The review should expose a practical dependency or unequal standard, without turning social relationships into an informal list of people who deserve reward or punishment.

Tenure can supply knowledge of earlier decisions and commitments. Current contribution concerns the work a person performs now. Disagreement with the founder does not prove disloyalty, and agreement does not establish competence. Evaluate the proposal and its evidence separately from the history of the people presenting it.

What the research supports

Weiner (2009) distinguishes shared change commitment from shared implementation efficacy. Ask whether groups can carry the same recovery work, rather than requesting declarations of support for the returning founder. A common slogan does not establish readiness. The theory does not validate faction labels or show that long-serving employees are either more resistant or more dependable than newer colleagues.

Edmondson (1999) examines team psychological safety concerning interpersonal risk taking. An advisory application is to make it possible to challenge a proposal without treating the challenge as a personal rejection of the CEO. Keep the route specific to work questions. The construct does not require everyone to agree, erase accountability, or settle allegations of misconduct without the proper process.

Emerson (1962) analyzes power through dependence and alternatives. Map actual information and resource relationships before interpreting a group as a faction. Someone who holds necessary knowledge may be important to delivery even when their proposal is weak. Conversely, a close relationship with the founder does not establish the ability or authority to perform the proposed work.

Industrial/organizational psychology is the psychology of work and organizations. It supplies lenses for examining cooperation and decision conduct. The common-evidence review below is an operating method, not a psychological classification of employees. Use it to make proposal scrutiny and handoffs fairer in practice while preserving separate qualified channels for protected concerns or alleged misconduct.

The common-evidence faction review

Use the common-evidence faction review on comparable decisions. Publish the work criteria before hearing competing proposals, and identify the evidence required from each sponsor. Ask someone outside the historical relationships to check whether your access and exception practices give one group an unearned advantage.

1. Map the groups around actual work

Identify who shares information, controls resources, and depends on each handoff.

Map the work relationships relevant to the disagreement. Identify who supplies information, who performs the next task, and which handoff is blocked. Avoid starting from a list of people described as yours or theirs. A useful map shows what must happen for delivery, including cooperation across historical groups that an allegiance label might obscure.

2. Separate history from current contribution

Ask each executive for the same recent examples and operating evidence.

Request recent examples of contribution against the same role expectations. Retain historical knowledge where it explains a current commitment or constraint. Separate that knowledge from a claim that past loyalty entitles someone to win the present decision. Give newer colleagues the same opportunity to explain their work, including evidence that does not fit your preferred account of the company’s history.

3. Set one decision standard

Explain the criteria before evaluating proposals from either the old or the newer leadership group.

State the decision criteria before evaluating either group’s proposal. Ask which customer requirement, resource limit, or implementation responsibility the choice must satisfy. Apply the same questions when a familiar colleague presents a favored option. If a criterion changes because new information arrives, explain the reason and reconsider comparable proposals rather than changing the standard privately for one sponsor.

4. Assign shared work with explicit ownership

Resolve dependencies without requiring declarations of personal loyalty.

Assign shared work through clear owners and handoffs. Explain which person decides and which people provide necessary input. Do not require a public display of personal loyalty as the price of participation. Where a relationship conflict blocks delivery, name the operating dependency and use the proper management route to resolve it instead of expecting staff to repair the history themselves.

5. Review exceptions and exclusions

Check whether your access practices recreate the advantage you asked the team to remove.

Review who received access, exceptions, or early information during the decision. Include your own private conversations. Correct an unequal route where it affected the work, and explain the current standard to the responsible team. If the evidence raises a separate conduct allegation, refer it appropriately rather than treating a faction review as an informal disciplinary process.

Put the conversation into usable words

Use this proposed framing with the relevant work owners. Keep the discussion on current evidence and decisions, and preserve proper routes for sensitive allegations outside the general review.

We are choosing [specific option] against [announced criteria]. Each proposal needs [same evidence]. Historical knowledge is useful where it explains a current constraint, but access to me does not approve an exception. [Role] owns the decision and [roles] own the handoff. Tell me where the criteria or information route has been applied differently so we can check the work.

Ask each proposal sponsor to show the same evidence before discussing tenure or relationships. If a story about loyalty dominates the comparison, return to the role requirement it is supposed to demonstrate.

If someone believes the process favors another group, request a concrete example of different treatment or evidence standards. Check it without requiring them to prove a hidden motive. Correct the operating inconsistency and preserve the account of the change. Do not respond by demanding reassurance that they support your return or by excluding them from the next work discussion.

Check the method against a live example

In a hypothetical continuation of the weekend conversation, an old colleague recommends rejecting a newer executive’s plan because the executive was not present during an earlier crisis. Ask what current requirement the history changes. If it reveals a genuine commitment, add that evidence to the review. If it supplies no relevant constraint, evaluate the proposal on the announced criteria and keep personal allegiance outside the rationale.

Suppose two groups each hold information needed for a customer handoff. Assign an accountable owner and define the required exchange. Avoid asking the groups to reconcile every historical disagreement before essential work can proceed. Inspect whether the handoff occurs through the agreed route and address specific failures without assuming that a difficult relationship proves deliberate obstruction.

Imagine you privately approve a request for a longtime colleague after declining a comparable proposal in the formal meeting. Bring the inconsistency back through the decision owner and correct it. Explain any legitimate new evidence. Otherwise, the review would ask employees to follow a standard that your own conduct had made unreliable, regardless of how clearly the public message was written.

What to record and what to leave out

Document the proposal criteria, submitted evidence, work dependencies, and authorized decision. Note any material change in the standard and its reason. Preserve the operating consequence of an access exception without building a loyalty register. Give the decision record an owner who can correct a factual error raised by either group.

Exclude social affiliations, private friendships, and speculative intentions unless a legitimate, properly reviewed issue requires relevant facts. Handle misconduct allegations through their authorized process. The general work map should identify necessary cooperation and responsibilities, not circulate reputational labels that employees cannot meaningfully inspect or correct.

Use this completion check before closing the discussion:

What work dependency lies beneath the dispute?
Did comparable proposals face the same evidence requirement?
Which historical fact changes a current obligation?
Who owns the cross-group handoff?
Have your own exceptions recreated unequal access to approval?

Use these checks to inspect decisions and handoffs. They do not diagnose factions or authorize an employment consequence based on perceived loyalty.

Judge progress by follow-through

Compare equivalent proposals and completed handoffs at the next review. Check the evidence and access each sponsor received, including whether exceptions were explained through the same authorized route.

Ask whether current work can proceed without employees invoking a historical group to obtain a different answer. Preserve useful institutional knowledge while revisiting unsupported labels. If the standard still varies by relationship, correct the process and your own contribution before adding more team messaging. Progress means comparable scrutiny and workable cooperation, without claiming that a single review has resolved every longstanding conflict.

Investigate alleged misconduct through appropriate channels. A faction map must not become an informal list of people to punish.

For related preparation, use Returning as CEO: how to lead a company turnaround, How to reset promises made by the previous leadership, How to choose leaders who can carry a company turnaround, What to do when your executive team splits into factions. Choose the guide that addresses the next concrete decision, and keep responsibility with the person authorized to make it.