How can Jobber enhance its job scheduling feature to better accommodate last-minute changes and emergencies?

Introduction

To enhance Jobber's job scheduling feature to better accommodate last-minute changes and emergencies, we need to dive deep into the current user experience, pain points, and potential solutions. I'll outline a comprehensive approach to address this challenge, focusing on user needs, technical feasibility, and business impact.

Step 1

Clarifying Questions (5 mins)

• Looking at Jobber's position in the field service management market, I'm thinking it's crucial to understand our competitive advantage. Could you share insights on our market position and what sets our scheduling feature apart from competitors?

Why it matters: Determines if we should focus on enhancing unique features or catching up with industry standards. Expected answer: Jobber has a strong position with small to medium businesses, known for ease of use. Impact on approach: Would focus on maintaining simplicity while adding flexibility for emergencies.

• Considering the nature of last-minute changes, I'm curious about the current user behavior. What percentage of jobs typically experience last-minute changes or emergencies, and how are users currently handling these situations?

Why it matters: Helps quantify the problem and understand current workarounds. Expected answer: About 20-30% of jobs face last-minute changes, users often resorting to phone calls or manual adjustments. Impact on approach: Would prioritize automated notification systems and quick-edit features.

• Given the potential impact on various stakeholders, I'm wondering about our key performance indicators. What metrics are we currently tracking related to scheduling efficiency and customer satisfaction?

Why it matters: Aligns solution with business goals and provides baseline for measuring success. Expected answer: Key metrics include time to reschedule, customer retention rate, and on-time job completion rate. Impact on approach: Would focus on solutions that directly improve these metrics.

• Considering the technical aspects, I'm interested in understanding our current system architecture. How flexible is our current scheduling backend to accommodate real-time changes and notifications?

Why it matters: Determines the feasibility of potential solutions and helps estimate development effort. Expected answer: Current system uses a microservices architecture with real-time capabilities, but may need optimization. Impact on approach: Would explore solutions leveraging existing architecture while identifying areas for enhancement.