A way of reading the system around the work
Hidden Dynamics Advisory is for founders who can tell the stated problem is not explaining enough.
Sometimes the strategy really is weak. Sometimes the offer is unclear. Sometimes the team is underbuilt for what the founder keeps expecting from it. But when those fixes have already been tried and the same strain keeps returning, the problem is usually organized somewhere deeper.
Every business organizes itself around something.
Sometimes that organizing force is healthy: clear roles, honest exchange, a strong mission, a shared understanding of what the work requires.
Sometimes the organizing force is strain. One person over-functions. The group waits. The founder translates everything. The client says yes to the idea and no to the change. The offer is sold from the solution while the buyer is still trying to name the pain.
What I mean by hidden dynamics
The pressures, loyalties, imbalances, habits, and unspoken agreements that shape what becomes possible inside a business, team, or founder-led container.
They are not mysterious once they are named. The problem is that most teams keep treating them as personality issues, communication issues, or motivation issues long after those explanations have stopped helping.
What this work is
Founder-facing systems advisory for moments when the obvious problem is no longer enough.
We look at the repeated behavior, the pressure points, the roles people are occupying, and the places where responsibility or exchange has drifted. Then we turn the read into practical decisions.
What this work is not
Not therapy. Not done-for-you operations support. Not a strategy engagement with better language.
The work is invitational by design. It only matters if what surfaces can be met honestly and used responsibly.
An outside read, brought back in plain language.
I pay attention to what is visible, what is repeated, what feels out of proportion, and what happens when pressure enters the system.
Sometimes that means noticing where the founder is carrying too much. Sometimes it means naming the passivity in a group that says it wants ownership. Sometimes it means seeing that the business is trying to sell the deepest truth of the work before the client can recognize the immediate pain.
My job is not to make the pattern more interesting. It is to make it useful.
What this can look like.
One founder came in convinced the problem was messaging, team buy-in, and execution. Those were real, but they were not the whole picture.
What became visible was that he had drifted further from the group than he realized. He was leading with the depth of the solution before clients had enough language for the problem. And the team had learned, quietly, to rely on his force more than their own ownership.
What changed
- The offer language moved closer to the client’s lived pain before asking them to leap to the deeper diagnosis.
- Expectations with the team became clearer, especially around ownership and self-organization.
- The founder could lead with less frustration because he could see where he had been compensating for the group.
The value was not a dramatic insight. It was a more accurate read on what had been organizing the work, and a better set of moves because of it.
Grounded in systems, transformation, and complex human work.
My background is in operational environments where breakdowns had real cost. I spent eight years in Army signal operations, then moved into enterprise transformation and large-scale business systems where the visible problem was rarely the whole problem.
Across that work, the pattern was consistent: teams trying to solve for execution while the actual constraint sat in role confusion, misaligned expectations, unspoken strain, distorted exchange, or too much depending on the strongest operator in the room.
This practice is also informed by study with Michael Spayd through The Collective Edge. His work supports coaches, facilitators, and transformation practitioners in systemic and integral approaches to change. Hidden Dynamics Advisory is complementary, not the same offering: that training informs how I facilitate, while this practice applies the lens directly with founders, teams, and founder-led containers.
What I believe
Strategy cannot fix a system organized to avoid the real problem.
Founder dependency is not impact.
What is unsaid in a system still shapes what happens there.
When the work matters, it is worth understanding what the system has been organized around before asking it to do more.