Beyond the screen: how product design is changing inside complex enterprises

From design artefacts and handoffs to systems of knowledge, intelligence and collaboration.

The screen was never the whole product

For years, product design has been measured by what we can see: interfaces, journeys, components, prototypes and design systems.

A complex business process becomes a flow.

A product requirement becomes a screen.

These are useful transformations. They turn ambiguity into something tangible, give teams a shared language and help people understand what they are building.

But in complex enterprise environments, particularly in pharma and healthcare, the interface is only one small part of a much larger system.

Behind a single screen might sit clinical workflows, regulatory obligations, data dependencies, legacy platforms, organisational decisions, operational constraints and multiple teams with different responsibilities.

A screen can be beautifully designed and still fail if the underlying process is broken, the data cannot be trusted, the organisational context is missing or the people involved cannot coordinate their work.

The challenge is no longer simply to design better interfaces. It is to make complex systems understandable, usable and trustworthy.

From screens to artefacts

The first shift is from thinking in screens to thinking in artefacts.

An artefact is any tangible representation of a problem, decision, workflow or solution. It might be a user journey, a service blueprint, a prototype, a process model, a data structure, a design-system component or a specification.

These artefacts allow multidisciplinary teams to externalise their thinking. They make assumptions visible, support discussion and turn abstract requirements into something people can inspect, challenge and improve.

In regulated environments, this becomes particularly valuable. A workflow cannot be understood in isolation from its requirements, dependencies, evidence and intended outcomes.

Design artefacts therefore become more than deliverables. They become the building blocks through which teams communicate, reason and make decisions.

Yet artefacts alone are not enough.

A collection of well-designed documents and interfaces does not automatically produce a coherent product experience.

From artefacts to systems

The next shift is from individual artefacts to the relationships between them.

Enterprise products exist within ecosystems of people, processes, technologies and data. Their behaviour emerges from the interaction of these elements rather than from any single component.

A seemingly simple user action might trigger several downstream processes, involve different teams, depend on data from another system and create obligations that must be fulfilled elsewhere.

Designing at this level requires systems thinking.

The designer must understand not only what a user sees, but also what happens before, during and after an interaction. They must identify dependencies, model responsibilities, expose failure points and understand how local decisions affect the wider system.

In pharma, where clinical, operational, scientific and regulatory processes intersect, this perspective is especially important.

The design challenge becomes one of making the entire system coherent, rather than optimising one interface in isolation.

From systems to knowledge

Systems thinking reveals another challenge: the knowledge needed to operate a complex organisation is often fragmented.

It lives across documentation, conversations, decision logs, subject-matter experts, operational procedures, research findings, legacy systems and the experience of individuals.

Much of this knowledge is implicit. Some of it is outdated. Some contradicts other sources. Some disappear when people leave a team or when a project ends.

The result is familiar: repeated discovery, duplicated work, inconsistent decisions and teams that struggle to understand why a system behaves the way it does.

This is where product design begins to intersect with knowledge engineering.

The objective is not simply to document more information. It is to structure knowledge so that it can be connected, understood, retrieved and applied in the right context.

Research findings, business rules, user needs, technical constraints, design decisions and operational procedures can become interconnected parts of a shared knowledge environment.

The designer’s contribution evolves from producing individual artefacts to helping create the structures that preserve the reasoning behind them.

Knowledge becomes part of the product infrastructure.

From knowledge to intelligence

AI introduces another layer to this evolution.

When information is structured, contextualised and connected, AI can help teams navigate complexity in ways that were previously difficult or prohibitively time-consuming.

It can synthesise research, connect requirements to design decisions, identify inconsistencies, explain complex workflows, surface relevant evidence and support the exploration of alternative solutions.

In product design, this opens up possibilities beyond generating screens or accelerating routine tasks.

AI can help designers reason across larger bodies of information, explore dependencies and work with knowledge distributed across multiple systems and disciplines.

However, intelligence is not simply a matter of adding an AI assistant to an existing interface.

Useful AI depends on the quality of its context, the reliability of its sources, the clarity of its boundaries and the ability of people to evaluate its outputs.

In pharma and healthcare, these considerations are fundamental. An apparently convincing answer is not necessarily a correct one, and an efficient workflow is not necessarily a safe or compliant workflow.

The opportunity is to create systems in which intelligence is grounded in relevant knowledge, its limitations are visible and people retain appropriate control over consequential decisions.

