What Does People-Centered Leadership Mean?
“People-centric” is showing up in almost every conversation about culture and talent, but we think most people misunderstand its actual meaning. The common assumption is that it translates to giving your team whatever they ask for, whether it be a raise, more flexibility, a different title, etc. If people say they want it, a people-centric organization provides it. Right? Wrong. Following that path can actually be more harmful than helpful.
Nobody Wants a Hole In the Floor
There’s an old idea in production design that’s worth borrowing here. A customer calls and says they need a hole cut in their floor. A good production person isn’t going to just grab a saw and start hacking away. They ask why. The customer explains they want to run a cord through it to plug in an upstairs lamp that’s next to their bed. Ask why again, and it turns out they want the lamp so they can read before bed. Follow that thread far enough and, rather than ripping a hole in a perfectly good floor, a light that clamps to the headboard or an e-reader with its own backlight turns out to be the better, more effective solution. The request was real. It just wasn’t the actual goal.
The space between an initial request and the problem behind it is where some of the most useful People work happens. Grant every permission with no questions asked and you’ll end up drilling a bunch of holes that nobody needs.
What That Looks Like in a People Function
That same gap shows up constantly in partnership surveys, exit interviews, and the offhand comments that never make it into either one. An employee says they want more flexibility, and it’s tempting to simply take the schedule request and run. But before changing the schedule, a People leader needs to understand what problem the employee is trying to solve. Is the issue when the work happens? Where it happens? A recurring conflict with the current schedule? A lack of clarity around how availability is measured? The answer matters because each of those problems calls for a different response.
This is the real job of a People leader, and it’s a harder one than “just listen to your people” makes it sound. It means taking requests seriously without always taking them literally and having enough pattern recognition to know when a request for a policy change is really a call for clearer communication or a faster decision process.
Listening Plus Discernment
None of this is a case for ignoring what people say. It’s the opposite, and it starts by listening closely and treating what people tell you as real information rather than a symptom to explain away. The discernment comes after, in understanding the problem behind the request and weighing potential solutions against what the organization can realistically support. A request that makes sense for one person in isolation doesn't always make sense once you consider everyone else asking for something different, or what the budget and the calendar allow. Balancing those two things is the whole discipline. Neither one on its own is enough.
That's the version of people-centric we try to practice — closer to thoughtful problem-solvingthan a wish list. It's also the entire premise behind our Talent Diagnostic. We don't start by asking what you want us to do. We start by figuring out what's actually going on. Those two things are more often different than most people expect.
