01 / THE PROBLEM
When relationships are hidden, complexity leaks into the UI.
Linked campaigns introduced dependencies that were not obvious from the interface. Users needed to understand what changed, what would propagate and where the source of truth lived.
The challenge was larger than a screen redesign. I first had to understand backend behaviour, existing product rules and the places where the current experience diverged from the intended model.
02 / INVESTIGATION
I mapped the system before I designed the screen.
- Mapped the workflow across connected campaign states.
- Investigated backend behaviour and propagation logic.
- Uncovered a production bug and a mismatch between product behaviour and design.
- Documented edge cases so Product, Design and Engineering shared the same model.
03 / DIRECTION
Make the relationship visible without making the product feel heavy.
The direction used clearer hierarchy, predictable states and progressive disclosure. Users could understand the relationship when it mattered without being forced to process every dependency at once.
I created a phased product plan rather than trying to solve every dependency in one release.
04 / PROTOTYPE
Prototype the behaviour, not just the pixels.
An interactive prototype helped communicate connected states and edge cases with Product and Engineering. It became a shared artifact for discussing what should happen before implementation.
05 / REFLECTION
Complex SaaS problems require product thinking before interaction design.
The strongest decisions came from understanding the system underneath the UI and creating a shared model that Product, Design and Engineering could use.