Every product tells the truth about the organization that built it.
There’s no getting around it: looking honestly at your product can feel uncomfortable, even intimidating. Your website, app, platform, or service is visible to customers, investors, employees, and competitors. It feels like a reflection of your capabilities.
The interface may be where the problem appears. But it is rarely where the problem begins.
Table of Contents
- Confusion is usually organizational confusion made visible
- Fragmentation reveals fragmented ownership
- Arbitrary boundaries are rarely arbitrary
- When two steps become seven
- Why redesigning screens alone fails
- The Decision Design approach
- Use your product as a diagnostic
Confusion Is Usually Organizational Confusion Made Visible
When a product is confusing, the organization behind it is usually confused about something as well.
That confusion may be strategic. The business may not have agreed on its most important audience, its clearest value proposition, or the action it wants customers to take.
It may be operational. Or what we call shoe horning. Cramming features into existing places instead of looking at the experience holistically.
Sometimes the confusion is simply a lack of alignment. If one voice at the Product, Design and Engineering table is dominant, this becomes apparent in the solution.
The result is familiar: unclear navigation, competing calls to action, inconsistent terminology, buried information, and a product that makes users work too hard to understand what to do next.
Confusion is not just a usability issue. It is often evidence that the business has not made a clear decision about what matters most.
That is why a new visual hierarchy or a rewritten headline may improve the surface without resolving the underlying issue. If the organization is still debating its audience, promise, or priorities, the product will eventually become confusing again.
Fragmentation Reveals Fragmented Ownership
When a product feels fragmented, it is a safe bet that fragmentation exists inside the organization too.
A customer may move from a marketing website to a sign-up flow, then into a dashboard, help center, billing portal, or support tool. Each piece may have been thoughtfully designed by the team responsible for it.
Yet the experience can still feel like five unrelated companies stitched together.
Why?
Because the organization may be structured around siloed product managers rather than cohesive customer journeys. One owns one part. Another owns another feature. And engineering hems them both in with technical constraints.
Each team may be doing its job. No one may be responsible for the whole experience.
This is one reason organizational silos have such a direct impact on customer experience. Research and industry analysis consistently connect siloed teams with duplicated systems, delayed decisions, inconsistent data, and poor collaboration across the moments that matter to customers. Twilio’s overview of organizational silos offers a useful look at how these internal divisions affect the outside experience.
A fragmented product often means no one inside the organization has permission, context, or accountability to make it whole.
A design system can help create consistency. Shared components matter. But visual consistency is not the same as organizational alignment.
You can make every button look the same and still have five teams disagreeing about what the button should be labelled or where it should be placed or where that features should fit.
Arbitrary Boundaries Are Rarely Arbitrary
When the experience forces users to navigate a dozen arbitrary boundaries, I will usually look for those same boundaries between departments, teams, systems, or owners.
A customer should not have to be constrained by your org chart to complete a task.
They should not need to know which business unit owns their account, which platform stores their information, or which department handles the next step. Yet those invisible distinctions often become very visible in the product:
- A customer must create separate accounts for related services.
- Information has to be entered more than once.
- A task stops because a handoff between systems is required.
- A user is sent to a different product area with a different navigation model.
- Support cannot see what the customer already completed elsewhere.
- One part of the experience uses a different definition, tone, or approach.
From the inside, these boundaries may be perfectly rational. They may reflect acquisitions, legacy technology, compliance requirements, or ownership agreements.
From the customer’s perspective, they are simply friction and obstacles.
The customer does not experience your departments separately. They experience your organization as one thing.
That makes customer experience design more than a matter of mapping screens. It requires understanding the operating model, data flows, incentives, and decisions that determine what the customer is allowed to experience.
When Two Steps Become Seven
When something that should take two steps takes seven, somewhere behind the scenes there are often seven people protecting seven different requirements.
One person needs a field for reporting.
Another needs it for compliance.
A third wants to collect information for sales.
A fourth wants to prevent a support issue.
A fifth is preserving a legacy process.
A sixth is concerned about a technical limitation.
And a seventh has authority over the final approval.
And yet another says we don't have time to implement the full feature.
None of these requirements is necessarily unreasonable. That is what makes this problem so difficult.
The customer sees seven steps. The organization sees seven valid reasons.
The product becomes the compromise everyone can live with internally and no one can enjoy externally.
Each team protects its own goal, metric, system, or responsibility. The total experience becomes slower and more complicated, even while every individual decision appears defensible.
How can you know whether this is happening in your organization?
Look for the moments when people say:
- “That’s just how this team does it.”
- “We can’t change that because another department owns it.”
- “The system requires it.”
- “Our customers have always done it this way.”
- “We tried to simplify it, but everyone wanted their piece included.”
- “That's how our legacy data is structured.”
Those statements are clues.
They point to a product that is carrying the weight of unresolved decisions.
Why Redesigning Screens Alone Fails
Most teams begin with the visible problem. They commission a website redesign, update the interface, reorganize the navigation, or ask a digital product design agency to make the experience feel more modern.
Those efforts can be valuable. Customers should not have to struggle with illegible type, poor accessibility, inconsistent layouts, or outdated interaction patterns. Good UX and product design absolutely matter.
But screens cannot solve a disagreement or resistance to change that exists in the operating model.
A redesigned interface may temporarily hide the friction. It may arrange the content more clearly, use better language, and create a more coherent visual system.
Then the next business request arrives.
A new product line needs its own path. A department adds another approval. A legacy integration forces a duplicate step or work around. A stakeholder insists on preserving a competing approach. The organization continues fighting itself, and the dysfunction finds its way back to the surface.
It always does.
This is also why redesign projects can frustrate everyone involved. Designers are asked to create clarity from unresolved strategy and internal incongruence. Product teams are asked to prioritize without shared goals. Developers are asked to implement exceptions or legacy code workarounds. Leadership expects transformation, while the organization has only approved cosmetic change.
A beautiful product cannot compensate for an organization that has not agreed on the experience it wants to deliver.
That does not mean you should avoid redesigning. It means you should diagnose the dynamics of what is happening before you decorate.
The Decision Design Approach
This is why ZIV is a creative consultancy, not just a design shop.
Our Decision Design philosophy starts with a simple question: what is creating friction in the decision to choose you?
Sometimes that friction is visual. Sometimes it is verbal. Sometimes it is technical.
And sometimes, it is organizational.
We look at the full system, from brand alignment, business strategy, customer needs, internal workflows, technology, and the moments where decisions get stuck. A strong brand strategy agency should not only define how your organization looks and sounds. It should help clarify what your organization stands for and how that promise is carried through every experience.
That work may involve:
- Aligning around the customer journey. Instead of beginning with departments or channels, we identify what customers are trying to accomplish and where the experience breaks down.
- Clarifying ownership and decision rights. Someone must be accountable for the end-to-end experience. If responsibility is divided without coordination, fragmentation is almost guaranteed.
- Establishing a shared strategic foundation. Teams need common language around the audience, value proposition, priorities, and measures of success.
- Connecting brand and operations. Your brand promise cannot live only in a campaign or visual identity. It has to be supported by the product, service, systems, and people delivering it.
- Designing and validating the experience. Once the underlying decisions are clearer, we can reimagine, prototype, test, and build a product that makes those decisions easy for customers to understand.
Our work with Intent followed this kind of customer-centered process. Before redesigning the product, ZIV conducted sessions with the executive team and staff, spoke with current clients, clarified goals, and used those insights to shape the information architecture and navigation model.
That research and alignment matters.
Strategy informs experience. Experience reveals operational gaps. Research keeps assumptions honest. Design turns alignment into something people can actually use and get behind.
Use Your Product as a Diagnostic
Your product is not hiding the problem.
It is telling you exactly where to look.
If customers are confused, investigate what the organization has not clarified. If the experience is fragmented, look for fragmented teams, systems, incentives, or ownership. If users cross arbitrary boundaries, examine the internal boundaries that created them. If a simple task requires seven steps, ask whose requirements those steps are protecting.
The product is a diagnostic surface.
Use it to align everyone behind excellence for serving and solving for the customer.
Walk through your highest-value customer journeys. Observe where language changes, where ownership changes, where data disappears, and where customers are asked to do work your organization could do for them.
Then invite the people responsible for those moments into the same conversation.
Not to assign blame. To find the truth.
Your product is not merely an output of your organization. It is evidence of how your organization thinks, decides, and works together.
The good news is that evidence gives you somewhere to begin. Once you can see the organizational issue behind the interface, you can address the right problem : and create an experience that is clearer, more coherent, and easier for both customers and employees to navigate.
Want to understand what your product is telling your customers about your organization?
Let us know. ZIV can help you find the friction, align the people and systems behind it, and design a better way forward.
You may not need another surface-level redesign.
You may need to redesign the decisions underneath it.
