The Best Delivery Leaders Learn the Business Before They Try to Fix the Process

One of the easiest mistakes in delivery leadership is walking into an organization, seeing an inefficient process, and immediately deciding how to fix it. Add a framework. Change the meetings. Restructure the backlog. Introduce new governance. Implement another tool.

Sometimes those things are necessary. But one of the most important lessons I learned during my time at Boston Mutual Life Insurance Company was this:

You have to understand the business before you can effectively change how the business gets work done.

Learn How the Business Actually Works

Insurance is a great example because what looks relatively straightforward from the outside is anything but simple once you understand the business. At Boston Mutual, the business wasn't simply about selling an insurance policy. The company serves individuals and families as well as employers and employees through workplace benefits, with products including life, accident, critical illness, and disability insurance.

That means there are multiple customers and stakeholders in the equation. Policyholders. Employers. Employees. Brokers and producers. Sales teams. Customer service. Operations. Finance. Actuarial. Technology.

A change that makes perfect sense from one perspective can create complexity somewhere else.

That experience reinforced for me that delivery leadership requires more than understanding the project you're assigned. You need to understand how the organization creates value and how the pieces of the business connect.

Where does revenue come from? How are products sold and distributed? What does the customer experience look like? What happens after a policy is sold? Where does technology enable the business? Where does regulation constrain it? And what happens downstream when you change something upstream?

Until you understand those things, it's difficult to know whether you're actually improving the business—or simply improving one part of a process.

The Process Isn't the Business

This is where delivery leaders can get into trouble.

We tend to arrive with expertise.

Agile. Project management. Portfolio management. Governance. Process improvement. Technology delivery.

Those are valuable capabilities. But they are tools.

The methodology is not the outcome.

At Boston Mutual, I learned that improving delivery meant understanding the people doing the work and the business outcomes they were responsible for—not simply introducing a "better" process.

Sometimes a process exists because of a regulatory requirement.

Sometimes a handoff that looks unnecessary protects against a very real business risk.

Sometimes the issue isn't process at all. It's competing priorities, unclear ownership, technology constraints, or two parts of the organization trying to optimize for different outcomes.

You don't know which problem you're solving until you understand the business behind it.

That Lesson Travels

I've carried that lesson into every environment I've worked in since.

In Nebraska state government, the definition of value changed. The goal wasn't generating revenue; it was fulfilling a public mission, meeting policy and federal requirements, responsibly using public resources, and delivering services to the people who depend on them.

Now, opening a BODYBAR Pilates studio, the scale has changed dramatically—but the principle hasn't.

Marketing, sales, hiring, training, construction, technology, payroll, and member experience are all connected. A decision in one area can quickly affect three others.

Whether you're working inside an insurance company, a large government organization, or a small business, the questions are remarkably similar:

• What are we actually trying to accomplish?

• Who are we serving?

• How does this organization create value?

• What matters most to the customer?

• Where does the work really get stuck?

• What dependencies aren't obvious?

• What problem are we actually trying to solve?

Only after answering those questions should we start redesigning the process.

Listen Before You Solution

The longer I've worked in strategic delivery, the more valuable I've found it to resist being the person who immediately has the answer.

Ask the business leader why something matters.

Ask the person doing the work where it actually gets difficult.

Ask customer-facing teams what they hear repeatedly.

Ask technology what constraints the business may not see.

And then listen for where those answers don't align.

That's often where the real delivery problem lives.

A problem labeled as a technology issue may actually be a business decision that hasn't been made. A backlog problem may really be a prioritization problem. A process problem may actually be an ownership problem.

Changing the workflow won't fix a problem you haven't correctly diagnosed.

Learn the Business First

My time at Boston Mutual shaped how I think about strategic delivery leadership today.

Before trying to improve how an organization works, learn how it works.

Understand how it makes money—or fulfills its mission. Understand its customers. Understand its products and services. Understand the people doing the work and the constraints they're working within.

Then bring the delivery expertise.

Because the best delivery leaders aren't the ones who can implement their favorite methodology everywhere they go.

They're the ones who can walk into very different organizations, learn what makes each one work, and help people deliver better outcomes within that reality.

The business comes first.

The process should serve it—not the other way around.