The visible kind shows up cleanly on a line. The other kind, the judgment that holds a team together and the connective work that keeps everything upright, usually lives trapped in a few people's heads, where it can't scale and slowly erodes. That second half is where I work. I take what's invisible and fragile in an organization and build it into something the whole place can run on.
Most organizations are built to see and reward one kind of contribution: the kind that fits cleanly on a line. The deal closed, the number next to a name, the thing the spreadsheet already had a box for. That makes sense, because it's measurable, and measurable is reassuring. But the work that actually makes an organization function often doesn't fit that box. The system that lets everyone else move faster. The problem caught before it became a crisis. The judgment in one person's head that the whole team quietly runs on. When attributable revenue is the only thing you measure, all of that becomes invisible by default. Not unimportant. Invisible.
And here's the part I think matters most: invisible work is fragile work. It stays trapped in the few people who happen to carry it, unsupported and unable to scale, right up until those people get stretched too thin or move on and take it with them. Nobody files a report that says we lost the thing holding this together. You just notice, eventually, that everything depends on a handful of people who can't be everywhere at once, that the work has gotten more brittle, and that you can't quite name why.
The dashboard stayed green the whole time, because half the picture was never on it.
The work isn't to admire that layer, and it isn't only to name it, though naming it is usually a relief no one was expecting. The real work is making it structural. I take the expertise that lives between people's ears and the judgment that holds a team together, and turn it into something the organization can run on without depending on any one person to carry it.
The deliverable changes depending on what's actually needed: a framework, a curriculum, brand architecture, an AI tool, the source-of-truth documentation everything else hangs on. Different outputs, same underlying move, which is turning work that was invisible and fragile into something visible, reliable, and able to outlast the people who originated it.
I tend to hold the strategy and the build in the same hand. The thinking only counts once it actually runs.
I don't think good strategy is intuition with a confident voice. Mine follows a discipline I call the Strategic Engagement Arc: six phases grounded in how people and organizations actually take in information, decide, and act, so the work doesn't end up fighting how your team already moves.
That's the shape of it. The longer version is really a conversation, not a paragraph.
Here's what I keep finding. When you build for the people and the systems at the same time, you stop having to choose between caring for your team and chasing growth, because the first tends to produce the second. The scale everyone's actually after usually lives downstream of getting this right. It's a less obvious route, and I think it's the more durable one.
So if you're heads-down on the main thing, as you should be, but you can feel there's another layer underneath that quietly decides whether you scale or stall, that's the work I do.
If that's the tension you're sitting in, I'd love to talk.
I work with mission-driven organizations, agencies, and leaders navigating real complexity.
Tell me what you're wrestling with, especially the thing that doesn't sit neatly on anyone's dashboard. We can figure out together whether I'm the right person for it.