I want to tell you about a member of my team. For today’s purposes, we’ll call him “Matt”. He was not a manager, not a director, and not part of any group with the word “leadership” in its name. Matt was a service desk representative, and what he said to me in a closed conference room in Boston in 2016 changed the way I see people, purpose, and leadership; permanently and without exception.
Understanding Real Leadership: The Diagnostic Question
Ten years ago, I stepped into a new role as Vice President of IT Managed Services. New title, new responsibility, new everything. And the very first thing I did before I sat in a single meeting, before I reviewed a single report, before I did a single thing that a VP is supposed to do, I got on a plane. Two planes, actually. One to Boston and one to Sacramento. No one asked me to do that. It was not in any onboarding checklist or transition plan. My gut told me to go, and I have learned over the years that when your gut speaks that clearly, the only right response is to listen.
These were two newly acquired companies, two teams of people who, as of very recently, now worked under the same organizational umbrella I did. Most leaders in that situation would start with data, org charts, performance metrics, client retention numbers, and financials. I understand that instinct, and those things matter. But they were not what I needed first. What I needed first was to understand the people. Not their titles, not their output, not what a spreadsheet said about them. I wanted to understand who they actually were, what drove them, and why they showed up every single day to do what they did.
So I arranged a series of one-on-one meetings. One person at a time, a private conference room, just the two of us. No agenda distributed in advance, no HR representative in the room, no formal structure. Just a conversation.
Here is something important I want you to sit with. When employees were called into that conference room, one by one, to meet a VP they had never seen before, they were scared. Every single one of them. Not one person walked through that door thinking that someone finally wanted to know their story. They assumed something bad was coming: a restructuring conversation, a role elimination, or a performance concern. Trust had not yet been established, and psychological safety was nowhere near where it needed to be. I understood that walking in. I felt it in every handshake, every careful smile, every person who sat down just a little too straight in their chair. And despite all of that, I asked my one question anyway.
Why do you work here?
That was the entire diagnostic. One question. Not “what do you do,” not “what are your goals for next quarter,” not “how do you feel about the acquisition.”
Just that, “Why do you work here?”, and then I closed my mouth and listened.
Not to respond, not to evaluate, not to build a mental file on each person. I listened to understand. There is a profound difference between those things, and most people who carry the title of leader never actually experience it, because they walk into rooms with their conclusions already half-formed and their next sentence already half-written.
Leadership Insights: What I Learned from My Team
Most people gave me some version of the same answer. They were hourly employees; they were there to keep the networks running, the routers up, the servers operational, and the workstations virus-free and functional. That was the job, that was what they were paid to do, and I want to be clear that there is absolutely nothing wrong with that answer. It is honest and grounded, reflecting the reality of what these professionals do every single day. Good work, done well, matters.
But then I sat down with Matt, and Matt’s answer was something I was not prepared for.
I asked him the same question I had asked everyone else.
Why do you work here?
And without any hesitation, without any performance or positioning, he looked at me and said: “I’m trying to find a cure for brain cancer.” I looked at him like he had three heads. I said, "What are you talking about? And he said, “Our biggest client here in the Boston area is a research firm that is working to find a cure for brain cancer. If their servers go down, if their network fails, if their workstations stop functioning, their researchers cannot work. Their data becomes inaccessible. Their progress stops. And if their progress stops, the cure does not get found.” He paused for just a moment, and then he said it plainly: “So it is my job, as a service desk rep, to make sure that every single piece of their infrastructure works exactly the way it should. Because when I do my job right, I am part of finding a cure for brain cancer.”
I sat in that conference room and felt something shift inside me. Not metaphorically; I mean, I felt it physically, the way you feel it when something true and unexpected lands directly in the center of your chest. Ten years later, I remember that moment as clearly as if it happened this morning. I remember the room, I remember the light, I remember the way he said it without any pride or performance. He was not trying to impress me. He was just telling me the truth about why he showed up.
Lessons from a Service Desk Rep: Leadership Without a Title
Here is what I need you to understand about what happened in that room. I walked in as the VP. I had the title, the organizational authority, and the formal responsibility. I was the one who had flown across the country with the explicit purpose of understanding my team. By every conventional measure, I was the leader in that conversation. And yet Matt led me.
He led me without knowing he was doing it. He led me without a strategy or an agenda. He simply answered a question honestly, and in doing so, he reframed how I see work, purpose, and people. He made me ask myself whether I knew why I showed up. Whether I understood the real impact of what I did every day. Whether I was connected to something larger than my own job description. A service desk representative did that to a VP in a closed conference room in Boston, with nothing but a genuine answer to a genuine question.
That is leadership. Not a title, not a reporting structure, not an organizational designation. Leadership is what happens when one person’s clarity, purpose, and authenticity cause another person to think differently and act better. Matt did that for me, and I have no doubt he did it for the people around him every day without any of them having a formal framework for what they were experiencing. They just knew they wanted to work near him, because being near him made the work feel like it mattered.
That moment did not influence me temporarily. It did not give me a useful anecdote to tuck away for future reference. It permanently rewired how I think about the people I work with, what I look for when I sit across from someone, and what I believe a leader actually is. Matt gave me that. And he gave it to me by answering one question.
The Leadership Cycle: Show Up, Listen, Act, and Empower
There is a pattern inside the Matt story, and it is one that anyone can follow, not because it is simple, but because it is learnable. It requires discipline and intention, but not a title.
It starts with showing up before you have a reason to. Getting on the plane, nobody asked you to. Scheduling the one-on-one that nobody put on your calendar. Going to the room before there is a crisis, a performance issue, or an agenda driving you there. This is not a small thing. The act of showing up proactively, of being present with people before you need something from them, communicates a kind of respect and genuine interest that no memo, no company-wide email, and no all-hands meeting can replicate. People feel the difference between a leader who shows up because something is wrong and a leader who shows up because they actually want to understand. Be the second kind.
Then ask the real question, not the safe one and not the procedural one, but the one that cuts to the actual human being sitting in front of you.
Why do you work here? What drives you? What makes this more than just a paycheck to you?
And then, and this is where most people fail, stop talking. Completely. Stop thinking about your response, stop forming your next question, stop evaluating what they are saying against your existing assumptions. Just listen. Listen for what is underneath the words, listen for what they care about but have not been given permission to say out loud, listen for the moment when something true and unexpected comes through. Because if you ask the right question and you are genuinely still enough to hear the answer, someone will surprise you. I promise you that.
When that moment comes, when you see something in someone that nobody else has taken the time to notice, act on it. Do not file it away, do not mention it in a performance review six months later, do not wait for them to ask you to do something about it. Act. Recognize it explicitly, develop it intentionally, and when the time comes, promote from what already exists rather than hoping a title will manufacture what was never there to begin with. Matt never came to me to ask for a promotion. He never made a case for himself or told me he was ready for more responsibility. I promoted him because I had seen what he was already doing. The title of manager came after leadership was already fully in place. That is the correct sequence.
This is the cycle, and it is self-perpetuating once you commit to it. Show up. Ask deeply. Listen completely. See what others miss. Act before they ask. Watch them lead. Let them change you. Then do it again with the next person, and the one after that. That is how real leadership multiplies. That is how it creates the kind of ripple that keeps moving long after you have left the room.
Leadership Is Earned: Stop Waiting for a Title to Lead
Here is what I want to leave you with. Stop waiting for a title to start leading, and if you already have a title, stop hiding behind it. Leadership is not something handed to you in an offer letter or embedded in a job description. It does not exist because your name appears on an org chart with direct reports underneath it, and it does not disappear because your name does not. It is earned by how you show up, proven by how you listen, and demonstrated in the moments when you ask the question nobody else has asked and then actually stay quiet long enough to hear what comes back.
Matt did not need a title to lead me. He just needed someone to finally ask him why he showed up.
So I am going to ask you the same question I asked him:
Why do you work here?
Not what do you do, not what are your responsibilities, not what does your job description say. Why do you work here? If you can answer that the way Matt answered it, if you can connect your daily work to something that genuinely matters, something bigger than the role, something you would still care about even if no one was watching and no one would ever know, then you are already leading. You may not have the title yet. You may be the Matt in your organization right now, sitting at a service desk or in a cubicle or on a team where nobody has thought to ask you that question. And if that is where you are, I want you to know that the right leader will eventually sit across from you in a closed conference room and ask. And when they do, tell them the truth.
Because that truth is what leadership is actually made of. Not titles, not org charts, not the names we give to the rooms where decisions get made. The truth about why you show up. That is where it starts. That is where it has always started.
