How can Justworks improve its time tracking feature to better accommodate remote and hybrid work schedules?

Introduction

Justworks' time tracking feature needs improvement to better accommodate remote and hybrid work schedules. This challenge is crucial as the nature of work continues to evolve, with more companies adopting flexible arrangements. I'll analyze the current situation, identify key pain points, and propose strategic solutions to enhance this feature.

Step 1

Clarifying Questions (5 mins)

• Looking at the product context, I'm thinking Justworks might be targeting small to medium-sized businesses with a mix of office-based and remote employees. Could you confirm the primary user base and their typical work arrangements?

Why it matters: Determines the scope and focus of our improvements Expected answer: Primarily SMBs with 50-500 employees, 60% hybrid, 30% remote, 10% office-based Impact on approach: Would tailor solutions to hybrid workforce needs

• Considering user behavior, I'm curious about the current adoption rate of the time tracking feature. What percentage of Justworks customers actively use this feature, and how does it vary between remote and office-based employees?

Why it matters: Helps identify if the problem is feature awareness or usability Expected answer: 70% overall adoption, higher among remote (85%) than office-based (50%) Impact on approach: Would focus on improving usability for office-based users if adoption is low

• Regarding pain points, I'm wondering about the most common complaints or feature requests related to time tracking for remote and hybrid workers. What are the top 3 issues reported by users?

Why it matters: Directly informs our prioritization of improvements Expected answer: Lack of integration with popular remote work tools, difficulty in tracking non-standard hours, limited reporting options Impact on approach: Would prioritize integrations and flexible time entry options

• Thinking about the product lifecycle, where does the time tracking feature stand in terms of maturity and how does it align with Justworks' overall product strategy?

Why it matters: Determines if we should focus on core functionality or advanced features Expected answer: Relatively mature feature, but lagging behind in accommodating new work trends Impact on approach: Would focus on modernizing the feature to align with evolving work patterns