G · Learning, adaptation, and sustained growth
Structured reflection
Checking oneself through facts, judgment, action, and result.
Classification boundary
Include: Include reviewing decisions, actions, impact, and improvements based on evidence.
Choose a neighboring leaf when: Use resilience for recovery after setbacks and learning transfer for applying lessons elsewhere.
This capability may appear in standards across different stages. Explore stage expectations
28 questions
Choose a group based on the evidence you need. Groups follow existing question formats, not difficulty or mandatory prerequisites. Each batch has up to eight questions.
Judgment and options9
Compare goals, constraints, options, and trade-offs.
Questions 1–8
- You help build offline caching; success improves, but sync conflicts and support contacts rise. How would you review the approach and decide what next?
- The same backward-compatibility issue happened again. Earlier reviews added tests, but they still missed a real user combination. How would you find out why the corrective actions failed?
- Prototype testing was positive, but adoption is low after launch. How would you examine research context, participant selection, and implementation differences?
- The team produced several visual concepts, but users still struggle with the core task. How would you assess the exploration direction, problem definition, or validation?
- Teams keep old components after a new design system launches, citing limited flexibility and migration cost. How would you review the rollout?
- After launch, low-vision users cannot complete a key task, and the original study did not include them. How would you review and correct the research process?
- The team adopts many review suggestions, making the interface more complex without retesting user tasks. How would you review feedback handling?
- Under what conditions could that failed project have succeeded? Could you have had those conditions at the time, and how would you design it now for a better chance?
No questions in this section match your target. ·
Questions 9–9
No questions in this section match your target. ·
Experience and reflection19
Use past facts to examine contribution, results, and learning.
Questions 1–8
- 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?
- Promotion feedback says your work is reliable but its impact remains limited to individual delivery. How would you turn that feedback into next-stage experiments and determine whether your impact actually expanded?
- A high-risk decision produced a good outcome, but key assumptions were disproved and luck contributed. How would you reflect and change the next decision?
- Startup time improves after your change, but caching and server changes also shipped. How would you assess your contribution?
- The app store rejects a release, and the team says rules were unclear and launch is affected. How would you review preparation, communication, and validation?
- Crashes rise slightly during a limited rollout, but the team expands the audience and later receives widespread complaints. How would you review the decision?
- A teammate completes a learning goal and earns a certificate, but independent project capability does not improve. How would you review the goal?
- You completed a quarterly learning plan on time but still need help in real work. How would you determine where the plan missed the job need?
No questions in this section match your target. ·
Questions 9–16
- When you run a retrospective, how do you avoid glossing over the hard parts, switching the definitions, or making the facts sound better than they were?
- 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?
- Tell me about a time your judgment was overturned by the facts. Which parts of it were reasonable at the time, which signals were missed, and what exactly did you change afterwards?
- 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?
- Tell me about a mistaken judgment or operational error that led to a poor outcome. How do you see your responsibility, the system conditions that allowed it, and a specific later action that shows what you changed?
- Tell me about a project that did not succeed. Why did it fail, which causes were direct and which more fundamental, and how much of it related to your own judgment?
- If you redid this project with the same resources, how would you do it? Would you get more benefit, or stop earlier?
- The team correctly identifies an incident’s root cause and records improvements, but operating habits have not changed months later. How would you evaluate the retrospective?
No questions in this section match your target. ·
Questions 17–19
- A project was cancelled for insufficient market demand, but its technical capability may be reusable. How would you decide what to retain, transfer, or stop investing in?
- You changed code-review practices after a retrospective, but team defect rates remain flat. How would you judge effectiveness, sample size, or the mechanism?
- You underestimate work several times, and the team finishes through overtime, so projects appear on time. How would you reconstruct estimation error and hidden cost?
No questions in this section match your target. ·
No questions in this capability match your target. ·