Five real-world situations. Five distinct challenges. One consistent outcome — clarity from complexity, and results that last. Select a use case below to explore the challenge, the approach, and the impact delivered.
A major enterprise program was stalling — not because of technology, not because of budget, but because the people who needed to change weren't changing. Adoption rates were critically low, key stakeholders were disengaged, and the program was at risk of delivering a system no one would use.
A large cross-functional program had entered its final deployment phase but faced widespread resistance from end users, middle management, and select senior stakeholders. Training completion was below 40%, shadow systems were proliferating, and vocal detractors were influencing broader perception of the initiative.
Interested in how this approach could apply to your organization's next major initiative?
Let's TalkA strategic enterprise client had reached their limit. After months of unresolved delivery issues, broken commitments, and escalating frustration, they submitted a formal notice of intent to cancel — a contract worth millions in annual recurring revenue. I was brought in to stop the bleed and rebuild the relationship.
The account had experienced repeated missed milestones, a lack of senior engagement, and a pattern of escalations that went unresolved. The client's executive team had lost confidence and trust. Internal teams were defensive and misaligned on the actual state of the relationship. A formal cancellation notice had been received.
Facing a high-stakes client relationship that needs immediate attention?
Let's TalkCorporate hiring constraints had created a critical staffing gap on a high-priority delivery program. Traditional approaches — headcount requests, agency staffing, contractor onboarding — were either blocked or too slow. I designed an innovative resource model that solved the problem without waiting for permission to do it the old way.
A corporate-wide hiring freeze had left a critical delivery program without the resources needed to hit its committed milestones. Headcount requisitions were blocked. Traditional staffing agency routes required approvals that would take months. The program could not slip — contractual and financial penalties were attached to the delivery dates.
Working through a resource constraint that the traditional playbook can't solve?
Let's TalkAn account with significant revenue was operating well below its margin targets. The issue wasn't revenue — it was structural cost inefficiency, misaligned pricing, and a delivery model that consumed more than it produced. I led a cross-functional team through a disciplined margin recovery effort that turned the account from a drag into a model.
The account was generating consistent revenue but persistently missing its margin targets by 15–20 percentage points. Multiple prior attempts to address this had produced short-term improvements that didn't hold. The team was working hard but not working profitably — and no one had a clear picture of exactly where the margin was being consumed.
Dealing with an account or business unit where the margin story doesn't match the revenue story?
Let's TalkAn entire portfolio was running 25% below revenue target with no clear consensus on why. Initial explanations pointed to market conditions and client factors — but an intensive review of the portfolio's hydraulics told a different story. The gap was structural, operational, and fixable. A series of focused sprints cut the gap in half within six months, returned the portfolio to target within a year, and drove it 15% above target by month 18.
A full portfolio was running 25% below revenue target with no clear consensus on why. After conducting an intensive review of the portfolio's hydraulics — mapping how revenue was generated, where it was leaking, and what was blocking it from flowing — three distinct structural root causes emerged that together explained the entire gap.
Is your portfolio carrying a revenue gap that keeps getting explained away rather than fixed?
Let's Talk