Experience Design & Digital Strategy
Product roadmaps, UX/UI design systems, and workflow automation that align technology with business direction.
Plenty of enterprise software does exactly what the requirements document said and still gets worked around. The requirement was written by someone describing the process they wish existed, and nobody watched what the job actually looks like at four on a Friday.
We do the design and strategy work that sits in front of the build: what to build, in what order, for whom, and how to tell afterwards whether it worked.
What this includes
- Product roadmaps sequenced against business outcomes rather than against a feature list
- Research with the people who will use the thing – operators, branch staff, dealers – in the place they will use it
- Service and workflow design, including the steps that should be removed rather than digitised
- UX and UI design systems: components, states and rules, handed over as something engineering can build from directly
- Prototypes tested before a sprint is committed, because a wrong assumption is cheapest to find in Figma
- Workflow automation for the queues and handoffs that quietly consume the most staff hours
How we run it
Watch the work. A short period of observation with the actual users tends to overturn at least one requirement everybody was sure about. It is the cheapest risk reduction available on a large programme.
Design that is buildable. A design system is delivered as tokens, components and states that map onto the front-end, not as flat screens an engineer has to interpret. Interpretation is where consistency dies.
Decide what not to build. Most roadmaps are too long. The useful output of a strategy engagement is usually a shorter, ordered list with the reasoning attached.
What you get at the end
- A sequenced roadmap with the reasoning and the trade-offs visible
- Research findings, including the ones that contradict the brief
- A design system in Figma and as front-end components
- Success measures agreed before the build rather than reverse-engineered after it
Where this usually starts
A system that launched and is being bypassed. A backlog nobody can prioritise because everything is a priority. Or a transformation programme with a budget and no agreement on what it is for.
Add your design team size and the tooling you standardise on. If you have run research in a regulated or industrial setting – a factory floor, a branch network, dealer sites – say so. It separates you from agencies that have only done consumer work.