Identify a useful part to own and a checkable correction
This group concerns your part in a setback, known impact, a feasible correction and follow-up. Taking responsibility does not mean accepting every blame or fixing what you cannot control.
Keep values for items 19, 20, 22 and 23. Items 21 and 24 use 6 minus the response. Divide the six-contribution sum by six and round once to one decimal.
Responsibility can be specific and bounded
The items ask whether you examined your part, communicated known impact, agreed a correction within your control, checked its effect and mentioned a blockage. They do not ask you to accept blame for another person’s actions or to repair a system beyond your authority. A four-week self-report cannot establish what happened in a dispute. It can help identify one question about a task. The group is editorially defined and is not a validated accountability scale or a measure of how much responsibility you should bear.
A worked example with two reversals
Raw responses of 3, 4, 2, 3, 3 and 2 become contributions of 3, 4, 4, 3, 3 and 4. The total is 21, divided by six to display 3.5. A larger number means greater endorsement of these coded habits, not proof that a correction worked or that you caused a problem. The four group means are never averaged into an overall ethical grade. Each complete group remains available if another has an unscored response, with no zero replacement or estimated answer.
Correct a duplicate without claiming the whole system
Suppose a fictional shared list contains a duplicate that you added. You can identify the duplicated line, explain which use might be affected and agree a permitted correction. A follow-up checks that the duplicate is gone and the intended information remains. A counterexample is blaming the whole tool before checking your own entry; another is accepting responsibility for every unrelated error. The example separates a traceable contribution from broader causes. It is not a finding about any real colleague, and serious incidents require their appropriate procedures.
Separate a blockage from refusal or personal failure
A repair may depend on access, approval, another person’s input or a safe reporting route. The questionnaire does not know whether these were available. A smaller coded mean can reflect context, wording or recall and does not prove avoidance. If the situation did not occur or you cannot judge, choose unscored. All six numeric responses are needed for this mean, but the full guide stays readable without it. No missing response is interpreted as an admission, and an all-unscored form can still finish.
Agree a correction with a stopping point
For an ordinary low-stakes issue, state what is known, the part you can change and any permission or help needed. Name a single check that would show whether this correction addressed that issue. If blocked, communicate the constraint through an appropriate route rather than quietly promising the impossible. Stop when the agreed criterion is met or when a new decision is needed. This is an optional planning exercise, not a demand for unpaid work, unlimited responsibility or public disclosure of an incident.
Keep the next step proportional to the evidence
A useful reflection records the bounded problem, the agreed action and the observed check, without deciding that you are responsible or irresponsible as a person. The form has no established norms, reliability or predictive validity and cannot decide hiring, sanctions or trust. Use actual evidence and appropriate support for consequential disputes. All four public readings remain free and separate from your answers. When sharing, the tool copies only the public title and URL, not an incident description, private responses or personal means.