I’d done everything right. I gave my source everything it needed. Make, model, specs. It came back confident. SATA. So I bought SATA.

I cloned the old drive. Installed the new one. The case slid back in place. It booted clean. Everything that could go wrong went right.

And then nothing worked.

Shortcuts were missing. Programs wouldn’t load. It took one click in File Explorer to understand what had happened: the drive I’d disconnected to install the new one was my data drive. Not the OS drive. Not the one filling up. My C: drive was an M.2 stick tucked behind the motherboard. Right advice, but wrong drive.

The execution was clean. The diagnosis was wrong.

I’ve been in enough organizations to know what that moment feels like at scale. The campaign that launched on time and landed flat. The restructure that ran smoothly and solved nothing. The new software that got adopted and didn’t fix the problem. Everyone did their job. The thing still didn’t work.

Bad advice isn’t neutral. It’s worse than no advice.

No advice leaves you uncertain. Uncertain people ask more questions. They slow down. They look around. Uncertainty is uncomfortable, but it’s honest. It keeps you in the problem longer.

Bad advice closes the loop prematurely. It feels like clarity. You have a diagnosis, a plan, a part on the way. You stop asking questions because the question feels answered. And the better you are at execution, the deeper you get before you realize the premise was wrong.

The most dangerous moment isn’t when things go badly. It’s when everything goes right and nothing works.

The hard question, and the one that rarely gets asked, isn’t “what’s the solution?” It’s “are we solving the right problem?”

That question requires something most advice-giving skips. It requires sitting with the problem long enough to understand it. Not pattern-matching to a familiar answer. Not reaching for the closest available solution. Actually asking: what’s really going on here?

For me, it took pulling the service manual. Slowing down after the pivot didn’t work. Reading the actual specs of the machine in front of me. That’s when I found the extra SATA port I didn’t know existed. And realized the work I’d written off as wasted was actually done. The clone was good. It would boot from the new location. The false start wasn’t a failure. It just wasn’t useful yet.

The fix came. But only after I stopped executing and started diagnosing.

Here’s what I’ve come to believe after years of working inside organizations that were stuck: most execution problems are diagnosis problems in disguise. The plan is fine. The team is capable. The effort is real. But somewhere upstream, someone answered a question nobody fully asked.

What you actually need — before the plan, before the solution, before the confident advice — is someone willing to ask whether you’re working on the right drive.

So I asked for help. The advice was confident. I provided make, model, specs, everything it needed.

It told me SATA. I bought SATA.

I cloned the old drive. Installed the new one. The case slid back in place smoothly. It booted up without a problem. Everything that could go wrong went right.

But then shortcuts were missing and programs didn’t load. The drive I replaced was my data drive, not the OS drive.

My C: drive was an M.2 stick drive, not SATA. The execution was clean, but the diagnosis was wrong.

I sat with that for a minute. The frustration of it. Not just the mistake. The specific quality of a mistake that only happens when you do everything right.

Eventually I pulled the service manual. Found an extra SATA port I didn’t know existed. Ordered a data cable and a power splitter. And figured out that the clone I’d written off as wasted work would boot fine from the new location.

The false start wasn’t wasted. It just wasn’t useful yet.

But the thing I keep coming back to isn’t the pivot. It’s the moment before it. When everything worked and nothing was fixed.

Confident advice isn’t the same as correct advice. And the gap between them is usually invisible until it isn’t.

There’s a version of that I’ve always called discipline. Show up when you said you would and finish what you started. Don’t improvise when you committed to something. Eliminate decision fatigue.

But at one point this weekend, I had a window and a choice. The plan said wait. Something quieter said go.

So I went.

It felt strange. Not wrong. Just unfamiliar. Like a muscle I don’t use enough.

After a bit of discomfort the muscle felt better for having been used. The drive would still get me home, but under the lights it was also something new.

Often the plan stops being a tool and starts being a rule. How often risk avoidance looks like discipline from the inside. How often we stay in our processes, procedures, and the way we’ve always done it, not because it’s the right call, but because leaving wasn’t in the plan.

Rigidity dressed up as discipline is still rigidity.

Worth noticing.

So far, I’ve been using my two modern Lodge skillets, but last weekend I stumbled across a late-period era Wagner at an antique shop. Probably from the 60s or early 70s. Not quite vintage, but older than I.