From intelligence to orchestration

As AI becomes more capable, the focus shifts again: from helping people perform individual tasks to coordinating work across people, tools, agents and systems.

This is the territory of orchestration.

A complex workflow might involve gathering information, validating requirements, consulting evidence, generating an artefact, checking it against established rules and routing it to the appropriate person for review.

Some activities can be automated. Others require human judgement, specialist expertise, approval or escalation.

The challenge is to design how these activities fit together.

Who initiates the process? Which information is required? What can an agent do independently? When should a person intervene? How are decisions communicated? What happens when the system encounters uncertainty or conflicting evidence?

These are product-design questions as much as engineering questions.

The designer increasingly works on the experience of the entire workflow: the transitions between humans and AI, the distribution of responsibilities, the visibility of progress, the handling of exceptions and the preservation of context across handoffs.

The interface remains important, but it becomes one point of interaction within a broader operational system.

The work is no longer only about designing an interaction. It is about designing how work gets done.

From orchestration to governance

The more connected and intelligent a system becomes, the more important governance becomes.

In regulated environments, trust cannot be treated as a final layer added after implementation. It must be designed into the system from the beginning.

Governance encompasses the rules, controls and responsibilities that determine how a system operates. It includes access, permissions, data handling, validation, traceability, auditability, accountability and the conditions under which automated actions are allowed.

For AI-enabled workflows, it also means making the distinction between recommendations and decisions clear, ensuring that outputs can be evaluated and establishing appropriate mechanisms for human oversight.

Good governance should not make a product unusable. Nor should usability come at the expense of safety or accountability.

The design challenge is to make necessary controls understandable and usable while ensuring that the system behaves within its intended boundaries.

This requires close collaboration between design, engineering, product management, security, legal, compliance and domain experts.

Governance is not separate from the user experience. It is one of the conditions that makes the experience trustworthy.

The evolving role of the Product Designer

These shifts do not make interface design obsolete. They change the scope of the problem a designer is expected to solve.

The Product Designer increasingly operates across several interconnected levels:

• Interface: How people interact with a product.
• Artefacts: How ideas, requirements and solutions are represented.
• Systems: How people, processes, technology and data work together.
• Knowledge: How organisational context and decisions are captured and connected.
• Intelligence: How AI helps people interpret information and solve problems.
• Orchestration: How humans, tools and agents coordinate work.
• Governance: How safety, trust, compliance and accountability are maintained.

These are not necessarily sequential stages in a delivery process. They are complementary perspectives on the same product ecosystem.

A designer might move between them within a single project, depending on the problem, the maturity of the organisation and the risks involved.

The differentiator is not simply the ability to work at every level. It is the ability to recognise which level a problem belongs to, understand how the levels influence one another and bring the right disciplines together to address it.

This requires a broader combination of skills: research, interaction design, systems thinking, information architecture, service design, data literacy, AI fluency, facilitation and an understanding of organisational and regulatory constraints.

It also requires a different relationship with delivery.

Instead of treating every output as an isolated deliverable, designers can help create connected, reusable and evolving structures that support teams long after a particular feature has shipped.

Designing the conditions for better decisions

Perhaps the most significant change is that product design becomes less about producing outputs and more about improving the conditions in which decisions are made.

A screen communicates an available action.

An artefact makes an idea tangible.

A system reveals relationships and dependencies.

Knowledge provides context.

Intelligence helps interpret that context.

Orchestration coordinates action.

Governance establishes the boundaries within which action can be trusted.

Each layer builds on the others, and none can fully compensate for weaknesses in the rest.

AI will undoubtedly accelerate parts of product development. But acceleration alone is not the same as progress. Producing more artefacts, generating more interfaces or automating more tasks does not guarantee better outcomes.

The real opportunity is to reduce fragmentation, preserve organisational knowledge, make complexity navigable and enable people to make better-informed decisions.

For Product Designers working in pharma, healthcare and other complex enterprise environments, this represents a meaningful expansion of the role: from shaping individual product experiences to helping shape the systems through which organisations understand problems, coordinate work and create value.

The interface still matters. It is where much of the experience becomes visible.

It was simply the part we could see.

Beyond the screen: how product design is changing inside complex enterprises was originally published in Bootcamp on Medium, where people are continuing the conversation by highlighting and responding to this story.