The Three Rs of Leadership: Respectful, Reliable, Rational
A senior manager at a mid-sized healthcare organization once described her team’s dysfunction this way: “We have all the right processes on paper. The problem is nobody trusts that anyone will actually do what they say, people are afraid to speak up when something’s wrong, and half our decisions get made on gut feeling and office politics.” She wasn’t describing a skills gap. She was describing a culture that had been quietly shaped — decision by decision, interaction by interaction — into something that worked against the people inside it.
She’s not alone. Gallup’s 2023 State of the Global Workplace report found that only 23% of employees worldwide are engaged at work, with poor management cited as the primary driver of disengagement. McKinsey research consistently identifies leadership behavior — not strategy or structure — as the single largest predictor of team performance and organizational health. And Christine Porath’s two-decade research program on workplace incivility, conducted across industries and continents, found that 98% of workers have experienced uncivil behavior at work, and 80% lose time worrying about it.
The problem isn’t that leaders don’t know what good leadership looks like. Most can recite the principles on demand. The problem is that the behaviors that drive team performance — or undermine it — are outputs of systems, not just personal choices. Leaders behave the way their environments reward them to behave. And most organizational environments, if we’re honest, reward the wrong things.
Three behaviors sit at the foundation of effective leadership: being Respectful, Reliable, and Rational. Not as virtues to aspire to. As structural inputs to organizational performance. Get them right, and you’ve built the conditions for accountability, innovation, and sound decision-making. Get them wrong — or build systems that undermine them — and no amount of strategy or process redesign will save you.
Respect Isn’t a Soft Skill — It’s Infrastructure
For decades, “respect in the workplace” has been treated like a values-statement line item: important-sounding, difficult to measure, and easy to deprioritize when harder metrics are on the table. That framing has cost organizations enormously. (See also: Everything Feels Harder Because It Is.)
In 2012, Google launched Project Aristotle — an internal research initiative designed to answer a deceptively simple question: what makes a Google team effective? The researchers coded hundreds of variables across dozens of teams: individual skill, personality mix, education, tenure, social dynamics. After years of analysis, one factor emerged as the dominant predictor of team performance: psychological safety. Specifically, whether team members felt safe to speak up, take risks, and make mistakes without fear of punishment or humiliation. (See also: The Most Expensive Leadership Mistake Is the Question You Didn’t Ask.)
Amy Edmondson at Harvard Business School had been building the theoretical and empirical foundation for this finding for over twenty years. Her research across medical teams, manufacturing, and financial services showed the same pattern: teams with high psychological safety outperform low-safety teams on virtually every measure — error detection, innovation, learning agility, and long-term performance. Crucially, she found that psychological safety is not a personality trait of team members. It is a climate variable, created and maintained by leader behavior.
“Psychological safety is not about being nice. It’s about being candid, about making it possible for the inevitable human errors and learning opportunities to surface and be addressed.”
— Amy Edmondson, The Fearless Organization
And the engine that drives psychological safety is respect — not as a feeling, but as a set of observable behaviors. Christine Porath’s research is unsparing on what happens in its absence. Her studies found that workers who experience incivility perform 26% worse and are 45% less creative. Witnesses to incivility — not just targets — show declines in performance and are more likely to disengage or leave. Incivility is contagious: one disrespectful leader can shift the behavioral norms of an entire team.
Gallup data reinforces the structural nature of this problem. Their Q12 engagement research consistently finds that feeling cared for and recognized at work are among the strongest predictors of engagement — yet only one in three employees strongly agree that they received recognition or praise in the last seven days for good work. This isn’t a kindness problem. It’s a systemic inattention to a behavior that drives measurable performance outcomes.
What does respect as infrastructure look like in practice?
- Consistent acknowledgment of contributions — not sporadic praise, but regular recognition built into team rhythms
- Active solicitation of dissent — explicitly asking what you’re missing or what could go wrong, particularly from people with less positional power
- Meeting behavior as a signal — who gets interrupted, whose ideas get credited, who gets shut down. These micro-behaviors broadcast the actual safety level of the team.
- Zero tolerance for derision — eye-rolls, dismissive comments, and subtle put-downs are not minor annoyances. They are system signals that shape whether people will surface critical information in the future.
Systems thinking reframes respect this way: it is not a character virtue that individual leaders either have or don’t. It is a set of behaviors that organizational systems either reinforce or discourage. Cultures that reward “results at any cost,” that celebrate dominant personalities, or that conflate toughness with effectiveness will produce disrespectful leadership regardless of who sits in the chair. That’s the system talking.
Reliability Is How You Build a Trust Economy — or Destroy One
Patrick Lencioni’s foundational work on team dysfunction identifies trust as the base layer — without it, conflict becomes political rather than productive, commitment is shallow, and accountability disappears. But it’s worth being precise about what kind of trust we’re talking about. The trust that makes teams functional is not affective trust (I like you, you seem like a good person). It is reliability-based trust — I can predict your behavior, you do what you say you’ll do, your word means something.
This distinction matters because many leaders assume they have trust because they have positive relationships with their teams. Gallup’s Q12 research cuts through that assumption. The Q1 item — “I know what is expected of me at work” — is one of the most foundational predictors of engagement and performance in the dataset. When leaders fail to follow through on commitments, shift expectations without explanation, or communicate one thing and do another, they erode the very foundation that Q1 measures. Employees stop building plans around what leaders say because they’ve learned those plans will be revised or ignored.
The organizational cost of low reliability compounds over time in ways that rarely show up in a single quarter’s numbers. When people can’t count on follow-through, they build informal workarounds. They stop escalating problems because the last three times they did, nothing happened. They hoard information because sharing it didn’t lead to action. They stop taking initiative because previous initiatives were abandoned. Each of these is a rational adaptation to an unreliable system — and together they create exactly the disengaged, low-accountability culture that leaders then try to address with engagement surveys and team-building exercises.
“Trust is the highest form of human motivation. It brings out the very best in people. But it takes time and patience.”
— Stephen Covey, The 7 Habits of Highly Effective People
Building a reliability-based trust economy requires leaders to treat their commitments as load-bearing structures. Specifically:
- Make fewer, clearer commitments — and honor them fully. Over-promising and under-delivering is worse than being direct about what you can and can’t take on.
- Close the loop explicitly — when someone brings you an issue or request, acknowledge the outcome. “Here’s what I did with that” is as important as the action itself.
- Be transparent about constraints — when you can’t follow through, explain why. Unreliability without explanation is interpreted as not caring. Unreliability with honest explanation is still a setback, but it’s workable.
- Treat expectations as a two-way contract — Gallup’s research shows that clarity of expectations is not just about telling people what to do. It’s about co-creating understanding so that accountability is shared, not imposed.
The systems dimension here is critical. Organizations that overload managers with competing priorities, that shift strategic direction frequently, or that don’t give leaders the authority to actually follow through on what they commit to are systematically producing unreliable leadership. The leader isn’t the problem — the system is setting them up to fail. Fixing reliability requires examining what the organization is actually making possible for leaders to keep their word.
Rationality Means Fighting Your Own Brain — On Behalf of Your Team
Daniel Kahneman’s Nobel Prize-winning work on cognitive biases — popularized in Thinking, Fast and Slow — revealed something uncomfortable for leaders who pride themselves on their judgment: the human brain is systematically irrational in predictable ways. System 1 thinking (fast, intuitive, pattern-based) dominates our decision-making far more than most of us realize. Under stress, uncertainty, or time pressure — the conditions that define most consequential leadership decisions — System 1 is essentially in charge. And System 1 is subject to confirmation bias, availability heuristic, anchoring, sunk cost fallacy, and dozens of other well-documented distortions.
This is not a personal failing. It is a structural feature of human cognition. The rational leader is not the one who has overcome their cognitive biases — no one has. The rational leader is the one who has built systems and habits that surface those biases before they drive decisions.
W. Edwards Deming made this point from a different angle fifty years ago. His critique of management was fundamentally a critique of irrationality: decisions made on fear and assumption rather than data, managers tampering with stable systems based on noise mistaken for signal, leaders attributing systemic problems to individual performance because it was easier than examining the system. Deming’s insistence on data-driven decision-making wasn’t bureaucratic formalism — it was a discipline for keeping System 1 from running the factory floor.
Research on emotional reactivity in leadership adds another dimension. Studies on “amygdala hijack” — the neurological phenomenon where emotional threat responses override prefrontal cortex function — show that leaders under pressure are disproportionately likely to make reactive, regret-generating decisions. The leader who responds to a difficult situation by escalating emotionally doesn’t just make a bad decision in the moment; they signal to their team that pressure produces unpredictability, which feeds directly back into the psychological safety deficit described earlier.
Rational leadership, in practice, looks like this:
- Slowing down high-stakes decisions deliberately — Kahneman’s research is clear: we feel most confident about our intuitions precisely when we should be most skeptical of them. Build in time, even when it’s uncomfortable.
- Seeking disconfirming evidence — actively looking for data and perspectives that contradict your working hypothesis, not just those that support it
- Separating the person from the pattern — Deming’s “85/15 rule”: roughly 85% of problems are systemic, and 15% are attributable to individuals. Most leaders get that ratio exactly backwards.
- Naming your reasoning out loud — sharing the logic behind decisions, not just the conclusions. This creates accountability for the quality of reasoning and models analytical transparency for the team.
- Building decision-making structures that outlast moods — pre-mortems, red teams, structured debate, decision logs. Rationality is harder to sustain through culture alone than through process design.
Here again, the systems lens is decisive. Organizations that incentivize speed above rigor, that reward confident decisiveness regardless of accuracy, or that punish leaders for changing course when new data emerges are building irrational decision-making into their culture. The leader who makes reactive, bias-driven decisions isn’t necessarily weak or careless — they may be perfectly adapted to a system that rewards exactly that.
The Three Rs as a System — Not a List
The reason these three behaviors belong together is not that they’re alphabetically convenient. It’s that they are structurally interdependent. Respect creates the psychological safety that allows people to speak truth to power — which is the raw material that rational decision-making requires. Reliability builds the trust that makes respectful relationships durable and accountability functional. Rationality prevents the reactive, bias-driven behavior that most commonly erodes respect and breaks reliability.
And respect is the keystone — not because it’s the most important virtue, but because it’s the hardest one to sustain when it’s absent. A leader can be reliable and rational in an environment that lacks respect, but they’ll be reliable and rational in a room where no one is telling them the truth, and where people have learned to protect themselves rather than surface real problems. The data, the decisions, the commitments — they all become less trustworthy when the relational foundation is cracked.
The healthcare manager I opened with eventually worked through this with her team. Not through a training program or a values workshop. Through a sustained, deliberate shift in the system — how meetings were structured, how decisions were made and communicated, how commitments were tracked and closed, how leaders at every level were held accountable for the behaviors that made the culture work or not. It took time. It required honesty about what the system had been rewarding. And it required leadership that was willing to hold the Three Rs not as aspirational language, but as operational disciplines. (See also: Culture Is Not a Feeling.)
That’s the real work. Not knowing what good leadership looks like. Building the systems that make it possible — and that make anything less than that the exception, not the norm.
