
Invisible Leadership: The Work You Don’t See Often Matters Most
Updated: Sep 28
On invisible work, creating the conditions for teams to succeed, and redefining what productivity looks like as a leader.
The more senior I’ve become as a leader, the less my best work looks like something I made.
Earlier in my career, productivity was much easier to see. I designed the thing. Created the deliverable. Solved the problem. At the end of the day, there was something tangible I could point to and say, “I did that.”
Leadership is different.
Some of my most valuable work now happens in a conversation, a question, a connection between two workstreams, or advocating for something my team needs.
There isn’t always an artifact at the end. But there can be an outcome.
And I’ve learned that those aren’t the same thing.
Rethinking What It Means to Be Productive
I’ll admit it: days filled entirely with meetings are still hard for me.
I like making things. I like solving problems. There’s something satisfying about ending the day with something tangible that didn’t exist when the day started.
But I’ve had to rethink how I measure productivity.
Instead of asking, “What did I produce today?” I try to ask: What was the outcome of the time I spent?
Was the ROI of that meeting worth an hour of everyone’s time?
Did we make a decision that had been holding up a team?
Did someone leave with more clarity?
Did we identify a connection between two pieces of work that could prevent duplication or create a better experience?
Sometimes a document that takes three hours to create is incredibly valuable. And sometimes one insight in a 30-minute conversation changes the direction of months of work.
That has changed how I think about leverage. As a leader, the highest-value thing I do may take only a few minutes if it improves the quality of a decision, removes a barrier for several people, or helps a team avoid solving the wrong problem.
Productivity isn’t always about how much we produce. It’s about the value created from the time and energy we invest.
Connecting the Dots Is Part of the Work
One of the things I spend a lot of time doing as a leader is connecting dots.
As organizations get larger, it’s easy for teams to become deeply focused on the problem directly in front of them. That’s not a bad thing. We want teams close to their customers and focused on delivering meaningful outcomes.
But it also means they don’t always see what’s happening three teams over.
A similar customer problem might be showing up somewhere else. One team may be solving something another team has already explored. A decision in one part of the product could create an unintended experience somewhere else.
Someone has to be looking across those boundaries.
At a certain level of leadership, seeing the system becomes part of the job. The value isn’t knowing every detail. It’s recognizing patterns, dependencies, repeated problems, and opportunities that are difficult to see from inside one team.
Sometimes the most useful thing I can do isn’t provide an answer. It’s simply say: “You two should talk.”
That connection might take five minutes. The value it creates can be much bigger.
Build the Scaffolding, Then Get Out of the Way
One of the hardest transitions in leadership is learning that helping doesn’t always mean doing.
When someone brings me a problem, my instinct is often to start solving it with them. That’s part of being a designer. We like problems.
But if I always provide the answer, I’m not necessarily helping the team grow.
When I can, I try to ask questions instead:
What do we know?
What don’t we know?
Who could help us understand this?
What would you try?
What do you think we should do next?
Then let them go figure it out.
My role is to create enough structure and scaffolding that they can confidently explore the way forward—not to map every step for them.
That scaffolding might be context, decision boundaries, access to the right people, a framework, a question, or simply confidence that they have room to make the call.
If I always have to be in the room for the team to succeed, I haven’t really empowered the team.
Sometimes You Run Defense. Sometimes You Let Them Swim.
Creating psychological safety is incredibly important to me, but I’ve learned that protecting a team doesn’t always mean shielding them from difficult situations.
Sometimes leadership means running defense—absorbing organizational noise, pushing back on something unreasonable, or creating enough space for the team to focus.
Other times, protecting someone too much can actually prevent them from growing.
There are moments when I need to let someone jump into the deep end. The difference is that I’m still standing at the edge of the pool.
They get to swim. They get to struggle a little. They get to figure out what they’re capable of. And if they really need it, I’m there to throw them a line.
That balance changes constantly. The person, the situation, and the level of risk all matter.
Leadership judgment lives in that balance. Too much protection creates dependency. Too little support can turn a stretch opportunity into failure without learning. The goal is enough safety to take a real risk and enough ownership for the growth to belong to them.
Leadership isn’t knowing that you should always protect or always push. It’s knowing which one the moment calls for.
I Shine When They Shine
One of my favorite parts of leadership is watching someone on my team do great work and making sure other people know they did it.
If someone had the insight, I want their name attached to it. If they created the work, I want them presenting it when possible. If they stretched into something new and succeeded, I want people to see that growth.
I shine when they shine.
That’s not just about giving credit. It’s part of developing people.
Visibility creates opportunities. Presenting the work builds confidence. Being recognized for an idea helps someone begin to see themselves differently.
It also changes how the organization sees them. Sponsorship is often this practical: creating opportunities for someone’s judgment and impact to be visible before they need the next opportunity.
Sometimes one of the most valuable things a leader can do is step slightly out of the spotlight so someone else can step into it.
But Invisible Leadership Has a Limit
There’s a tension here that I continue to think about.
A lot of leadership work happens quietly. Coaching conversations. Advocacy. Connecting people. Creating structures. Navigating issues before they reach the team.
But being completely invisible isn’t necessarily good leadership either.
If I’m invisible, the team can become invisible.
Senior leaders need to understand what the team is accomplishing, where we’re creating value, what we’re learning, and why the work matters.
The balance, for me, is making the outcomes visible without needing to make myself the center of them.
That means translating the team’s work into impact: what changed for customers, what decision became possible, what risk was reduced, what we learned, and what capability the organization now has that it didn’t have before.
I don’t need credit for every connection or conversation that helped something happen. But I do need to make sure the organization can see the impact of the team.
That’s a fine line to walk.
Maybe the Outcome Is the Artifact
As I’ve grown as a leader, I’ve had to become more comfortable with the idea that my work won’t always leave behind something tangible.
Sometimes my work is a question that helps someone see the problem differently.
Sometimes it’s connecting two people who didn’t know they were solving related problems.
Sometimes it’s advocating for someone when they aren’t in the room.
Sometimes it’s giving someone enough structure to take on something they weren’t sure they could do.
And sometimes it’s deliberately doing nothing—because the team doesn’t actually need me.
Those things don’t always show up neatly on a roadmap or a list of accomplishments.
But I know I’ve had a good day as a leader when the structures and scaffolding I’ve helped put in place allow someone else to succeed. To own the work. To grow. To shine.
Maybe that’s the artifact.




Really enjoyed this, Susan. The idea that leadership isn’t always about creating something tangible, but about creating clarity, connecting the dots, and creating the right conditions for others to succeed, really resonated with me. Especially the point about making the team’s impact visible without making yourself the center of it. A great reminder that sometimes the outcome is the real artifact.