It wasn't in bad shape. No warping, no cracks. Just decades of carbon and old seasoning built up in uneven layers. Just rough and dark and a little neglected looking.

Someone had loved that pan.

There’s a whole process for restoring a pan like that: lye bath or Easy Off with the yellow cap and a day in a garbage bag to release the old carbon and seasoning, a good scrub, maybe a vinegar bath for rust. Followed by a good wash with soap and water, a towel dry, and a spell on the burner to completely dry things out and open the pores in the iron.

That’s all procedure. Written and repeatable.

What was unexpected, and what struck me, was the look of the bare iron.

Specifically the circular tooling marks from the craftsperson who pulled that skillet out of its sandy mold, hooked it to a lathe, and expertly machined it to a smooth finish. That’s something you don’t see in modern skillets. That’s a direct connection from that person’s labor, though the stovetops, ovens, and campfires of the last 60 years, and into my care where I can pass it along someday.

It’s been through three rounds of seasoning now and even cooked its first cornbread. Eventually I may not be able so see it, but I’ll know that fingerprint left by the lathe is there, proof of the care that goes into crafting something designed to endure.

It came from a consulting firm. Cost real money. Arrived with a presentation, a framework, and maybe a roadmap. The recommendations were probably reasonable. Some of them were genuinely good.

None of it was ever implemented.

Part of my onboarding at one point in my career was being handed exactly that binder. It was how I was supposed to learn what a system could do. Not what it did. No plan behind it. No resources dedicated to it. Just pages of what was possible from someone who had already moved on to the next engagement.

I’ve thought about that binder a lot since.

Not because it was unusual, but because it wasn’t.

There’s a version of help that feels like help but is actually designed to keep you dependent on the helper.

The manager who answers every question directly, immediately, and completely feels like a resource. What they’re actually doing is making sure the team never has to think without them. Every answer creates the next question. The manager stays indispensable. The team stops growing.

The consulting firm that delivers recommendations without implementation has the same dynamic, whether they intend it or not. The binder creates the follow-on engagement. The client has pages but not progress. The next conversation starts with “we could help you implement this.”

It feels like service. It’s actually a grip.

The alternative is harder to sell because it looks like less in the short term.

The leader who delegates outcomes instead of tasks gives the team a problem to solve, not an answer to execute. It’s messier. It takes longer. The team makes mistakes they wouldn’t have made with tighter control. But they also develop the confidence to move without being told. Eventually they stop needing the same level of guidance.

That’s the goal. Not to make yourself unnecessary forever. To make yourself unnecessary for this problem.

A good thinking partner works the same way. They help you define what you’re actually solving for. They work through it with you, not for you. And when you’ve found the answer, they stop. Not because the relationship is over. Because the work is done.

I think about this in two distinct ways in my own practice.

Advisory is available when you need a perspective above the weeds. You define the problem. We work toward clarity together. You move forward on your own. That’s not a standing meeting or an ongoing retainer. It’s a conversation when you need one.

A project is different. I’m filling a role you don’t currently have for a specific, defined engagement with a clear outcome. When the outcome is achieved, the engagement ends.

In both cases the goal is the same. You leave better than you arrived. Clearer. More confident. Still independent.

That doesn't mean the relationship ends. It means if we work together again, it's because I helped. Not because I made myself hard to leave.

The dusty binder is a symptom of help that was never designed to end.

The question worth asking before you engage a consultant or advisor is how do they talk about success? If the answer is a deliverable, be careful. If the answer is your progress, you are in the right room.

It came from a consulting firm. Real money, real pages, a roadmap for what a system could do. No plan behind it. No resources. No one accountable for what happened next.

It was how I was supposed to learn what was possible.

I’ve seen versions of it everywhere since. The recommendations that never became decisions. The framework that lived in a presentation and nowhere else. The follow-up engagement to implement the recommendations from the last engagement.

It’s not always bad intent. Sometimes it’s just what happens when help is designed around a deliverable instead of an outcome.

A deliverable ends when the pages are done. An outcome ends when something actually improves.

The people I work with are busy enough already. The last thing they need is more pages.

So the operations and servicing teams got to work. They spent months rebuilding the entire document library. New naming structure. New keywords. New workflow. Carefully designed, thoroughly tested, properly documented. And fully converted. By the time they finished, they had something genuinely good. A real solution to a real problem.

