From “Ohana Culture” to Operational Advantage: How Followership Delivers

The phrase “great leaders are great followers” is a useful correction to the hero-leader myth, but it goes deeper than humility or personality.

Followership is competence-based trust.

It sounds abstract until you look at what makes interdependent systems work. People separate tasks. People specialize. Then they rely on each other, because no one can be the expert in everything and no one can be everywhere at once.

This is older than markets. It is older than job titles. It is older than most of what we treat as “management.”

It is also one of the reasons humans survived in a world full of bigger, faster, stronger animals. We did not win because we were individually dominant. We won because we coordinated. We divided labor. We developed specialized knowledge. We shared information. We trusted each other enough to take risks together, and we corrected each other fast when reality disagreed.

Organizations are just scaled-up versions of that same problem.

So when I talk about followership, I am not talking about submission. I am talking about the operational decision to trust expertise. Leaders who know how to follow are leaders who know how to let specialization do its job.

Specialization creates power, trust makes it usable

Specialization is a double-edged sword.

On the upside, specialization makes people competent. It creates speed. It increases quality. It gives an organization more “surface area” for seeing problems early.

On the downside, specialization creates dependence. The more specialized the work, the more one person cannot simply “check everything.” That dependence can trigger a predictable managerial fear: losing control of the ship.

Often leaders try to exert influence over too many decisions because they fear losing control of the ship. The result is not better control, it's a bottleneck.

In practice, it produces micromanagement, slower decisions, duplicated work, and avoidable mistakes because the people with the most relevant expertise are not empowered to make decisions related to their specialized knowledge.

That last part matters. This is not just a “style” issue. It is an architecture issue.

If expertise lives in one place but decision rights live in another, you get predictable failure modes:

• Decisions slow down because everything must route through one person. Work gets duplicated because people hedge or “pre-solve” problems to survive the approval gauntlet.

• Mistakes increase because decisions are made without the knowledge that only the work owners can see.

• Over time, the people closest to the work stop giving early warnings, because early warnings are punished, ignored, or turned into extra bureaucracy.

That is how organizations quietly lose their ability to adapt.

So, in this context, followership is the discipline of letting expertise lead where it should lead and building the conditions where that is safe.

Rough consensus is a practical model for competence-based trust

Adapted from Rao's Rough Consensus and Maximal Interestingness

There are two very different ways groups try to reach consensus.

In many organizations, consensus is basically social smoothing. People sand down disagreements until nobody objects. That can work fine when the main problem is coordination and the main constraint is limited time, budget, or attention.

A room that gets to “yes” too quickly is often a room where the most relevant knowledge never made it into the decision. In environments where creative breakthroughs are necessary, harmony can turn into gridlock. Or worse, it can turn into groupthink, where the appearance of agreement masks missing data.

A better model is rough consensus: not perfect agreement, not a compromise that makes everyone mildly unhappy, but a clear enough short-term direction that the team can move and test independently prior to the final decision. Strong viewpoints are welcome, but they have to be open to revision when better evidence shows up.

In a healthy rough-consensus process, you do not try to eliminate dissent. You surface it early and use it to sharpen the direction (1). This allows you change course while it is still cheap to do so (See Jeff Bezos).

1. See Ray Dalio's concepts of Thoughtful Disagreement, Idea Meritocracy, Radical Truth and Radical Transparency

2. See Jeff Bezos’s Type 1 / Type 2 decision framework.

“Well-meaning conflict” is how organizations discover what they know

Most people hear “conflict” and picture ego clashes, politics, or disrespect. That is real, and it is corrosive.

But well-meaning conflict is not only healthy, it is necessary.

This happens when people are aligned on the goal but disagree because they are drawing on different knowledge sets.

Operations sees constraints. Finance sees exposure. The frontline sees failure modes. Specialists see edge cases. Each perspective can be correct within its slice of the system and still point to a different decision.

That disagreement is not dysfunction. It is the organization surfacing its distributed intelligence. If you force harmony too early, the conflict does not disappear. It just goes quiet, and the decision gets made with missing information.

A useful rule for making this work is “strong views, weakly held”.

Strong views mean people bring their best thinking and defend it with evidence. Weakly held means they are willing to update when another specialist introduces new information they had not considered.

Maximal interestingness as an intrinsic motivation strategy disguised as decision-making

"Maximal interestingness" does not require a perfect plan. It requires a fertile direction that invites motivated contribution and learning, while remaining clear enough in the next steps to keep the team moving.

This is not only a strategy advantage. It is also a motivation advantage.

Herzberg’s two-factor model draws a line between external factors (pay, policies, working conditions) and internal motivators (achievement, responsibility, growth, meaningful work). “Interestingness” is a type of motivator.

