A. G. | Portfolio
Alicja Galon | Portfolio
How to design
a complex system where data is shared across modules and contexts?
Before designing the interface, I had to define or redefine the dependencies between data, actions and next steps, and then turn them into a workflow that remained clear despite the number of exceptions and scenarios.
CONTEXT
The challenge was to create and structure a complex system where the process changed depending on multiple conditions - including the client, country, reporting type, product and previous user decisions.
Figma · FigJam · Miro · Jira · Teams · Adobe Photoshop · Adobe Illustrator · Adobe Acrobat · MS Excel · Paper and Pencil
DESIGN & RESEARCH & COLLABORATION TOOLS
From behavioural data to interface decisions
Information flows across modules, so what looks like a single screen is often just one step in a much longer workflow.
PROBLEM
Many actions depend on data entered and decisions made earlier in the process.
MY WORK
Designing Comply meant building a connected system while its modules, data and requirements evolved sprint by sprint. |
Building the system incrementally
Comply was developed over a year, with client configuration, imports, products, reporting and tasks designed and expanded in parallel through Agile sprints.
Keeping workflows and UI consistent
I mapped workflows, validation, exceptions and data dependencies, updating them as the system evolved. I worked with an existing design system, extending it with new components and patterns when the product required them.
KEY DECISIONS
Large tables, advanced filters, bulk actions, view configuration and forms needed to preserve context even when users were working with large amounts of data.
What was an effect?
Complex business logic war broken down into smaller operations and clear flows without unnecessary data, that users could complete without constantly thinking about the structure of the system.
SPECIAL FEATURE OF THE PROJECT
The scale of dependencies.
Here, design started with understanding the logic behind the process. Workshops and ongoing communication with people working with the data helped us clarify requirements, uncover dependencies and validate both the analysis and the interface design.
The biggest challenge for me...
was bringing together the needs of employees who used the same data in different ways and at different levels of detail. The system had to support all of them without making the workflows too complicated.
Product Designer · UX/UI Designer · Dog&human trainer
I turn complex problems into clear, useful, and buildable products. If you’re looking for a Product Designer who connects user needs, business goals, and technology - let’s talk. ;-)
Website copyrights by: Concept Pulse Alicja Galon
Check the Privacy Policy.