Generative Accountability

Concept and practice · Working definition adapted from the existing Story Dynamics material

Generative accountability connects an honest account of what happened and its effects with the work required for repair, more reliable conduct, and fewer recurring failures.

It asks what responsibility entails under the actual conditions: what was reasonably possible, what someone did or failed to do, what needs to change, and what resources or arrangements make that change feasible.

Make accountability possible

Marilyn Paul’s related framework describes an organizational setting that supports inquiry and follow-through. Households and informal arrangements may have to negotiate those conditions themselves: time to examine an account, willingness to participate, accessible communication, support, and a feasible way to respond or make repairs.

The first accountable move may therefore be arranging what makes the inquiry possible. Name who will do that work and what it requires. If those conditions remain unavailable, keep the gap visible alongside any immediate action needed to address harm or an unmet need.

Account for impact and conduct

What happened? Whose needs or interests were affected? Which commitments existed, and were they understood and accepted? What remains disputed?

Context may change a judgment about preventability, responsibility, or the appropriate response. It does not automatically settle those questions or erase the impact.

Show the work of a hard tradeoff

When demands collide, make the options, constraints, and costs visible. Identify what each option protects, what it leaves exposed, and who bears that cost. Look for a partial move or new resource that could change the choice.

A legible explanation makes a decision reviewable. Review can still find that a different decision, earlier action, acknowledgment, or repair was needed.

Change the conditions producing recurrence

The shot-calling working document develops this through advance preparation, lead-time triggers, buffers, and shared sequencing. Those moves can reduce the frequency of crisis-point decisions when the necessary capacity exists.

Other situations require changed behavior, clearer authority, a different allocation of work, paid assistance, institutional action, or an arrangement that can be ended or replaced. Record what is missing instead of presenting an unfunded demand as an improvement plan.

Make commitments answerable

For each proposed change, state:

• What changes, for whose benefit, and who has explicitly accepted responsibility.
• What time, resources, authority, or assistance it requires.
• What would show that it happened and whether it helped.
• When to review it, what happens if it cannot be done, and how affected people can challenge or revise it.

Acknowledgment, repair, performance improvement, protection, and changes in role can be pursued together where appropriate. They need not wait for everyone to endorse the same larger explanation.

A working test

After a repeated missed task, “try harder” leaves several questions unanswered. What caused this occurrence? Was an earlier step feasible? Would a reminder help, or is the binding problem absent time, money, skills, coverage, or incompatible demands? What immediate repair is due? What accepted change will be checked next time?

The outcome sought is an improved situation and a more reliable arrangement. The record must also preserve when harm continues or a proposed arrangement does not work.

Development sources: Story Dynamics working document, Accountability Knot section; Shot-Calling Under Command Collision, especially sections 2–3. Marilyn Paul’s Moving from Blame to Accountability is a related source on explicit agreements, inquiry, and ongoing review. Applying these practices across households and overlapping institutions is a further adaptation.