Beyond Architecture: Thinking in Value Flows

Introduction

Throughout this series, I have deliberately spent very little time discussing technology.

That may seem strange. After all, digital transformation is often described through technology.

PLM. ERP. CPQ. AI. Data platforms. Digital threads. Cloud migration. Modern architecture.

These technologies matter. Many of them are essential.

But over the years I have noticed something interesting.

Organizations frequently understand their systems better than they understand how value actually moves through the business.

And when that happens, transformation starts solving local problems rather than improving overall performance.

The result is often predictable. Technology improves. The organization changes. Yet the customer experience improves less than expected.

Because value never really originated in the systems. It moved through something much larger.

A flow.

The Organizational View

Most companies are designed around organizational structures.

Engineering. Sales. Manufacturing. Service. Operations. Finance. IT.

There are good reasons for this. Organizations need expertise. Responsibilities need owners. People need reporting structures. Work needs coordination.

The challenge is that customers do not experience organizational structures. Customers experience outcomes.

A customer does not care where a process begins and ends internally. A customer cares whether the organization delivers value.

This creates an interesting disconnect.

Businesses are optimized through structures. Markets reward outcomes.

And somewhere between those two perspectives, transformation becomes complicated.

Following the Product

One exercise I often use is surprisingly simple.

Instead of following the organization, follow the product.

A customer need becomes a requirement. A requirement becomes a design decision. The design becomes a product definition. The product definition becomes a commercial offering. The offering becomes a quotation. The quotation becomes an order. The order becomes manufacturing. Manufacturing becomes delivery. Delivery becomes operation. Operation becomes service. Service becomes experience. Experience becomes learning. Learning should influence the next requirement.

Viewed from this perspective, the lifecycle looks very different.

Not like departments. Not like systems. But like a continuous flow.

And that flow is where value is actually created.

Why Systems Create Blind Spots

One reason transformation programs often struggle is that systems create boundaries.

PLM manages one part of the lifecycle. ERP manages another. CRM manages another. CPQ manages another. Service systems manage another.

Each system has a purpose. Each system creates value. But no system owns the entire flow.

This means optimization naturally becomes localized.

Engineering improves engineering. Sales improves sales. Service improves service.

Technology investments often reinforce these boundaries.

The business becomes increasingly optimized in pieces, while the flow itself remains difficult to see.

The Question Customers Never Ask

I have never met a customer who asked:

"How effective is your PLM implementation?"

Or: "How mature is your ERP architecture?"

Or: "How many systems participate in your digital thread?"

Customers ask different questions.

• Can you solve my problem?
• Can I trust your product?
• Can I get what I ordered?
• Can you support me when something changes?
• Can you respond quickly?
• Can you improve over time?

These are value flow questions. Not system questions.

The distinction matters. Because organizations often invest according to system boundaries while customers evaluate performance across the entire flow.

Where Value Gets Lost

One of the advantages of thinking in value flows is that it exposes friction.

Not technical friction. Business friction.

Consider a common situation.

Engineering knows something. Sales does not. Sales promises something. Operations does not know. Service learns something. Engineering never hears about it. Customers experience delays. Nobody believes they caused the problem.

Every function performed its responsibilities. And yet value was lost.

Why?

Because the flow broke. Not the individual activities. The connections between them.

This pattern appears repeatedly in transformation initiatives. And it explains why local optimization often produces disappointing results.

The Handover Economy

Many organizations still operate as if value is created through handovers.

Engineering finishes. Then sales takes over. Then manufacturing takes over. Then service takes over.

Each handover represents ownership moving to another part of the business.

Historically this approach worked reasonably well.

The problem is that modern products rarely behave this way.

Software-defined products create continuous feedback. AI requires lifecycle context. Configuration affects service. Operational insights affect development.

The handovers never really end. Information keeps moving.

Which means value creation increasingly depends on collaboration rather than transition.

The flow matters more than the handoff.

What High-Performing Organizations Do Differently

When I look at organizations that consistently outperform their peers, I rarely conclude that they simply have better systems.

Of course technology helps. But that is usually not what stands out.

What stands out is how effectively information moves. How quickly decisions move. How efficiently learning moves. How clearly accountability moves.

Their value flows encounter less friction.

Knowledge reaches the right people faster. Problems are identified earlier. Decisions are made with more context. Improvements spread more effectively.

The organization behaves like a connected system rather than a collection of independent functions.

That difference compounds over time.

Architecture Is Still Important

To be clear, I am not arguing against architecture.

Quite the opposite. Architecture remains essential.

The problem is that architecture sometimes becomes the objective rather than the enabler.

An architecture discussion often starts with systems, interfaces, data models, platforms and infrastructure.

A value flow discussion starts somewhere else.

Which decisions create value? Which information enables those decisions? Where does friction occur? Where is learning delayed? Where is accountability unclear?

Only after those questions are understood does architecture become truly meaningful.

Because architecture exists to enable value. Not the other way around.

A Different Way to Prioritize

Thinking in value flows also changes investment priorities.

Instead of asking, "Which system should we improve?" we can ask:

Which flow loses the most value today?

That question often reveals something surprising.

The biggest opportunity rarely sits inside a single department. It usually exists where multiple departments interact. Where context is lost. Where decisions become disconnected. Where ownership becomes ambiguous. Where learning slows down.

In other words, the largest opportunities often exist exactly where traditional organizational thinking struggles to see them.

Why This Matters for Executives

Executives are increasingly expected to make decisions that cross organizational boundaries.

The challenge is that most management information still follows organizational structures.

Engineering reports on engineering. Sales reports on sales. Service reports on service. Finance reports on finance.

Very few organizations report on the effectiveness of value flows.

Yet value flows are often what determine:

• Customer experience
• Product quality
• Responsiveness
• Learning speed
• Adaptability
• Competitiveness

Understanding those flows may therefore become one of the most important leadership capabilities of the coming decade.

Because organizations that understand how value moves can improve it. Organizations that only understand structures often optimize around it.

Final Thoughts

The longer I work with transformation, the less convinced I become that systems, functions and organizational charts are the best starting point for understanding performance.

They remain important. But they are not where customers experience value.

Value emerges from movement.

From information moving. Knowledge moving. Decisions moving. Learning moving. Accountability moving.

In other words, value emerges from flows.

And once you begin looking at an organization through that lens, many transformation challenges suddenly become easier to understand.

Because what looked like disconnected problems often turn out to be symptoms of the same interrupted flow.

Perhaps that is why some organizations achieve extraordinary results without appearing dramatically different on paper.

They have not necessarily built better structures. They have simply become better at enabling value to move.

And in an increasingly complex world, that may be one of the most important competitive advantages available.