Then they rolled it out.

And the loan officers kept their desk files.

What followed got diagnosed as a change management problem. Communication wasn’t sufficient. Training fell short. The front line was resistant to new ways of working. All of that became the story.

None of it was wrong, exactly. But it wasn’t the real problem either.

Nobody had asked the loan officers how they worked. Nobody sat with them long enough to understand what they reached for during a loan, how they moved through a file, what they needed to find and when. The project had been built entirely from the ops and servicing perspective because that’s who supposedly owned the problem. Their better system would be better for everyone.

The case was never made to everyone who had to change.

In many ways, things were worse than before. At least before the months spent on the project, everyone knew where the files were. Now there were two systems, neither of them complete, and a front line that had learned not to trust the next initiative.

When leaders tell me they have a communication problem, I listen carefully.

Communication is almost always part of it. But it’s also a very safe thing to say out loud. A leader can acknowledge poor communication without putting the decision itself on the table. The plan was right, the path was right, but we just didn’t bring people along soon enough or clearly enough. Fix the communication and move on.

It’s a convenient place to stop. And stopping there has a cost.

Think about deciding where to meet your spouse for dinner without asking her. You pick the place, show up at six, and she isn’t there. You call. She didn’t know. That’s a communication problem, and it’s easy to fix.

But say you tell her. And she still doesn’t want to go.

Now the communication problem has been solved and the resistance didn’t go away. Which means it was never really a communication problem. You picked a restaurant for yourself and expected her to want what you wanted. The case wasn’t made. It was assumed.

That’s what happened at the bank. The ops team solved their problem, communicated the solution, and called it change management when the front line didn’t follow. The harder question never got asked. Did we build a case that works for the people whose daily work we’re asking to change? There wasn’t a good answer, so the conversation stopped somewhere safer.

Most change efforts that stall aren’t stalling because of poor communication.

They’re stalling because the case was built for the people already convinced. The people in the room when the decision got made, who lived with the problem long enough to feel the solution as obvious. By the time anyone notices the disconnect, the project is months in, the budget is committed, and re-examining the case feels like going backward.

So the diagnosis becomes communication. Or training. Or culture. Anything that leaves the original decision intact.

The people who aren’t moving are often the first clear feedback the effort ever got. They’re not obstacles. They’re information.

The question worth asking before you launch is whether you’ve made a case that works for everyone who has to say yes. The time to ask it is before the months of work, before the rollout, before the communication plan.

Most teams ask how to communicate the decision. Fewer ask whether they’ve earned the right to make it.

Those are different questions. The first one is easier. The second one is the work.

Spent real time on it. Picked the metrics, designed the layout, got it into production. It was genuinely well made.

People kept sending emails with questions the dashboard was supposed to answer.

The easy explanation was that nobody read the announcement. And we all know people resist new tools. And maybe the training wasn’t enough.

The harder explanation was that nobody asked the people sending emails what they actually needed to see.

The dashboard answered my questions. Not theirs.

I keep coming back to this when leaders tell me they have a communication problem. Communication is almost always part of it. But it’s also a safe place to stop. You can admit poor communication without confronting the work that came before it.

The harder question is whether the case was built for the people who had to say yes. Not just the people already in the room.

The people still sending emails weren't the problem. They were the answer to a question I didn’t ask.

We didn’t workshop each other’s drafts. We didn’t share what we were working on. We got on a call, said hello, and wrote. Silently. For up to two hours.

It sounds strange but it worked remarkably well.

Nobody pushed anyone. Nobody checked in. People came and went as they needed. But, when the time was over, we’d done the thing that was easy to put off.

The accountability wasn’t pressure. It was just the quiet knowledge that someone else had blocked the same time and would be there when I logged on.

I’ve been thinking about that lately.

Protected thinking time is one of those things most leaders know they need and almost nobody actually keeps. Not because they don’t value it. Because it’s the easiest thing to give away. A meeting request lands. A question needs an answer. The calendar fills from the outside in.

Early Ink didn’t solve that just by adding discipline. It solved it by adding company. Writing, like leadership, can be lonely. And nobody wanted to be the one who didn’t show up. Once you were there, the work came easier than it did alone.

I’m holding lunchtime on Wednesdays for that same reason. Office Hours. Come with a question or just come to work. Either way, you won’t be keeping the time by yourself.

