I stopped telling people what to do a long time ago. Not because I mellowed. Because it stopped working. Almost every executive I coach now runs a flat, matrixed structure where the people they most need to move do not report to them. Persuasion in a flat organisation is not a soft skill you layer on top of good management. It is the whole mechanism. Take it away and nothing moves, no matter how good your title sounds on the org chart.
This used to be optional. A senior leader with a clean reporting line could get compliance from position alone. Tell a direct report what to do, and mostly, they did it. That world is largely gone for anyone running a cross-functional team, a matrix organisation, or a flat structure built around squads and guilds rather than departments. You are surrounded by people whose cooperation you need and whose paycheque you do not sign.
Why Persuasion in a Flat Organisation Replaced the Chain of Command
In 1998, Jay Conger wrote an essay for Harvard Business Review called "The Necessary Art of Persuasion" that named exactly what I now watch play out inside client organisations every week, almost thirty years later. He wrote: "Gone are the command-and-control days of executives managing by decree. Today businesses are run largely by cross-functional teams of peers and populated by baby boomers and their Generation X offspring, who show little tolerance for unquestioned authority. Electronic communication and globalization have further eroded the traditional hierarchy."
Read that again and notice what he is not saying. He is not saying persuasion is a nice-to-have communication skill for people who want to be liked. He is describing a structural change: fewer reporting lines that actually carry weight, more peers who expect a reason rather than an instruction, and technology that lets anyone route around a manager who cannot explain themselves. Conger wrote this before Slack existed. He was describing the shape of the flat organisation before most companies had built one on purpose.
Nearly three decades on, the structure he described is not the exception, it is the default. A product leader needs engineering, design, data and marketing to move in the same direction, and owns none of them. A regional MD needs a shared services function based somewhere else entirely to prioritise her market. A programme lead sits inside a cross-functional team where every member has a different manager, and none of them is her. Command authority does not reach any of these rooms. Persuasion does the entire job that a job title used to do for free.
The Problem With Leading People Who Don't Report to You
This is genuinely hard, and not simply because it feels uncomfortable. In a hierarchy, you get one shot at persuasion and then you have positional authority as a backstop. You explain the decision, and if it does not land, you can still make the call. In a flat or matrixed structure, there is no backstop. If the head of finance is not convinced, the numbers do not move. If the platform team is not convinced, the sprint does not change. Every single result you need runs through someone else's genuine agreement, not their compliance.
Most leaders respond to this by getting louder, or by getting political, building coalitions in the corridor before the meeting so the meeting itself is a formality. Both work occasionally. Neither scales, and neither builds anything durable. What Conger offers instead is a method, not a mood. It treats persuasion as a discipline with a sequence, the same way you would treat a financial model or a release process. Skip a step and the whole thing tends to collapse at the point you skipped it, not at the end.
It is worth being precise about what this article is and is not, because the site already carries a different framework under a similar heading. Robert Cialdini's six principles, reciprocity, commitment, social proof, authority, liking and scarcity, explain why people generally say yes to a request (I have written about that framework in The Leadership Influence Multiplier, and it is worth reading if you want that lens). Cialdini's work is general. It applies whether you are buying a car or running a board. Conger's work is narrower and, for a flat organisation specifically, more useful: it is a sequence for the exact situation where you have no formal authority over the person you need to move, and you need them to act on their own conviction rather than your instruction.
Conger's Four-Step Framework for Persuasion Without Authority
Conger's own summary of the method is worth quoting in full, because the order matters as much as the content: "Effective persuasion involves four distinct and essential steps. First, effective persuaders establish credibility. Second, they frame their goals in a way that identifies common ground with those they intend to persuade. Third, they reinforce their positions using vivid language and compelling evidence. And fourth, they connect emotionally with their audience."
I use this sequence with clients as a diagnostic before I use it as a script. When a persuasion attempt fails inside a flat structure, it has almost always failed at one specific step, and going back to fix that step does more good than reworking the whole pitch from scratch.
- Establish credibility: Earn the right to be heard before you ask anyone to agree with you. In a flat structure this is built through expertise and relationships, not rank.
- Frame for common ground: State the goal in terms of what your audience already values, not what you need from them. A shared destination, not a favour.
- Reinforce with evidence: Back the position with vivid, concrete language and real evidence, not abstractions. People remember pictures, not policies.
- Connect emotionally: Match the emotional register of your own conviction to the ask. A flat pitch for an urgent change reads as insincere, and peers notice.
Each of those four lines is doing more work than it looks like on the page. What each one actually demands of a leader who has no title to lean on is worth spelling out in full.
- Establish credibility: Conger found credibility comes from two sources: expertise (you clearly know the subject) and relationships (people trust your judgement and your motives because they have seen it before). In a flat organisation, you cannot borrow either from a title. You build expertise by being specific rather than general, citing the actual number, the actual customer, the actual failure mode, instead of speaking in the confident generalities that titles usually get away with. You build relational credibility slowly, before you need it, by being someone whose word matched their result the last three times. If this is the first conversation you have ever had with a peer, you are not persuading them yet. You are auditioning.
- Frame for common ground: A framed goal starts from what the other person already cares about, not from what you need. Most failed persuasion attempts in a flat organisation start with the pitcher's own priority list. Reframe it around the audience's actual incentive and the same ask lands differently. If you need the platform team to prioritise your feature, do not open with your own plans. Open with the reliability problem it also happens to fix for them. Common ground is not spin. It has to be genuinely true, or the next two steps expose the gap immediately.
- Reinforce with evidence: Conger's phrase is vivid language and compelling evidence, and the vivid part is not decoration. A concrete story, a specific customer quote, a real number that someone can picture, moves a room further than a well-structured slide of aggregated statistics. Peers in a flat structure are evaluating your judgement in real time, because they have no other authority signal to fall back on. Evidence that is vague, or that only exists as a summary you cannot show your working for, reads as a weak case even when the underlying logic is sound.
- Connect emotionally: This is the step leaders skip most often, usually because it feels unprofessional in a business setting. Conger's own research found the opposite: the most effective persuaders calibrated their own emotional expression to match the feeling behind the argument, rather than presenting everything in the same flat, neutral register regardless of stakes. A genuinely urgent change pitched with no urgency in the room reads as something the pitcher does not actually believe. In a flat organisation, that mismatch is fatal, because your peers have no obligation to act on a case you do not sound convinced by yourself.
What This Looks Like Inside a Real Matrixed Team
Take a common scenario. A product leader needs a shared data platform team, run out of a different part of the business, to reprioritise a piece of infrastructure work ahead of their own backlog. There is no shared manager in the room. Command authority simply does not exist here. This is where the four steps stop being theory.
Credibility gets built weeks before the ask, through a track record of asking for the right things and being straight about trade-offs. Common ground gets named early: the platform team's own reliability metric improves if this work happens now, not later, so the ask is not a favour, it is a shared interest with a different owner. Evidence shows up as the actual incident report from the last outage, not a paraphrase of it. And the emotional register matches the stakes: if this is genuinely urgent, it gets said like it is urgent, plainly and without theatre. Teams that build this kind of shared operating rhythm across functions get to skip half of this negotiation every time, because trust carries over from the last round.
Each of the four steps is manageable on its own. The difficulty is doing all four, in order, under time pressure, with someone you cannot instruct. That is precisely the skill set that a cross-functional leader has to build deliberately, because nothing in a traditional management path teaches it. Command authority is easy to lean on and slow to unlearn.
The Mistake Flat-Organisation Leaders Make With Evidence
Step three is where I see the most avoidable failures. Leaders who have genuinely earned credibility and correctly framed the common ground still lose the room at this stage, because they reach for the wrong kind of proof. A dashboard full of aggregate metrics is accurate and unpersuasive. It proves the trend exists. It does not make anyone feel the trend, and feeling it is what moves a peer who is under no obligation to act on your numbers.
Compelling evidence, in Conger's sense, is concrete enough that someone can picture it without you in the room. One real customer story does more work than a chart showing the aggregate. One specific incident, named and dated, does more work than a quarter of trend lines. This is not a preference for anecdote over data. It is a recognition that a peer with no formal reason to trust your interpretation of the data needs something they can independently verify or picture for themselves, and vivid, specific evidence is what lets them do that.
Why the Emotional Step Gets Skipped, and Why It Shouldn't
Step four gets treated as optional far more than the other three, because most executive training actively discourages showing emotional register in a business case. Strip it out, the training says, and let the logic carry the argument. In a hierarchy, that can work, because the audience will act regardless of how you feel about it. In a flat organisation, the audience is choosing whether to act at all, and a flat delivery of an urgent case reads as a signal that the case is not actually urgent.
This does not mean performing enthusiasm. Peers can tell the difference between calibrated conviction and a sales pitch, and the second one damages the credibility you built in step one. What it means is matching your own visible investment to the true stakes of the ask, and being willing to say plainly that something matters to you, rather than hiding behind neutral corporate language that leaves your audience guessing how much you actually believe your own case.
- The pitch reads identically whether the stakes are trivial or critical, so nobody can tell which this one is.
- Every sentence is hedged, so the actual position never gets stated plainly enough to react to.
- The leader avoids naming what happens if the ask is refused, leaving the real cost invisible.
- Questions get answered with more data instead of a direct, human explanation of why this matters now.
Building This Into How You Operate, Not Just How You Pitch
The leaders who get good at this stop treating persuasion as something they do before a big meeting and start treating it as infrastructure. Credibility gets built continuously, in the small exchanges nobody is grading. Common ground gets mapped in advance, before there is a specific ask riding on it. Evidence gets collected as a habit, not assembled under deadline. And the willingness to say what actually matters, out loud, stops being reserved for the big pitch and becomes how the leader talks generally.
This is the same architecture logic I apply to every other part of leadership capability: a skill practised only under pressure will fail under pressure. Persuasion in a flat organisation works the same way. If credibility, framing, evidence and emotional honesty only show up when you need something, your peers notice the pattern, and the fifth ask lands worse than the first. Built as a standing practice, the same four steps compound. If you want a structured way to build this into how your leadership team actually operates, that is exactly the kind of work I do through CapabilityAI, and it is also the starting point of most engagements when you work with me directly.
Flat organisations were supposed to remove the friction that hierarchy created. In practice, they moved the friction somewhere else: into every single interaction where a leader now has to earn what a title used to hand them automatically. That is not a design flaw to route around. It is the design. Conger named the method for operating inside it nearly thirty years before most organisations actually flattened enough to need it.