Lead without authority through a credible coalition
Build support among the people whose knowledge, resources, and judgment are needed to make a cross-functional change work.
Leadership without authority requires a coalition capable of doing the work. Broad agreement with a proposal is encouraging, but implementation depends on specific people contributing knowledge, time, decisions, and support. A leader needs to understand whose participation is essential and what would make their commitment credible.
My EA leadership work treats influence as a practical enterprise skill. Architecture and cross-functional change often involve people who answer to different sponsors and performance expectations. The task is to build a shared case for action while recognising those obligations. Ignoring them can turn a reasonable enterprise proposal into an unworkable local commitment.
Start with the people who experience the problem
I would begin with a recurring issue that several teams can recognise. A planning handoff, for example, may generate repeated corrections for one group and unreliable commitments for another. Understanding both experiences helps frame a problem that participants can own together. It also gives the leader a way to test whether the proposed change addresses the actual difficulty.
The first conversations should include people close to the work and leaders who control the resources required to change it. A coalition made entirely of senior sponsors may lack operating detail. A group of committed practitioners may understand the problem but lack the authority to protect time or resolve a conflict. The change needs both forms of contribution.
Ask each participant what they need to protect: a customer commitment, a control, a production target, or an already stretched team. These concerns become design requirements to examine. Some can be accommodated, some require a trade-off, and some reveal that the proposal is incomplete. Taking them seriously strengthens the case for change.
Turn support into a specific contribution
A useful coalition has a defined piece of work. I would agree a small pilot with a clear outcome, limited scope, named contributors, and a decision date. Each participant should understand what they are committing and what evidence the group expects to produce. This is more dependable than asking everyone to support a broad transformation in principle.
The leader should also make the distribution of effort visible. One team may carry most of the implementation work while another receives the benefit. That imbalance needs to be acknowledged and addressed through sponsorship, sequencing, or resources. A shared objective does not automatically create a fair or feasible division of work.
Early evidence should be discussed honestly. If the pilot creates a new burden, the coalition needs to examine it. Concealing the cost to protect the proposal weakens trust and makes later expansion harder. Credibility grows when participants see that the leader will revise an approach in response to the work.
Keep ownership with the people who must sustain it
The coalition should help the organisation develop a routine that outlasts the initial leader’s attention. Process owners need to accept their responsibilities, managers need to protect the agreed commitments, and unresolved conflicts need an escalation path. Relationships help establish those arrangements; formal decisions help maintain them.
Share credit with the people who contributed and make the reasoning available to teams outside the pilot. That allows others to judge whether the approach fits their conditions. Expansion should follow demonstrated usefulness and a realistic capacity plan, rather than the persuasive force of the original presentation.
Influence becomes leadership when people can commit to useful work together. A credible coalition gives that commitment a practical form and creates the conditions for progress across the boundaries of the organisation chart.
Developed from my EA 878 paper on influence without authority; MGMT 831 Strategy Implementation and Organizational Change project. These recommendations extend the coursework; examples are illustrative and do not report an employer assessment or measured results.