Booketing
Introducing Venue and Event Management to Booketing
UX/UI Designer Contactor | Feb 2025 to Aug 2025
Wireframe, High-Fidelity UI Design, Customer Journey Mapping
Overview
Booketing is a travel-experience management platform that helps venue operators manage experiences, tickets, bookings, and other non-hotel inventory.
The company planned to add venue and event management to the existing platform. My role was to translate an engineering-led user flow into a complete interface, identify missing states, and recommend improvements.
One of my main recommendations was a draft state that allowed operators to save incomplete events before publishing them. No formal usability testing was conducted, so the impacts described here are intended outcomes.
Booketing customers relied on third-party platforms because the product did not support venue and event management. This separated event setup from the offerings they already managed in Booketing.
The initial workflow also required operators to complete every event detail before saving or publishing. This assumed that schedules, pricing, images, ticket options, and venue information would be available in one session.
Without a draft state, users could lose unfinished work, enter temporary information, or delay setup until every detail was confirmed.
Problem
My Goal
My goal was to design a venue and event management workflow that integrated with Booketing’s existing product.
The experience needed to support incomplete work, multiple events, pre-publication review, and patterns the engineering team could implement without rebuilding the platform.
What I Did
I reviewed the engineering team’s user flow to identify primary tasks, information requirements, dependencies, system constraints, and repeated interaction patterns.
The review showed that the workflow treated event creation as a single-session task. I challenged this assumption and recommended separating saved work from published content.
I also designed the navigation, core screens, interface states, and reusable components required to support venue and event management.
The Design Decision
I introduced two distinct actions: saving progress and publishing a completed event.
A draft state allowed users to record available information and return later. Publishing remained a separate action with stricter validation requirements.
This decision supported operators managing several events or waiting for details from other teams, suppliers, or venue partners.
The Solution
Users could save partially completed event information and return to it later.
Published
Publishing remained a separate action with stricter requirements.
This preserved the business requirement that customers should not publish incomplete offerings while giving them more flexibility during setup.
Draft State
Record available information without completing the entire form
Leave the workflow without discarding their progress
Manage several unfinished events
Review missing information before publication
I also designed the screens to align with patterns already used in Booketing. This reduced the need to introduce entirely new interactions and made the proposed feature more practical to integrate with the existing system.
Business Impact
The intended business value came from operational efficiency and reduced publishing risk rather than direct sales growth.
By adding venue and event management to the existing platform, Booketing could support more of the customer’s workflow without requiring external tools.
The draft feature also created a safer publication process. It allowed customers to save incomplete work while preserving validation requirements for live offerings.
From a product perspective, this could support:
Lower risk of incomplete event information being published
Better organization of work-in-progress events
Greater consistency between Booketing’s sales and management capabilities
Reduced dependency on third-party event-management tools
A reusable draft-and-publish pattern for future content-management features
