TOPIC
Planning
These are the same questions found in the library, grouped here by the capability each one mainly examines.
156 questions
Questions 51–100 of 156 on this page.
C · Value judgment and direction setting22
- If you had to plan a technical direction over three to five years, how would you do it? How do you keep it from becoming a vision list that cannot be tested?
- The company’s growth is slowing, and your manager asks you to explore an unfamiliar, highly competitive market with a limited budget. What would you learn and test in the first 30 days, and what evidence would determine whether to continue or stop?
- 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?
- Looking back at work you have already finished, which three things do you now think were not worth doing? Why did you do them then, and what changed in your judgment?
- 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?
- A new product exploration has consumed two quarters. Pilot completion stays below target, while the team argues one more feature will fix it. How would you judge evidence for further investment and stopping?
- 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?
- Looking back over the past six months, what were the three most worthwhile things you did? Why those, what benefit did they bring, and how did you confirm that benefit?
- Choose a project you are working on. Given its goal and ranking criteria, what are the three most important things to do and the two easiest to pause or stop?
- 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?
- Is your approach unique or forward-looking? What did you bet on at the time, was it later proven right, and what would show that you were wrong?
- Describe a product decision where a short-term metric worsened, but the team expected a longer-term benefit. What evidence informed the decision, how did you monitor it, and what later evidence linked the outcome to that choice rather than outside factors?
- A new process doubles weekly feature releases, but task completion is unchanged and support tickets rise slightly. How would you decide whether to continue, adjust, or stop?
- When you did your research, what were the industry level, the best practice in this direction, and the level already reached inside your company? Where does your solution fall, and why?
- Drawing on available material and direct observation, which kinds of companies do you think this technology will affect most over the next two years? Explain your own judgment and evidence rather than only repeating industry reports. What does it mean for your company, and what have you done to test or respond to it?
- A platform has migration, reliability, and productivity workstreams, but annual capacity supports only two. How would you sequence and trade off the quarters?
- Policy and procurement cycles in a new market are unclear, yet the company must set annual goals and budgets. How would you translate long-term direction into quarterly hypotheses, validation milestones, and triggers for adjusting the plan?
- The team plans to pilot a service in three cities, but supply quality, repeat use, and unit economics are unproven; sales materials already show a firm expansion timeline. How would you rewrite stage goals and external commitments?
- The same product has different technical debt, release cadence, and user behavior on iOS, Android, and web; the roadmap still schedules uniform feature milestones, leaving one platform early and another far behind. How would you plan across platforms and define consistency boundaries?
- The company sets an annual revenue target, while teams control only parts of product features, channels, or service capacity; quarter-end reviews often dispute attribution. How would you build a goal tree, dependencies, and team-controllable outcome measures?
- The roadmap lists many goals but no explicit exits; each new request is added on top, and commitments keep changing. How would you include stopped, deferred, and declined work in planning governance?
- The team releases monthly, and the business wants weekly releases, but automated testing, rollback, and monitoring are immature. How would you plan release capability without using deployment frequency as the only success measure?
No questions in this section match your target. ·
D · Delivery and ongoing operations23
- 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?
- Incidents and recovery work interrupt every iteration, and roadmap commitments keep slipping. Leadership wants the dates preserved without adding staff. How would you propose capacity and goal changes?
- For several quarters, production support, customer escalations, and cross-team requests have displaced roadmap work. Someone proposes a universal 20% reserve, though interruption rates vary. How would you set the reserve?
- How do you work out what your team can really commit to next cycle, rather than headcount times working days?
- When you made this decision, what resources did you have and how wide was your scope of collaboration? How did those limits shape your choices?
- A business partner brings you a problem that is not clearly defined. What sources would you check, whom would you consult, and how would you separate confirmed facts from assumptions? How would you turn the findings into an actionable plan?
- Halfway through a project, available capacity suddenly drops by half while the deadline stays fixed. How would you resequence work and reset expectations?
- 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 major incident produces 18 actions across architecture, monitoring, training, and process, but teams already have quarterly commitments. How would you select actions that reduce recurrence risk?
- 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?
- 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?
- Three projects list the same platform team as a critical dependency, and all buffer time is allocated. A new regulatory requirement must ship before quarter-end. How would you reallocate capacity and commitments?
- One owner is responsible for four high-priority projects. Status reports look normal, but risk handling, cross-team decisions, and retrospectives are all delayed. How would you decide whether to add support, reassign ownership, or reduce the portfolio?
- 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?
- A mobile release depends on app-store review with variable duration; backend and web can launch earlier, but a marketing campaign has a fixed date. How would you plan release windows, feature flags, and cross-platform degradation?
- Several teams use one deployment pipeline and fixed maintenance windows, but their changes differ in size and rollback readiness; one team's delay steals validation time from others. How would you plan release capacity and resolve conflicts?
- Five projects each look reasonable by their own value ranking, but they share three sequential dependency teams and cannot finish within the quarter. How would you identify portfolio bottlenecks, resequence work, and decide whether to split delivery?
- A business sponsor leaves before a project is complete; the replacement values different measures, yet the team continues spending to the old plan. How would you reconfirm benefit assumptions, ownership, and continuation criteria?
- A regulatory requirement has a fixed effective date, while Product wants to improve the experience; both depend on a backend change, but experience research is unfinished. How would you separate mandatory compliance scope from iterative experience work?
- Several teams rotate on-call for core services, but plans count only project hours; incident investigation and drills displace planned work, and service loads vary widely. How would you forecast capacity and create a fair cross-team model?
- Project plans list dependent teams but no delivery owners or confirmed dates; each project looks feasible alone, while the portfolio may compete for the same capacity. How would you build dependency commitments and a risk view?
- Several projects use budget and time as planned, but key business outcomes show no visible change; status reports mainly count completed tasks. How would you redefine portfolio progress measures and support resource changes?
No questions in this section match your target. ·
E · Collaboration, communication, and influence5
- 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-functional review is shortened to ten minutes, and decision-makers only want to know whether launch can stay on schedule. Your evidence shows two risks with different impact scopes. How would you organize the information so they can make an informed choice quickly?
- You want to push something valuable to the team in the long run that nobody is asking for now. Why do it, how do you persuade others, do you push top-down or bottom-up, and how do you show its value?
- Two teams have committed to quarterly goals, and a critical skill turns out to be held by only one engineer. Both request priority access. How would you negotiate an executable allocation while making the unmet side aware of the cost and review conditions?
- 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?
No questions in this section match your target. ·