Sizing a Proposed Product Change to Decide How Much Process It Needs
Company: Rippling
Role: Product Manager
Category: Product / Decision Making
Difficulty: medium
Interview Round: Other
A change to your product has been proposed. As the PM, how do you judge whether it is a complex change that needs heavier planning and review, or a lightweight one that can move quickly?
```hint Same effort, different stakes
Picture two changes that each take an engineer one day. What could make one of them far riskier to ship than the other?
```
### Clarifying Questions
- Does "change" cover only customer-facing features, or also data-model, API, configuration and pricing changes?
- What does the classification decide: how much spec, review and rollout process the change gets, or how it is estimated and scheduled on the roadmap?
- Is there already a launch-tier or review process to fit into, or am I defining one?
- Should I answer for a platform like Rippling's, where some changes touch pay, tax filings or employee data, or for products in general?
### What a Strong Answer Covers
- What the classification decides, and why misjudging it in either direction is costly
- Explicit criteria for sizing a change that go beyond engineering effort or lines of code
- A repeatable rule for combining the criteria, including who makes the call and how uncertain or disputed cases are settled
- The concrete differences in spec, review, testing, rollout and communication between a lightweight and a complex change
- How a classification is revisited when the work grows, and how the framework is checked against real outcomes
### Follow-up Questions
- An engineer calls a change a one-line configuration edit, but it alters how overtime pay is calculated for every customer in one state. How do you classify it?
- A change you labeled lightweight grows halfway through development. What tells you to reclassify it, and what do you do next?
- Teams start labeling everything complex to protect themselves, and delivery slows down. How do you fix the framework?
Overview: A product manager execution question on judging whether a proposed product change is complex or lightweight. It tests whether the candidate can set explicit sizing criteria that go beyond engineering effort, apply them with engineering partners, and match the depth of spec, review and rollout to the result.