Accountability without a scoreboard

Most accountability systems are built on the assumption that people behave differently when they know someone is watching. Review meetings, KPI dashboards, weekly check-ins - these are all variations of the same mechanism. External visibility creates external pressure, and external pressure produces results.

That works. The problem is that external pressure is intermittent. The meeting is once a week. The dashboard gets checked on Friday. Between those moments, there is a lot of time in which no one is watching, and the choices made in that time are where real accountability lives.

The Accountability step in the Lion Ethos is about building the internal version. The standard you hold yourself to in the absence of external pressure. Not because you are unusually disciplined, but because you have built the habit of honesty with yourself about whether you did the thing you said you would do.

This sounds simple and it is not. The gap between what we intend and what we actually do is one of the most consistently uncomfortable things to look at clearly. The reflex is to explain the gap in terms that make it smaller - circumstances, workload, priorities that shifted. Some of those explanations are accurate. Most of them are partial.

When I moved to Frøya, the absence of an office environment meant that external accountability structures mostly disappeared. No colleagues walking past. No culture of visible presence. The work happened or it did not, and no one was in a position to notice either way except me.

That is clarifying. After a few months you find out very quickly whether you have internal accountability or whether you were relying on external structure all along.

For founders and operators, this matters because external structures do not scale with the business. In a five-person team, accountability is informal and visible. At fifteen people, it has to be built deliberately. At thirty, the founder is increasingly removed from daily operations and their own commitments need to be the ones that hold - the commitments to process, to the team, to the rhythm of execution.

The way I build internal accountability is straightforward. At the end of each week, I review what I said I would do and write down whether I did it. Not to punish the misses, but to see them clearly. A pattern of misses in a specific area means either the commitment was wrong - too ambitious, misdirected - or the behaviour is wrong. Both are useful information.

Most accountability conversations in business focus on outcomes. Did the revenue number land. Did the project ship. Outcomes are lagging indicators. By the time you see them, the behaviour that produced them is weeks in the past.

Tracking the commitments directly, on a short cycle, is the leading indicator version. It tells you what the outcome will be before you get there.

Murphy Alex builds operational AI systems for Norwegian SMEs from Frøya, Trøndelag. IPRESTANDA is at iprestanda.com.