Join me for Office Hours here.

There’s a moment most leaders recognize, usually too late.

Production is slipping. The project is behind. People are quieter than they used to be. More mistakes. Fewer conversations. A kind of low-grade tension that wasn’t there two months ago.

The instinct is to push harder. Call more meetings. Ask people to dig in.

But the problem isn’t effort. It never was.

The Real Failure Mode

Most organizations launch change initiatives the same way: they identify the work then assign it to capable people. And then ask those people to carry it alongside everything they were already doing.

The day job doesn’t pause. The project gets added on top. And somewhere in the gap between intention and execution, both start to suffer.

It’s not a capability problem. The people are talented. They know what needs to be done. Nobody made room for them to do it.

This is the pattern I see most often in organizations navigating complex change. Three things tend to show up together.

First, no dedicated capacity. Everyone is expected to manage their regular responsibilities and the additive project work simultaneously. The assumption is that good people can absorb both. They can, for a while. But not indefinitely, and not without cost.

Second, no clear prioritization. When leaders don’t name what matters most, individuals fill the vacuum with their own judgment. Everyone is working hard. Nobody is working on the same thing. Alignment quietly erodes.

Third, no headroom. Most teams are already operating at or near full capacity before the initiative starts. There is no slack or dry powder. No room for the unexpected, which change always produces.

The result is predictable. Production slips. The project slips. People start to burn out. And the organization concludes, incorrectly, that the problem was communication or methodology.

So they add to the playbook, not capacity.

What Different Looks Like

I know what the alternative looks like because I lived it.

Years ago, I was managing a loan servicing unit at a regional bank when a major merger was announced. The combined organization would be significantly larger, and the integration was going to be one of the most complex operational efforts either institution had ever attempted.

Leadership made a decision I didn’t fully appreciate at the time. Rather than asking functional leaders to manage the integration alongside their existing responsibilities, they created dedicated integration teams with manager roles within each major operational area. They pulled people out of production and pointed them full time at the project.

I was one of them. I left my day job running the loan servicing unit to focus entirely on the loan integration.

It was the right call.

Because integration work is real work. It requires sustained attention, clear decision-making, and the ability to escalate and resolve issues without competing priorities pulling you in two directions at once. When you’re trying to run a unit and integrate a bank at the same time, neither gets your full attention. When the integration is your only job, everything changes.

The merger succeeded. The combined loan portfolio grew by 60%. Not only because the team was exceptional, though they were. Because the conditions were right.

The Question Worth Asking

Before your next initiative, before you build the plan and assign the work and set the timeline, ask one question.

Have we actually made room for this?

Not in theory. Not on a project plan. In practice. In people’s calendars. In how priorities are set and communicated. In whether the teams carrying this work have any capacity left to carry it.

If the answer is no, the plan isn’t the problem.

The conditions are.

And conditions are something you can fix, before things slip, before people burn out, and before the initiative becomes another story about why change is hard.

It doesn’t have to be that way.

I said yes. Rolled up my sleeves. Started working.

I didn’t ask when they needed it. Who was waiting on it downstream. What done actually meant to them.

I asked about the how. Not the what or the when.

By the time I figured out I had the priorities wrong, someone was already waiting. The work wasn’t late because I was slow. It was late because I jumped in before I understood what I was jumping into.

I talk about clarity before execution. I believe it. I’ve seen what happens when organizations skip it.

Apparently I needed the reminder too.

The question I skipped was thirty seconds. The recovery took longer than that.

When do you need this? Who else is counting on it? What does done look like to you?

Thirty seconds of clarity. A lot less cleanup.

What’s the last thing you jumped into before you fully understood what you were jumping into?

It doesn’t look like abdication. It looks like effort. They’re in early, head down, doing. Answering emails that aren’t theirs to answer. Solving problems that belong to someone else. Moving things forward. Or so it feels.

But direction quietly goes dark.

The team keeps moving, because that’s what good teams do. They fill the vacuum with their best guesses, their competing priorities, their own noise. And the leader, buried in doing, doesn’t notice because doing feels like helping.

I see this pattern often. Usually in the hard stretches, when pressure is high and everything feels urgent. The instinct to roll up your sleeves is understandable. Even admirable, on the surface.

But the work that only a leader can do: naming what matters, setting the direction, helping people see where they’re going, doesn’t get done when the leader is doing everyone else’s.

