B2B Dashboard Design for a Leading Middle East Exhibition & Events Organiser

The Core Problem

The exhibitor management process at ATEX was entirely manual before this system. There was no single source of truth where tasks were communicated through emails, requirements were tracked on spreadsheets, and deadlines were easy to miss because there was no system enforcing awareness of them.

The impact was felt on both sides. For exhibitors, the process felt fragmented and stressful, especially for mid to senior-age users who weren't digital natives and didn't need an interface that showed off design, they needed one that just worked. For the ATEX team, chasing exhibitors for outstanding requirements was a recurring operational drain.

The design challenge was specific: take a genuinely complex exhibitor workflow multiple task types, multiple deadlines, multiple stakeholders, and make it feel simple enough that a user could complete everything independently, without needing to ask for help.

Additionally, there are no pre-launch baseline metrics for this project the portal replaced a manual process entirely, so there was no previous digital platform to audit against. The measure of success was qualitative: could exhibitors complete everything independently, and did missed deadlines stop?

Competitive Research

B2B dashboard design has its own set of conventions that exist for good reason, consistency reduces the learning curve, especially for users who don't live inside a system every day.

I looked at how enterprise event management platforms and exhibitor portals structure their task flows, systems like Eventbrite's organiser backend, Salesforce event tools, and regional exhibition management software. The consistent finding: most of these systems are functionally complete but visually overwhelming. They prioritise feature density over task clarity. A user who logs in once every few weeks to submit documentation doesn't need a power-user dashboard, they need a clear answer to one question: what do I need to do right now?

I also considered the user demographic deliberately. ATEX's exhibitors span a broad age range, many are mid to senior-level professionals in industries where digital tools are used but not obsessed over. The interface needed to feel familiar and corporate, not experimental or trend-driven. Clarity over cleverness.

Design direction: Modern but grounded. Corporate without being cold. A UI that feels immediately trustworthy to someone opening it for the first time, one that shows them exactly where they are, what's done, and what's next.

The Solution

Mapping a manual process before designing a digital one. The most important thing I needed to understand before designing this portal was exactly what exhibitors were doing manually, because the system needed to replace a real workflow, not invent an imaginary one.

I ran a Google Meet discovery session with the ATEX operations team and account managers who managed exhibitor relationships day-to-day. These were the people who knew every pain point firsthand because they were the ones receiving the panicked emails when something was missed.

The questions I focused on:

• Walk me through exactly what an exhibitor needs to do between confirmation and event day, every task, every document, every approval.
• Which tasks do exhibitors most commonly miss or submit late, and what happens when they do?
• Where does your team spend the most time chasing exhibitors, and why does that keep happening?
• What does an exhibitor typically contact you about that they should be able to figure out themselves?
• Are there exhibitors who handle this smoothly every time, what do they do differently?

The answers were mapped in a Figma whiteboard, every task type identified, grouped by category, and sequenced by dependency. Some tasks couldn't begin until others were approved. Some had hard deadlines. Some were optional but easy to overlook. That complexity was the entire design problem.

From the whiteboard I built a detailed user flow diagram, the most complex of any project I've handled. Every task state (not started, in progress, pending approval, complete, overdue), every decision point, every notification trigger. Only once the full flow was mapped and reviewed did I move into UI design, because designing the interface before understanding the flow would have meant designing the wrong thing beautifully.

The dashboard UI was Figma-only given the complexity of the system, two weeks of hi-fi design covering every screen state, every empty state, every error condition, and a full component library for handover to the development team.

Brand Guidelines

The color system for the ATEX Exhibitor Portal was built around the brand's established identity: bold, confident, and corporate.

Typography: Clean, legible, corporate-appropriate, optimised for data-dense UI environments where readability at small sizes matters more than editorial flair.

Tone: Direct and functional. The portal communicates clearly the status labels, deadline notices, and confirmation messages are written without ambiguity. No marketing language inside a working tool.

The Outcome

The portal launched to ATEX's exhibitor base and the results came directly through user feedback collected by the SEO team and shared as data sets post-launch. There were no baseline metrics to compare against, this system replaced a manual process, not a previous digital one, but the qualitative shift was clear and consistent.

Exhibitors were able to navigate the dashboard independently, completing all required tasks without needing to contact ATEX staff for guidance. The most significant piece of feedback: missed deadlines, which had been a recurring issue under the manual process, were effectively eliminated. Users described the system as more efficient and more transparent than anything they had worked with previously for exhibition management.

For a system that replaced email threads and spreadsheets, those outcomes are exactly what the design was built to deliver.

What I Took From This

Designing a dashboard for occasional users is a completely different problem from designing for daily active users, and this project made that distinction very clear. When someone opens a tool once every few weeks, the onboarding experience essentially repeats every time, so the interface has to be self-explanatory on every single visit. The decision to anchor the entire experience around task status rather than feature navigation came from that insight, and the user feedback confirmed it was the right call. This was also my fourth system dashboard project, and what I've learned across all of them is that the most complex workflows become simple the moment you stop designing for the system and start designing for the next action the user needs to take.