Thought

The better answer lives between disciplines

Customers, businesses, technology, processes, people and design are parts of one problem—even when organizations separate them.

Real problems do not respect the organization chart.

A customer can encounter a policy, a system limitation, an operational handoff and an unclear interface inside one simple task. The organization may assign each part to a different team. The customer experiences all of them at once.

This is why difficult experience problems survive strong work inside individual disciplines. Each team can improve its own piece and the full journey can still remain confusing. The connections—where responsibility changes, information moves or a decision depends on another decision—often carry the real friction.

Working between disciplines means treating those connections as part of the design. It means understanding enough of each perspective to see the whole problem without pretending that one person should have every answer.

The customer does not experience departments. The customer experiences the decisions between them.

Look through six lenses.

Start with the customer. What are they trying to achieve, what do they understand and where do they struggle? Then look at the business. What outcome matters, what responsibility must be protected and what value makes the work sustainable?

Look at technology and process. What can the system do, what is the sequence of work and where are constraints being mistaken for permanent truths? Look at people. Who delivers the experience, what do they need and where does the current model depend on effort that cannot scale?

Then bring design into the conversation—not as the final layer, but as the practice of making those conditions understandable and intentional. Design gives the different lenses a shared form that can be examined, tested and improved.

Translation is part of the work.

Disciplines often use different language for related concerns. A customer problem may appear as a conversion issue, an operational exception, a technical dependency or a content question. Progress depends on translating those views without reducing them to the vocabulary of whichever team has the most authority.

Useful translation preserves what matters in each perspective and makes the relationship visible. A journey map, prototype, principle or clear decision can become common ground, but the artifact is not the point. The point is creating enough shared understanding for the organization to act as one system.

This is also where strategy becomes practical. Strategy is not only choosing a direction. It is helping many decisions remain connected to that direction when the work moves into detail.

Leadership has to cross the same boundaries.

Teams cannot collaborate well if every difficult issue becomes a negotiation over ownership. Leaders create progress by clarifying the shared outcome, giving people room to contribute their expertise and making unresolved trade-offs visible early.

This requires both standards and trust. Standards keep the experience coherent. Trust lets specialists challenge the plan, expose risk and improve the answer. Support matters most when the work becomes uncomfortable, because that is often when teams retreat into familiar territory.

Some of the strongest outcomes come from helping people see beyond the edge of their role without asking them to abandon what they know. The work gets better, and so do the people doing it.

Curiosity keeps the whole problem open long enough.

Working across disciplines does not mean delaying every decision until everything is known. It means resisting the first convenient definition of the problem long enough to ask whether an important perspective is missing.

Why does the customer struggle? Why does the business accept the complexity? What is the technology making possible now? What does the process protect? What do the people delivering the experience already know? What would make the design clearer?

The better answer is often already present in fragments across the organization. Curiosity helps connect them. The work is to turn that connection into a direction people can understand, build and improve together.

I do not separate customer, business, technology, process, people and design. That is usually where the better answers are.