GoReminders
Redesigning GoReminders — a scheduling and reminder platform used daily by service-based businesses.
About project
GoReminders is a scheduling and client communication platform built for appointment-based businesses. The product combines a calendar workflow with automated reminders and follow-ups, helping teams keep schedules accurate and clients informed. The agency delivered a UX/UI redesign focused on navigation, key settings, and the appointment creation flow—supported by a scalable component system for consistent growth.
TL;DR
01
Challenge
Navigation and scheduling slowed
as modules and data density grew.
02
Approach
Audit workflows, rebuild IA, design
reusable components and states.
03
Solution
Sidebar navigation, calendar-centric scheduling, consistent patterns across modules.
04
Outcome
Faster core tasks measured by time,
clicks, errors, and adoption.
Context & constraints
GoReminders expanded across scheduling, customers, booking, and messaging. The original structure became harder to scan and slower for daily operations. The redesign had to keep dense calendar work readable while making high-frequency actions feel instant. A scalable UI foundation was required to prevent pattern drift as the platform grows
Goals & success criteria
Reduce click depth to Calendar, Customers, and Settings (tracked via navigation events).
Reduce time-to-create appointments (Quick flow vs Full flow timestamps).
Reduce validation errors per appointment attempt (form error logs).
Keep calendar usable under dense schedules (view/filter sequences and backtracking).
Increase consistent module usage (adoption of filters, panels, and templates).
How we work
01
Rhythm
Regular design reviews with async checkpoints. Each iteration ends with a shippable UI slice and clear decisions.
02
Artifacts
Audit notes, IA structure updates, wireframes, hi-fi UI, and a component library with states.
03
Decisions
A lightweight decision log captured the problem, chosen pattern, and acceptance criteria.
04
Collaboration
Design/specs and implementation alignment stayed close through handoff walkthroughs and QA.
Discovery with evidence
What we reviewed
We audited navigation, scheduling, and settings across key roles. We also reviewed calendar usage under dense, real-world data states.
What we mapped
We mapped the scheduling flow from calendar to appointment detail and follow-ups. We also mapped supporting flows for customers, groups, imports, and booking requests.
What we learned
High-frequency actions should be contextual panels, not page trips. Consistent component states were required to scale modules without regressions.
ProblemsDecisionsSolutions
Sidebar-first navigation
01
Problem
Module growth increased scanning time
and click depth for daily tasks.
02
Decision
Shift to left sidebar IA with clear clusters
and predictable entry points.
03
Solution
Group modules by job-to-be-done, standardize icons, and keep global search visible. Collapsible sections reduce visual noise while preserving depth.
04
Impact
Fewer clicks to reach Calendar, Customers, and Settings
Appointment creation as action
01
Problem
Full-page appointment creation felt heavy and
increased drop-off on optional details.
02
Decision
Make scheduling a contextual action
with progressive disclosure.
03
Solution
Quick create captures essentials (customer + time), then expands into full details only when needed. Validation and field grouping prevent avoidable errors.
04
Impact
Lower time-to-create, measured by quick vs full flow timing.
Calendar for dense schedules
01
Problem
One calendar view could not serve planning
and dense scheduling equally well.
02
Decision
Support Month/Week/Day views with one filter model.
03
Solution
Month pairs overview with a focused list; Week/Day keep time blocks readable. Shared filters and chips narrow the view without losing context.
04
Impact
Faster slot selection, tracked via view/filter action sequences.
Appointment control panel
01
Problem
Post-create actions were scattered across status,
messaging, and payment steps.
02
Decision
Consolidate actions into a single appointment detail panel.
03
Solution
Provide primary actions (edit/status/message/payments) plus collapsible details. A reminders timeline makes follow-ups visible and auditable.
04
Impact
Faster post-create actions, measured by time-to-action events.
Feature Spotlight
Quick-to-full scheduling flow
Scheduling was redesigned around the calendar so users never lose context. Quick create captures essentials in seconds, then expands into advanced fields like timezone, reminder type, repeats, and service/staff/location. This reduces avoidable errors and keeps high-frequency scheduling fast and consistent.
System & Scalability
The redesign was translated into a reusable UI system: tokens, component variants, and validation states. Panels, modals, tables, and empty states follow shared rules across modules. Proof points include tokens, component variants, table/empty patterns, and overlay behavior. This reduces regressions and makes new modules cheaper to build.
Validation
& Risk control
The redesign prioritized the highest-frequency workflows first to reduce risk. Component states were locked early and verified under dense calendar data. Stability during implementation was maintained through responsive QA and walkthroughs focused on states, variants, and edge cases.
01
Edge-case checklist for scheduling and messaging.
02
Responsive QA across breakpoints and dense states.
03
Walkthrough of states,
variants, and specs.
Handoff &
implementation
Handoff was structured to reduce implementation ambiguity. Screens map directly to components and states, with consistent naming and interaction notes. Developer comments document edge cases and validation rules. This decreases back-and-forth and speeds delivery.
- Component library with states and variants
- Design tokens + typography/spacing rules
- IA map + page templates
- Annotated specs with edge cases
Value Delivered
Users can schedule and manage appointments without losing calendar context. Teams spend less time correcting avoidable input mistakes and more time on real work. Consistent patterns across Customers and Booking Requests reduce training load and UI fragmentation. For the business, the platform is easier to extend, lowering design and development overhead for future modules.
01
User value
02
Operational value
03
Product value
Behind the scenes
IA regrouping map
Shows how modules were clustered to reduce scanning time.
Appointment flow variants
Quick full progression plus edge cases.
Calendar view variants
Month / Week / Day aligned to one filter model.
Customers + groups modals
Consistent modal patterns for bulk operations.
Booking requests steps
Clear progression from request to confirmation.
Component states proof
Tokens, variants, and validation states across modules.
Got a project in mind?
Let’s make it happen!
- We review your request right away
- We’ll share case studies relevant to your industry
- If we’re the right match, you’ll get a custom proposal
- Then, we’ll start with a 3-day trial to get the ball rolling