Role
Senior Product Designer
Jug.ru Group · Product & brand · 2019–2021
One platform, four kinds of people who don’t want the same thing
Jug.ru Group runs a portfolio of deeply technical conferences for experienced developers. Behind each event sit speakers, a programme committee, the companies that buy tickets in bulk, and thousands of attendees.
Roles served
4, on one platform
Ticket processing
3× faster
Pivot to online
2 months
The problem
Companies buy 10 to 100 tickets at a time, and HR handed them out one by one, by hand — slow, and easy to get wrong. There was also no way to reach a guest after the event ended.
Then COVID cancelled every offline conference at once.
The solution
Personal accounts, each built around what that person actually had to do: companies buy and distribute tickets, speakers work on their talks with the programme committee, guests keep the recordings and materials.
And an online platform that carried the offline event over rather than replacing it with a video player — three parallel streams instead of three stages, brandable partner pages instead of expo booths, and an off-the-shelf 2D game engine so people could walk the venue, drop into a booth, sit down in a talk.
Four roles, four different jobs
- Guest — an invitation, then every recording, deck and extra material in one place once the event is over.
- HR — thirty tickets handed out in a few minutes instead of thirty emails.
- Speaker — submit a talk, work it out with the programme committee, see the edits and where the application stands.
- Organiser — every speaker’s progress and details on one screen.
Orders, ticket distribution, invitations and their status, and the archive a guest keeps afterwards.
A component library underneath
Elements built once and reused across layouts — faster to build, and consistent without anyone having to police it.
Selectors, inputs, grid, colour, buttons, menus, pagination, radios, checkboxes.
The conference, online
The main page opened on video from past conferences — talks, speakers, what is worth watching — and led into whatever was running next.
A conference page held what a venue holds: tracks, an exhibition, playlists of past talks. Booths carried the partner’s own branding and led through to their page. You could navigate it the ordinary way, or walk it in the 2D game.
Four days, several tracks a day. Favourite the talks you want and that is your schedule — miss one and it is there on demand.
The site, the venue you could walk through, the four-day programme, and a talk page.
Partners who could brand their own pages
Partner pages were customisable too. We did not build a separate tool for it — partners used ours, with a guide showing every combination, so the choice was made from examples rather than from a spec.
The same blocks in four treatments — a partner picks from examples, not from a spec.