Boeing
Boeing
Boeing
Boeing’s aviation software subsidiary Jeppesen builds the software airline dispatchers and operations control centers use to track their fleets and decide what happens next.
The Fleet Insight platform is used by major airlines worldwide. Pommer Design spent a year inside its product team and designed new decision-support features for dispatch.
Boeing’s aviation software subsidiary Jeppesen builds the software airline dispatchers and operations control centers use to track their fleets and decide what happens next.
The Fleet Insight platform is used by major airlines worldwide. Pommer Design spent a year inside its product team and designed new decision-support features for dispatch.
Boeing’s aviation software subsidiary Jeppesen builds the software airline dispatchers and operations control centers use to track their fleets and decide what happens next.
The Fleet Insight platform is used by major airlines worldwide. Pommer Design spent a year inside its product team and designed new decision-support features for dispatch.
Year
2023
Client
Boeing
Category
Aviation
Duration
1 year
Objective
Objective
Airline operations control runs around the clock, and Fleet Insight is part of it. A new feature goes straight into live operations, so it has to work under full load from day one.
Role
Role
Pommer Design owned the user experience. That meant redesigning core user flows, interviewing dispatchers and control-center staff, and deciding how to show fleet data so people can act on it. The work spanned the existing design framework and its successor.
Approach
Approach
The dispatchers’ workflows set the constraints. Pommer Design built prototypes from the research findings, tested them against real operational scenarios and turned what held up into reusable patterns.
Outcome
Outcome
New Fleet Insight features shipped to production, including Gantt-style timeline charts that show the status of a whole fleet in one view.
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.