In QAD's Cloud ERP offering, how do we weigh the benefits of rapid updates and new capabilities against potential disruptions to customer operations?

Introduction

The trade-off we're examining today is how to balance the benefits of rapid updates and new capabilities in QAD's Cloud ERP offering against potential disruptions to customer operations. This scenario touches on the core challenge of maintaining a cutting-edge product while ensuring stability for our enterprise clients. I'll approach this by analyzing the stakeholders, metrics, and potential experiments to inform our decision-making process.

Step 1

Clarifying Questions (3 minutes)

• Context: Based on the competitive landscape in the ERP market, I'm thinking frequent updates might be crucial for maintaining our market position. Could you share how our update frequency compares to our main competitors?

Why it matters: Helps gauge the urgency of increasing update frequency Expected answer: We're slightly behind in update frequency Impact on approach: Would prioritize finding ways to increase update speed safely

• Business Context: Considering our revenue model, I assume we have a mix of subscription tiers. How does our pricing structure align with update frequency or access to new features?

Why it matters: Informs potential segmentation of update rollouts Expected answer: Higher tiers get earlier access to updates Impact on approach: Could explore a phased rollout strategy based on subscription level

• User Impact: I'm thinking about the diversity of our customer base. Can you give me an overview of our customer segments in terms of industry and size, and how they typically respond to updates?

Why it matters: Helps tailor update strategies to different user needs Expected answer: Varied response, with larger enterprises generally more change-averse Impact on approach: Might lead to a more customized update approach for different segments

• Technical: Regarding our current architecture, I'm curious about our ability to implement feature flags or gradual rollouts. How flexible is our system for controlling feature availability?

Why it matters: Determines our technical capabilities for mitigating disruption Expected answer: We have some capability, but it's not fully mature Impact on approach: Would include improving our feature flag system as part of the solution

• Resource: Thinking about the potential increase in customer support needs, how scalable is our current support team structure?

Why it matters: Assesses our ability to handle potential issues from increased update frequency Expected answer: Support team is at capacity but could be expanded Impact on approach: Would factor in additional support resources in the recommendation