TA ČR: Designing an eGovernment system for three user groups

The problem: Newcomers and experienced users got the same intro screen. Some got lost, others clicked through unnecessary steps. Users didn't know where they were in the process or what was expected of them.

Solution: Returning users see quick actions for items in progress, newcomers get a short video walkthrough and a clear first step. A dashboard with contextual help right at each step, and a sidebar that changes with the phase of the process.

Why: Each group needs something different at the start. One screen for everyone doesn't work for either of them. Help should live where the question arises — not in a PDF manual.

The problem: Review results sat in long tables. Comparing two projects meant jumping between screens.

Solution: I turned the scoring report into cards that can be compared side by side, with a clear data hierarchy.

Why: Reviewers decide by comparing. With both in front of them, they decide faster and with fewer mistakes.

The problem: Every new screen was built from scratch, development was slow and the interface inconsistent.

Solution: I built the DISTA UI Kit with tokens and components in Figma, connected to Storybook for developers.

Why: One source of truth for design and code. New features are assembled from ready-made components and design patterns, so they ship in half the time compared with previous sprints. Specs are clearer for developers, and they know how to proceed.