H · Professional responsibility and work style

Ownership

Taking responsibility for outcomes, including the parts nobody asked for.

Classification boundary

Include: Include taking responsibility, closing loops, and owning outcomes.

Choose a neighboring leaf when: Use integrity for truthful disclosure and boundaries for the limits of authority and responsibility.

This capability may appear in standards across different stages. Explore stage expectations

20 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 options5

Compare goals, constraints, options, and trade-offs.

Questions 1–5

An external-system issue affects your team, but the owner is unresponsive and boundaries are unclear. How would you act without overstepping?
The team fixes a known cause, but operational metrics do not return to baseline and the engineering task is closed. How would you prevent premature closure?
Two teammates each believe they handed off work, but a critical item is missed and a customer waits. As the manager, what would you do?
A user issue requires product, engineering, and operations, but each team completes its local tasks while the overall result still misses the goal. How would you name a coordinator and drive the issue to resolution?
While reviewing a partner document, you find exposed customer credentials. This is outside your team’s remit, the owner is away, and the material may be public. How would you contain and hand off the risk?

Experience and reflection15

Use past facts to examine contribution, results, and learning.

Questions 1–8

You deliver an interface on schedule, but the downstream team has not integrated it and the business workflow still cannot be used. Your contractual task boundary is complete. How would you decide what responsibility to take next and communicate it?
Your quarterly outcome has not definitively failed, but new validation has sharply reduced the chance of meeting it on time. You worry early reporting will look like weak execution. How would you communicate and organize next steps?
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 find a definition error in analysis you submitted, and decision-makers have already shifted resources based on it. How would you take responsibility and correct the impact?
You championed automation to reduce manual effort, but maintenance rises and savings are small. How would you respond?
Tell me about the piece of work you are proudest of. Why is it the best, what yardstick do you measure it by, and which parts were your own contribution?
A critical delivery is falling behind on work owned by another team, so you step in and prevent a delay. This has happened three times, and people now assume you will handle it. How would you protect the current result while clarifying future owners and ways of working?

Questions 9–15

Describe a project or module you owned that fell short of its commitment. How did external dependencies and unvalidated assumptions affect the result? How do you explain your judgment, responsibility, and recovery actions, and what would you validate earlier next time?
Tell me about a time you took on a challenge beyond your role. Why did you do it, how did you balance your regular work, and what were the result and the cost?
Tell me about a time you noticed something that nobody owned but that affected the outcome. What did you do, and how did you define your own responsibility in it?
After proactively taking on a cross-team issue, your original project begins slipping. The team also depends on you for the new issue. How would you address priorities and boundaries openly?
A colleague’s change caused a data gap, but they fear blame and have not reported it. The team is deciding whether to expand rollout using incomplete data. How would you respond?
An operations tool shipped to specification, but downstream teams did not adopt it and users still rely on manual steps. How would you decide whether to stay involved?
You find that customers may have been overcharged. The owner is offline, and mitigation crosses your role boundary. How would you contain impact, escalate, and document authority?

Back to the whole domain