System
logic · data · integrations · states
E7A / 02
About E7A
Principle
Complexity should stay inside the system — not in the interface.
Every serious digital product is complex inside.
Logic, data, integrations, states and constraints do not disappear.
We design so people don't have to carry that complexity themselves.
Position
We don't remove complexity. We put it where it belongs.
Practice model
One accountable lead. Additional roles when the work needs them.
E7A is an independent author-led practice spanning product design, UX, frontend and digital-system architecture. The practice lead stays inside the work from the first diagnosis through decisions and implementation.
- 01
Accountability
One person holds the product and technical context, makes the key decisions and remains accountable for a coherent outcome.
- 02
Team shape
Additional specialists join only where the work genuinely requires them. Roles and responsibility boundaries are agreed before the stage begins.
- 03
Collaboration
The work can run directly with a product owner or alongside an internal team, keeping strategy, interface and implementation in one line of context.
Complexity distribution
The interface is not where a system explains all of its internal complexity. It is the layer that leaves the person with only the context, action and outcome they need.
Interface
context · action · feedback · outcome
03Person
How we work
We do not start with screens. We first understand the system, decide where complexity should live, and only then design the interaction.
- 01
Understand
We examine the system, its constraints and the real task.
- 02
Distribute
We decide which choices belong to the system and which belong to the person.
- 03
Design
We shape an interaction where complexity does not get in the way of the task.
Where to start
The starting point depends on the state of the product.
We can begin by diagnosing an existing system, designing a new workflow or rebuilding a product that has outgrown its original logic. A short brief is enough to identify the first step.
Diagnose
For an existing product that has become complex, inconsistent or demanding to use.
Design
For a new product, service or critical workflow that needs to be built from first principles.
Rebuild
For a system that has outgrown its interface and needs new logic, a design system or a frontend layer.