About
Strategic Gumption is an advisory practice for leaders whose important work has outgrown the operating systems that built it.
The work begins by making the business visible. Strategy becomes clear once a leader can see the system they're actually running — not the one they remember, not the one they intend. The one in front of them today.
The work is collaborative. The leader remains the author. The job is to study the terrain the leader has been too close to see, and report what's there. Decisions stay where they belong.
The shape of the work
Most engagements begin with a specific situation a leader is carrying — a department that works but underperforms what they know it could be, a role that needs to be reconstructed after a key person leaves, a company whose internal workings have become too tangled to explain.
The work begins with that situation, in plain operational terms.
Once the situation becomes visible, something else usually becomes visible with it: how the operation connects to other operations, how the system holds together, why certain patterns keep recurring that nobody can quite explain.
What started as a question about operations becomes a question about the structure underneath them.
From there, the conversation opens. The strategic questions that have felt vague — where to invest, how to grow, what to let go — become answerable. Not because the strategy has changed. Because the leader can now see the system they're actually running.
This is what altitude means here. Enough elevation that the patterns become visible, and decisions become possible.
Common situations we engage with
The shape varies. Three common ones:
Role Reconstruction. A key person leaves — sometimes after years, sometimes after decades. The role they held was real, but it was never fully written down; it mostly just evolved. Much of what they did was shaped by who they were, and the next person can't simply step into it. The work reconstructs enough of what the role actually was, what it now needs to become, and what the person who holds it next needs to be able to do.
Department Overhaul. A department works. It has been working for years. But the leader knows it's underperforming what it could be — slower than it should be, fragmented in ways that don't quite make sense, organized around how things grew rather than how they should be now. The work studies the department from the inside, surfaces what's actually happening, and works with the leader to design what needs to come next.
How Your Company Actually Works. The company runs. It has been running for years. But nobody — including the leader — can quite explain how all the pieces fit together. Decisions get made; work gets done; outcomes happen. The system holds. But the leader has lost the ability to see the system as a whole. The work maps how the company actually works, in operational detail, so the leader can see the full system again.
Engagements often begin with situations like these. The work develops from there.
Who is Steve?
In his own words:
“I immerse. I learn the basics. I learn the structure underneath the basics. Then I move on.”
That pattern has held across very different chapters.
He reports what he sees. He carries the complexity of a business long enough for patterns to surface that no one closer to it can quite catch. Decisions stay with the people who have to live with them.
How to begin
The first step is a conversation.
A leader reaches out and describes what has been on their mind. Steve listens. Questions move in both directions. By the end of the conversation, both people have a clearer sense of whether another conversation would be useful.
That's the whole of it. Nothing is committed; nothing is sold. If the work belongs together, it becomes apparent on both sides.
Our work is designed so important thinking doesn't disappear after the conversation ends.
steve@strategicgumption.comSteve on LinkedIn.