TOPIC
Risk management
These are the same questions found in the library, grouped here by the capability each one mainly examines.
163 questions
Questions 51–100 of 163 on this page.
C · Value judgment and direction setting10
- The team needs months to build shared data capability, but the near-term roadmap shows no direct feature output. How would you express value, milestones, and exit criteria?
- The team proposes pausing feature work to rebuild a core module, but past refactoring benefits were hard to quantify. How would you set a baseline, pilot, and stop criteria?
- You discover that a new direction you pushed is wrong. How do you cut your losses, how do you judge whether to continue, adjust, or stop, how do you treat sunk cost, and how do you explain it to those involved?
- After the bot upgrade, sessions with no handoff to a human are counted as resolved, and the rate went from 72% to 91%. In the same week the handoff button moved into a submenu and the denominator changed. How do you respond today to the proposal to cancel weekend human coverage?
- The target metric improved, but refunds, complaints, or manual handling also worsened. How would you decide whether the outcome is acceptable?
- The company's funding lasts about 12 months, the key capability you need takes roughly 18 months to grow, and the market window has only 6 months left. How does your plan handle these unsynchronized time scales?
- 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 release window moves up by two weeks, and the team can finish only three of six planned items. Business, reliability, and compliance leads each say their work cannot slip. How would you prioritize and explain what is cut?
- A team plans to end support for an old technology, but critical systems still depend on it and replacement is expensive. How would you create a retirement roadmap?
- A critical flow is two weeks from launch when a review finds that keyboard users cannot complete one step. A full redesign would affect the date. How would you assess the impact, negotiate scope with the team, and explain what can be staged versus what cannot safely ship?
No questions in this section match your target. ·
D · Delivery and ongoing operations25
- The business asks to “improve customer experience” without a clear pain point or deadline. How would you decompose it into verifiable problems, workstreams, and milestones? Follow-up: If a critical dependency slips by one cycle, how would you re-sequence the critical path, reset commitments, and reduce waiting?
- The requester has prescribed a service rewrite, but incident data points to several possible causes. How would you return to problem definition and decide the validation order?
- A new regulatory requirement makes the original scope impossible, yet teams still cite old milestones. How would you update baselines, dependencies, and external expectations?
- A project stays green until a critical data migration is found untested just before launch. How would you improve status signals and decision cadence?
- Three projects independently build similar permission and notification capabilities, each seeming reasonable alone. How would you detect portfolio-level duplication and change governance?
- When a payment-risk dependency slows, checkout times out. The business wants to preserve conversion without bypassing critical safety checks. How would you decide which checkout functions can be temporarily disabled and which checks must remain?
- Faced with a large problem that is still unclear, how do you plan how many people and resources are needed? How do you estimate under uncertainty, invest in stages, and ask upward for resources?
- How do you work out what your team can really commit to next cycle, rather than headcount times working days?
- You receive a request in an area you have never worked in. How do you break it down and give an estimate that can be checked later?
- 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?
- The promotion strategy is set and you are responsible for execution. What goals, rules, resources, risks, and acceptance criteria would you confirm before launch?
- Sales, support, and engineering can all label customer issues top priority, so the queue cannot distinguish business outages from general dissatisfaction. How would you design severity and escalation?
- 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 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?
- Five projects flag the same platform dependency as a possible delay, yet each remains green. What evidence would tell you to change the portfolio instead of following up project by project?
- What was the biggest challenge in this project? Why was it hard, how did you push it forward at the time, and how did it end?
- A business lead says change approval slows market opportunities and asks teams to insert requests outside review. Past urgent work has caused rework. How would you design an exception path?
- 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?
- A key vendor has delayed an interface twice, but the project plan still uses the original date. Internal teams are building a temporary adapter in parallel. How would you reset the baseline, account for added work, and show leadership which commitments remain credible?
- Three weeks into a project you find two risks nobody owns. How do you make them manageable?
- An automated approval service stops working, so the operations team temporarily switches to a spreadsheet and limits user impact. Two weeks later, the service is still down, and the spreadsheet has inconsistent permissions and records. How would you manage the temporary process, restore automated approvals, and decide when to shut it down?
No questions in this section match your target. ·
E · Collaboration, communication, and influence7
- A cross-time-zone team relies on chat history for handoffs, and recipients repeatedly misunderstand status and open decisions. How would you shape handoff information and verify understanding?
- A product page advertises automation accuracy without a key applicability limit, and customers have used it in purchasing decisions. After finding the issue, how would you decide whether to withdraw, correct, and notify?
- 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?
- You have five minutes to brief a leader on a project that is not going well. How do you structure the message?
- A vendor risk may affect a launch, but neither cause nor likelihood is clear. Leadership wants an answer today. How would you report facts, unknowns, safeguards, and the next update time?
- A storage migration could briefly hide some customer data, but the business owner does not know replication lag or rollback limits. How would you explain risk and enable a sound decision?
- 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?
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 growth1
No questions in this section match your target. ·
H · Professional responsibility and work style6
- A critical data migration has no owner, and each team says it is outside its scope. How would you make sure the migration is completed safely while naming the final owner and ongoing responsibilities?
- A project falls short of its commitment, partly because of external dependencies and untested assumptions. How would you distinguish your responsibility, external factors, and corrective actions? If a dependency team refuses to address a gap, how would you assign ownership and escalate?
- You realize your status report omitted a risk that could change the decision, and executives have already relied on it. How would you correct it?
- A leader asks you to show only favorable segments and describe an insignificant result as a trend. How would you respond and preserve factual accuracy?
- You notice another team’s operation may expose user data; they have not invited you, and release is imminent. How would you decide whether and how to intervene?
- You are asked to commit to a delivery date before dependencies and risks are confirmed, with unclear authority. How would you communicate without making a false commitment?
No questions in this section match your target. ·