TL;DR: Expertise and sound ideas alone don't drive organizational change. Influence — the ability to co-author initiatives with key stakeholders — is the skill that determines whether good ideas move from agreement to execution. We name the gap, show what influence through co-authorship looks like in practice, and makes the case for measuring it.
The meeting went well. Everyone agreed. The data was sound, the proposal was clear, and the room nodded along. But two weeks later, nothing happened.
No one blocked it. No one raised objections. The initiative simply died in the space between agreement and execution. It drifted into "we should circle back on that" territory and never returned.
If you lead operations, you have seen this. If you design training programs, you've probably built programs to solve problems just like this. And if you have ever been the person in the room proclaiming the answer but could not get anyone to act on it, you already know what was missing. It was not strategy, expertise, or communication. It was influence. And most organizations do not treat influence as a skill.
This is not a one-off. It is structural. Organizations are increasingly creating situations where positional authority does not apply. As structures flatten and work becomes more cross-functional, influence—not title—becomes the determining factor in whether ideas gain traction, decisions are made, and progress occurs. In these environments, leaders succeed less by issuing direction and more by earning followership through credibility, expertise, and relationship-based influence.
Consider home appliance and consumer electronics company, Haier. They dismantled much of its traditional hierarchy by organizing employees into thousands of self-managed micro-enterprises. These small units operate with full profit-and-loss responsibility and are directly accountable to customers rather than bosses.
In this system:
Haier explicitly frames leadership as mobilizing others around customer value. When hierarchy and managerial span of control is removed, influence becomes the primary mechanism for coordination, execution, and results.
Let's explore this more deeply. Strength in influence can determine whether we thrive or fail even in more traditional structures. An operations leader gets pulled into a project with marketing, IT, and regional management. Nobody reports to anyone. The org chart still exists—it just doesn't govern the room.
Most organizations now acknowledge this reality. Roughly two thirds of senior leaders say it's critically important to work beyond traditional functional boundaries. Yet only a small minority believe their organizations are truly doing this well. That gap is where most cross-functional teams live: structurally necessary, but culturally and behaviorally unsupported.
The work depends on collaboration, clarity, and shared decisions—but influence is still treated as if it flows down a reporting line that no longer applies.
Skills-first organizations hold an advantage in that their teams are ready to move laterally as well as vertically. Roles change faster than titles, and careers look more like lattices than ladders.
Yet only about one third of organizations have any kind of formal internal mobility structure. Most employees still feel uncertain about how—or whether—they can move internally. At the same time, more than half of learning and development leaders now say internal mobility is a top priority.
The result? Lateral moves are happening, but without the scaffolding to support them. People land in new roles where their prior title carries little weight. They must rebuild credibility, navigate new stakeholders, and gain traction without formal authority—all while delivering results.
In a skills-based organization, expertise earns you a seat at the table—but not the decision.
Trainers, technical experts, and senior individual contributors often need buy-in from people who outrank them. They know the material cold. They can explain the protocol, demonstrate the system, and answer every question with confidence.
Their expertise is unquestionable.
And still, nothing moves.
Without influence skill, knowledge remains theoretical. Recommendations get “considered.” Best practices get kicked to the next quarter. Change stalls—not because the expert lacked insight, but because technical skill alone rarely bridges authority gaps.
The Skill We're Missing isn't Communication, but Influence
When initiatives stall, the default diagnosis is familiar: we need to communicate better. Clearer emails. Better slide decks. More town halls.
But the person in the meeting who could not get adoption was not unclear. Everyone understood the proposal. What they did not understand was how to move.
Communication moves information from one person to another.
Influence moves people to act on it.
That distinction matters, because the intervention is completely different. Better presentations do not solve a buy-in problem. Neither does talking louder, sending more emails, holding more meetings, or escalating to a VP.
Research on transformation failures makes this painfully concrete. When frontline employees or line managers are not actively engaged, success becomes the exception rather than the norm. In organizations where leaders later describe transformation efforts as failures, the most common barriers cited are employee resistance and management behavior—not flawed strategies, not insufficient resources, not changing market conditions. The plan was understood. People just didn't move.
This is where the real gap shows up.
Across large-scale change efforts, most leaders believe they are involving employees in the strategy. Yet only a minority of employees agree. Leaders think inclusion is happening; employees experience it as something being done to them, not with them. That distance is not caused by silence. Leaders are talking. Employees are listening.
What is missing is the influence that makes inclusion feel real rather than performative.
The difference shows up most clearly at the manager level. Transformations are far more likely to succeed when managers make it easy for their teams to understand the case for change. Not when they forward announcements. Not when they read scripts. When they help the logic land, answer resistance, and translate intent into personal relevance.
That work—making the case land—is influence work.
And most organizations still treat it as if it were a communication task.
Let's make this tangible across industries where cross-functional coordination is not optional.
Hospitality and cruise operations. A cruise ship is a floating operation where departments that would be separate companies on land share a hallway. Entertainment, food service, housekeeping, guest relations, safety. All intersecting constantly. Guest experience depends on whether people across hospitality functions can coordinate without escalating to leadership (or the home office ashore).
Royal Caribbean recognized this when they built their assessment approach. They specifically measured a candidate's confidence in influencing others alongside flexibility, curiosity, positivity, and drive to serve. The goal was to precisely identify applicants with exceptional cross-disciplinary leadership and a service-driven mindset. The outcome: a positive impact on guest service and satisfaction. They did not just hope influence would show up. They assessed for it.
Airlines. You might have witnessed a flight attendant manage seating or any number of other types of conflict between passengers. The task is to influence two strangers into resolution in real time, in a confined space, while maintaining safety, operational, and service standards. Successful airlines and flight crews hinge on influence running upward and outward to passengers. Cabin crew escalate safety concerns. Expertise is acted on from specialized role to specialized role. Failing to influence in that direction has life-safety consequences.
In both examples, the person on the receiving end of an influence failure is often our key stakeholder: the customer (or guest, patient, client). The trainer who struggles with transfer and adoption fails to influence the customer experience. The operations leader who cannot motivate departments continues the status quo.
Consider that -
Wherever work crosses functional lines, the same problem emerges: collaboration drag. Decision cycles stretch. Coordination costs rise. Progress depends less on clarity and more on someone's ability to persuade without authority.
Organizations caught in this pattern are less likely to meet their performance goals, and employees living inside it burn out faster. The work is not failing because people refuse to collaborate. It fails because collaboration now requires influence skill that most roles were never developed to use.
Often the difference that makes a difference happens before the meeting.
Two people with the same technical knowledge, the same training, the same years of experience. One gets adoption. The other does not. Same room, same proposal, same data.
The one who gets adoption never walks into the room cold. Before the formal presentation, she has had three separate conversations. One with the VP of Operations, who is worried about disruption to current workflows.
"If we were going to do this, what would the rollout need to look like for your team to absorb it without breaking what is already working?" Now the VP is not defending against a proposal. She is designing the implementation. Her concern about disruption just became a constraint she is helping solve.
One with the finance lead, who needs to see the cost picture on his terms. "I want to make sure I am framing the investment the way you would need to see it. Are we talking about upfront cost against projected savings, or does this need to show up as a line-item reduction in Q3?" Now the finance lead is not evaluating a number someone else chose. He is choosing the frame. He is already working inside the initiative.
One with the regional director, whose teams are stretched thin. "I know your locations are running lean. What if we scoped a version that one site could pilot without adding headcount, so we would have real data before asking anyone else to take it on?" Now the regional director is not being asked to say yes to scale. She is being asked to say yes to learning. The risk just dropped.
By the time the meeting happens, three people in the room have already shaped the plan. They are not hearing a proposal for the first time. They are seeing their own thinking reflected back. The meeting is not where buy-in happens. It is where buy-in gets ratified.
The person who struggles with adoption skips all of this. Not because they are incapable, but because nobody ever named what they were skipping. They default to "build the best case and present it." They believe the work speaks for itself and the best idea wins. One pitch, one framing, delivered to everyone at the same time. The idea is strong. The data is sound. And nothing moves—because the room was never co-authored.
This is what influence through co-authorship looks like: each stakeholder becomes a co-author of the initiative before they are ever asked to be a supporter. It requires three observable behaviors.
Identifying who holds the real decision weight before the formal ask.
Modeling what each person cares about and adapting the framing accordingly.
And creating conditions where the ask feels like a next step people already helped design, not a surprise they need to evaluate on the spot.
Commitment and adoption require bridges. And most organizations quietly assume they will build themselves.
They don't.
Every successful initiative has someone playing the same role, even if no one names it: a leader who curates the right partners, translates across silos, and integrates work that would otherwise fragment. That's the role of the bridger — and it's key to leadership (whether we have the title or not).
Different frameworks use different language, but they all point to the same conclusion: without someone actively doing this work, good ideas stop at the boundary between the people who built them and the people who need to make them real.
This is not charisma. It is not personality. It is a definable pattern of behavior. And most competency models do not name it. They include "communication" or "collaboration," which describe inputs. Influence through co-authorship is an outcome—it is what happens when communication actually moves people. When it is not named in the framework, it cannot be coached, assessed, or developed. It stays invisible until an initiative stalls and everyone wonders why.
Expertise is the price of admission. Influence is what makes it count.
Here is where most content about influence stops. The leadership gurus tell you to 'build trust' and 'be empathetic.' They usually never ask the harder questions:
How do you know if someone has this capability before you put them in a cross-functional role?
How do you develop it systematically rather than hoping it shows up?
How do you track whether it is growing?
When influence is called out in our competencies— not as "communication" but as the specific behaviors we have described — we can scale. It can be screened for at hire, measured for development, and used as a signal in promotion and succession decisions. It does not have to remain the thing organizations notice only after a failure. Or when we ask, "why aren't we doing things the way we talked about last quarter?" We can select for, and grow it, before we fall short.
Most organizations rigorously measure whether someone has the technical skill to do the work. What they rarely assess is whether that person can bring others along.
That gap matters. The ability to mobilize others is what turns expertise into impact. Yet it remains largely unnamed—and therefore undeveloped—in most leadership models.
Corvirtus has spent 40+ years building assessment and development systems grounded in the science and practice of industrial-organizational psychology. Influence is one of the capabilities we measure, not as a personality trait, but as an observable, buildable skill that determines whether expertise actually lands in the organization.
We work with organizations across hospitality, healthcare, aviation, and beyond to build systems that identify and develop the capabilities that matter most when the work crosses boundaries.
If your organization is building toward a skills-based talent strategy, influence belongs in the model. We can help you define it, assess it, and develop it.
In the next piece in this series, we look at what happens when influence is missing at the leadership level, why great trainers, senior individual contributors, and high performers still fail despite having everything else right, and what organizations can do to close the gap before it costs them their best people.
In skills-based organizations, influence is developed by defining it as a set of observable behaviors—not a personality trait. These behaviors include reading stakeholder priorities, framing ideas in the listener's terms, building coalitions before formal requests, and sustaining advocacy when resistance shows up.
Once defined, influence can be developed through scenario-based practice and structured feedback. Development is most effective when paired with assessment data that shows where an individual's influence patterns are strong and where they tend to stall.
Influence without authority is the ability to mobilize action when you do not have positional power over the people involved.
It shows up most clearly in cross-functional projects, lateral moves, and training or expert roles. It requires understanding what others value, framing ideas accordingly, and creating conditions where adoption is voluntary rather than enforced through hierarchy.
Yes. Influence shows up in consistent, observable behaviors.
These include how someone frames proposals, whether they build alignment before making formal asks, how they respond when advocacy becomes uncomfortable, and whether they sustain effort through resistance. Validated behavioral assessments and structured interview scenarios that force tradeoffs can measure these patterns reliably.
Persuasion is a moment-based tactic aimed at changing someone's mind in a specific interaction. Influence is broader and cumulative.
Influence involves building receptivity over time, maintaining advocacy through resistance, creating shared ownership, and sustaining outcomes beyond the initial conversation. Persuasion is one tool within influence—but influence operates at the system level.
High performers often succeed because their expertise carries authority within a functional domain. Cross-functional roles remove that advantage.
Deep technical skill and decisiveness do not automatically translate when progress depends on buy-in from peers who report to different leaders and operate by different priorities. What's missing is influence—the ability to move work forward without relying on positional power.
Skills-based organizations treat influence as a capability that can be defined, assessed, and developed.
They include influence in competency models, evaluate it during hiring and promotion decisions, design development programs around specific influence behaviors, and track growth over time. This differs from traditional approaches that treat influence as a byproduct of seniority or personality rather than a skill essential to modern work.