Global Schedule Settings
Turned a narrow one-module brief into a universal scheduling system that gave every CMS module automated publish and unpublish capability. across 3 teams, 8+ modules, 0 future design engagements.
The brief was contained: let clients pick a date and time for a page to go live. One module. One feature. But the brief had no visibility into who was actually waiting on this, or why. A nonprofit needed a fund to close at midnight. An events team needed a page live the moment ticket sales opened. An admin needed config changes active before a campaign, without going public early. Same feature. Three completely different scheduling needs. I expanded the scope before writing a pixel.
Client
Ticketmaster
Services
Product Design · Systems Thinking · Stakeholder Alignment
Industries
Live Entertainment · Enterprise SaaS · Ticketing
Date
2024
The UX decision: one universal flow, not three bespoke ones. Different modules have different UI patterns and content hierarchies. The easy answer was to optimise scheduling per module. The right answer was to establish a consistent scheduling language across the CMS, so clients would recognise the pattern instantly on the second encounter, regardless of which module they were in. The core interaction is identical everywhere: Enable scheduling → Select type → Set date/time → Confirm. Scheduling is opt-in. Default remains instant publish. The date/time picker only surfaces after a client indicates intent to schedule, keeping the primary path fast and the scheduling path deliberate. The process move: I shipped the first slice, then went looking. After it landed, every CMS module was audited against three scheduling types and brought to a PM workshop. That session surfaced use cases neither party had anticipated, and turned a UI feature into a scheduling model for the entire CMS. The instinct to look beyond the brief was right. If I ran this again, the audit would happen first.
8+ CMS modules now have universal scheduling built in. 3 schedule types designed: publish, unpublish, and a combined publish + unpublish window. 1 PM workshop that redefined the project scope entirely. 0 future modules needing a new design engagement, the universal flow means every new module inherits scheduling automatically. Clients can now go to sleep before go-live.