In any organization, it is the manager—not the strategy, the software, or the slide deck—who most directly determines whether a team flounders or flourishes. Yet for all the emphasis placed on leadership, the definition of a great manager often remains vague or fragmented. We praise charisma, reward output, and occasionally celebrate empathy—but we rarely pause to articulate the full architecture of what actually makes management effective, sustainable, and transformative.
Great managers are not just task assigners or performance reviewers. They are system builders, energy stewards, and judgment multipliers. Their influence shapes the air their team breathes: how decisions are made, how feedback is received, how conflict is addressed, and how success is understood. A great manager isn't simply “nice” or “smart.” They design clarity, create safety, set the tempo, and push people toward a better version of themselves—while doing the same for their systems and for themselves.
The difference between a competent manager and a great one often comes down to how deliberate they are about the invisible work. Great managers don’t just react to problems; they architect environments in which problems are surfaced early and solved collaboratively. They don’t rely on authority alone—they leverage influence, trust, and context. They don’t delegate and disappear—they coach, scaffold, and calibrate ownership to each individual’s readiness and ambition.
Critically, great management is not a fixed personality trait. It is a discipline of behaviors—a composite of mental models, interpersonal skills, and structural habits that anyone can learn, refine, and master over time. From Andy Grove’s principle of managerial leverage to Brené Brown’s work on trust and vulnerability, the consensus across disciplines is clear: greatness in management is less about style and more about how consistently one embodies essential functions that generate clarity, safety, growth, and alignment.
This article presents a synthesized model of the sixteen essential features of a great manager, each supported by insights from some of the most respected thinkers in leadership, organizational psychology, and operational excellence. This is not a personality checklist—it is a functional blueprint. Whether you’re a seasoned executive or a first-time team lead, these features will help you understand what your team needs from you—and how to become the kind of manager whose impact resonates far beyond their calendar.
The Features Overview
1. Self-Awareness
“Build self-awareness to build mutual awareness.” — Claire Hughes Johnson
A great manager starts by managing themselves—understanding their patterns, blind spots, triggers, and strengths—because what’s unconscious becomes culture.
2. Clarity in Communication
“Clear is kind. Unclear is unkind.” — Brené Brown
The best managers make expectations unmissable, decisions explicit, and goals legible. Clarity is not just helpful—it is humane.
3. Consistent Feedback & Coaching
“The output of a manager is the output of their organization plus the output of those they influence.” — Andy Grove
Managers are multipliers of capability. They give frequent, direct, and forward-facing feedback. They don’t fix problems; they grow people who can.
4. Psychological Safety & Trust
“Trust is built in the smallest of moments.” — Brené Brown
When people feel safe to be candid, wrong, or unfinished, teams thrive. Safety isn’t softness—it’s the precondition of innovation.
5. High Standards + Empathy
“Compassion isn’t about lowering the bar. It’s about staying with someone while they learn to clear it.” — Paraphrased from Julie Zhuo
The best managers challenge their teams rigorously—because they care. Empathy isn’t an escape from standards; it’s what makes high standards sustainable.
6. Focus on Output, Not Just Activity
“Busy-ness is not the same as progress.” — Claire Hughes Johnson
A great manager doesn’t reward motion—they reward impact. Output is what matters. Everything else is noise.
7. Strong Decision-Making
“Consensus is desirable, but not mandatory.” — Andy Grove
Decisions require clarity, ownership, and timing. The best managers know when to listen, when to align—and when to close.
8. People Development
“Your legacy as a manager is who you help grow.” — Julie Zhuo
Managers don’t just supervise—they sculpt trajectories. They stretch talent, unlock potential, and help people scale with the company.
9. Operating Rhythm
“Structure is what allows people to move fast without breaking each other.” — Claire Hughes Johnson
Effective managers create steady, shared cadences—1:1s, reviews, planning cycles—that bring coherence to execution and reduce chaos.
10. Adaptability
“Let chaos reign. Then rein in chaos.” — Andy Grove
A great manager evolves faster than the system. They adjust plans, behaviors, and beliefs as context changes—without losing integrity.
11. Vision and Context Setting
“People don’t buy what you do. They buy why you do it.” — Simon Sinek
Managers must not only execute—they must orient. Context connects the dots, unlocks meaning, and gives direction its force.
12. Delegation & Trust
“Delegation without context is abdication. Context without trust is micromanagement.” — Claire Hughes Johnson
True delegation is giving someone ownership, not just tasks. It’s trust in motion—empowering others without abandoning oversight.
13. Courage to Have Hard Conversations
“The hardest feedback conversations I had were the ones I didn’t have.” — Julie Zhuo
Great managers name tension early. They speak hard truths kindly, directly, and without delay—because silence costs more.
14. Cross-Functional Collaboration
“At scale, almost nothing important happens inside a single team.” — Claire Hughes Johnson
The best managers orchestrate across boundaries. They influence without authority, align incentives, and build bridges between silos.
15. Resilience and Emotional Regulation
“You can’t lead if you’re emotionally hijacked every time something goes wrong.” — Paraphrased from Brené Brown
A manager’s emotional steadiness is the team’s psychological anchor. Their regulation sets the climate when conditions get stormy.
16. Leading by Example
“Who we are is how we lead.” — Brené Brown
Your habits become norms. Your tone becomes culture. Great managers don’t instruct excellence—they model it, daily.
The Features in Detail
1. Self-Awareness
What it is:
Self-awareness is the ongoing process of understanding your internal state—your patterns, triggers, intentions, blind spots—and how they manifest in your external behavior. For a manager, it’s the foundational operating system; without it, everything built atop it risks corruption.
Its impact:
Self-awareness is not soft. It is the difference between a team that trusts your consistency and one that walks on eggshells. It affects how clearly you communicate, how you receive dissent, how you respond under pressure, and how safe your team feels being honest with you.
Insights from the books:
Claire Hughes Johnson opens Scaling People by declaring:
"Build self-awareness to build mutual awareness."
She treats it not as a virtue but as a core managerial technology—the thing that governs whether you can handle feedback, spot your overreaches, or scale gracefully with your team. She describes self-awareness as the “meta-skill” behind knowing when your habits are getting in the way of the company’s needs. At Stripe, she created templates and prompts not just for planning but for understanding your default reactions to conflict, ambiguity, or praise.
Julie Zhuo, in The Making of a Manager, reinforces the point with subtlety. When she recounts her early days as a new manager at Facebook, she notes that:
“The most challenging part of being a manager isn't managing others—it's managing yourself.”
She describes her emotional overreactions to underperformance or critical feedback as "distortions" that only self-awareness helped her temper. She emphasizes that high-functioning managers routinely perform a self-diagnostic loop:
What am I feeling?
Why am I reacting this way?
What part of this is about me, not them?
Andy Grove in High Output Management doesn’t use the term “self-awareness,” but models it in his obsession with measurement. He says the manager must be aware of their own leverage points, where their actions cause amplification or attenuation of team output. This is a form of externalized self-awareness: knowing what effect your time and decisions actually have, not just what you believe they have.
Brené Brown makes it emotional and existential in Dare to Lead. Her leadership thesis begins with:
“You can’t be a courageous leader without self-awareness.”
She equates lack of self-awareness with leading from fear rather than grounded confidence. She even links poor self-awareness to an inability to regulate shame—resulting in defensive, blame-driven cultures. Her prescription? Daily, humble reflection, and inviting truth from others without resistance.
What to remember:
Self-awareness isn’t static—it’s a reflexive loop. You don’t “have it” once; you sustain it.
It must be reinforced by external mirrors—feedback, coaching, journaling, 1:1s where you do more listening than talking.
Without it, you will mistake your impulses for strategy. And your team will feel that dissonance in every interaction.
2. Clarity in Communication
What it is:
Clarity in communication is the ability to translate complex thoughts into simple, actionable, shared understanding. It’s what makes expectations tangible, feedback usable, and alignment operational—not theoretical.
Its impact:
Clarity is not “nice to have”—it is the precursor to accountability, autonomy, and momentum. When a team lacks clarity, it doesn’t slow down—it fractures. People fill the silence with assumption and overcompensation. Clarity is the antidote to ambiguity-induced burnout.
Insights from the books:
Claire Hughes Johnson frames clarity as an organizational multiplier. She writes:
“You know why playing a game is fun? Because it has rules, and you have a way to win.”
This metaphor isn’t cute—it’s fundamental. Without clearly stated operating principles, decision rights, and shared definitions of success, people flail. She recommends templated Operating Manuals for every manager, detailing how they make decisions, run meetings, and give feedback. Her core insight: people don’t resent structure—they crave it when it’s tied to purpose.
Andy Grove ties clarity to production. He doesn’t use poetic language—he uses the factory floor.
“A manager’s output = the output of their organization + the output of the organizations under their influence.”
From that equation, Grove builds a religion of clarity:
Goals must be defined clearly enough to measure
Tasks must be delegated clearly enough to execute
Feedback must be specific enough to guide future output
In Grove’s universe, ambiguity is expensive. And bad managers confuse vagueness with flexibility. Clear planning, clear decision-making authority, and clear metrics are not bureaucracy—they’re throughput enablers.
Julie Zhuo offers a psychologically tuned variant. In The Making of a Manager, she explains that unclear communication often stems from internal insecurity—the desire to be liked, to avoid conflict, or to seem smart. She recounts how her early attempts at giving feedback were clouded by “polite fog,” and how that led to disorientation in her reports. Her turning point came when she realized:
“Clarity is kindness. Ambiguity is cruelty in slow motion.”
And the most important place for clarity is not in documents—but in 1:1s, where human-to-human expectation setting occurs.
Brené Brown pushes the same line hard.
“Clear is kind. Unclear is unkind.”
She connects lack of clarity to fear—fear of being disliked, fear of confrontation. Her counsel is surgical: when delivering feedback or setting expectations, state:
What you observed
What your expectation is
What the consequences are
Anything less is performance theater—not leadership.
What to remember:
Clarity is not about talking more; it's about talking precisely.
True clarity is tested not by what you said—but by what the other person understood without asking again.
High-performing managers return to clarity constantly. They don’t “set it and forget it”—they re-clarify as contexts evolve.
If you’re afraid to be direct, you’re choosing your comfort over their growth.
3. Consistent Feedback & Coaching
What it is:
This is the sustained, intentional practice of helping others improve through direct, thoughtful, and timely reflection on their work. Feedback is the mirror. Coaching is the scaffolding.
Its impact:
Feedback keeps performance from drifting. Coaching develops the slope of a person’s growth curve. Without both, you get atrophy: talent plateaus, assumptions harden, and cultural entropy sets in.
Insights from the books:
Andy Grove frames feedback and coaching as a manager’s highest-leverage activity:
“Training is the boss’s job. Productivity depends on the manager’s ability to multiply output—not just through tasks, but through people.”
Grove proposes that feedback has maximal ROI when delivered close to the point of performance, and when tailored to the individual’s “task-relevant maturity” (TRM). A senior contributor with high TRM needs autonomy and strategic nudging. A junior hire with low TRM needs daily tight-loop feedback. The manager’s coaching style must match the situation to avoid either micromanagement or neglect.
Julie Zhuo elaborates on the emotional intelligence of feedback. Early in her career, she avoided hard feedback out of fear it would make her team uncomfortable. The cost? Confusion, resentment, and underperformance.
“If I had just told them exactly what wasn’t working and what better would look like, they could have actually improved.”
She now anchors feedback in the idea of partnership: you are co-owning someone’s development. Coaching, in her language, is not telling people what to do, but pulling clarity out of the fog: “What’s your goal here? What’s your strategy? What’s getting in the way?”
Claire Hughes Johnson institutionalizes feedback. At Stripe, she helped implement regular, lightweight “Pulse” reviews and insisted on frequent informal feedback rituals, not just the biannual formal reviews.
Her principle:
“The more you normalize feedback, the less dramatic it becomes. Feedback should feel like brushing your teeth—not like going to the dentist.”
She also insists managers coach not just for correction, but for expansion—asking what someone wants long-term, and helping build the bridge from now to there.
Brené Brown addresses the psychological barrier. Most managers don’t give feedback because they fear discomfort.
Her insight:
“You cannot shame someone into growth. But you can’t protect them from discomfort either.”
She introduces a trust-based frame: every time you give honest feedback, you are saying, “I believe in your ability to improve.” She calls this braving trust—offering truth with dignity, not control.
Eric Ries in The Startup Way pushes feedback from the individual to the system level. He advocates systemic feedback loops—metrics tied to behavior, learning reviews after every initiative, and cross-functional retros that turn “failure” into innovation inputs. Coaching, in his view, is about building feedback loops that the org itself can feel and respond to.
What to remember:
Don’t save feedback for performance reviews. The shelf-life of relevance shrinks by the hour.
Coach people at the edge of their current ability—not too far beyond, not behind.
Feedback must be specific, non-judgmental, and aimed at future behavior.
If you’re coaching well, your people feel two things: seen and stretched.
4. Psychological Safety & Trust
What it is:
Psychological safety is the team’s shared belief that it is safe to take risks, speak candidly, ask questions, and admit mistakes without fear of humiliation or punishment. Trust is the prerequisite; safety is the environment it generates.
Its impact:
Without psychological safety, high-performing teams become silent compliance machines. People prioritize self-preservation over candor, speed, or innovation. You get politeness at the cost of performance. With safety, you get truth, learning, and adaptability.
Insights from the books:
Brené Brown builds her entire leadership philosophy on this foundation. In Dare to Lead, she writes:
“You can’t have vulnerability without trust. And without vulnerability, there is no innovation, no creativity, no learning.”
She breaks trust into what she calls the BRAVING inventory—boundaries, reliability, accountability, vault (confidentiality), integrity, non-judgment, and generosity. Safety isn't a vibe; it’s a discipline of consistent behavior over time.
Julie Zhuo found that psychological safety wasn’t about being “nice”—it was about creating space for dissent.
She writes:
“The most effective teams weren’t the ones with the least conflict—they were the ones that surfaced and navigated conflict well.”
She learned to actively solicit disagreement and to thank people for challenging her—even when they were wrong. The message is: your voice matters more than my convenience.
Claire Hughes Johnson operationalizes safety through rituals of inclusion. Every Stripe meeting begins with a round where everyone is heard. She encourages managers to:
Name when they're unsure
Admit when they’re wrong
Ask questions that signal permission: What are we missing? What’s the hard thing we’re not saying?
These micro-acts reinforce that the manager doesn’t equate uncertainty with weakness—but with curiosity.
Andy Grove, despite his factory logic, implies safety by his insistence on truthful performance dialogue.
“People who can’t be told when they’re off-course are never going to get back on.”
For Grove, trust is established by fairness and follow-through. You earn the right to challenge people because they believe you’re doing it to make them better—not to make yourself look smarter.
Eric Ries raises the stakes. In entrepreneurial orgs, psychological safety is required for experimentation. Teams must feel safe to run experiments that might fail. When they don’t, they revert to political theater. Safety, then, is not just cultural—it’s strategic. Innovation depends on it.
What to remember:
Psychological safety isn’t “being nice”—it’s being brave enough to tell the truth and kind enough to receive it.
Leaders model safety by being publicly fallible. If you can admit fault, they will speak up.
The smallest betrayals of trust (interruptions, dismissals, unkept promises) are more destructive than big conflicts.
You get the candor you model, not the candor you request.
5. High Standards + Empathy
What it is:
This feature captures the essential polarity in effective management: the ability to hold people to exceptional standards without dehumanizing them in the process. It's about setting the bar high—intellectually, behaviorally, and culturally—while also recognizing the human condition behind the output.
Its impact:
Managers who emphasize only standards create burnout. Managers who emphasize only empathy create drift. It is only in their integration that trust, excellence, and growth emerge. This duality builds teams that are both resilient and remarkable.
Insights from the books:
Julie Zhuo insists that this is the most emotionally intelligent skill a manager can develop. She recounts a shift in her leadership when she realized:
“When you lean only on being nice, your team gets weaker. When you lean only on being tough, your team grows resentful.”
Her evolution came from realizing that challenge is a form of care. She tells the story of a designer she’d been soft with—until she realized her fear of hurting his feelings was actively robbing him of growth. Her guidance: “Say the hard thing clearly. Then help them rise to it.”
Claire Hughes Johnson frames this in operational terms. She advises managers to define what “great” looks like in clear language, while also “tuning your coaching to the moment.”
“The best managers are adaptive. They know when to push and when to pause.”
She also warns against emotional outsourcing: If you try to “be liked” instead of holding the line, you’re relieving yourself of discomfort—but transferring it to the team through lowered clarity and lost momentum.
Brené Brown offers a scalpel-sharp insight here.
“Clear is kind. Unclear is unkind.”
Empathy, in her framework, means honoring someone’s capacity—not assuming fragility. It means saying, “This isn't where we need to be yet, and I believe you’re capable of getting there.”
She calls this grounded confidence—the ability to stay warm while being uncompromising.
Andy Grove, ever the pragmatist, embeds this into performance management itself. In High Output Management, he writes:
“A manager’s responsibility is not to make people feel good—it’s to ensure they are producing at their best level.”
But Grove was no tyrant. His performance appraisal philosophy is to base feedback entirely on observable behavior, not character. This objectivity is the empathy—it keeps people from being subject to politics or personality wars.
Jim Collins in Good to Great introduces a related idea: the Stockdale Paradox—the ability to confront brutal facts without losing faith. Great managers don’t sugarcoat reality. But they pair it with belief that their team can meet it.
“You must never confuse faith that you will prevail in the end... with the discipline to confront the most brutal facts of your current reality.”
What to remember:
Empathy without standards infantilizes. Standards without empathy dehumanize.
The most growth-generating sentence you can say as a manager is: “This isn’t good enough yet—but I believe you can get it there.”
You have to teach what high standards mean. Don’t assume people know.
Compassion isn’t about lowering the bar. It’s about staying with someone while they learn to clear it.
6. Focus on Output, Not Just Activity
What it is:
This is the principle of managing based on results, not motion. It means evaluating team and individual performance not by how busy they are—but by what tangible value they produce. It’s the gravitational pull that prevents entire organizations from mistaking effort for progress.
Its impact:
When managers fail to distinguish output from activity, performance becomes performative. Meetings proliferate. Slack fills with signals, but none of them move the company. A focus on output sharpens prioritization, accountability, and velocity.
Insights from the books:
Andy Grove is the godfather of this idea. In High Output Management, he states the core law:
“A manager’s output is the output of their organization plus the output of the organizations under their influence.”
This insight means that your job isn’t to do work. Your job is to ensure work gets done—by improving systems, coaching individuals, removing blockers, and setting priorities.
He introduces the concept of managerial leverage: some activities (like giving feedback or setting clear goals) yield disproportionate returns. Managers should seek these high-leverage actions relentlessly.
Claire Hughes Johnson echoes this in her insistence on creating operating systems—mechanisms for measuring what matters and reviewing performance against clear objectives.
She writes:
“Your goal as a manager is not to observe busyness. It’s to align effort with purpose.”
She recommends structured operating reviews, written goal artifacts, and shared definitions of success—so that conversations are about outcomes, not opinions.
Julie Zhuo, in The Making of a Manager, shares that her early instincts were to “notice how hard someone was trying.” But over time, she saw this created perverse incentives—people working visibly hard, but not usefully.
“The shift for me was when I began to care less about how much someone was doing, and more about whether it mattered.”
She encourages managers to set output-oriented expectations—"Here’s what great looks like at the end"—and then give space to let people get there.
Eric Ries pulls this principle to the systems level. In The Startup Way, he advocates for innovation accounting—defining progress by validated learning and real outcomes, not vanity metrics.
“Speed is irrelevant if you're headed in the wrong direction.”
Focusing on output means knowing whether you're actually getting closer to value—or just moving.
What to remember:
You get what you measure. So if you measure presence, you get attendance. If you measure output, you get outcomes.
Make your expectations observable and verifiable: “What does success look like in two weeks?”
Don’t reward effort without impact. But do investigate when high effort yields low results—there may be a system failure.
Review goals regularly. Not to tick boxes—but to ask: Are these still the right outputs?
7. Strong Decision-Making
What it is:
The ability to make timely, high-quality decisions—especially under uncertainty, complexity, or incomplete information. It’s not about always being right. It’s about moving forward with clarity, logic, and resilience in the aftermath.
Its impact:
Decisions shape motion. A team that sees its manager stuck in indecision or over-analysis loses tempo and trust. Conversely, decisiveness—tempered with listening—creates momentum, confidence, and learning.
Insights from the books:
Andy Grove treats decision-making as a central managerial muscle. He makes a distinction between consensus-based and responsibility-based decisions. His rule:
“Consensus is desirable, but not mandatory. The manager’s job is to decide when consensus is blocking action.”
He also describes decision hygiene—the need to separate gathering information, debating, and deciding into clean phases. The sin, in Grove’s eyes, is looping endlessly because no one wants to commit. The manager must create closure mechanisms: “By Friday we decide. If no one owns it, I do.”
Claire Hughes Johnson also demands clarity in decision frameworks. At Stripe, she promoted “D/RI” models (Decision/Responsible/Inputs):
“If a decision doesn’t have a clear ‘D’—the decider—it’s going to rot.”
Her advice is that managers must assign the decision, define the input roles, and set the deadline. When they don’t, issues hang unresolved and erode trust. She’s also clear that good decision-making can be taught—with post-mortems, decision quality tracking, and escalation templates.
Julie Zhuo emphasizes that how a decision is made often matters more than what decision is made. Her early failure: trying to be democratic about everything. The result? Gridlock.
She writes:
“Decisions need owners. And teams need to understand who gets input and who gets to call it.”
She also describes how great managers explain the why behind decisions—even unpopular ones—to retain trust. Transparency in rationale is as important as sound logic.
Brené Brown, characteristically, gets at the emotional side of indecision:
“Leaders who avoid tough calls aren’t protecting anyone. They’re just delaying discomfort.”
She sees decision avoidance as fear masquerading as empathy. She urges leaders to “rumble with vulnerability” early—inviting discomfort into the decision space before it metastasizes into dysfunction.
What to remember:
Separate input from decision rights. Everyone can speak—not everyone decides.
Use time-bound decision cadences. If you wait for perfect information, you'll always be late.
Post-mortem your decisions—not to judge, but to learn how you decide.
The credibility of your leadership is shaped less by being right, and more by being clear, consistent, and accountable.
8. People Development
What it is:
The discipline of deliberately growing the capabilities, confidence, and career trajectories of your team. Not just supporting people. Stretching them. Sculpting them. Sponsoring them.
Its impact:
People don’t leave companies—they leave managers who stop investing in them. People development creates retention, talent density, internal mobility, and team resilience. It transforms management from supervision into multiplication.
Insights from the books:
Julie Zhuo sees this as the central arc of great management.
“A manager’s legacy is not what they achieved. It’s who they helped grow.”
She defines a strong people developer as someone who helps people see both their next challenge and their potential blind spots. She emphasizes giving stretch assignments slightly beyond current skill, paired with active coaching. Her rule of thumb:
If people succeed easily, you’re under-developing them.
If they fail repeatedly, you’ve thrown them too far.
“The sweet spot is challenge with support.”
Claire Hughes Johnson introduces the concept of scaling to the call:
“As a company scales, every role changes—even if the title doesn’t. Your job is to help people rise to that next version of their role.”
She describes tracking each team member’s trajectory across skills, behavior, influence, and ambition. She recommends quarterly career conversations—not annual—and measuring not just current output, but growth potential.
Andy Grove views people development through a systems lens. To him, training and coaching are multiplicative force functions:
“How well you train determines how scalable your team is.”
He recommends documenting common processes, using peer-to-peer teaching, and setting explicit development goals alongside performance goals. He’s obsessed with leveraging managerial time to create more competent, autonomous contributors.
Brené Brown makes development personal.
“When people know you see their potential, they try to live into it.”
She emphasizes that development is not just about skills—it’s about self-belief. The manager’s job is to create a space where people feel safe to grow, even if that growth means making mistakes publicly. She also warns:
“You can’t develop people you don’t know.”
Trust precedes stretch.
Eric Ries takes it further—suggesting that companies should institutionalize people development as part of innovation infrastructure. Cross-functional project work, experiments, rotations, and retros aren’t just for product—they’re for talent expansion.
“Learning is the only durable competitive advantage. That goes for people as much as it does for systems.”
What to remember:
Career conversations should happen more often than performance reviews.
Match development to ambition—don’t project your goals onto your team.
Document learning. Codify it. Make it shareable across teams.
If someone’s growth has stalled, ask: Have I challenged them lately? Have I supported them in that challenge?
9. Operating Rhythm
What it is:
Operating rhythm is the set of repeatable managerial cadences—1:1s, staff meetings, planning reviews, performance check-ins, and retrospectives—that give a team a shared pulse. It’s how a manager turns chaos into continuity, and urgency into cadence.
Its impact:
A strong rhythm aligns execution with strategy. It reduces decision fatigue, clarifies priorities, and makes performance visible without micromanagement. Without it, people rely on improvisation, which over time becomes inconsistency—and inconsistency becomes erosion.
Insights from the books:
Claire Hughes Johnson builds a central thesis around operating systems. She writes:
“Structure is what allows people to be creative, to be independent, to move fast without breaking each other.”
Her chapters in Scaling People offer not abstract encouragement but literal templates—for weekly reporting, quarterly planning, hiring cycles, and even how 1:1s should be framed. She insists that managers establish rituals early:
Weekly team syncs for alignment
Quarterly OKR reviews for recalibration
1:1s as a platform for performance and well-being
“If you don’t build these systems, culture becomes a side effect of random motion.”
Andy Grove offers a complementary—and more militant—take. In High Output Management, he writes:
“You must run your team like a factory: every input tracked, every process observable, every output measured.”
But this is not rigidity—it’s responsiveness. Grove advocates for a rhythm that creates early visibility of deviation. In his model, meetings aren’t bureaucracy—they’re inspection tools:
Daily check-ins to spot blockers
Regular 1:1s to transfer judgment and context
Planning cycles to force trade-offs
“If you can’t observe it, you can’t improve it.”
Julie Zhuo adds a more empathetic dimension:
“The best rituals aren’t just about getting things done. They’re about helping people feel the heartbeat of the team.”
She frames operating rhythms as the foundation for psychological predictability. When people know when decisions are made, when feedback comes, and how planning happens, anxiety drops. Her advice:
Be consistent, but update as the team evolves
Make sure the rhythm reflects current priorities
Drop what’s no longer useful—don’t calcify
Eric Ries, meanwhile, brings operating rhythm into the innovation loop. In The Startup Way, he describes companies like GE and Toyota using Lean Startup cycles as their new cadence.
“What matters isn’t speed—it’s consistent speed in the right direction.”
He proposes Build–Measure–Learn as an operating rhythm—not just for products, but for teams and leadership. Iteration isn’t a one-off—it’s a calendar discipline.
What to remember:
Operating rhythm is the nervous system of a team. Without it, communication fragments.
Rituals must be both repeatable and responsive—if it’s not helping the team adapt, it’s just inertia.
Managers must own the metronome. If they don’t, chaos will.
A good rhythm creates trust not just in people—but in time itself.
10. Adaptability
What it is:
Adaptability is the manager’s ability to adjust expectations, tactics, structures, and even principles when context shifts. It is not indecision or inconsistency. It is the competence to reorient without unraveling.
Its impact:
In fast-changing environments, rigidity becomes fragility. Teams led by adaptable managers remain agile under pressure. They’re able to pivot without panic. They respond to change with precision, not chaos.
Insights from the books:
Andy Grove famously said:
“Let chaos reign. Then rein in chaos.”
In High Output Management, he describes management as a balancing act between entropy and control. His point is: managers must tolerate disorder long enough to understand it, then act decisively to shape it.
He also viewed planning as fundamentally probabilistic:
“The most important output of a plan is the process of planning.”
In other words, adaptability isn’t reactive—it’s built into how you think.
Claire Hughes Johnson ties adaptability to managerial maturity.
“The most scalable managers are the ones who constantly adjust their own behavior before asking others to change.”
She tells stories of adapting Stripe’s hiring, performance, and compensation systems as the org matured—what worked at 150 employees became counterproductive at 1,500. Her rule:
Systems should evolve faster than culture ossifies
Managers should evolve faster than systems lag
Julie Zhuo reflects on how personal growth demanded adaptive behavior. Early on, she micromanaged. Then she swung toward over-delegation. Over time, she realized:
“There is no one-size-fits-all management style. You have to shift based on the person, the moment, and the mission.”
She recommends quarterly self-reviews where managers ask:
What has changed about my team?
Where are my current instincts not working?
What should I unlearn?
Brené Brown reframes adaptability as emotional agility.
“You can’t armor up with certainty. You need the flexibility to stay curious when the map no longer matches the territory.”
Her warning: when leaders resist change, they unconsciously create fear-driven teams. Adaptability, in her framework, means modeling psychological flexibility—especially under pressure.
Eric Ries views adaptability not as a virtue, but as a system design constraint.
“Every system must be built to pivot—or it will break when reality shifts.”
In his mind, adaptable organizations are not ones that decide to change—they’re ones that are built to detect when change is needed. The manager’s role? Build those detection mechanisms and reward their use.
What to remember:
Adaptability requires awareness of what no longer works—and the courage to kill it.
Don’t just ask what should we do differently? Ask what assumptions no longer hold?
Flexibility isn’t about surrender—it’s about responsiveness without instability.
The more senior the manager, the more adaptive modeling they must do.
11. Vision and Context Setting
What it is:
The ability to connect the team’s day-to-day work to a higher purpose and a long-term direction. But beyond inspirational slogans, it’s about context—defining why this work matters, how it fits, and where it’s going.
Its impact:
People don’t get demotivated because they’re lazy. They get demotivated because their effort feels disconnected. Vision anchors motivation. Context aligns execution. Without it, even high performers lose coherence—and the team becomes a group of task-doers, not mission-drivers.
Insights from the books:
Simon Sinek in Start With Why is relentless on this point:
“People don’t buy what you do. They buy why you do it.”
This isn't just about customers. It's true inside organizations. When people understand the "why," they navigate complexity and ambiguity better. Sinek’s point is not that vision replaces execution—but that it organizes execution. Managers who don’t contextualize leave their teams blind to trade-offs, unmoored in crises, and demotivated by abstraction.
Julie Zhuo learned this the hard way:
“I used to assume that people could connect the dots themselves. I was wrong.”
She describes realizing that her team was shipping features without understanding the product narrative or user impact. Once she started framing team goals in terms of the company’s broader journey, morale and creativity surged.
Her advice:
Start projects with a “why this matters” memo
Reference the company mission in 1:1s and reviews
Repeat the core narrative until people can say it without you
Claire Hughes Johnson introduces context setting as a management obligation, not a bonus.
“If your team doesn’t understand the company’s priorities and how their work fits in, that’s your fault.”
She emphasizes that context is how managers enable better decisions at every level. Her template:
Company priorities
Team goals
Individual responsibilities
What’s changing in the environment
With that, people stop waiting for permission—and start making judgment calls that align.
Andy Grove, true to form, makes this mechanical.
“The manager’s job is to provide context so their people can act autonomously without creating misalignment.”
He argues that the cost of misalignment increases geometrically as organizations grow. The antidote? Upstream clarity. In his eyes, even the most tactical job must be plugged into a chain of cause-and-effect that leads to the company’s real goals.
Brené Brown reminds us that vision only inspires when it’s accompanied by vulnerability:
“We trust leaders who take us somewhere—and let us see them struggling to get there, too.”
Her concept of wholehearted leadership demands that vision not be abstract—it must include the emotional stakes. Why does this matter to you, the manager? Why should it matter to us? That’s where belief is born.
What to remember:
Context is not fluff. It’s cognitive infrastructure.
Set the “why” before the “what.” Then refer back to it constantly.
Ask yourself weekly: Does every person on my team know what their work is in service of?
If people aren’t aligned, it’s likely not because they don’t care. It’s because they don’t see.
12. Delegation & Trust
What it is:
Delegation is not about offloading tasks. It’s the deliberate transfer of ownership, judgment, and decision authority to others. Trust is what makes that transfer durable. Together, they are how managers scale themselves without becoming bottlenecks or tyrants.
Its impact:
Delegation builds capacity, accelerates execution, and grows future leaders. Trust transforms direction into ownership. Without it, managers either micromanage—or abdicate responsibility. With it, they create force-multiplying teams.
Insights from the books:
Andy Grove defines managerial output as a function of leverage:
“You must delegate everything that someone else can do 70% as well as you. Your time should only go to high-leverage work.”
He distinguishes delegation with inspection from abandonment. The former builds competence and keeps you in the loop. The latter is just irresponsibility. He suggests managers explicitly state the level of autonomy expected for each task:
Tell me what you plan to do
Make the decision and tell me afterward
Make the decision and don’t bother telling me unless it goes wrong
Julie Zhuo captures the psychological arc of delegation. Early in her career, she struggled to let go.
“I felt like delegating meant giving up control, and that made me nervous. But trying to control everything made me ineffective.”
She describes learning to delegate outcomes, not tasks—telling her reports what success looked like, but letting them find the path. Her key shift: moving from Doer to Enabler.
And when trust was broken? She didn’t yank control back—she coached for recovery
Claire Hughes Johnson introduces a brilliant framework:
“Delegation without context is abdication. Context without trust is micromanagement.”
She writes that trust isn’t about assuming the best. It’s about building shared expectations, and then observing reliability. Her advice is to write down what you’ve delegated, review it weekly, and reflect on where trust needs reinforcement or correction.
Brené Brown makes it deeply human.
“Trust is built in the smallest of moments—not in grand gestures.”
She argues that trust is rarely broken by a single failure—it’s eroded by unacknowledged patterns. Delegation is an act of trust, but it also creates trust—when people rise to the responsibility, they prove their own capability to themselves and to you.
Eric Ries again pulls this up to system level. In The Startup Way, he argues that scalable companies bake delegation into their structures—not as permissions granted by managers, but as roles and rituals embedded in governance. The manager’s job? To create conditions of autonomy—clear metrics, decision rights, and feedback loops.
What to remember:
Don’t delegate what. Delegate what and why. Let others figure out how.
Start small. Build trust iteratively—through reliability, not assumption.
Track what you’ve delegated. If you’re still reviewing it the same way six weeks later, you haven’t really let go.
If you don’t trust someone, ask: Is it them—or is it me not setting expectations well enough?
13. Courage to Have Hard Conversations
What it is:
This is the ability to directly engage in uncomfortable truths—feedback, conflict, misalignment, underperformance, values violations—without avoidance, aggression, or sugarcoating. It is about saying the necessary thing, even when it’s risky or emotionally charged.
Its impact:
Avoided conversations don’t disappear. They metastasize into resentment, confusion, and dysfunction. Courageous conversation doesn’t just resolve problems—it sets a cultural tone: here, we name what’s true. And we deal with it.
Insights from the books:
Brené Brown devotes the opening of Dare to Lead to this:
“Clear is kind. Unclear is unkind.”
She unpacks how leaders disguise fear of confrontation as empathy or diplomacy—but in truth, they’re choosing their own emotional comfort over another person’s growth.
She introduces the idea of “rumbling”—staying in the discomfort long enough to find clarity:
“We want to be brave. But we don’t want to be vulnerable. And you can’t have one without the other.”
Her approach:
Start from shared values
State observable behavior, not identity
Stay curious, not accusatory
Signal belief in the person, even when their actions need correcting
Julie Zhuo reflects on her early avoidance:
“The hardest feedback conversations I had were the ones I didn’t have.”
She describes one report who drifted further and further from expectations while she kept saying “You’re doing fine” in 1:1s. When she finally delivered the truth, it was too late.
Her shift: build a culture where feedback is frequent, specific, and face-forward. It’s not about the past—it’s about what happens next.
Her tactical advice:
Frame feedback as a shared commitment to growth
Prepare your clarity ahead of time
Never deliver criticism in public—but always deliver it
Claire Hughes Johnson offers an operational lens:
“Hard conversations become easier when you’ve been clear all along.”
She stresses that the real courage is often in the prep work: expectations not set, feedback not documented, metrics not agreed on. If those are in place, the conversation becomes not personal—but professional.
She teaches managers to practice “if-then scenarios”:
If this metric isn’t hit, we talk.
If there’s a pattern in this behavior, we review.
“Discomfort is the cost of clarity. Avoidance is the tax you pay forever.”
Andy Grove keeps it clinical—but no less pointed:
“The purpose of feedback is not to make people feel good. It’s to improve performance.”
He recommends frequent, blunt performance discussions, always tied to observable work outputs. His principle: never surprise someone in a performance review. If you’ve done your job, the hard conversation has already happened, multiple times.
What to remember:
Delivering hard truths is not cruelty. It’s responsibility.
Don’t wait for perfection in your words. Truth lands best when it’s honest, specific, and steady.
You can be both direct and kind. That’s not a contradiction. It’s leadership.
If you're not having hard conversations, you're outsourcing your culture to silence.
14. Cross-Functional Collaboration
What it is:
The ability to lead and influence across teams, departments, and domains without formal authority. It is the art of aligning incentives, navigating politics, and orchestrating shared outcomes in the white space between org charts.
Its impact:
Most failures in execution don’t happen within teams. They happen between them. Managers who can’t collaborate across silos slow initiatives, fracture alignment, and allow competing priorities to fester. Those who can—accelerate everything.
Insights from the books:
Claire Hughes Johnson breaks this wide open:
“At scale, almost nothing important happens inside a single team.”
She teaches that the manager must become a translator—of goals, of context, of language. One team speaks product, another speaks ops, another finance.
Her playbook:
Build relationships before you need them
Share your goals and ask for theirs
Create escalation paths before escalation is needed
“Cross-functional collaboration is mostly pre-work: understanding who matters, what they care about, and how to work with them.”
Andy Grove embeds this in his concept of influence beyond authority:
“The output of a manager includes the output of the teams they affect, even if they don’t manage them.”
He describes managers as nodes in a network, not just heads of teams. The good ones cultivate upward, sideways, and diagonal leverage. His tactic: dual reporting, dotted lines, and regular inter-team meetings to keep friction low and information rich.
Julie Zhuo names the emotional tax:
“The hardest part of cross-team work is ego.”
She warns against turf wars, where managers guard their boundaries instead of extending them. Her insight: great managers don’t claim credit—they build coalitions. She recommends celebrating shared wins, acknowledging others’ constraints, and solving for the system, not just your sprint
Brené Brown reminds us that collaboration doesn’t work without trust at the edges:
“You don’t need to trust everyone. But you need to act in a way that makes you trustworthy.”
She suggests that inter-team respect often breaks down because of unmet expectations and silent resentments. Her fix? Overcommunicate assumptions, apologize when you misfire, and invite feedback from peers, not just direct reports.
Eric Ries reframes this structurally:
“Cross-functional collaboration should be designed into the system—not just expected from individuals.”
He promotes shared metrics, joint accountability, and co-owned goals as architecture that makes collaboration the path of least resistance. Otherwise, every project becomes a negotiation between fiefdoms.
What to remember:
Influence starts before alignment. Invest in trust, then ask for coordination.
Translate—not just your own goals, but others'. Understand their pressures and success metrics.
Celebrate joint wins. Attribution is political capital—spend it generously.
If you’re solving for your team’s success but ignoring others’ constraints, you’re not collaborating—you’re competing.
15. Resilience and Emotional Regulation
What it is:
This is the manager’s ability to stay grounded and resourceful under stress, ambiguity, and disappointment. It’s not about avoiding emotion—it’s about regulating emotion so that it doesn’t damage decisions, relationships, or trust.
Its impact:
When a manager destabilizes, the team mirrors it. When a manager stays centered—even while naming difficulty—the team feels safety, continuity, and permission to focus. This trait governs how teams weather pressure, change, and failure.
Insights from the books:
Brené Brown is unequivocal:
“Who we are is how we lead.”
She argues that emotional regulation is not a personality trait—it’s a practiced leadership discipline. Her field data shows that leaders who cannot process their own fear or frustration tend to discharge it onto others—through blame, silence, control, or deflection.
She writes: “When we deny our stories, they define us. When we own our stories, we get to write the ending.”
Her protocol for emotional resilience:
Name the emotion—don’t bury it
Write your first draft—What story am I telling myself?
Reality check—What else might be true?
Respond from values, not reactivity
Claire Hughes Johnson links emotional regulation to managerial predictability.
“People can handle tough news. What they can’t handle is inconsistency.”
She recommends setting internal “grounding rituals” before high-stakes conversations—whether it's journaling, scenario planning, or practicing delivery aloud. Her view:
Resilience doesn’t mean feeling nothing
It means managing your face and your frame so your team stays regulated with you
Julie Zhuo acknowledges that for many first-time managers, emotional spillover is common:
“I’d take a frustrating meeting, and the residue would show up in my next one.”
Her evolution was learning to reset between contexts—to avoid carrying judgment, tension, or stress from one conversation into another. She started keeping a notepad: “What happened? How do I want to enter the next interaction?”
Andy Grove approaches it tactically, not therapeutically. But it’s still present. His rule:
“A manager must always be operating—not reacting.”
Even during chaos (layoffs, crises, product failure), Grove believed the manager had to serve as the stabilizer—the person who would make decisions calmly, absorb tension, and project rational directionality.
What to remember:
Emotions are signals, not scripts. Name them. Don’t act them out.
Rituals (writing, breathing, walking, music, decompression) aren’t indulgences—they are regulation levers.
Your tone under stress becomes the culture under stress.
If you're visibly cracked every time things go wrong, your team will learn to hide problems from you.
16. Leading by Example
What it is:
The practice of embodying the very standards, behaviors, and values you expect from others. It is not performative—it is consistent alignment between words and actions, especially when no one is watching.
Its impact:
Culture is not what’s written on walls. It’s what the team experiences in moments of ambiguity. The manager’s behavior sets the upper and lower bound of acceptable conduct. People copy what you do, not what you say.
Insights from the books:
Brené Brown calls this integrity in action:
“You can’t ask people to be brave if you’re not willing to be vulnerable. You can’t demand accountability if you don’t own your mistakes.”
Her concept of wholehearted leadership demands congruence: your calendar reflects your priorities. Your reactions reflect your professed values. Your feedback reflects your own openness to growth.
“Trust is built when words and actions match—over time, in the smallest of ways.”
Julie Zhuo writes of her early realization:
“When I was late, my team was late. When I didn’t prep, my team didn’t prep. My habits were contagious.”
She began documenting her own workflows—not to show off, but to create an observable model of what “good” looked like. She focused on modeling learning, preparation, empathy, and personal growth—not perfection.
Claire Hughes Johnson emphasizes self-consistency as a management asset.
“If your standards shift based on mood, people will learn to manage your moods—not manage themselves.”
She urges managers to audit how they show up:
Do you meet your own deadlines?
Do you interrupt or listen?
Do you admit what you don’t know?
She also notes that leading by example often happens in micro-acts: replying to the junior person, documenting decisions, being on time—even when no one’s watching
Andy Grove doesn’t preach role modeling—he institutionalizes it:
“Every manager is a teacher. The question is—what are you teaching through your behavior?”
He viewed every meeting, every email, every correction as a learning signal to the team: this is what matters. This is what good looks like. This is how we work. His rule: if you’re frustrated by your team’s behavior, first check your own.
What to remember:
You’re always being watched. Not for perfection—but for consistency.
Your standards are not what you declare. They are what you enforce, and what you tolerate.
Role model not just performance—but recovery, feedback, and humility.
If you want people to go first—you must go first.
