To understand user needs and pain points, we conducted stakeholder interviews and internal research sessions with commercial team members responsible for client tariff configuration. We mapped typical workflows and collected open questions around business rules, data dependencies, and operational risks. We also explored how tasks are triggered, what data needs to be visible or editable, and how user actions impact related systems. This helped clarify edge cases — like expired contracts, data validation sources, and the need for automated inputs (e.g. from uploaded documents or UUIDs).

Based on this research, we formulated and prioritized key Jobs to Be Done, such as:

• “When I receive info about a new client, I want to add all relevant data (name, contract, tariff grid) so I can access it later without relying on developers.”
• “When a contract expires, I want to mark it in the system to avoid further actions on outdated data.”
• “When I assign a tariff to a client, I want to ensure it’s linked to the correct contract and clearly reflected in the UI.”
• These JTBDs directly shaped the structure of the interface and informed constraints, validation rules, and hierarchy logic.

I assumed users struggled with tariff management due to the absence of a centralized interface and reliance on backend teams.

I hypothesized that allowing users to create and manage clients, contracts, and tariff grids in one place — with a clear hierarchy and constraints — would reduce errors and make them fully autonomous.

Based on all the insights and ideas gathered during the research phase, I translated them into a functional architecture by building a structured feature map

I translated the feature map into connected user scenarios and built a task flow to show how actions relate to each other.
Key flows included creating clients, linking contracts, assigning tariff grids, and managing entity status with cascade logic — ensuring a consistent and error-free experience.

designed the interface for managing clients, contracts, and tariff grids as a single, structured space. Each entity was represented in a tree-like hierarchy with contextual actions and clear relationships.

To validate usability, I ran moderated UX testing sessions with target users. I observed how they navigated the flow, created and edited entities, and handled edge cases like expired contracts or data conflicts.

Based on insights from UX testing, I refined the interface, clarified visual hierarchy, and addressed edge cases that caused hesitation or confusion.

After iterating on key flows, I prepared the final high-fidelity designs in Figma, documented interaction logic, and handed off the components to developers with specs and annotations.

What used to take hours of backend developer time, multiple sync calls, Jira tickets, reviews, and cross-team coordination — can now be done with just a few clicks.

The new interface gave the commercial team full control over client tariffs without relying on engineering. It significantly reduced time-to-action, eliminated unnecessary communication loops, and became the go-to tool for all tariff-related operations.