ISSUE 03
B2B SaaS UI Branding

Reducing Identified Scheduling Friction By 55%

Designing Rent Manager's first shared scheduling platform to unify property managers, technicians, and tenants

Business Challenge

What was broken, why it needs to be fixed & who benefits once we do

Overview

Property managers, technicians, and tenants relied on fragmented workflows to coordinate maintenance across multiple properties. Without a centralized scheduling system, teams manually tracked technician availability, coordinated appointments through calls and emails, and struggled to keep everyone aligned—resulting in delays, miscommunication, and unnecessary operational overhead.

My Role
  • Led end-to-end product design (visual, interaction, design systems)
  • Cross-functional partnership with Product and Engineering
  • Prototyping, research, validation, and launch
The Crew
  • Sydney H.·Designer
  • Michelle P.·Business Analyst
  • Sasank T.·Software Developer
Timeline
Feb ‘23 – Jan ‘24
Tools
Adobe XD · Adobe Illustrator

Solution

A shared workflow designed for everyday coordination

Solution: A shared scheduling platform that gives property managers, technicians, and tenants one place to coordinate maintenance—assigning work through drag-and-drop boards, tracking technician availability, and guiding new users through it all with built-in product tours.

Impact: Reduced scheduling friction by 55% Designed and launched 0-1 Introduced 6 scalable design patterns

What I Owned

I led the design direction 0→1, introducing boards, expandable cards, isometric illustrations and animations for the product tours that introduce users to new features.

How I Collaborated

I worked closely with my developer, Sasank, to get the tour flyout component and feature tour implemented 1:1.

Chat message from developer Sasank with an annotated screenshot of the Maintenance Schedule board, discussing tech availability during a time block

The Flow

Maintenance Scheduling reaches across 3 separate programs (TWA, RM12, and RMX) and supports web and mobile touch points.

Step 1: maintenance scheduled in Tenant Portal

Select up to 3 time frames for the Maintenance Tech to arrive.

TodayMON12
1PM - 3PM
3PM - 5PMAlternate 1
5PM - 7PM
TUE13
8AM - 10AM
10AM - 12PMPreferred
1PM - 3PM
3PM - 5PM
WED14
8AM - 10AMAlternate 2
10AM - 12PM
1PM - 3PM
Selected Time Frames

Select up to 3 time frames, starting with your preferred time. You’ve selected your preferred time. Please select additional time frames to continue. All set. Submit to send your request. Request sent. We’ll confirm your time.

Preferred
Select a time
Tue, October 13th10AM – 12PM

Alternate 1
Select a time
Mon, October 12th3PM – 5PM
Alternate 2
Select a time
Wed, October 14th8AM – 10AM
Submit

Step 2: issue appears in the Service Issues tile

Service Issues

46 Results
Open
13Scheduled
6In progress
Done
DescriptionStatusTenantUnit
Sink leaking · P-trapScheduledIn progressDiane Bailey4B
Front door won’t latchIn progressMarcus Lee2A
Garbage disposal jammedOpenAmy Rodriguez1B
1 of 16

Step 3: issue scheduled on the Maintenance Schedule

Issue #157219 Assigned to Jack Forrest
Show Unscheduled (1)Show Unscheduled (0) Tuesday, October 13th New Issue
Unassigned (1)Unassigned (0)
JFJack Forrest
CEChance Ekstrom
DDDavis Dias
8:00AM - 12:00PMAvailable in TWA
Diane Bailey RIVER · 4B #157219 · Sink leaking · P-trap Preferred Tue 10AM – 12PM
Chaka KhanRIVER · 3BGutter clog over entryAgent Carrie U.
Charlie ApegianRIVER · 2ADryer vent inspectionAgent Carrie U.
Priya NairRIVER · 7CSmoke detector chirping
12:30PM - 4:00PMAvailable in TWA

Step 4: technician heads to the issue on Service Tech Map

Locate TechsCurrent IssuesCheck-In Review Tech Location
Back

Techs Near Issue #157219

Sink Leaking · Possible P-trap issue

Currently assigned to Issue #157219 Jack Forrest — 1.23 miles away En route · ETA Checked-in: #2290520 · just now
Chance Ekstrom — 0.25 miles away Assign Issue #157219
Davis Dias — 0.49 miles away Assign Issue #157219
+−
Jack Forrest checked in · Issue #157219

Pain Points

How we identified the biggest sources of friction across users

Pain points across tenants, technicians, and property managers
Constraint 01

0 → 1 Design

There were no established patterns to build from.

Constraint 02

Legacy Enterprise Platform

New workflows had to coexist with existing functionality.

Constraint 03

$ Premium Feature

The feature must demonstrate clear customer value.

Research

Insights that informed our design decisions

What We Did

After speaking with a number of users who showed us they were using several softwares to schedule service issues, we dug in to what other property management systems were doing to figure out how we could do it better. We used a mix of:

Contextual Inquiry

User Interviews

Competitive Analysis

What We Cut

Reschedule Issues

We chose not to include a dedicated "Reschedule Issue" flow in the initial release because RM12 does not currently allow users to reschedule maintenance issues.

Design

Exploring iterations and tradeoffs to reach a user centric solution

Image 1-2: Shows the initial and final iterations of the board.

Image 3-4: Shows the initial and final iterations of the Walkthrough Wizard.

Flyout onboarding tour

Flyout Tour component

Flyout tour component in Rent Manager Express

Impact

How the business and its users benefitted after launch

My Influence

I established new design standards, improved collaboration between product and engineering teams, and enhanced craft across the product

Prospect Leasing Board, annotated to highlight the Boards view and an Entity Card
Add Maintenance Techs walkthrough wizard, annotated
Placeholder noting an animation made in Figma is coming soon

Reduced user friction by 55%

Reduced identified user friction by 55% by prioritizing the 6 highest-impact user problems for the initial release.

Designed and launched from 0-1

Designed and launched Rent Manager's scheduling platform from 0→1, improving day-to-day coordination while creating a licensable, revenue-generating feature.

Introduced 6 scalable design patterns

Introduced 6 scalable design patterns that have since been adopted across the software.

How We Measured

55% reduction in identified friction

We received 11 support-ticket issues related to maintenance scheduling and prioritized the 6 highest-impact problems for the initial release, resolving issues that had been in the backlog for years.

qManage support ticket #710779, 'Cindy — Service Issues & Scheduling Calendar', marked Resolved and Closed: a request to add times and timeframes to work orders in Rent Manager rather than working around it with Google Calendar.

Reflections

Hindsight is 20/20

What I Learned

  • Not every problem needed to be solved in the first release.
    By identifying the 5 highest-impact problems we were able to ship a focused experience rather than trying to build every part of a new workflow at once.
  • The most lasting impact wasn't limited to what we shipped.
    Designing a 0→1 experience gave me the opportunity to establish interaction patterns that could solve similar problems elsewhere in the product, further reinforcing the value of designing for systems, not just individual features.

What I'd Do Differently

Now that the initial feature is shipped, I would like to go back and create the weekly view that was cut from scope due to time.

Want to hear more?

Reach out
Previous Issue Next Issue