UX practice
Product & interface design
For complex products that are harder to use than they should be.
At a glance
- Format
- a fixed-scope project, typically 4–12 weeks.
- You receive
- information architecture, wireframes, prototypes, high-fidelity UI, and a handover your engineers can build from.
- For
- teams whose complex product needs to feel simple.
The problem
People cannot find things. The menu has grown by committee. Designs reach engineering with questions still open, and the build drifts from what was drawn.
What you get
- Information architecture. We structure content and navigation for findability, so the product matches how people think about it.
- Wireframes and prototypes, to test ideas with real users before they are built.
- High-fidelity UI, grounded in research and ready for production.
- Interaction design, for how each screen behaves, not only how it looks.
- Design-to-development handoff. Production-ready designs and documentation your engineers can build with confidence.
Is it right for you?
For
- Complex products that need to feel simple.
- Payment or self-service flows that are losing customers.
- Teams whose handover to engineering keeps breaking down.
Not for
- Shared components across several products and teams. See Design systems.
How it works
Most engagements begin with a short discovery call to scope the right first step. Every engagement is tailored, but the backbone stays the same.
Understand
We immerse in your business goals, constraints and users — reviewing what exists and what's missing.
Define
We frame the real problem, shape the information architecture and agree on how we'll measure success.
Design
We wireframe, prototype and validate with real users — iterating until the experience is right.
Deliver
We hand off production-ready design, documentation and a system your team can extend with confidence.
Proof and further reading
From roles Matthaios held before and alongside UXellence. Client names are covered by non-disclosure agreements.
- One group, four kinds of business: ote.gr, otetv.gr, cosmote.gr and germanos.gr, from a gold-awarded corporate portal to a mobile operator's and a retail chain's online stores.
- Billing and self-service for a telecom operator: call-centre data set what to fix first in online bill payment and self-service. 90% satisfaction with online payment; overdue payments down 40%.
- Merging two brands into one digital experience: customer journeys mapped, the new navigation tested with customers, and both brands' content inventoried and redirected.
- The handover check: the free 22-point check of one design file before it goes to engineering.
- The UX iceberg: problem framing, information architecture, content design, states.
Who does the work
Matthaios Mantzios leads every engagement himself, and we take on a limited number at a time. He has worked as researcher, information architect, designer, product owner and manager, and connects research, strategy, design and delivery into a single, accountable thread.
Questions
What happened to the information architecture service?
It is part of this service now. Information architecture, navigation and findability are where the design starts.
How long does a project take?
Typically 4–12 weeks, with a fixed scope agreed before it starts.
Will our engineers be able to build from it?
That is the point of the handoff: production-ready designs your engineers can build with confidence.
What if we need more afterwards?
If the work shows you need shared components across products, that is Design systems.
Ready to get started?
Tell us where you stand. We'll suggest the right first step.
Book a discovery call