Should Built Technologies prioritize expanding its construction loan management features or focus on improving the user interface for existing tools?

Introduction

The trade-off we're examining today is whether Built Technologies should prioritize expanding its construction loan management features or focus on improving the user interface for existing tools. This decision is crucial for the company's growth strategy and user satisfaction. I'll analyze this trade-off by considering business objectives, user needs, technical feasibility, and potential impacts on key metrics.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking our current market position might influence this decision. Could you share how our market share compares to competitors in the construction loan management space?

Why it matters: Helps determine if feature expansion or UI improvement is more critical for competitiveness. Expected answer: We're a top 3 player with room for growth. Impact on approach: Strong position might favor UI improvements, while catching up might prioritize feature expansion.

• Business Context: Based on our revenue model, I assume loan management features directly impact our bottom line. How significant is the revenue from these features compared to other product offerings?

Why it matters: Aligns solution with primary revenue drivers. Expected answer: Loan management features contribute 60-70% of revenue. Impact on approach: High revenue contribution would justify prioritizing feature expansion.

• User Impact: Considering user behavior, I'm curious about our current user satisfaction scores. How do they compare between our loan management features and overall UI experience?

Why it matters: Identifies which area needs more immediate attention. Expected answer: Loan features score well, but UI lags behind. Impact on approach: Lower UI scores might shift focus towards interface improvements.

• Technical: Regarding our tech stack, I'm wondering about the complexity of expanding loan management features versus overhauling the UI. How do our engineering teams assess the technical debt and effort required for each option?

Why it matters: Ensures solution is technically feasible and efficient. Expected answer: UI overhaul is more straightforward; feature expansion requires backend changes. Impact on approach: Easier UI improvements might be favored for quicker wins.

• Resource and Timeline: Thinking about our current team structure, how are our product and engineering resources allocated between feature development and UI/UX work?

Why it matters: Determines if we have the right team composition for either approach. Expected answer: 70% feature development, 30% UI/UX. Impact on approach: Might need to reallocate resources or hire based on chosen priority.