The quiet question I keep sitting with:

What have you stopped leading because you started doing?

Many organizations reach a point where strategy is not the problem. Execution is. Teams are working hard, but the work is not moving the way it needs to. People feel the pressure to deliver, yet they do not always have the tools, structure, or shared understanding to lead initiatives with confidence.

This Case Note looks at how I help organizations build internal capability so they can execute more consistently and move through change with less strain. The focus is simple. Give people practical skills they can use right away. Create shared language. Build confidence. Strengthen alignment.

Workshops and training sessions are not events. They are ways to help teams work together more effectively.

The Challenge

Even strong strategies fall apart when teams are unclear on how to move the work forward. I see the same patterns across many small and mid sized organizations:

• people are unsure about roles or decision making

• teams use different approaches to planning and execution

• initiatives stall because expectations are not aligned

• leaders rely too heavily on external support

• momentum fades once the initial push is over

These gaps create frustration, missed deadlines, and unnecessary friction. The work becomes heavier than it needs to be.

Organizations do not need more inspiration. They need practical, repeatable skills that help people lead work with clarity.

My Approach

When I design a workshop or training session, I start with the real work teams are trying to move forward. I listen to where things feel unclear, where projects slow down, and where people are compensating for a lack of structure.

From there, I build a learning experience that fits the organization. The goal is not to teach theory. It is to give people tools they can use the next day.

The work often includes:

• creating shared language around project and change management

• helping teams understand roles and expectations

• introducing simple frameworks that make planning easier

• practicing conversations that improve alignment

• building confidence through real examples and hands on exercises

The purpose is to strengthen the organization’s execution muscle so teams can lead work with more clarity and less stress.

Why This Kind of Support Helps

Training only works when it is practical, grounded, and connected to the work people are already doing. My focus is on helping teams:

• understand how to move work from idea to execution

• communicate more clearly

• reduce friction and confusion

• build confidence in their ability to lead change

• create consistency across teams and locations

The certifications and experience matter, but they are not the point. What matters is helping people feel more capable and aligned.

When teams have a shared way of working, execution becomes more predictable. Change becomes less overwhelming. Leaders can focus on what matters most.

Case Notes: Strengthening Execution Through Hands On Learning

Context

A growing organization was preparing to launch several strategic initiatives. The leadership team was confident in the direction, but they were concerned about execution. Teams were working hard, but not always together. People used different approaches to planning and communication. The work felt heavier than it needed to be.

They asked me to help build internal capability so teams could lead projects and change with more confidence.

What Was Unclear

The organization knew they needed more consistency, but they were not sure how to create it. They wanted a shared approach to execution without adding unnecessary complexity. They wanted teams to feel equipped, not overwhelmed.

The question was how to build capability in a way that fit their culture and supported their goals.

What I Paid Attention To

I looked closely at:

• how teams planned and communicated

• where projects slowed down

• how decisions were made

• what tools people used and how they used them

• where confidence was strong and where it was thin

I also paid attention to the culture. The organization valued collaboration, clarity, and practical solutions. Any training had to reflect that.

What Helped

We designed a series of workshops that focused on real work, not abstract concepts. The sessions included:

• simple planning frameworks

• practical tools for communication and alignment

• exercises that helped teams practice new skills

• conversations that clarified roles and expectations

• examples drawn from the organization’s own projects

The goal was to make execution feel more manageable and to give people a shared way of working.

What Changed

Teams left the sessions with more confidence and a clearer understanding of how to move work forward. Leaders saw better alignment across departments. Projects became easier to plan and easier to manage. The organization built capability that would support future growth.

They did not just learn new skills. They strengthened the way they worked together.

Closing

If your organization is trying to build stronger execution capability or prepare teams for upcoming change, 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.

Small and mid-sized organizations hit moments where the work gets complex. Growth, transitions, new initiatives, or changes in direction can create more questions than answers. Leaders feel the weight of it. Teams feel the ripple effects. Progress slows.

In these moments, people don’t always need a full-time executive. They need someone who can step in, understand what’s happening, and help them move forward with clarity. Someone who can steady the work, shape the path, and support the decisions that matter.

This is the role I often play. I come alongside leaders during periods of change and help them see the situation more clearly. Sometimes that looks like fractional leadership. Sometimes it’s advisory support. Sometimes it’s a mix of both. The goal is always the same. Reduce the noise. Focus the work. Create momentum.

