An Africa Venture Group initiative

Management

From Board Decision to Team Action: A Practical Accountability Loop

Learn a practical accountability loop that connects governance decisions to owners, deadlines, evidence and operational escalation.

Boards and executive committees spend significant time reviewing risks, approving plans and allocating resources. Yet after the meeting, the question that determines the value of that work is simple: what changes in the organisation now? If the answer cannot be found in assigned, followed-up actions, the decision may stay in minutes that few people revisit.

Accountability does not mean searching for someone to blame when a result is missed. It means making authority, commitment, support and escalation clear. A good loop lets teams work with autonomy while helping leaders see delays and make trade-offs in time. It should be light enough to use and precise enough to keep important work from disappearing between meetings.

Step 1: state the decision in executable terms

A decision should be written in language the people doing the work can understand. “Improve sales performance” is not an executable decision. “Run a six-week weekly pipeline review led by the sales director, with a first assessment on 30 June” is clearer. The record notes the issue, the option selected, the reason for the choice and, when useful, the alternatives considered.

The wording should preserve authority boundaries. A board may approve a direction and request a report; a chief executive may appoint an owner; that owner may organise delivery within agreed limits. Confusing these levels creates either micromanagement or a responsibility gap. The AMOS Framework connects governance and execution so decisions remain connected to work while roles stay distinct.

Step 2: name one owner and confirm authority

For each action, identify one person responsible for progress. That person does not need to do every task. They coordinate contributors, flag dependencies and request decisions when needed. But the owner must be singular and known. “Operations” may describe a team; it does not tell anyone who will report next.

Confirm the owner’s mandate. Can they commit the agreed budget? Can they request support from another unit? Which changes require approval? If the person lacks authority or resources, the organisation should recognise that before the deadline is missed. Accountability works when authority, responsibility and means fit together.

Step 3: set a due date and a review point

A useful due date reflects the work remaining, dependencies and risk. Complex actions can be broken into observable milestones. Follow-through does not mean asking “where are we?” every day. It means agreeing on a predictable point when the owner will share status, evidence and blockers.

A weekly review may be enough for operational priorities. Governance items can follow the calendar of the relevant committee. Between meetings, a shared register records what must happen, who owns it, by when, its status and its evidence. The public AMOS Core Standard is an entry point to common management requirements; confirm access conditions for other editions and related documents on the site.

Step 4: review evidence and handle gaps

“Done” needs a definition. Depending on the action, evidence might be a signed contract, a completed bank reconciliation, a tested process, documented training or an updated measure. The evidence should match the importance of the risk. The purpose is not to create bulky files. It is to answer reasonably: what shows that the work was completed and is functioning?

When a gap appears, distinguish among causes: an assumption was wrong, capacity was missing, priorities changed, an external dependency blocked delivery or the action did not happen. The owner states what is needed: a decision, resource, revised date or escalation. Leaders resolve the issue at the appropriate level and record the next step. The AMOS Evidence, Assessment and Decision Protocol encourages a careful review of what the evidence can support and where its limits lie.

Step 5: close, learn and reuse

Closing an action means confirming the outcome, keeping useful evidence and deciding whether further follow-up is needed. An action can be completed without producing the intended effect. That distinction matters: finishing a task does not always solve the problem. A review can separate “activity completed” from “result observed.”

For boards and executive teams, this loop also improves oversight. Members can focus on material exceptions rather than reviewing every operational detail. They can ask whether management has enough evidence, whether the owner has authority and whether the proposed response fits the organisation’s risk appetite. Teams, in turn, can see which matters require escalation and which they are empowered to resolve. The record becomes useful institutional memory when it preserves the reasoning behind a decision, not only its final wording. That context helps new leaders understand why a commitment was made and whether changing conditions require a new decision.

Teams can keep the record lightweight: a shared spreadsheet or simple task board may be enough. The test is whether participants can find the current owner, due date and next decision without searching through long email threads. Review the tool after a month; remove fields nobody uses and add only information that supports a real choice.

At the end of the cycle, ask what helped delivery and what slowed it down. The organisation may adjust its reporting template, delegation, review frequency or data quality. The goal is learning, not a permanent layer of control. The AMOS Facilitator and Cohort Guide may help people who support teams to lead these conversations; check the page for access terms and document status.

Test the loop on a real decision

Choose a recent decision that is not progressing as expected. Reconstruct the chain: wording, owner, authority, resources, date, review, evidence and escalation. Find the point where the loop broke, then test one improvement over the next two meetings. Compare time to closure and the quality of available information; ask participants whether the process helps them act.

AMOS is in a pilot phase, and no AMOS certification is currently issued. Organisations should describe experiments as learning in progress, not as general validation. Explore the AMOS Framework and AMOS Resources to understand the approach. A decision earns its full value when an organisation can show not only that it made the decision, but how it was carried out, what was learned and what should happen next.

← All articles

Pilot organisation