Context & problem
This project was for an Indian subsidiary of a leading European trade fair organiser, which runs 25 shows a year across agriculture, technology and consumer products. Each show has its own exhibitors, visitors, finance approvals, vendor logistics and legal sign-offs, managed by a team of 100 to 150 people. Despite that scale, the platform had never really been designed. It had grown piece by piece. To do anything, you had to navigate into a specific event, find the right screen, and start from there. Several workflows, including visitor registration and vendor onboarding, had no digital version at all.
There was no comparable system to reference in the Indian trade fair market. I was the only designer, responsible for every role, every flow and every screen across both the internal application and the public-facing websites. The hard part was understanding a system where how Finance handled an event directly shaped what Operations could or could not do next, and a change in one role could break the workflow of another. The question I kept coming back to was: how might we give a team managing 25 shows a year a way to work across all of them at once, instead of treating each event as a separate island?
Users & conflicts
Process
Leadership was hesitant to brief teams on the incoming changes early on, out of concern about resistance to adoption. This limited how much direct user input I could get in some roles before designs were finalised.
System map & flows
Key decisions
Handoff
I worked with the dev team daily throughout the build rather than handing off designs all at once. Every screen was annotated with states, edge cases, permission conditions and responsive behaviour. For more complex flows like the approval chain and the admin permission system, I wrote separate logic documents alongside the Figma files, since the screens alone could not capture everything that needed to happen on the backend.
The admin permission system works across four levels, role, event, page and action within a page. At some point during development it became clear the team had interpreted the hierarchy differently from how it was designed. They were applying event scope before role scope, which would have broken the entire model. Catching it during a review call saved the backend team a large rework.
Outcomes
Takeaways
What I enjoyed most about this project was working on a complex system with a large number of stakeholders. I also got to go to real trade fairs and see what the internal teams go through while an event is running. Seeing it first-hand changed how I thought about the design, because some of that pressure never comes up in a meeting.
Access to users was limited early on, so I relied on system audits and conversations across roles to fill the gaps. It worked, but it added iteration cycles. I did ask for direct access, but I could have made the need clearer from the start. On a future project I’d make that case early, with a clear view of what direct access would save the team.


















