In my view, the leadership frameworks for scaling companies worth your time answer different questions, so comparing them head to head misleads. One is a library of competencies. One runs a coaching conversation. One models senior roles. One designs the system around the leaders. I set four side by side below, with what each is for and where each stops.
Scaling is the point where informal leadership stops working. In a ten-person company the founder settles most things by being in the room. At a few hundred people, decisions queue, standards drift between teams, and the people promoted for strong delivery are asked to lead before anyone has told them how. A framework is meant to replace that guesswork with something shared. The trouble is that the word covers very different tools, and buying the wrong kind costs a year.
How I compared these leadership frameworks for scaling companies
I asked four questions of each framework. What question does it answer? Where does it live: in a library, in a conversation, in a programme, or inside the business? What does it ask of the company that adopts it? And where does it stop?
The last question matters most. Every framework is useful inside its own boundary. The failure I see is a company expecting a framework to do something outside that boundary, then deciding the framework does not work. A competency library will not fix unclear decision rights. A coaching model will not tell you which of your forty managers needs coaching first. Knowing the edge saves you the disappointment.
I have more than 25 years of experience leading transformation and building leadership capability, and the pattern repeats across every size and sector I have worked in. The frameworks differ. The mistake of asking one tool to do another tool's job does not.
1. Korn Ferry Leadership Architect: A Library of Competencies
Korn Ferry describes its Leadership Architect as a framework "comprised of 38 behavior-based leadership skills", and its page says the framework "can serve as a benchmark for your assumptions against the performance of over 92,000 leaders globally". Both figures are Korn Ferry's own, and I have not checked them independently. The page says the competencies are meant to enable "employees of all levels within the organization" to contribute, and it points to a Research Guide and Technical Manual for the research behind it.
Access works through the company rather than a download. The page tells readers to contact their local Korn Ferry account managers to request technical manuals, and to visit a certification page to become certified to use the dataset. It shows no prices.
Its job is to give a company one shared language for what good looks like, so that hiring, promotion, feedback and development all use the same words. If your managers describe the same behaviour five different ways, a competency library solves a real problem.
The limit is that a library describes behaviour. It does not decide who owns which call, how often leaders meet, or what happens when a team lead is promoted into a role they have never seen done well. A company can hold a beautiful list of 38 skills and still have every significant decision running through one person.
2. Center for Creative Leadership: Assessment, Challenge and Support
The Center for Creative Leadership calls its Assessment, Challenge and Support model a "simple, proven leadership coaching framework" that "provides a clear path for guiding coaching conversations". On its own page the stated purpose is to "spark self-awareness, stretch thinking, and encourage follow-through". The three phases are Assess ("Where Are They Now?"), Challenge ("What's Possible?") and Support ("What's Next?"). The same page sets out six principles for coaches, among them "Work within the coachee's agenda" and "Model what you coach". The organisation describes itself as a global nonprofit provider of leadership development, founded in 1970.
Its use is to structure a coaching conversation so it does not drift into advice-giving or pleasant chat. For a company that has managers coaching their teams, or external coaches working with several leaders, a shared conversational shape makes the quality more even.
It stops at the edge of a single conversation. It does not tell you which leaders to prioritise, what capability the company needs across levels, or how to know in a year whether the coaching moved anything the business cares about. Those need something wrapped around it. I wrote about that gap in my comparison of a leadership framework and leadership architecture.
3. FranklinCovey: The 4 Essential Roles of Leadership
FranklinCovey presents The 4 Essential Roles of Leadership as "A framework to understand leadership roles", aimed at leaders promoted into mid-level or senior positions. The four roles on its page are Inspire Trust, Create Vision, Execute Strategy and Coach Potential. The page says experienced leaders in those roles need "hands-on work sessions", and lists a 360 Diagnostic, a Participant Workbook, an Implementation Plan and on-demand modules among the included materials. No price is shown on the page.
It earns its place with newly senior leaders: it gives them a simple picture of their job. People promoted for being excellent at the work often assume the job is more of the work. Four named roles give them something to measure themselves against, and they give a leadership team a common vocabulary for conversations about role fit.
Its boundary is that it describes what a senior leader does. It does not describe how the company produces the next group of senior leaders, or what the structure around them has to provide. A leadership team can understand all four roles and still be unable to execute strategy because nobody agreed how decisions escalate.
4. 5D Leadership Architecture: Designing the System Around the Leaders
This is the framework I built. It has five stages: Discover, Desire, Define, Deliver and Drive. Discover diagnoses where leadership capability is thin. Desire aligns the leadership vision with the growth ambition. Define designs the architecture itself, meaning the systems, rhythms and capability pathways. Deliver embeds development inside the business. Drive sets up leaders who grow other leaders.
My Architecture Accelerator is a six-week sprint built on it, with nine one-to-one sessions and a completed Leadership Capability Blueprint at the end. Admission is by application, so it is not something you can pick up off a shelf the way a competency library can. I am also not a neutral party about it.
It suits companies where the problem is structural. Decisions queue, standards differ by team, promotions outrun preparation, and no amount of better individual leaders fixes the pattern because the pattern lives in how the company is arranged. The architecture names the decision rights, the cadences and the pathways, then builds them.
It asks a lot of the company, and that is its limit. Someone senior has to own it, the leadership team has to make real decisions about how work runs, and the result is a design to be lived, not a certificate to hang. For a company that only needs shared language for feedback, it is more than the job requires.
How to choose between these leadership frameworks for scaling companies
| Framework | Question it answers | Where it lives | Best when |
|---|---|---|---|
| Korn Ferry Leadership Architect | What does good look like? | A competency library | Managers describe the same behaviour in different ways |
| CCL Assessment, Challenge and Support | How do we run a good coaching conversation? | The coaching conversation | Many people coach, and quality varies |
| FranklinCovey 4 Essential Roles | What is a senior leader's job? | A role model and course | Leaders were promoted without role clarity |
| 5D Leadership Architecture | How is leadership capability produced in this company? | The operating system of the business | Decisions queue and standards drift as you grow |
Read the right-hand column honestly. Most scaling companies have more than one of those problems, which is why the frameworks stack better than they compete.
A sensible order of operations
Start with the structural question, because it decides how much the others can achieve. If decisions are queuing behind one or two people, nothing else will stick until that is addressed. Ask who decides what, how often the leadership team meets to decide, and what happens when a decision is disputed. If the answers are vague, that is where to begin.
Then add shared language. Once the structure exists, a competency library gives it consistent vocabulary, and the same words can run through hiring, promotion and feedback. A library laid on top of an unclear structure just describes the confusion more precisely.
Add the conversation model third. When the roles and the language are settled, a coaching model makes the conversations that carry both far more even. Finally, use a role model to onboard each new senior leader quickly, so that the move into a bigger job comes with a picture of what it asks.
You can read more about the structural layer in what a leadership capability framework is, and about the sprint format on the Architecture Accelerator page. If you want a quick read on where your own leadership system is thin, the free Leadership Diagnostic scores five structural pillars. My thinking on the AI companion to this work is on the CapabilityAI page.
None of this needs a big purchase to start. A leadership team can spend one afternoon answering the structural questions on a whiteboard and learn more than a month of vendor demos would teach. Then you know what you are buying, and which of these four frameworks, if any, is the right answer.