Most organizations unintentionally do the opposite of this. They over-specify the vision in ways that reduce autonomy and under-specify the immediate next steps in ways that create confusion. That combination kills motivation and kills learning.

A rough-consensus approach flips the pattern. It gives people room to pursue problems in the best way they see fit, which is often the most interesting way for them. That interest is an intrinsic motivation that keeps specialists doing the hard cognitive work long after superficial (external) incentives have run out.

When people bring strong, interesting-to-them views that are still weakly held, a team can produce a better outcome than any single leader could generate alone.

That is the point of expertise. That is the point of coordination.

Where leadership actually belongs: intent, constraints, and arbitration

None of this means leaders “let go” and hope for the best.

Trust does not mean abdication. Competence-based trust is structured.

The leader’s job is to set intent, define constraints, and design decision rights so that specialization can operate without turning into chaos.

Intent answers: What are we trying to accomplish, and why?

Constraints answer: What cannot happen, what must be protected, what tradeoffs are off-limits?

Arbitration answers: Who decides, who advises, who executes, and who gets the final call if specialists disagree?

Once those are clear, specialists can do what they do best: explore, test, challenge, build, and refine.

If rough consensus emerges, leadership bandwidth is preserved. The system moves without turning the leader into a bottleneck.

If rough consensus does not emerge, that is where leadership earns its keep. Managerial decision-making bandwidth intervenes, not to override expertise casually, but to resolve a deadlock using the broader organizational view: priorities, timing, risk tolerance, values, and accountability.

This becomes even clearer if you separate decisions into two buckets.

Some decisions are reversible. If you test and learn, you can recover. These decisions benefit from maximal interestingness and fast iteration.

Other decisions are one-way doors. Compliance failures, safety failures, reputational collapses, major contractual commitments. In those situations, leadership may need to decide quickly and conservatively.

The difference between “decisive leadership” and “authoritarian leadership” is whether expertise is being used or merely tolerated.

Why this matters even more in Hawaiʻi

It is worth adding a Hawaiʻi lens here, because the mainland “generic leadership” conversation often ignores what tight markets do to trust.

In Hawaiʻi, business ecosystems are relationship-driven. Reputations travel fast. Word-of-mouth matters. Cultural fit and values alignment are not soft considerations; they are practical constraints.

That means internal trust practices leak into external reputation.

If an organization routinely sidelines expertise, over-centralizes decisions, and suppresses well-meaning conflict, people feel it. Turnover rises. Partners notice friction. Customers encounter inconsistency. Community stakeholders interpret the signals.

Competence-based trust, on the other hand, becomes a competitive advantage. It increases speed without increasing recklessness. It improves decision quality without bloating bureaucracy. It keeps people engaged because interesting work stays close to the people who do it.

In a small market, that kind of organizational health shows up everywhere.

REFERENCES

Chamorro-Premuzic, T., & Edmondson, A. C. (2026, January 14). The best leaders are great followers. Harvard Business Review.

Dunn, S. T., Jr. (2025). Deep learning, deeper insights: A multilevel exploration of “value” (Doctoral dissertation, University of Hawaiʻi at Mānoa). Shidler College of Business, University of Hawaiʻi at Mānoa.

Grant, R. M. (1996). Toward a knowledge-based theory of the firm. Strategic Management Journal, 17(S2), 109–122.

Harvard Business Review. (2026, February 13). To be a great leader, become a great follower [LinkedIn Pulse article]. LinkedIn.

Herzberg, F., Mausner, B., & Snyderman, B. B. (1959). The motivation to work. John Wiley & Sons.

Rao, V. (n.d.). Rough consensus and maximal interestingness. Breaking Smart. Retrieved February 20, 2026, from https://breakingsmart.com/en/season-1/rough-consensus-and-maximal-interestingness/ 

APPENDIX 1: A note from the comment section: followership can be misread

One of the most thoughtful themes in the comments to HBR's article ("To Be a Great Leader, Become a Great Follower") was the tension between “following well” and being recognized for leadership, especially for women in male-dominated environments.

That tension is real. Many organizations are trained to recognize leadership only when it looks like assertion, visibility, and authorship. Quiet competence and behind-the-scenes influence can be discounted, even when it creates the results everyone depends on.

Competence-based trust does not require invisibility.

In fact, the healthiest version of followership includes making your reasoning visible. You can stay collaborative while still narrating tradeoffs, naming risks, and closing the loop on outcomes. You can focus on the mission while still documenting your contributions. You can be coachable without making yourself small.

If followership is competence-based trust, then part of the leader’s job is also to create an environment where competence is credited accurately. Otherwise, the organization trains people to prioritize optics over outcomes, and that is a slow poison.