USE CASE
Operations review
These are the same questions found in the library, grouped here by the capability each one mainly examines.
132 questions
Questions 101–132 of 132 on this page.
C · Value judgment and direction setting6
- A market window is short and a full solution takes two months. A reversible one-week pilot is possible, but cannot validate every long-term risk. How would you choose the sequence?
- The team lacks capacity for all three: a short-term revenue project, strategic exploration, and technical refactoring. What criteria would you use to compare and rank them? How would you explain strategic value or maintenance risk that cannot be measured directly?
- In a review, three candidate projects are each marked P0 by their owners, all for the reason 'very important.' How would you turn the review from arguing about order into a trade-off people can check?
- The team wants to 'use our own product more,' but the last experience night produced only scattered impressions. How would you design it so self-use becomes a feedback loop that runs from a real task to a verified fix?
- After a redesign of an important flow, the expected completion rate does not improve. Support requests decline, existing users respond more positively, but new users behave worse. How would you check metric definitions and user segments, determine what effect the design had, and choose the next action?
- How do you prioritize when several important projects compete for limited resources?
No questions in this section match your target. ·
D · Delivery and ongoing operations17
- How do you work out what your team can really commit to next cycle, rather than headcount times working days?
- A campaign goes live overnight, but heavy traffic stalls the system. Users cannot claim coupons and start complaining. As an engineer involved in the campaign, how would you coordinate with operations and support on temporary business measures while restoring the system?
- A system keeps having problems again and again, and each fix is followed by another failure. How do you find the root cause, how do you move the team from firefighting to real repair, and how do you show it no longer recurs?
- A production service suddenly fails widely. In what order do you act during the first hour?
- How do you keep the same kind of personal mistake from happening again? Did you improve the process and tooling, or just remind yourself to be careful? How do you know the improvement works?
- Describe a re-engagement or referral campaign you contributed to as an engineer. Which systems, data, or delivery work did you own, how did you clarify budget and key user behavior with operations, and how did you verify incremental impact and your actual contribution?
- The promotion strategy is set and you are responsible for execution. What goals, rules, resources, risks, and acceptance criteria would you confirm before launch?
- When managing a large platform ecosystem, gray areas such as fake orders, abusive bonus hunting, and borderline content often appear. How do you build a governance mechanism that does not harm the healthy ecosystem, and how do you build the defense together with risk control, legal, and technology teams?
- You are about to run a growth experiment in production. What checkpoints and stop conditions do you prepare first?
- A two-sided platform has a local supply-demand imbalance: peak-time orders exceed available providers, or a new city has providers but too few users. How would you identify the main constraint and adjust pricing, incentives, or supply while controlling cost and long-term effects?
- A strategic change requires you to shut down at once a business that brings many users but has lost money for years. How do you, in the shortest time, reassure thousands of affected partners, complete the wind-down compliantly and smoothly, and prevent a group public-relations crisis?
- A critical operations playbook is still used by multiple regions, but its author has left and recent system and policy changes were never incorporated. How would you identify which steps remain safe, establish temporary controls and ownership, and verify that frontline teams can use the new version correctly?
- Two weeks before launch a stakeholder asks for one more feature. How do you decide to accept, defer, or decline, and what do you record?
- A release date has been promised externally, but teams keep requesting features and fixes. How would you decide when to freeze scope, which exceptions to allow, and who owns replanning consequences?
- How do you measure engineering effectiveness? Which metrics do you choose, how do you keep the numbers from being gamed, and how do you turn the measurement into real improvement?
- Two projects' schedules collide and both need the same people. What do you do, how do you turn the conflict into options that can be discussed, and how do you get both sides to accept the result?
- Three weeks into a project you find two risks nobody owns. How do you make them manageable?
No questions in this section match your target. ·
E · Collaboration, communication, and influence5
- You discover an incident may affect customer data, but the affected list and restoration time are unknown. How would you organize the first notice and subsequent updates?
- A launch decision must be made today, but one key experiment result is missing. How would you distinguish facts, assumptions, unknown risks, and reversible options in your update?
- A disagreement was not resolved and the group decided to proceed with one option. What do you leave behind so it can be reviewed later?
- A cross-department meeting records a decision, but an affected team says it cannot deliver on time. How would you confirm who accepted the decision, which objections remain, and who owns the next step?
- The release owner decides to ship on schedule. The security team says residual risk exceeds its acceptance range, but leadership chooses to continue. How would you record dissent, responsibility, and review conditions and clarify executable scope and escalation boundaries?
No questions in this section match your target. ·
F · People and organization building1
No questions in this section match your target. ·
G · Learning, adaptation, and sustained growth2
- Were the improvements proposed in a retrospective actually carried out afterwards? Did each one have an owner, a date, and a way to verify it? For those not carried out, why not?
- Pick a project you recently finished and walk through a retrospective: what did you set out to achieve, what actually happened, and what would you keep, change, or stop next time?
No questions in this section match your target. ·