These Case Notes share examples of what that looks like in practice.

The Challenge

Many organizations reach a point where the work becomes heavier than the structure around it. Growth, transitions, new programs, or shifts in direction create pressure on teams that are already stretched. Leaders feel responsible for keeping things moving, but the path forward isn’t always clear.

These moments don’t always call for a full-time executive. They call for someone who can step in quickly, understand the situation, and help steady the work. Someone who can bring clarity to a complex moment and support the decisions that matter.

Without that kind of support, progress slows. Teams lose alignment. Important work stalls. The organization feels the drag of uncertainty.

This is often where I come in.

My Approach

When I’m brought into a complex moment, the first step is always the same. I take time to understand what’s really happening — the pressures, the expectations, and the places where the work feels stuck. Every organization has its own rhythm, and the support has to fit that rhythm.

Sometimes the work calls for steady, hands-on leadership for a season. Sometimes it calls for a quieter advisory role. Many situations fall somewhere in between.

I might step into a fractional role to help carry the weight of a transition or a complex initiative. I might support a leader through a series of conversations that help them make decisions with more confidence. I might join a team’s weekly rhythm to keep a project moving.

The form of the support shifts. The purpose doesn’t.
I help leaders move through complexity with more clarity and less strain.

Why This Kind of Support Helps

I’ve found that leaders often know what needs attention. What they don’t always have is the time, space, or support to work through it. When the work gets complex, it helps to have someone who can step in quickly, understand the situation, and help carry the weight for a while.

Fractional or advisory support works because it gives organizations access to experienced leadership without the pressure of a long hiring cycle or a full-time commitment. It creates room for clarity. It gives teams a steadier path forward. And it lets leaders focus on the decisions that matter most.

My approach is practical and human. I pay attention to how people are experiencing the moment, not just the mechanics of the work. I focus on alignment, communication, and the small signals that show whether a team is moving together or drifting apart. The certifications and experience matter, but they’re not the point. What matters is helping people move through complexity with more confidence and less strain.

That’s the work I care about.

Case Notes: Integrating a Loan Portfolio During a Merger

Context

A commercial bank in Ohio was preparing for a merger that would nearly double its size. The deal looked strong on paper, but everyone understood the real test would come after the announcement. Two organizations. Two sets of systems. Two ways of working. The success of the merger depended on whether the combined bank could operate as one.

The loan portfolio was at the center of it. Different platforms. Different processes. Different expectations. If the integration didn’t go well, the merger wouldn’t deliver what leadership hoped for.

What was unclear

The teams were experienced, but the path forward wasn’t. People were trying to keep day-to-day work moving while also preparing for a major transition. There were questions about data, workflows, compliance, and how the combined organization would function once the systems came together. Everyone felt the weight of getting it right.

What I paid attention to

In moments like this, the technical work matters, but the human work matters more. I paid attention to how teams were communicating, where assumptions were being made, and where the work was slowing down. I looked for the places where people were unsure but didn’t feel like they could say so. Those small signals usually point to the real risks.

I also focused on alignment — not just on the systems, but on the expectations behind them. A merger isn’t just about combining data. It’s about creating a shared way of working.

What helped

We created a clear path for the integration. Not a binder. Not a slide deck. A practical plan that people could follow. We worked through the system conversion, the operational model, and the compliance requirements in a way that kept teams informed and involved. The goal was to reduce uncertainty and keep the work moving at a steady pace.

Regular conversations helped more than anything. They gave people space to surface concerns early, adjust quickly, and stay aligned as the merger took shape.

What changed

The integration was successful. The combined loan portfolio grew from $9 billion to $14 billion, and the organization emerged stronger and more unified. The merger delivered what leadership hoped for — not because the systems were perfect, but because the people doing the work had clarity and support when they needed it.

Closing

If your organization is moving through a complex moment and the path forward feels unclear, I’m always open to a conversation. Sometimes a short discussion is all it takes to see the situation differently.

If you’re navigating a moment like this and want to talk it through, I’m always open to a conversation.

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.

Organizations often reach a point where the way they have been working stops working. Processes that once made sense become slow, expensive, or misaligned with the business. Teams feel the strain. Leaders feel the pressure to fix it. The path forward is not always clear.

