EnBW
EnBW
EnBW
EnBW, one of Germany’s largest energy companies, is building a new cloud platform for its energy trading: the software its power traders and analysts work in all day.
Pommer Design led UX for the trading suite. In prototype tests, interaction errors fell by 40% against the legacy tools.
EnBW, one of Germany’s largest energy companies, is building a new cloud platform for its energy trading: the software its power traders and analysts work in all day.
Pommer Design led UX for the trading suite. In prototype tests, interaction errors fell by 40% against the legacy tools.
EnBW, one of Germany’s largest energy companies, is building a new cloud platform for its energy trading: the software its power traders and analysts work in all day.
Pommer Design led UX for the trading suite. In prototype tests, interaction errors fell by 40% against the legacy tools.
Year
2024
Client
EnBW
Category
Energy
Duration
Nearly 2 years
Objective
Objective
Traders make decisions in seconds, on screens full of live market data. The new platform had to make core trading workflows simpler and faster than the legacy tools did.
Role
Role
In one five-month cycle, Pommer Design ran eight interviews and two co-creation workshops with traders and analysts. It mapped user journeys across the front, middle and back office and produced wireframes, interactive prototypes and final UI in EnBW’s design language. The team: three product owners, six developers and two quantitative analysts.
Approach
Approach
Pommer Design built the information architecture and components to support more products later. It tested them throughout against real tasks: deal capture, market monitoring and position tracking.
Outcome
Outcome
Compared with the legacy tools, prototype tests showed 40% fewer interaction errors, 25% better task efficiency and stakeholder usability ratings up from 5.6 to 8.1. The first stable beta is being prepared for rollout to several trading desks. The expected gain is 20 to 30% less time per trade in core workflows; an analytics dashboard will measure it after launch.
Illustrative views. Client work is confidential. We show the real work under NDA, on request.
More work More work
03
//FAQ
Questions
ANSWERS
01
How does a project start?
With a short discovery phase. We agree on goals, constraints and success criteria and put them in writing first.
02
What kinds of organizations do you work with?
Organizations that run on information: banks and insurers, airlines and rail operators, energy, pharma and software companies. Size matters less than the ambition for the product. The common thread is complexity: dense data, several product teams, or expert users with no time to spare. Early-stage companies with a hard problem are welcome too.
03
How do you approach complex digital platforms?
We map the work before we design for it: who decides what, under which business rules, and how the systems depend on each other. That map becomes the frame for every feature and team that follows.
04
How do you keep a large product portfolio consistent?
With a design system that engineering owns as much as design does: shared components, documented decisions and a review process for changes. New teams start from it instead of from scratch, and the portfolio still feels like one product as it grows.
05
How do you measure success?
We test the new product against the old one on the same tasks and compare time, errors and ratings. A project succeeds when the new version wins on all three. After release we measure again, and the work counts as done when the numbers hold in daily use.
06
Who will work on our project?
Programs of six to twelve months run with a core team led by Moritz Pommer, the founder. Specialists in research, interface design and engineering join larger programs.
07
Can we see the real work?
Yes. The views on this site are illustrative, because client work is confidential. In a call under NDA, we walk you through the real projects.
08
Do you work in German?
Yes. Interviews, workshops and documents run in German or English, whichever your teams work in.
09
Which accessibility standard do you design to?
WCAG 2.2 AA, by default. We design and test against it, so accessibility is part of the specs engineering builds from.
03
//FAQ
Questions
ANSWERS
01
How does a project start?
With a short discovery phase. We agree on goals, constraints and success criteria and put them in writing first.
02
What kinds of organizations do you work with?
Organizations that run on information: banks and insurers, airlines and rail operators, energy, pharma and software companies. Size matters less than the ambition for the product. The common thread is complexity: dense data, several product teams, or expert users with no time to spare. Early-stage companies with a hard problem are welcome too.
03
How do you approach complex digital platforms?
We map the work before we design for it: who decides what, under which business rules, and how the systems depend on each other. That map becomes the frame for every feature and team that follows.
04
How do you keep a large product portfolio consistent?
With a design system that engineering owns as much as design does: shared components, documented decisions and a review process for changes. New teams start from it instead of from scratch, and the portfolio still feels like one product as it grows.
05
How do you measure success?
We test the new product against the old one on the same tasks and compare time, errors and ratings. A project succeeds when the new version wins on all three. After release we measure again, and the work counts as done when the numbers hold in daily use.
06
Who will work on our project?
Programs of six to twelve months run with a core team led by Moritz Pommer, the founder. Specialists in research, interface design and engineering join larger programs.
07
Can we see the real work?
Yes. The views on this site are illustrative, because client work is confidential. In a call under NDA, we walk you through the real projects.
08
Do you work in German?
Yes. Interviews, workshops and documents run in German or English, whichever your teams work in.
09
Which accessibility standard do you design to?
WCAG 2.2 AA, by default. We design and test against it, so accessibility is part of the specs engineering builds from.
//FAQ
Questions
ANSWERS
How does a project start?
With a short discovery phase. We agree on goals, constraints and success criteria and put them in writing first.
What kinds of organizations do you work with?
Organizations that run on information: banks and insurers, airlines and rail operators, energy, pharma and software companies. Size matters less than the ambition for the product. The common thread is complexity: dense data, several product teams, or expert users with no time to spare. Early-stage companies with a hard problem are welcome too.
How do you approach complex digital platforms?
We map the work before we design for it: who decides what, under which business rules, and how the systems depend on each other. That map becomes the frame for every feature and team that follows.
How do you keep a large product portfolio consistent?
With a design system that engineering owns as much as design does: shared components, documented decisions and a review process for changes. New teams start from it instead of from scratch, and the portfolio still feels like one product as it grows.
How do you measure success?
We test the new product against the old one on the same tasks and compare time, errors and ratings. A project succeeds when the new version wins on all three. After release we measure again, and the work counts as done when the numbers hold in daily use.
Who will work on our project?
Programs of six to twelve months run with a core team led by Moritz Pommer, the founder. Specialists in research, interface design and engineering join larger programs.
Can we see the real work?
Yes. The views on this site are illustrative, because client work is confidential. In a call under NDA, we walk you through the real projects.
Do you work in German?
Yes. Interviews, workshops and documents run in German or English, whichever your teams work in.
Which accessibility standard do you design to?
WCAG 2.2 AA, by default. We design and test against it, so accessibility is part of the specs engineering builds from.
03
//FAQ
Questions
ANSWERS
01
How does a project start?
With a short discovery phase. We agree on goals, constraints and success criteria and put them in writing first.
02
What kinds of organizations do you work with?
Organizations that run on information: banks and insurers, airlines and rail operators, energy, pharma and software companies. Size matters less than the ambition for the product. The common thread is complexity: dense data, several product teams, or expert users with no time to spare. Early-stage companies with a hard problem are welcome too.
03
How do you approach complex digital platforms?
We map the work before we design for it: who decides what, under which business rules, and how the systems depend on each other. That map becomes the frame for every feature and team that follows.
04
How do you keep a large product portfolio consistent?
With a design system that engineering owns as much as design does: shared components, documented decisions and a review process for changes. New teams start from it instead of from scratch, and the portfolio still feels like one product as it grows.
05
How do you measure success?
We test the new product against the old one on the same tasks and compare time, errors and ratings. A project succeeds when the new version wins on all three. After release we measure again, and the work counts as done when the numbers hold in daily use.
06
Who will work on our project?
Programs of six to twelve months run with a core team led by Moritz Pommer, the founder. Specialists in research, interface design and engineering join larger programs.
07
Can we see the real work?
Yes. The views on this site are illustrative, because client work is confidential. In a call under NDA, we walk you through the real projects.
08
Do you work in German?
Yes. Interviews, workshops and documents run in German or English, whichever your teams work in.
09
Which accessibility standard do you design to?
WCAG 2.2 AA, by default. We design and test against it, so accessibility is part of the specs engineering builds from.
Project inquiries
Frankfurt and London. Operating worldwide
Interaction design for mission-critical software
Product and interaction design for enterprise platforms and apps. Tell us about your project.