DDC Case
Defesa de Cor
When people get lost between products in the same suite, a simple design decision can bring back clarity — and productivity.
Color and identity as the anchor for "where am I" in the suite
DDCThe decision
Where am I?
Before: two identical products — the user does not know which one they are in.
An abstract diagram: the real suite is confidential and the colors here are illustrative. The structure of the two products is the same; only the identity changes.
Context
Launch of the second product in a suite. Name and logo are omitted for confidentiality.
Problem
Users did not know which program they were in during the flow.
My role
Product Designer: a diagnosis from the feedback, and a proposal for differentiation.
Decisions
Use color and product identity as the context anchor, without fragmenting the suite.
Solution & artifacts
Screens and project details.
Identity as the context anchor
The solution was deliberately simple: differentiate the products in the suite by the color and identity of each program, keeping visual cohesion — without inventing heavy navigation or "AI" where the problem was ambiguous context.
- A diagnosis from the feedback: "I don't know which program I'm in."
- Color and identity per product as a persistent signal in the flow.
- Suite cohesion kept — differentiation without fragmentation.
What we discarded
Problem
Users did not know which program they were in during the flow.
Qualitative result
Better identification of the active product, and less risk of acting in the wrong program.
Impact
Qualitative impact: better identification of the active product and less risk of acting in the wrong program. No numeric metrics published.
What I learned
A simple solution can have a high usability impact when the problem is clarity, not a missing feature.