TOPIC
Planning
These are the same questions found in the library, grouped here by the capability each one mainly examines.
156 questions
Questions 1–50 of 156 on this page.
A · Professional problem solving and implementation3
- For a given capability, how do you decide between building it, adopting open source, or buying it? How do building and open source differ in cost, control, maintenance, and risk, and when should you switch from one to the other?
- How do you identify and record technical debt and pay it down without stopping business delivery? Which debts are worth paying and which can be left for good, and how do you judge?
- A major promotion or international launch may increase traffic fivefold next year. Starting from the current architecture, how would you check for bottlenecks in the gateway, critical request flows, storage, and machine resources? How would you phase the work, staff it, and validate your assumptions?
No questions in this section match your target. ·
B · Business understanding and domain modeling4
- A major customer has a special rate in its contract, but the exception may end at renewal. How would systems and operations avoid keeping the old exception indefinitely?
- Map the area you have owned over time: what users are trying to do, where the main process obstacles are, what your module can influence, and what is outside its control.
- A new plan makes more users willing to try the product, but some customers who would have bought a higher-priced plan switch to the cheaper option. What commercial model and observation window would you use to judge whether the plan portfolio creates incremental value?
- A new industry or regulatory requirement forces a product workflow change. How would you trace from the requirement to affected participants, value-chain steps, business commitments, and internal systems?
No questions in this section match your target. ·
C · Value judgment and direction setting23
- A membership program increases repeat-purchase frequency, but average order value and margin both decline. How would you distinguish a healthy habit change from purchases pulled forward or low-quality, promotion-driven growth?
- You inherit a mature product with a stable user base and stalled growth, and the team wants to launch new features immediately. What product understanding would you build in the first two weeks before deciding where to invest?
- The team needs to test a growth hypothesis while customer-impacting maintenance work keeps arriving. How would you set capacity, triggers, and stop rules?
- The annual conversion target depends on an untested channel assumption. How would you separate current commitments, assumptions to validate, and checkpoints for continuing, changing, or stopping?
- 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?
- In the past year, how much team capacity did you secure to address technical debt (accumulated maintenance and rework) or improve engineering infrastructure such as builds and releases? When these problems slow product work, how do you explain their impact and risk to business leaders and secure time to refactor?
- The team wants to keep optimizing the performance of a core API. What basis do you use to decide how far is far enough, and when to stop investing more?
- A new platform could reduce future development cost, but the legacy system needs two more years of support and this quarter funds only one major investment. How would you compare build, migration, and status-quo options?
- A design-research team has two researchers, while three product lines want critical interviews this month. One decision is irreversible; another can start with low-cost data. How would you allocate capacity?
- Three business teams have raised similar needs, and someone suggests building a shared platform. How do you judge whether it is worth building, or whether each domain should first get a local solution?
- The boss or the business side squeezes the schedule and says "ship first, messy code is fine". As the owner, how do you respond? Which quality can give way and which cannot, and how do you make the concession open and time-limited rather than quietly becoming permanent debt?
- What were the short-term and long-term benefits of this project? When the two conflicted, how did you trade them off?
- 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?
- The business wants new features while the team has built up technical debt. How do you decide how much to invest in each this quarter?
- The boss raises a business pain, such as high acquisition cost and poor retention. How do you translate it into goals the technical team can tackle, and show how technical means act on those business metrics?
- User mix or external conditions change during a project, making the original baseline incomparable. How would you continue judging the outcome?
- The final business outcome will take months to appear, but the team must decide whether to continue investing now. How would you use leading indicators?
- A pilot meets its target, but results vary when expanded to more regions or segments. How would you judge whether the result is replicable?
- 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?
- When planning the next six months, do you work forward from your resources and current state, or backward from the goal? Do the two give the same conclusion?
- Your quarterly plan leaves out several important items. How do you record them so that when someone wants to revisit one later, the discussion rests on the judgment rather than re-arguing how important it is?
- How do you confirm that your team's goals are consistent with the company's strategic goals? When they are not, do you adjust the team's goals or try to influence the goals above?
No questions in this section match your target. ·
D · Delivery and ongoing operations12
- For three consecutive quarters, several teams underestimated integration and acceptance time. How would you use forecasts and actuals to determine whether the error comes from estimation, scope change, or scheduling, and improve the next forecast?
- Project requests backed by senior sponsors tend to move ahead, while compliance and infrastructure work without executive sponsorship repeatedly slips. How would you create a transparent portfolio intake and prioritization process?
- A project depending on a platform interface is already integrating when the upstream team announces a semantic change this quarter and cannot support both formats indefinitely. How would you decide compatibility, migration order, and release boundaries across projects?
- Four months after delivery, the targeted cost reduction has not appeared in financial reports. The sponsor says the system is still in a learning period, while finance considers the project closed. How would you clarify benefit ownership and the validation window?
- A serious production incident pulls two specialists from a project team for a full week, putting a milestone at risk. How would you update the forecast, separate incident and project responsibilities, and help stakeholders make trade-offs?
- After a strategic shift, several in-flight projects no longer support the new goals, but teams have invested effort and made external commitments. How would you decide what to stop immediately, what to close out, and how to transfer knowledge, contracts, and capacity?
- 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 project depends on another team for an interface or data contract, but there is no clear delivery owner, plans keep changing, and the work may not fit next quarter’s schedule. How would you establish a commitment, prepare alternatives, manage critical-path risk, and decide when to escalate or change scope?
- 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?
No questions in this section match your target. ·
E · Collaboration, communication, and influence1
No questions in this section match your target. ·
F · People and organization building4
- The team plans to double in size within two months, and a senior contributor wants to become a lead. How would you give them real but supported management responsibility before expansion and assess the result?
- A team translated its quarterly goal into easy-to-deliver internal improvements, while the business concern about customer churn is absent from the plan. How would you reconnect team goals and work?
- The product is organized around a customer journey while engineering teams are split by technical layer, making cross-layer work queue up. How would you assess whether boundaries should change?
- After two teams merge, overlapping roles lack clear ownership and old decision paths remain. How would you redefine responsibilities and check the result?
No questions in this section match your target. ·
G · Learning, adaptation, and sustained growth3
- You are considering moving from core product engineering to reliability engineering to broaden your technical impact, with no near-term level change. How would you define learning goals and evidence of success for this lateral move?
- A new role has no clear first-quarter goals, and the team is busy with routine work. How would you identify a problem worth owning and calibrate with your manager?
- You set a long-term capability goal, but urgent daily work keeps displacing learning and improvement. How would you create a sustainable way to make progress?
No questions in this section match your target. ·