DHO Case
DHuO
Product design on a B2B platform for APIs and integration — two years collaborating on the evolution of an enterprise product.
2 years in the ecosystem · co-creation of the Sphere DS · cross-functional proof
DHOThe system
People, product, and language.
-
People
- engineering
- architecture
- operations
Decision: design from the real tasks
-
Product
- API management
- integration
- AI
Decision: consistency across modules
-
Sphere
- foundations
- components
- alignment with engineering
Decision: a shared language
Different technical personas in the same multi-module product. The design system is the layer that keeps it coherent.
Context
DHuO is a platform for API management, integration, and AI (Engineering), used in complex enterprise operations. The interface has to serve technical depth and lower-code operation in the same experience.
Problem
Different personas (engineering, architecture, operations) share the same product. Consistency across modules and clarity of flow are product problems, not only UI problems.
My role
Product Designer for about two years, supporting the Principal Product Designer (Luca Di Monte): interviews, prototyping, UX for technical audiences, and co-creation of the Sphere design system.
Decisions
Inconsistency across modules → invest in Sphere (foundations, components, alignment with engineering). A developer persona is not a generic user → design from the real vocabulary and the real tasks.
Solution & artifacts
Screens and project details.
Technical UX + a design system at scale
The solution at DHuO was not "more screens". It was reducing ambiguity between technical personas, modules, and engineering — with discovery, prototyping, and the co-creation of Sphere.
- Flows and interfaces aligned with the vocabulary of the people who operate APIs and integration.
- Sphere as a shared language across products in the ecosystem.
- Collaboration with the Principal PD — without rewriting the lead's story.
What we discarded
Do not claim the "Principal PD / from scratch / 5 years" narrative — that story belongs to the lead. The honest case is a deep collaboration: discovery, UX for technical personas, and a design system at scale.
Impact
Qualitative evidence from peers (Lead PD, Architect, PM/SE): a design system in collaboration, translation of complex requirements into interface, interviews, and a technical persona.
What I learned
In a technical B2B product, good design reduces ambiguity between systems, people, and decisions — more than it "invents screens".