What FLOCK actually looks like in practice

The brief before the cycle starts

Teams that come to FLOCK usually arrive with a specific problem. A Beta assessment is close. Governance is asking questions nobody can answer cleanly. A new Delivery Manager has joined and nobody agrees on what done looks like. Something is not working, and the team knows it.

The intake conversation is not about FLOCK. It is about delivery. What decisions are live? What evidence exists? What does governance currently receive and what does it actually need? The cycle is designed from that, not from a template.

What most teams discover at this stage: they have more evidence than they realised, and less clarity on their active decisions than they expected.

Weeks one and two: what the team already has

The first fortnight is not about doing new things. It is about surfacing what already exists. Evidence from research. Decisions that have been made informally. Assumptions that have been treated as facts.

A team running their first cycle will spend the first session just mapping their active decisions. It takes longer than expected. There are usually more decisions in flight than anyone realised, and several of them overlap or contradict.

By the end of week two, the team has an Evidence Index — a lightweight register that names each active decision, the evidence that informs it, and where that evidence lives. This is not a document for governance. It is a working tool for the team.

We thought we knew what we were deciding. Then we wrote it down and realised three different people had three different versions of the same decision.

Weeks three to five: the rhythm starts to form

FLOCK runs on a fortnightly rhythm. Not weekly, which is too frequent to generate new evidence. Not monthly, which is too slow to stay useful. Every two weeks: what have we learned, what does it change, what are we deciding next.

The first few cycles feel mechanical. Teams report that the rhythm feels forced. That is expected. The point is not that the rhythm feels natural — it is that it creates enough structure to surface the things that would otherwise stay invisible.

Around week four, something usually shifts. The team starts anticipating the rhythm rather than reacting to it. Evidence gets gathered with a decision in mind, not retrospectively. The governance update gets easier to write because the decisions are already visible.

• Fortnightly check: what have we learned, what does it change
• Evidence gathered with a decision in mind, not retrospectively
• Governance updates written from the decision register, not from activity reports

The governance update in week six

The governance update is where the change becomes visible externally. Most teams go into their first cycle producing updates that are progress reports — what we did, what is next, any risks. These updates are easy to write and almost impossible to challenge.

A FLOCK-structured governance update looks different. It names the active decisions. It says what evidence informed each one. It names the trade-offs that were considered and the ones that were deferred. Governance can engage with this. They can challenge the trade-offs. They can ask for more evidence on a specific decision. The conversation changes character.

The Delivery Manager on one recent engagement described it this way: in the first update they were explaining what the team had been doing. By the third, they were asking governance to ratify a decision. Those are different conversations.

In the first update I was explaining what we'd been doing. By the third I was asking them to ratify a decision. That felt like progress.

What resists, and why

Not everything shifts easily. The most common resistance pattern is the team that produces strong evidence but cannot connect it to decisions. Research exists. Synthesis exists. But the step from 'here is what we found' to 'here is what we are deciding because of what we found' does not happen reliably.

This is not a capability gap — it is a structural one. The team has not established the habit of framing evidence as decision input. FLOCK creates that structure, but the structure has to be actively used. A good first cycle names this pattern explicitly and works on it.

The second common resistance: the assumption that governance wants information rather than decisions. Some teams have learned, through experience, that being seen to decide is risky. FLOCK cannot fix that culture directly. What it can do is give the team a language for surfacing the decisions that governance actually needs to engage with.

• Evidence exists but does not connect to active decisions
• Governance framed as an audience for information rather than a decision-maker
• The team avoiding visible decisions because of prior experiences with governance

Week eight: what did the cycle produce

By week eight, the cycle has produced a set of traceable decisions, an evidence register that shows what informed each one, and a governance trail that demonstrates the team's decision-making under pressure. This is the assurance artefact — not a document written for assessment, but a record of how the team actually works.

Some teams continue. They find the rhythm useful and integrate it into their delivery cadence. Some teams do not — they use the cycle as a diagnostic and take the findings into their existing ways of working. Both outcomes are valid.

What changes in either case: the team knows where their evidence is, what decisions are live, and how to explain their reasoning to governance without writing a retrospective. That is not a small thing.