This Case Note looks at a moment like that. A consumer finance company realized its long-standing collections model was no longer delivering what the business needed. Legal expenses were rising. Performance was slipping. The outsourced structure made it difficult to see what was actually happening inside the work.

I was brought in to help the organization rethink its approach, rebuild its operations, and create a model that could sustain performance over time.

The Challenge

The company had relied for years on a multi-state law firm to manage its recovery collections. It was a familiar model, but the results had begun to decline. Legal expenses kept rising. Collections performance weakened. The company lacked visibility into the process and could not see where the work was slowing down.

The leadership team knew something had to change, but the path was not obvious. They needed clarity on what was driving the decline, what a better model could look like, and how to make a transition without disrupting the business.

This is the kind of moment where organizations benefit from someone who can step in, understand the situation quickly, and help shape a path forward.

My Approach

The first step was understanding the current state. I spent time with the teams, listened to where the work felt slow or unclear, and looked for the friction points that were costing the company time and money.

From there, we rebuilt the collections operation from the ground up. That included:

• streamlining workflows

• integrating analytics into daily decision making

• clarifying roles and expectations

• reducing unnecessary legal dependency

• designing a model the internal team could own

The goal was not only to fix the immediate issues. It was to create a system that would continue to work long after the project ended.

Why This Kind of Support Helps

Transformational work like this is not about installing a new process. It is about helping people move through a complex shift with clarity and confidence.

I focused on:

• making the work visible

• reducing uncertainty

• aligning teams around a shared way of operating

• building internal capability so the company did not have to rely on external partners

The certifications and experience matter, but they are not the point. What matters is helping people see the situation clearly and giving them a model they can sustain.

Case Notes: Transforming a Collections Operation

Context

A leading consumer finance company was facing diminishing returns from its outsourced collections model. Legal expenses were rising. Performance was declining. The company lacked visibility into the work. They needed a new approach that was more efficient, more transparent, and more aligned with their long-term goals.

What Was Unclear

The company knew the current model was not working, but the root causes were not obvious. Was it the workflow? The legal strategy? The data? The structure of the partnership? Or something deeper in the way the work was organized?

People were doing their best within the system they had, but the system itself was holding them back.

What I Paid Attention To

I looked closely at:

• where decisions were being made

• how cases moved through the process

• where delays and bottlenecks appeared

• how legal resources were being used

• what data was available and what was missing

I also paid attention to the human side. Where teams felt stuck. Where they lacked clarity. Where they were compensating for gaps in the system.

What Helped

We redesigned the entire collections operation. That included:

• building a streamlined, in-house process

• integrating analytics to guide prioritization

• reducing unnecessary legal escalation

• creating a clear workflow that teams could follow

• aligning the operation with the company’s financial goals

The work was not about installing a new system. It was about creating a model that made sense for the business and empowering the team to run it confidently.

What Changed

The results were significant:

• Collections tripled, which dramatically improved revenue recovery.

• Legal expenses dropped by 66 percent, which reduced cost and increased profitability.

• The new model was so effective that it became a standalone business offering for other clients.

The company did not just fix a problem. They built a capability.

Closing

If your organization is facing a moment where the work feels heavy, unclear, or misaligned with your goals, I am always open to a conversation. Sometimes a short discussion is all it takes to see the situation differently.

If you’re navigating a moment like this and want to talk it through, I’m always open to a conversation.

Last week we asked all the right questions using our Clarity Card, a simple tool to help leaders pause, refocus, and move forward with intention. Here are five quick checks I use with SMB owners and other leaders to cut through the fog and get started with the first thing first.

1. Are priorities clear? (Three max)

We’ve all heard the saying: “If everything’s a priority, nothing is.”

It’s the first prompt on the Card and one of the first questions we ask leaders during a Clarity Sprint discovery session. “What business goal does this advance?” Notice, the question is proactive, not reactive. “Goal” not “problem.”

The reason we ask is that teams should limit their focus to three core outcomes. Then, write them down. Share them. Protect them.

Productivity starts with constraint.

2. Do people understand their roles?

Confusion isn’t just inefficient. It’s exhausting.

Make sure everyone knows what they own, what they support, and what they can ignore. It’s also in this role clarity that people understand the WIIFM (What’s in it For Me?), a key driver for building the desire for change.

Clear roles reduce friction, build trust, and power change.

