Case study — 01
Anjumanlar
A conference platform for 40,000 researchers — rebuilt around one question: what does this person need to do next?
- Client
- Anjumanlar.uz
- Role
- Product design · Design system
- Team
- Solo designer + 3 engineers
- Year
- 2025
Registration was a 14-step form that nobody finished.
Anjumanlar hosts around 300 academic conferences a year. Every one of them needed abstracts submitted, reviewed, revised and scheduled — and all of it ran through a single form that had grown a new field every time somebody asked for one.
We started by watching eleven researchers try to submit a paper. Nine of them stopped to ask a colleague what a field meant. That was the whole brief.
One submission object, four views, zero duplicate fields.
Instead of a form, we modelled a submission as a living object that changes state — draft, under review, revision requested, accepted. Each role sees the same object through the view that matches what they can actually do with it.
The component library that came out of it now covers 62 components and three products. New conference types ship in days rather than a quarter.
- +38%
- Submissions completed without support contact
- −52%
- Time from draft to accepted abstract
- 62
- Components in the shared library
Next project
NurbankDigital banking · Product design · 2024