Service · Training

Your team learns UX for specialist systems, on your own product instead of examples.

We train product, engineering and business teams in what complex specialist systems demand: usability that holds up under pressure, research with expert users, design systems that engineering actually uses, and content that does not slow down case handling. On site or remote, hands-on, with your system on the table.

Book an initial call How it works

In short

Training is our service for teams that want to master UX for specialist systems themselves instead of buying it in permanently. We bring the methods we apply every day in banking and industry and apply them in the training to your own product: your screens, your processes, your expert users. Participants leave with results that can land in the next release, not with slides. Formats exist for product teams, engineering teams, business departments and content teams, on site at your premises or remote.

We do not teach generic UX. Specialist systems follow different rules from consumer products: the users are experts, the tasks are deadline-critical, the interface must not hide complexity but make it manageable. That is the centre of every training. Anyone who learns with us how to interview a tax department or observe a control room learns it with the pitfalls that actually occur in regulated and industrial environments.

Who it is for

Product teams at software vendors
You build specialist software for banks, depositaries or industrial customers and want new modules to be understood without lengthy training. The team should recognise and fix usability problems itself, before customers report them.
Engineering teams with a design system
Your development builds interfaces from components, but library, tokens and documentation are drifting apart. The team should understand how a design system is maintained, extended and defended against deviations.
Business departments shaping their systems
Fund accounting, tax, operations or the control room formulate requirements for a system they use every day. They should learn to describe and verify requirements in a way development and vendors can implement.
Content and CMS teams
You maintain texts, help, error messages or documentation in specialist systems and portals. The team should use language so that expert users work faster and more safely, and build the structures in the CMS accordingly.

What is included

Every training is a format with a fixed core that we tailor to your product and your team.

UX for specialist systems
Fundamentals and patterns for interfaces that experts operate under time pressure: information density instead of emptiness, error prevention, deadline logic, status displays, tables and data-entry screens. We work on your screens and improve them during the training, with a rationale you can reuse later.
Research with expert users
Interviews, observation at the workplace and usability tests with people who know their system better than any designer. The team learns to ask questions that do not put experts off, to document sessions and to turn findings into decisions. Practice happens on real tasks from your product.
Design system for engineering teams
How a design system is built, documented and anchored in code: tokens, components, variants, states, accessibility, versioning. We work in your team's repository and show how design decisions become code decisions without one side blocking the other.
CMS and content teams
Language in specialist systems: labels, error messages, help texts, notifications. Plus information architecture and content models in the CMS so that content stays consistent, findable and maintainable. Practice happens on your texts and your system.
Working on your own product
No case study from another industry. We prepare the training with your screens, processes and questions and let participants work on exactly what they face in their daily work. What emerges in the training is a first draft for the backlog.
Material and follow-up
Participants receive guides, checklists and templates we use ourselves: interview guide, observation protocol, test plan, component checklist. After the training we summarise results and open points as a handover to product and development.

How it works

1
Clarifying the need
In the initial call we clarify which team is being trained, which decisions it should make better afterwards and which product goes on the table. From that we choose the format or combine building blocks into a programme.
2
Preparation on the product
We review your system, your screens or your design system and build the exercises on them. For research trainings we clarify with you which expert users are available for practice sessions and how we involve them.
3
Training, hands-on
On site or remote, with short inputs and long working phases. Every unit ends with a result on your product: a reworked dialog, an interview guide, a documented component, a tested flow.
4
Handover
We summarise what was produced and what remains open and hand it over to product and development. The team has not only learned but has a state it can continue working from directly.
5
Support afterwards
On request we stay available: for follow-up questions, a second look at the first research sessions run by the team, or reviews of the first components. Where more is needed, training transitions into UX Support.

What we commit to

Trainers who design specialist systems in banking and industry themselves, not just teach about them.
Every exercise runs on your product, not on someone else's example.
Participants leave the training with results that can go into the backlog.
Material we use ourselves in day-to-day projects, free for the team to use.
On site or remote, in German or English, with the same depth.

Extensions

Training can be combined with services that anchor what was learned in daily operation.

UX retainer with quarterly tests
Hour package for further development
Design System as a Service
Regular maintenance

UX retainer with quarterly tests: We test your system quarterly with expert users and discuss with the team what it derives from that for the next releases.
Hour package for further development: An allocation the team can draw on for reviews, sparring or implementation help when it continues on its own after the training.
Design System as a Service: We keep running the design system your engineering team built up in the training: components, tokens, documentation and versioning.
Regular maintenance: We take over the upkeep of library and documentation in a fixed rhythm so the team can concentrate on features.

Frequently asked questions

Is this a standard course or tailored?: Tailored. The formats have a fixed core, but exercises, examples and material come from your product. A design-system training for an engineering team looks different from one for a product team, even if the fundamentals are the same.
How many people can take part?: Trainings work in groups where everyone works on real tasks and gets feedback. The right size depends on the format, and we set it together. For larger organisations we split into several groups or combine a training with multipliers inside the team.
Do participants need prior UX knowledge?: No. We assume professional knowledge of your product and your processes, not a design education. For engineering teams we start from code and components, for business departments from processes and requirements, for product teams from backlog and roadmap.
On site or remote: which is better?: Both work, with different strengths. On site, observation at the workplace and whiteboard work are easier to include. Remote suits distributed teams and formats that happen on screen, such as design-system work in the repository. We recommend depending on the format.
Can we combine several formats?: Yes. A common combination is UX for specialist systems plus research with expert users for product teams, or design system plus UX for specialist systems for engineering. We build a coherent programme from them instead of lining up individual courses.
What happens to the results from the training?: They belong to you. Reworked dialogs, interview guides, documented components and test findings are handed over in a structured way to product and development. Many teams take them straight into the backlog.
Can training accompany an implementation?: Yes, as a complement. During the introduction of a new specialist system we train key users, for example, to capture requirements and feedback in a structured way, while implementation support carries the introduction itself. The two interlock.
How do you handle confidential content?: We sign a non-disclosure agreement up front and work with test or anonymised data. Training material that shows your product stays with you and is not used for other clients.