3. Are timelines realistic?

Urgency is fine. Fantasy isn’t.

If your calendar is built on best-case scenarios, you’re setting your team up to fail. Build in breathing room. Ask your team, “what do we need to stop doing to make space for this objective?”

4. Have risks been named?

You can’t manage what you won’t name.

Call out the dependencies and the “if this breaks, we’re stuck” moments.

Naming and planning for risk is leadership. It’s not resistance or pessimism.

5. Is there a communication plan?

Don’t assume people will “just know.”

Decide how updates flow, who shares what, and when. Who needs occasional updates? Who needs more frequent communication?

It doesn’t need to be complicated. Even a simple rhythm—weekly check-ins, shared notes, one point of contact—can change everything.

Final Thought

You don’t need a multi-day retreat to find clarity. But you do need a moment of pause—and someone who knows how to guide it.

That’s what our Clarity Sprint is built for: a focused, high-impact workshop that helps small teams name what matters, align around it, and move forward with confidence. All in just 90 minutes.

If your organization is navigating change, planning for next year, or just trying to finish strong, let’s talk. I work with businesses, nonprofits, and civic groups to turn complexity into clear next steps.

Not sure where your team stands—or where to begin? Take our no-obligation readiness assessment. A few multiple-choice questions can put you on the road to clarity. And confidence

Ready to move from swirl to structure?

Book a Clarity Sprint or grab the printable Clarity Card on our LinkedIn page. Let’s help your team finish strong.

Book a Call

Using a quarterly planner (Full Focus, by the way) forces me to evaluate every goal each quarter and decide which are achievable and still make sense in a dynamic world.

In my quarterly reviews, I ask the same questions over and over and encourage my clients to do the same.

I’ve pulled the five prompts I use for goal-setting and prioritizing, along with a quick checklist, together into the Clarity Card for quick reference. Here are the five prompts and why they matter.

Prompt #1: Which business objective does this advance?

Ask this question first for two reasons. First, it ensures that the time, money, and resources spent accomplishing this goal are aligned with your highest-level objectives. This calls back to the famous Drucker quote:

“There is nothing so useless as doing efficiently that which should not be done at all.”

Second, by framing the question as ‘what goal’ instead of ‘what problem,’ you drive toward objectives instead of chasing symptoms. For example, how many times have you been part of a meeting to talk about a problem that started with ‘communication’ being named as the culprit? But, it’s rarely the true challenge. Overwhelm, misalignment, change fatigue, and shifting priorities all can feel like communication problems.

Prompt #2: What does success look like in one sentence?

We use this question to get crystal clear on the definition of success. Like a SMART goal, or other framework, the best outcomes start with the clarity of a single sentence aligned to a business objective.

Prompt #3: Who needs to be aligned for this to work?

Answering the first two questions without this one is just noise. This is where we identify everyone involved in the effort, along with their needs, motivations, and their influence. A full consideration of this prompt creates a list of what’s in it for everyone and how to make sure that they get it.

Prompt #4: What is the next smallest step we can take?

We’ve all seen posts about the power of compounding change or eating an elephant one bite at a time. Even with the well-known clichés, how many times have you been part of something that became so large that it not only never finished, but it also lost any sense of its original purpose? Zombie Projects are real and they feed on your time and money.

Asking this question, and then asking it again and again, keeps the effort manageable and aligned and unlocks value with each iteration.

Prompt #5: What do we need to stop doing in order to make space?

This brings us back to Zucker and closes the circle. Prioritization is as much about knowing what not to do as what to do first. Especially when your focus and resources are limited.

Need an extra hand sorting through your priorities?

Whether you need an hour or an expert on speed dial, we’re offering our popular Clarity Bundle at a discounted rate during the fourth quarter. Visit hersherconsulting.com and end 2025 with clarity and start 2026 with renewed focus:

• Strategic Office Hour: Designed for leaders who want targeted help with real-world challenges: prioritization, stakeholder prep, meeting strategy, or just untangling the fog.

• Clarity Sprint: Helps small teams name the real need, define success in plain language, and take the next smallest step—with calm, strategic momentum.

• Retained Advisory and Retained Advisory Plus: for SMB leaders heading into year-end with too much on their plate and not enough strategic bandwidth, the Q4 Retainer Sprint offers calm, consistent guidance—on demand and without the complexity of a full engagement.