The Work
Every engagement is different.
Every engagement is different.
The pattern underneath is always the same.
Something the business normalized, and what changed once it was named.
When the System Is Working, and the Business Still Isn't
The operating system worked as intended. It had meetings, accountability, and clear roles on paper.
Decisions still routed back to the founder.
Not because the COO wasn't capable. Not because the system wasn't working. No one had clearly defined who owned which decisions without escalation.
The operating system could track accountability. It couldn't change where decisions landed.
"It's answering the question the system couldn't ask."
The Situation
A wealth management firm had a founder who was still actively guiding it. A recently promoted COO, capable and experienced, was moving toward equity partnership. The goal was clear: increase leadership, expand ownership, and reduce founder dependency.
Their operating system was designed to support this transition. They defined roles, tracked accountability, and established clear processes for escalation and resolution.
And yet the same patterns persisted. A compensation decision, a marketing direction, and a hiring call all led back to the founder. The COO carried real responsibility, but not the authority to match it. The business functioned, but it still depended on the same people it had always depended on.
The Constraint
An operating system organizes how a business runs. It creates rhythm, visibility, and a common language for accountability. What it can't do is answer who really has authority over what.
That question has to be decided separately. In most businesses, it never is.
The COO had a title and a defined role. He lacked explicit authority. He and the founder weren't aligned on which decisions he could make alone and which ones needed input. Without that understanding, the operating system could track whether things were happening. It could not define who held final decision-making power.
The system assumed the authority question had already been answered. It hadn't.
The Work
The main question became clear: what decisions did this role actually allow him to make? Where did the founder need to step in? And where was it just the system not being updated yet? What did the path to equity partnership really need, in structure, not just feelings?
Those weren't coaching questions. They were structural ones. Both sides of the system needed to be honest about what was transferred and what wasn’t.
What Changed
The operating system didn't change. The COO's title didn't change. What changed was the clarity underneath both.
Specific decisions shifted to the right level. The COO's authority became clear and defined. It was now true in practice, not just on paper. The founder's involvement became intentional rather than default. This shift ensured the system operated with accountability. Consistently..
When the Founder Is the Ceiling
An accounting firm. Two capable directors. A founder who said he wanted them to lead.
Decisions kept coming back. Not because the directors weren't ready. Because they were never allowed to.
"You don't remove them. You raise the ceiling."
The Situation
Two directors became strong leaders under a founder who was a skilled operator. Clear vision. Strong instincts. Deep trust from his team.
The founder said he wanted them to lead.
But the business wasn't moving forward. Decisions would be made, then revisited. Direction would be set, then adjusted. Ownership would be offered, then pulled back. Not overtly. Not intentionally. But consistently.
The directors felt it. Things would start to change and then settle back into the same pattern.
The Constraint
This wasn't a strategy problem, a capability problem, or a communication problem.
The founder's patterns, not his intentions, were setting the ceiling. Conflict avoidance meant hard decisions stalled. People-pleasing meant direction never stuck. And a reluctance to release control meant authority never fully landed.
The directors were in charge of results they didn’t completely control. They also had to manage a firm they couldn’t fully lead. Authority existed in theory, but not in practice.
Everything still routed back to the founder. Not by design. By default.
The Work
The work started by making the system visible, not conceptually, concretely. Decisions were made in different ways. Sometimes they stalled. Authority was often assumed, but it didn't always match where it really existed.
What became clear was this: the business had outgrown the way authority was being held. The directors were already operating at the edge of what the system allowed. The founder's patterns were the constraint.
The work had two main goals: to show founder patterns in real time and to highlight their impacts on operations, not just as critiques. It also clarified authority by defining what the directors owned. Which decisions no longer came back to the founder, and what the founder would no longer handle. The work then required holding that line. Not once, but repeatedly, until it stopped being a conversation and became how the business ran.
What Changed
The people didn't change. The founder didn't become someone else. The directors didn't suddenly become more capable than they were.
What changed was that someone beyond the founder held authority. Decisions started sticking. Ownership stopped reverting. The directors began operating with confidence grounded in consistency, not permission.
The founder noticed something new: letting go didn't weaken the business. It allowed it to function.
When the Next Generation Is Ready, and the Business Isn't
A minority partner in a growing firm. Significant ownership. A clear sense of where the business needed to go next.
He wasn't wrong about any of it.
The firm hadn't yet decided what his role in that future actually was. So the only tool he had was advocacy.
"Advocacy without authority is a slow instrument. It builds pressure, releases it temporarily, and then the cycle repeats."
The Situation
The firm was performing well under a principal who had built the business from the ground up and expected to stay for five more years. Meanwhile, a minority partner was stepping further into the business. His responsibilities increased. His views on the firm's direction sharpened. His vision for the company's future became clear.
In a system where the principal controlled hiring, investment, and structure, advocacy was the main tool available. Nothing was broken, but the business wasn't evolving the way it should have been.
The Constraint
The issue was not the minority partner's thinking. It was the gap between his vision for the firm and what he was actually authorized to decide.
He could recommend a hire, but he could not make it. He could advocate for long-term investment, but he couldn't override the focus on present profitability. He could build the case, but he lacked the power to make the decision.
That is not a communication problem. It is an authority problem.
The firm's successor lacked the authority to make decisions for its future. That structural misalignment was the constraint, even if rarely named.
The Work
The work began with naming that tension. Not every delay was structural, and we had to be honest about that. The minority partner defaulted toward cohesion. In some contexts, that instinct served the partnership well. In others, it delayed decisions that were already his to make.
But the more consequential work was structural. The principal's change didn't mean we had to wait to ask about authority. Hiring, investment, strategic decisions all lived in the present. We needed a new type of conversation. This wasn't about advocacy. Instead, it was about directly discussing how the partnership was set up and what needed to change.
What Changed
The business itself did not change, not immediately. The minority partner changed his understanding of the constraint and what he was willing to do about it.
He gained a clearer view of which decisions were truly his and which needed the partnership to change. He also better understood how his drive for unity helped the firm and when it held it back. He could navigate the conversations that would grow his role in the partnership, not just his influence within it.
The gap between his internal influence and formal authority had been the gap all along.
When Capability Isn't the Constraint
A founder had built his firm over nearly a decade and led a team that was ready. Individual coaching confirmed their capability.
The business still defaulted to him.
The team was ready, but the system had never been built to function without him.
"Individual coaching got three people clearer. Making that clarity durable required something different."
The Situation
The firm was led by a founder in his early sixties. He built the business himself and stayed continued to drive its direction. He had a respected reputation, loyal clients, and a team that had thrived under his leadership.
A more experienced team member was skilled and growing more confident in the field. Another was organized, ambitious, and openly positioning for equity partnership. These two were capable and ready for more.
The founder wanted to work differently. Less execution, more relationships. He wanted to spend less time on problems and more on strategic work. He believed this would help the firm move forward.
Everyone in the firm was pointed in the same direction. Yet the gap between intention and reality failed to close.
The Constraint
Coaching validated what we knew: the team had skill, awareness, and desire to step up.
The process also confirmed that individual clarity doesn't change a system.
The founder was still the implicit final word. Not always explicitly, not always intentionally, but consistently. The field-facing team member made good decisions. However, they often checked these against the founder's wishes. This meant they had responsibility but not full authority. The partner-in-waiting was doing genuine strategic work but operating without a defined path. And the founder, despite real intent to step back, was still the load-bearing wall. When something mattered, the employees still knew to seek him out for the final decision.
The team lacked clear authority, so power never truly shifted away from the founder.
The Work
Each person worked alone and found a similar issue. Confidence wavered without the founder around.
For the field team member, the question was straightforward. What did he really own? What would it take to act on that ownership without asking first? For the partner-in-waiting, the question was both structural and personal. What did the path to partnership call for? This was not about feelings but about clear agreements. For the founder, the toughest question was: Did he trust the team? The issue was deeper: He had to decide if he would change the system that kept him at the center of every decision.
The work wasn't about encouragement. It was about forcing the questions that good intentions had previously replaced.
What Changed
Each person developed. The field-facing team member became more willing to hold his ground. The partner-in-waiting became more explicit about what he needed. The founder realized his team wasn't the problem. Instead, he lacked the structure needed to step back and focus on what mattered most.
Individual coaching got three people clearer. Making that understanding durable required something different.
The process turned those insights into changes.
If any of these situations feel familiar, that's where the conversation starts.