How can Operative balance improving the user interface of its Order Management System against maintaining compatibility with legacy client systems?

Introduction

Balancing the improvement of Operative's Order Management System (OMS) user interface against maintaining compatibility with legacy client systems presents a critical trade-off. This scenario involves modernizing a core product while ensuring existing clients can still operate effectively. I'll analyze this trade-off by examining the product context, stakeholder impacts, potential experiments, and decision frameworks to guide our strategy.

Step 1

Clarifying Questions (3 minutes)

• Based on the business context, I'm thinking this OMS is a critical revenue driver. Could you share how much of our revenue comes from this product and how it fits into our overall product portfolio?

Why it matters: Helps prioritize the importance of this trade-off against other initiatives Expected answer: OMS contributes significantly to revenue, potentially 50%+ Impact on approach: Higher revenue contribution would justify more resources for a careful transition

• Considering user impact, I'm assuming we have a mix of clients using both modern and legacy systems. What's the current split between these client types, and how has it been trending?

Why it matters: Informs the urgency and scale of the UI update vs. legacy support Expected answer: 60% modern, 40% legacy, with legacy slowly decreasing Impact on approach: Would influence the timeline and resources allocated to legacy support

• From a technical perspective, I'm curious about the architecture of our OMS. How tightly coupled is the UI with the backend systems that interface with legacy clients?

Why it matters: Determines the feasibility and complexity of updating the UI independently Expected answer: Moderate coupling, requiring careful API management Impact on approach: Would influence the development strategy and potential phased rollout

• Regarding resources, I'm thinking this might require a dedicated cross-functional team. What's our current capacity for a project of this scale, both in terms of personnel and budget?

Why it matters: Helps determine the scope and timeline of the project Expected answer: Limited resources available, competing priorities Impact on approach: Might necessitate a more gradual, phased approach to the UI update

• Looking at timelines, I'm wondering if there are any upcoming contract renewals or market events that could impact our decision timeline. Are there any key milestones we need to consider?

Why it matters: Identifies external pressures and opportunities for the project Expected answer: Major client contract renewals in Q4 Impact on approach: Could influence prioritization and potentially accelerate certain aspects of the project