Simplifying content scheduling: Designing a date-agnostic calendar interface & recurrence model to replace legacy spreadsheets for 80%+ of users.

  →   Designed a web-based timeline interface that replaced fragmented offline planning tools, enabling users to manage and publish content across thousands of distributed digital signage endpoints.

This project was initiated during a massive strategic inflection point. The company was migrating its core product offering away from a desktop-based architecture that was nearing the end of its operational lifecycle. The business committed heavily to research and development to build a modern, web-based SaaS platform.

Rather than executing a risky, 1:1 replication of the massive desktop app, leadership decided to break the software's capabilities into logical, task-focused web modules, mirroring how major cloud suites separate platform features into independent tools. As the first product designer hired to support this transition, my responsibility was to anchor the design patterns for one of the platform’s most critical operational pillars: network-wide content scheduling.

  →   Grounded the product direction by mapping information architecture and wireframing standard linear calendar concepts before uncovering deep usability bottlenecks.

Before landing on a novel layout paradigm, our team had to explicitly define the foundational infrastructure of the product. Schedulers at large organizations were handling hundreds of disparate visual assets, data feeds, and hardware configurations. Through intensive collaborative whiteboarding sessions, user flows, and ecosystem maps, we plotted out how data would flow through the cloud web application. We designed early technical schemas to link standalone files and asset libraries with independent time parameters.

Our initial design concepts leaned heavily on familiar UI patterns. We structured full-screen layout iterations built around traditional multi-day, linear weekly grids, mirroring standard consumer calendar platforms. However, as we progressed into interaction planning and early concept validation, we ran into an immediate wall of visual clutter and data bloat...

  →   Based on real-world user workflows, we made a critical pivot to collapse a sprawling calendar into a date-agnostic 24-hour timeline to reduce repetitive tasks and significantly increase utility.

To match this "Repeating Daily Schedule" mental model, I designed the interface as a full-screen, date-agnostic 24-hour canvas. It completely side-steps the clutter of a multi-day view. Users can click and drag directly on the vertical timeline to create a content block, adjust its duration on the fly, and assign a specific playlist or media asset to that slot.

When a user selects a standard time block, the system applies a focus state, pulling the precise hourly parameters and a live visual preview of the media asset into the right-hand details inspector panel. This gave enterprise communicators an instantly recognizable, highly tactile way to map out their baseline daily broadcast without any structural clutter.

Designing a 24-hour visual timeline to be 100% responsive without collapsing into a completely unusable, microscopic grid was a major constraint. Rather than treating mobile as an afterthought or executing a lazy mobile-first strip-down, I maintained feature parity by shifting the interaction layout.

On smaller screens, the side-by-side multi-column desktop layout stacks fluidly into a single-column view. The 24-hour timeline uses an isolated vertical scroll container with enlarged, thumb-friendly tap targets for content blocks. Selecting a block pulls up a panel overlay, giving field operators full access to duration controls, asset swaps, and live media previews on the go.

  →   Built a layered UI paradigm that allowed users to visualize calendar exceptions directly over the master daily schedule without breaking the underlying layout continuity.

While the 24-hour recurring schedule solved the vast majority of our users' needs, we knew a completely static daily recurrance wouldn't handle every real-world scenario. Schedulers still had to account for the messy edge cases, like a special morning weather warning, a one-time company town hall, or a repeating afternoon announcement from the CEO.

The interaction challenge was highly complex: how do you show a date-specific exception sitting right next to a day-agnostic schedule without breaking the user's sense of time?

The solution was a novel overlay system that split the screen into clear behavioral depths. On the left side of the screen, I designed an isolated "Interrupts" shelf, which functions as a dedicated repository for exception-based rules. These interrupts can be configured as one-time events or recurring exceptions tied to specific dates.

The real interaction victory happens when a user interacts with an item this shelf. When an interrupt is clicked, the card highlights in a colored focus state, and the interface dynamically displays the exception blocks right over the 24-hour timeline using a floating layer with a subtle drop-shadow.

This design gave users the ultimate mix of flexibility and predictability. They could select any override from their list and instantly see exactly how it would interact with, block out, or supersede their baseline daily scheudle on the specific day it was scheduled to run, all without ever leaving the page or changing their view.

  →   Validated the web application modular strategy by hitting comprehensive engineering milestones and successfully transitioning the foundational tier of legacy desktop accounts.

Every complex, v1 enterprise product requires careful trade-offs to clear the runway for deployment. During early concept validation and testing loops, we identified a few interaction gaps where our initial implementations didn't perfectly align with a user’s ultimate mental model. The technical handling of concurrent, overlapping content blocks and the complexity of managing complex "interrupt" priorities remained somewhat abstract in the interface.

Additionally, we had to table advanced features like a live visual timeline scrubbing mechanism and deeper usage analytics for a future iteration. Acknowledging and documenting these product concessions early allowed us to protect our active engineering sprint cycles without losing sight of user experience improvement opportunities.