People-centric, not people-pleasing
People-centric does not mean making everyone comfortable. It means:
- I take the time to understand what each person on my team actually wants — from this job, from their career, from their week.
- I assume good intent until I have strong evidence otherwise. Then I act on the evidence.
- I treat my team's growth as a primary deliverable of my role, equal in weight to whatever we're shipping.
- I notice when someone is struggling before they have to ask for help.
- I hold a high bar, because lowering the bar is itself an act of disrespect.
It does not mean:
- Avoiding hard conversations because they will be uncomfortable.
- Letting performance issues drift because the person is well-liked.
- Mistaking my desire to be liked for my obligation to lead.
What I believe
The work happens through people, or it doesn’t happen. Strategy, architecture, process — all of it gets executed by humans choosing to do their best work, or it dies on the page. My first job is the people. Everything else follows from that.
Trust is built in small moments, lost in large ones. I'd rather build it slowly and keep it than perform it quickly and break it.
Clarity is kindness. Vague feedback, unclear expectations, and unspoken concerns are not kindness — they are the appearance of kindness, which is worse, because it deprives people of what they need to grow and succeed.
Teams should be the ones doing the work, including the thinking. If decisions all flow through me, I have built a bottleneck, not a team.
The 3 A's: Autonomy, Authority, Accountability
The teams I want to build operate under three commitments, and they are inseparable. Each one only works in the presence of the other two.
Autonomy
People decide how to do the work. I tell them the what and the why, and I get out of the way on the how. If I find myself dictating implementation, I check whether I've actually failed to communicate the goal.
Authority
People have the power to make and execute decisions in their domain without needing my permission. Authority that has to be re-confirmed every time isn't authority — it's the illusion of it. My job is to define the scope of authority clearly, then defend it when it's challenged from outside.
Accountability
People own the outcomes of their decisions — good and bad. When things go well, the credit goes to them publicly. When things go badly, we look at what happened together, and the lessons are theirs to own. Accountability without blame, but accountability all the same.
What this requires from me
- Spending real time defining context, goals, and constraints — not just tasks.
- Letting decisions I would have made differently stand, as long as they're inside the scope of authority and not catastrophic.
- Resisting the urge to rescue people from the natural consequences of their choices. The lesson is worth more than the rescue.
- Pushing back when the org tries to undermine the team's authority from above or beside.
What this is not
- "You decide" is not the same as "I'm not paying attention." (Abdication)
- Repeated failures of judgment in a domain mean we revisit fit, scope, or growth — honestly. (Not a free pass)
Radical Candor as the connective tissue
The 3 A's only work if feedback flows freely in all directions. That's where Radical Candor comes in. Care personally; challenge directly. Both, always. I aim to be in that quadrant, and I name the others honestly.
Radical Candor
Care personally + challenge directly
Both, always. This is the aim.
Ruinous Empathy
Caring without challenging
My most likely failure mode as a people-centric leader — softening a hard message until it disappears, delaying a difficult conversation because the relationship matters.
Obnoxious Aggression
Challenging without caring
Sharp without warmth. I'd rather err toward empathy than land here, but neither is the goal.
Manipulative Insincerity
Neither caring nor challenging
The worst quadrant. Saying what's easy in the moment because I don't care enough to do the harder thing.
↑ Care personallyChallenge directly →
How this shows up in practice
- I ask for feedback before I give it. I won't ask people to receive what I'm not willing to receive myself.
- I praise specifically, often, and in public. Generic praise ("great job") is noise; specific praise ("the way you de-escalated that thread on Tuesday was leadership") is signal.
- I deliver critical feedback in private, quickly, and specifically. I don't save it up for reviews. By review time, nothing should be a surprise.
- I name the dynamic when it's happening. "I think I've been too soft on this — let me be direct." Or: "That came out sharper than I meant. Let me try again."
- I assume the other person can handle the truth. Pre-softening is its own form of disrespect.
The contract
This is the section I can share — and intend to share — with a new team: what you can expect from me, and what I need from you in return.
What to expect from me
- I will spend the first weeks listening. I won't make big changes early. When I do start making changes, I'll explain why.
- I will be in regular 1:1s with you, and they are your time. Your agenda comes first. If I have something I need to drive, I'll flag it ahead.
- I will tell you what I think, including when I disagree. I will tell you quickly. I will tell you specifically. I will tell you in private when it's critical and in public when it's praise.
- I will defend your authority when it's challenged from outside the team. If I disagree with a decision you made inside your scope, I'll bring it to you directly, not around you.
- I will give credit publicly and take responsibility publicly when things go wrong. That is the deal.
- I will make mistakes and name them when I do. I will not pretend to know things I don't, and I will not punish you for catching me on it.
- I will protect your time and focus as if it were my own. Meetings I can absorb, I'll absorb. Context I can translate, I'll translate.
- I will be honest about your performance and your growth. You will never learn from me at a review that you've been struggling for six months. That would be a failure of mine, not yours.
What I need from you
- Tell me what you actually think, especially when you disagree with me. Silence is the most expensive thing on a team.
- Tell me early when something is going sideways. Surprises cost more than bad news.
- Tell me what you want from your career, and update me when it changes. I can't help you get somewhere I don't know you want to go.
- Push back when I'm encroaching on your authority. I will overstep sometimes. Name it.
- Give me feedback. Specifically, frequently, and including the things you wish I did differently.
- Assume I'm doing my best with imperfect information. I will extend the same to you.
Non-negotiables
The hard lines. These don't move.
- NONo public criticism of a team member, ever. Praise in public; criticize in private.
- NONo blame for a decision made in good faith inside someone's scope of authority. We learn from it. We don't punish it.
- NONo talking about people behind their backs in ways I wouldn't say to them. This applies to my team, my peers, and my manager.
- NONo surprise in performance conversations. Anything I say at a review, the person has heard from me already.
- NONo participation in dynamics that exclude, demean, or punish people for who they are. I will name it and address it, even when uncomfortable.
- NONo pretending to know things I don't. I'd rather say "I don't know — let me find out" a hundred times than be wrong with confidence once.
Where I'll be tested
This is one leader's honest account of his own likely failure modes, offered as something you can adapt to name your own.
The honest list of my likely failure modes, so I can spot them in myself and so the people closest to me can call them out.
Ruinous empathy
I will sometimes soften feedback past the point where it lands. If you sense this happening, ask: "What's the version of this you didn't say?"
Slow on personnel decisions
I care about people, and that can translate into hoping a struggling team member will turn it around longer than is fair to them or to the rest of the team.
Over-investing in consensus
Not every decision needs everyone to feel great about it. Some need to be made, communicated, and moved past.
Hiding in 1:1s
When the strategic work feels overwhelming, I will retreat into the people work because it's where I feel most confident. The team needs both from me.
Absorbing too much
Taking on context, meetings, and noise to "protect the team" until I am the bottleneck I was trying to prevent.
The remedy for all of these is the same: people who know me well enough to name it, and a habit of asking.
A living document
I revisit this once a quarter. I update it when I learn something. I share the relevant parts with new teams. If any of the above ever stops being true of me, I owe it to the people I work with to either change my behavior or change the document — but not to leave the gap between them unspoken.