Leadership is not defined by who can redirect a problem fastest. It is revealed by who helps move it forward
At some point in every career, a problem will land in front of you that does not technically belong to you.
It may arrive through the wrong ticket queue, appear in an email sent to the wrong department, or surface during a meeting where everyone immediately begins deciding who should handle it. The easiest response is also the most common…
“That isn’t ours.”
Sometimes that statement is completely accurate. The system may belong to another department. The affected customer may be supported by another team. The decision may sit outside your authority. You may have neither the access nor the expertise required to resolve it.
But identifying that a problem belongs somewhere else is not the same as helping solve it.
You can be technically correct and still contribute nothing.
Throughout my career, I have found that the people who become truly valuable to an organization are not necessarily those who know every answer. They are the people who create forward movement. When a problem crosses their path, they leave it in better condition than they found it, even when they are not its ultimate owner.
They own the outcome, even when they do not own the problem.
The Difference Between a Handoff and Passing the Buck
A legitimate handoff transfers a problem with enough context for the next person to act. Passing the buck merely transfers the inconvenience.
Passing the buck sounds like this…
“Wrong department. Sending this to someone else.”
A productive handoff sounds more like this…
“This appears to involve the network path rather than the user’s workstation. Here is who is affected, what they are experiencing, when it began, what we tested, what changed the behavior, and who can provide any additional details.”
Both responses move the request to another team, but only one moves the problem forward.
A good handoff might include:
- A concise description of the issue and its business impact.
- The people, systems, and locations affected.
- What has already been tested or ruled out.
- Relevant logs, screenshots, ticket numbers, or timestamps.
- The condition that causes or resolves the behavior.
- The people who can answer the remaining questions.
- A reasonable hypothesis, clearly identified as such.
You do not need to conduct a forensic investigation into every misplaced request. You simply need to contribute what you reasonably can. Five thoughtful minutes can prevent several people from repeating the same discovery process and can shorten the path to resolution by hours… or days.
That is not overstepping. That is organizational awareness.
Ownership Is a Behavior, Not a Box on an Org Chart
Many organizations talk about ownership as though it begins and ends with formal responsibility. We assign systems, queues, projects, and processes to particular teams, and those boundaries are necessary. Clear accountability prevents confusion and ensures that work has a home.
But ownership is also a behavior.
It is the decision to help create clarity when everyone else is creating distance. It is the willingness to make the phone call, gather the missing detail, connect the right people, or explain why the problem appears to belong somewhere else.
You may not own the infrastructure, but you can own the quality of your handoff.
You may not own the application, but you can own the accuracy of the information you provide.
You may not own the final resolution, but you can own whether your involvement creates momentum or delay.
That mindset changes how people experience working with you. Instead of becoming another stop in a frustrating chain of referrals, you become someone who reduces friction. Over time, people learn that when something reaches you, it will become clearer, more organized, and closer to resolution.
That is how trust is built.
“Not My Job” May Be Correct, and Still Not Be Good Enough
There are situations in which “not my job” is an important boundary. No one should make unauthorized changes, assume authority they do not have, or conceal a problem by improvising outside their expertise. Responsible professionals know when to stop and engage the appropriate owner.
But too often, “not my job” is not a boundary. It is an escape hatch.
It becomes a way to avoid effort, uncertainty, accountability, or interruption. The person recognizes the problem, knows where it should go, and may even know something that would help, but contributes none of it.
The result is predictable… the next team receives an incomplete request, asks for information the first person already had, and sends it back. The issue circles through email threads and ticket queues while everyone remains busy and nothing gets accomplished.
The customer, employee, or business leader who needs help does not care how accurately the organization distributed its internal frustration. That person cares whether the problem was resolved.
From their perspective, there is no meaningful distinction between departments. There is only the organization.
Initiative Should Create Momentum, Not Permanent Ownership
There is an important caution here… helping with a problem does not mean adopting it forever.
One of the hidden risks of being dependable is that initiative can be mistaken for ownership. Because you took the time to organize the issue, people may begin treating you as its coordinator. Because you made the introduction, they may expect you to schedule every follow-up. Because you provided useful context, they may continue asking you questions that should be directed to the actual owner or affected party.
That is not collaboration. It is responsibility drifting toward the person most willing to help.
A strong handoff should transfer ownership, not create an endless obligation for the person who was conscientious enough to assist.
The boundary can be both helpful and clear…
“Here is everything I was able to gather, what we have already checked, and who can provide additional information. This now requires investigation by the team that owns the system. I remain available if something specific is needed from my area.”
That is not passing the buck. It is responsible facilitation followed by appropriate accountability.
Why I believe this matters…
- Ownership means helping the issue progress.
- Collaboration means contributing what you reasonably can.
- A handoff means transferring responsibility with useful context.
- Accountability means the correct owner accepts and drives the work.
- Deflection means repeatedly pushing the investigative burden elsewhere.
Healthy organizations need all four of the first behaviors and far less of the fifth.
Leaders Remove Friction
Leadership is often discussed in terms of vision, influence, and decision-making. But much of everyday leadership is less dramatic. It consists of removing friction.
Leaders translate vague concerns into actionable problems. They make sure questions reach the people who can answer them. They prevent context from being lost between teams. They resist the temptation to minimize an issue before understanding it. They do not use organizational boundaries as an excuse for organizational paralysis.
Most importantly, they do not stand at the edge of a problem explaining why someone else should move first.
This behavior is not limited to managers. Some of the best examples of ownership come from individual contributors who have no authority over anyone involved. They lead by being useful. They demonstrate judgment, curiosity, and follow-through. They become the people others trust when the answer is not obvious.
Being an asset does not mean having all the answers. It means consistently improving the situation.
Leave the Problem Better Than You Found It
A simple principle has served me well –> Whenever a problem crosses your path, leave it in better condition than you found it.
You might solve it completely. You might identify the correct owner. You might uncover one fact that changes the investigation. You might document what has already failed so the next person does not waste time repeating it. You might simply bring the right people together and make the objective clear.
Every one of those actions has value.
The opposite also compounds. Every vague forward, incomplete ticket, unanswered question, and unnecessary redirect adds friction. Multiply that behavior across dozens of employees and hundreds of requests, and the organization becomes slower… not because its people lack ability, but because too much energy is spent avoiding ownership.
Organizations become effective when people stop asking only, “Is this mine?” and begin asking, “What can I contribute?”
You do not need to own every system, process, department, or final decision. But whenever a problem crosses your path, you can choose clarity instead of confusion, momentum instead of delay, and contribution instead of excuses.
Own what you can. Make the handoff useful. Respect the boundary. Then expect the rightful owner to carry it forward.
That is how problems get solved. It is how trust is earned. And it is how people distinguish themselves as true assets to an organization
