Building a Repeatable System for Execution and Change
A look at what helped a fast growing lender stay aligned as it scaled.
Executive Summary
Growth is not a single moment. It is a discipline. As organizations expand, launch new initiatives, or move through periods of change, the gaps in how work gets done become more visible. Teams feel the strain. Leaders feel the pressure to keep momentum without losing alignment.
This Case Note looks at a company that reached that point. A retail mortgage lender had grown quickly through an entrepreneurial culture and a focus on speed. As the organization scaled, the way work was being managed could not keep up with the pace of the business. They needed structure that supported growth without slowing it down.
I was brought in to help the company build a system for execution and change that could scale with them.
The Challenge
The company had expanded rapidly over nearly two decades. What began as a small, fast moving lender had become one of the top three in the nation. The decentralized structure that once fueled growth was now creating friction. Branches operated independently. Initiatives competed for attention. Teams were working hard, but not always together.
Leadership recognized the pattern. They needed a way to align strategic priorities, coordinate work across functions, and maintain the pace that had defined their success. The challenge was to introduce structure without losing the entrepreneurial spirit that made the company what it was.
This is the kind of moment where organizations benefit from someone who can understand the culture, see the gaps clearly, and help build a system that fits the way people actually work.
My Approach
I started by listening. I spent time with leaders and teams to understand how work moved through the organization. I paid attention to where decisions were being made, where projects slowed down, and where people were compensating for a lack of structure.
From there, we designed an Enterprise Project Management Office that fit the company’s rhythm. The goal was not to impose a rigid framework. It was to create clarity, visibility, and alignment so the organization could scale without losing its identity.
The work included:
creating a structured way to prioritize initiatives
building processes that supported collaboration across branches
introducing tools that made work visible and predictable
helping leaders turn down low value work with clarity and confidence
establishing a shared language for execution and change
The purpose was simple. Give people a system that helps them do their best work.
Why This Kind of Support Helps
When organizations grow quickly, the work becomes more complex than the structure around it. People feel the pressure to keep up, but they do not always have the tools or clarity they need.
My role in moments like this is to help teams see the work more clearly. I focus on alignment, communication, and the small signals that show whether an organization is moving together or drifting apart. I help leaders create systems that support growth instead of slowing it down.
The certifications and experience matter, but they are not the point. What matters is helping people build a way of working that they can sustain.
Case Notes: Scaling Success With an Enterprise PMO
Background
A retail mortgage lender grew from founding to one of the top three lenders in the country in less than twenty years. The culture was entrepreneurial and fast moving. That speed helped the company grow, but it also created challenges as the organization became larger and more complex.
What Was Unclear
The company knew it needed more structure, but it was not obvious what that structure should look like. How do you introduce consistency without slowing people down. How do you align work across dozens of branches that are used to operating independently. How do you maintain the pace of innovation while improving coordination and visibility.
These were the questions the leadership team was wrestling with.
What I Paid Attention To
I looked closely at:
how initiatives were prioritized
where work was getting stuck
how teams communicated across functions
what information leaders needed but did not have
where the lack of structure was creating unnecessary strain
I also paid attention to the culture. The company valued speed, autonomy, and innovation. Any system we built had to support those values, not replace them.
What Helped
We designed an Enterprise PMO that gave the organization a clear way to manage strategic work. The structure included:
a framework for prioritizing initiatives
standardized processes that supported collaboration
tools that improved visibility across teams
a portfolio management approach that focused attention on the work that mattered most
The goal was not to slow the organization down. It was to help it move with more intention and less friction.
What Changed
The Enterprise PMO became a critical part of the company’s continued growth. It helped maintain the entrepreneurial spirit while adding the visibility and consistency needed to operate at scale. The organization became more aligned, more coordinated, and better equipped to execute on its strategic goals.
The company did not lose its identity. It strengthened it.
Closing
If your organization is growing quickly and the work is starting to feel heavier than the structure around it, I am always open to a conversation. Sometimes a short discussion is all it takes to see the situation more clearly.
If you’re navigating a moment like this and want to talk it through, I’m always open to a conversation.