Lessons from the rooms where things actually get built.
I do not write about leadership from a distance. Every perspective I share here was shaped inside a real environment, with real pressure, real people, and real consequences for getting it wrong.
I am not here to give you a framework you can print and laminate. I am here to share what I have actually seen, what I have actually learned, and what I genuinely believe, because I think honest reflection from people who have been in it is one of the most undervalued resources in professional life. Read what resonates. Push back on what doesn't. That is how good thinking grows.
The First Question I Ask in Every Room
Leadership · Systems · Organizational Health
I have walked into a lot of organizations over 25 years. Different industries. Different sizes. Different levels of complexity and dysfunction and ambition. And every single time, on day one, sometimes in the first hour, I ask the same question: Do we have a process people can follow? Do we have an SOP? What are the guidelines?
The reaction to that question tells me almost everything I need to know about the health of an organization.
Sometimes people look relieved, like someone finally asked the thing everyone was thinking. Sometimes they look slightly embarrassed and start explaining why the documentation is outdated or why things have been moving too fast to formalize anything. Sometimes, and this is the one that stays with me, they look at me like I asked something strange. Like the question itself revealed an expectation they had never considered reasonable. Like if I suddenly switch my language to Spanish without even noticing (I have done it before🤣 ) That last reaction is always a signal.
But the most common answer, across industries, across organization sizes, across every level of leadership, is a version of the same thing:
"We don't really have one. We've been meaning to build it. But honestly, we're getting hit from every direction right now. We don't have time. We just need to go, go, go."
I have heard that answer more times than I can count. And every time I hear it, I feel two things simultaneously.
The first is empathy, because I believe the people saying it. They are not making excuses. They are genuinely overwhelmed. They are moving fast because the demands are real, the pressure is real, and the expectation to deliver yesterday is real. I have never once met a team that was reactive by choice. Reactivity is what happens to organizations when they have been running too hard for too long without stopping to build the structure that would let them run smarter.
The second thing I feel is urgency, because what that answer describes is not a temporary state. It is a trap. And without intervention, it compounds.
Here is the thing about the go-go-go culture that nobody says out loud: It feels like momentum. It is not.
Real momentum is when an organization moves fast and in the right direction and without burning through its people to do it. What most reactive organizations are experiencing is not momentum, it is velocity without navigation. Speed without a map. And the faster you move without a map, the further you get from where you actually needed to go.
I have watched talented teams work themselves to exhaustion solving the same problems repeatedly, not because they were not smart enough to fix them permanently, but because the pace never allowed them to stop long enough to build the fix. Every week brought new fires. Every fire consumed the time that could have been spent on the system that would prevent the next one.
The cruel irony of reactive culture is this: the busyness that prevents you from building the process is caused by the absence of the process. You are too busy to fix the problem because the problem is making you too busy. Round and round. Faster and faster. And the team gets more exhausted, more frustrated, and more convinced that this is simply how things work, not understanding that it is how things work here, in the absence of structure, not how things have to work.
I have never walked into a reactive organization and found that the people were the problem. Not once. In 25 years.
What I find, consistently and without exception, is a group of capable, committed human beings who have been placed inside a structure, or the absence of one, that has set them up to fight fires indefinitely. They did not design the chaos. They inherited it, or it grew around them while everyone was too busy to notice, and at some point it became the water they swam in.
You cannot hold people accountable to a standard that has never been defined. You cannot expect consistent results from a process that has never been documented. You cannot onboard someone well when the knowledge of how things work lives exclusively inside the heads of the three people who have been there the longest, and those three people are, themselves, too overwhelmed to explain it properly!
This is not a talent problem. It is a structure problem. And structure problems have structure solutions.
The first step is almost always the hardest: you have to stop long enough to build.
I know what that feels like to say to an organization in reactive mode. I know how it lands. Stop? We cannot stop. Do you see what is happening right now?
I do see it. And I am telling you that the cost of stopping for two weeks to build the process is a fraction of the cost of not stopping for the next two years.
There is a point in every reactive organization where someone has to make a decision that feels counterintuitive in the moment, to slow down deliberately, not because the pressure has lifted but because they understand that the pressure will never lift until the foundation is built. That decision requires courage. It requires a leader who can hold the line when the urgency is screaming and the instinct is to just keep moving.
It is one of the most important decisions a leader can make. And in my experience, the organizations that make it, that pause, that document, that build the SOP, that define the guidelines, do not regret it. Not once. Not ever.
What they say, almost universally, six months later, is some version of: I cannot believe we waited this long.
Writing the process is an act of respect.
When you document how things work, when you create the SOP, establish the guideline, define the workflow, you are not creating bureaucracy. You are making a statement to every person on your team:
I thought about your success before I asked for your performance.
I cared enough to remove the guesswork. I respected your time enough to give you a map. I believed that you deserved clarity, not because it makes my job easier, but because you cannot do your best work inside a system that was never explained to you.
Structure is not a constraint. Done with intention, it is one of the most generous things a leader can give. It frees people from the exhausting, demoralizing work of constantly figuring out what they are supposed to be doing and how, so they can direct that energy toward the work itself.
The teams that perform at the highest level over time are almost never the ones operating in the most dynamic, freewheeling environments. They are the ones who know exactly what they are doing and why, who can make decisions quickly because the framework for those decisions already exists, and who trust that the foundation beneath them was built by someone who cared whether it held.
So the next time someone answers my question with "we don't have one, we're too busy going go-go-go"
I hear it differently than they mean it. I do not hear an explanation. I hear a diagnosis. And I get to work.
My recommendation to all the teams out there: Build the map. Leave it for the people who come after you. You will not regret it.
Servant Leadership Is Not Soft. It Is the Hardest Thing You Will Ever Do.
Leadership · Systems · Organizational Health
There is a version of servant leadership that gets talked about in conference rooms and leadership retreats: a warm, feel-good philosophy about putting your team first and leading with empathy. It sounds wonderful. It gets nodded at enthusiastically. And then people walk back to their desks and lead exactly the way they always have.
I understand why. The version of servant leadership that gets presented most often makes it sound passive. Gentle. Accommodating. Like the opposite of strength.
That is not the servant leadership I practice. And it is not the version I believe in.
Real servant leadership begins with a decision that most leaders never make...To actually learn who your people are.
Not their job titles. Not their performance metrics. Not their quarterly objectives. Who they are, as human beings, outside the four corners of whatever role they occupy in your organization.
Do they have a family? Do they coach their kid's soccer team on Saturday mornings? Are they training for something? Going through something? Carrying something that has nothing to do with work but is quietly affecting everything about how they show up to it?
I make it my business to know. Not in an intrusive way. In a human way. The way any person who genuinely cares about another person would, by asking, by listening, by remembering what they said last time and following up on it the next time you see them.
This is not a management technique. It is not a strategy for improving engagement scores. It is just what it looks like to treat the people around you as full human beings rather than as resources assigned to a function. And here is what I have learned, consistently, over 25 years of doing it: that is exactly where real empathy gets created. Not in the team-building exercise. Not in the annual review. In the moment you ask someone how their daughter's recital went and they realize, sometimes visibly, sometimes with a pause that tells you everything, that you actually remembered. That you actually cared enough to ask.
That moment changes the relationship. Not dramatically. Quietly. But permanently.
Conscious relationships are built in the small moments, not the big ones.
I use that phrase deliberately "conscious relationships" because there is a difference between the professional relationships that happen to you and the ones you build with intention.
Most workplace relationships are transactional by default. You interact when the work requires it. You collaborate when the project demands it. You engage when there is an agenda. And then the meeting ends and everyone goes back to their separate realities until the next agenda item requires them to reconvene.
That is not a relationship. That is a series of transactions with the same people.
A conscious relationship is something different. It is one where you have invested enough genuine attention in another person that you understand not just what they do but how they think, what motivates them, what drains them, what they are proud of, and what they are struggling with. It is a relationship where the other person knows, not because you told them but because they have felt it, that you see them as more than the sum of their deliverables.
Those relationships do not develop by accident. They develop because someone decided to pay attention. Because someone asked the question that was not on the agenda. Because someone remembered. I decide to be that person. Every time. In every team I lead.
And here is where it becomes not just human, but operationally critical...Most performance issues are not performance issues.
I want to say that again because it runs counter to how almost every organization is wired to think about this.
When someone's output drops, when a deadline gets missed, when the quality of work falls below what you know that person is capable of, the instinct in most organizations is to manage the performance. Have the conversation. Document the concern. Put them on a PIP (Performance Improvement Plan).
Sometimes that is the right response. But in my experience, more often than not, what looks like a performance issue is actually a symptom.
And the root cause, if you are close enough to the person to see it, is almost always a bottleneck that happened upstream and was never surfaced.
A process that broke down and nobody told them how to navigate it. A dependency on another team that quietly stopped delivering and left them unable to move forward. A tool that stopped working, a communication that never arrived, a decision that was supposed to come from above and never did , and rather than escalate, they absorbed it. They tried to work around it. They kept going until the weight of it showed up in their output.
If you know your people, if you have built the kind of relationship where they trust that you are not going to shoot the messenger, where they believe that telling you about a problem will result in help rather than blame, they will tell you these things before they become performance issues. They will come to you when the bottleneck first appears, not three weeks later when the damage is already done.
That early warning system is not a technology. It is not a dashboard or a weekly status report. It is a relationship. Built consciously. Over time. Through all the small moments that did not seem to matter.
Prevention is the highest form of management.
Every bottleneck I have ever caught early, every performance issue I have headed off before it became a formal conversation, happened because I knew my people well enough that something felt off before the numbers reflected it. A different energy in a one-on-one. A silence in a meeting where there is usually a contribution. A small shift in how someone responds to a question. You cannot read those signals in a person you do not actually know. And when you miss them, when the bottleneck goes unaddressed, when the person suffers quietly, when the performance finally drops to the point where it cannot be ignored, by then you are not solving the original problem. You are managing the consequence of not solving it sooner. That costs more. In time, in trust, in the human toll it takes on someone who deserved better leadership.
I refuse to manage consequences when I can prevent them. That refusal is not policy. It is personal. It comes from believing that the people I lead deserve a leader who is paying close enough attention to catch the problem before it becomes their problem to carry alone. Real servant leadership is one of the most demanding disciplines I know. It requires you to hold high standards and hold people with care at the same time, and to never confuse the two. It requires you to have the difficult conversation, give the honest feedback, make the hard call, and do all of it in a way that leaves the person on the other side feeling seen rather than diminished.
It requires you to know who your people are as human beings, not as a management strategy, but as a genuine expression of the belief that they are worth knowing.
And it requires you to stay close enough to the work, and to the people doing it, that you can see the bottleneck forming before it becomes the performance issue. Before it becomes the resignation. Before it becomes the conversation that everyone wishes had happened six months earlier.
Leading through authority is straightforward. You have the title. People comply. Simple. Transactional. And deeply limited in what it can build. Servant leadership asks something harder...
Will you invest in people even when it costs you something?
Will you pay attention even when the calendar is full?
Will you ask about the soccer game, remember the answer, and follow up the next week?
Those are the real tests. And they happen not in the inspiring moments but in the ordinary, unremarkable, Tuesday afternoon moments when nobody is watching and you have seventeen things on your list. I learned what service looks like from people who never called it leadership.
My mother did not have a framework or a title. What she had was a commitment (quiet, daily, and absolute) to showing up for the people she loved even when it cost her something. She taught me that service rendered without keeping score is not weakness. It is the highest form of strength there is.
I carried that into every organization I have ever led. Not perfectly. Not always gracefully. But consistently, because the people I work with deserve a leader who is paying attention. Not just to the work. To them.
The competitive advantage nobody talks about is this:
Organizations led by genuine servant leaders retain people longer, develop talent faster, and catch problems earlier, because the relationships are real enough that people tell the truth before the situation demands it.
That is not soft. That is the most sophisticated form of organizational leadership I know. And it starts with a simple question asked on a random Tuesday afternoon, with no agenda and no ulterior motive: How was the game this weekend? How's fantasy league? How's Bruno Boy (the dog)?