Planning Center Resources (as it was originally called) began as a basic facilities management tool for tracking equipment, rooms, and their availability. Over six years, I led design in the product evolution that transformed it into Planning Center Calendar, a comprehensive church-wide event calendar with full event management functionality, conflict resolution, and cross-product integrations. This wasn't a single redesign but a thoughtful progression of improvements that fundamentally shifted how churches manage their events.
We started by modernizing the Rooms and Resources interface, borrowing design patterns from Planning Center Services (Planning Center's flagship product), to introduce inline editing with automatic saving. We also added crucial tracking fields churches needed: photo uploads for equipment condition, location tracking, and asset management features.
A major redesign consolidated event management onto a single page. As a product team, we established a guiding principle to remove steps rather than add them, making all common actions visible or one click away. We designed a tabbed interface (Overview for scheduling, Activity for audit trails, Details for additional event context and settings) with an inline search-based booking interface and color-coded approval statuses. This became the foundation for future feature development of event management.
We also designed a conflict resolution system that maintained transparency while giving staff flexibility to share rooms with other events in certain cases. We introduced a designated permissions role for members who could resolve conflicts by choosing which event had priority.
Following this, we designed a brand new calendar view with advanced filtering and tagging capabilities. Previously, the calendar was a minor, non-interactive sidebar element used to view events. We repositioned it front-and-center, making it the primary interface for event management and making it fully featured and interactive. We also replaced rigid folders with flexible tag groups, and added advanced filtering by rooms, resources, departments, approval status, and more. We also added the ability to create event templates for commonly recurring events.
Throughout these iterations, I collaborated closely with our product manager on design decisions and worked with our development team to ensure everything integrated smoothly with Planning Center's broader system. The frontend was built primarily in React with CSS-in-JS styled components on a Ruby on Rails backend.