FP&A Agile Finance · 6 / 6

The Wednesday Test

The finale of the Agile Finance series. One unscheduled question from the CEO is the simplest test of whether your finance function is genuinely top-tier agile, and the binding constraint it exposes isn't tools or talent. It's culture.

The Wednesday Test: agile versus non-agile finance. On the left, a team that passes: asked at 9am what happens to covenants if Brent drops 30% and a key contract is lost, they model it immediately and promise a board-grade response with second-order implications by 3pm. On the right, a team that fails: they must convene, refresh the models and report back by Friday, treating revision as confession. The verdict: top-tier agile is an organisational posture, not just software.
Same question, two cultures. Top-tier agile is an organisational posture, not just software.

Here's a test for whether your finance function is genuinely top-tier agile.

The CEO walks in on a Wednesday morning. No appointment. She asks:

Wednesday, 9am, no appointment

"What happens to our covenants if Brent drops 30% over the next two quarters, and we lose the X contract?"

Can someone in finance give her a board-grade response that day?

What doesn't count

"We'll come back to you Friday." "Let me convene the team." "We need to refresh the model first."

What does

That same day, with confidence intervals, second-order implications, clear assumptions, traceable lineage, and a recommended course of action.

If yes, you are agile. If no, you are not.

Why most fail

Most finance functions, including most that describe themselves as agile, fail this test. Not because they lack talent. Not because they lack tools. Because the underlying architecture (model, data, decision rights, and culture) was not built for a question that arrives unscheduled.

The cultural answer

The interesting part isn't the technical answer to the Wednesday Test. It's the cultural one.

Where it passes

Revising a forecast is professionalism. "Our previous number is no longer the best estimate" is met with respect, not suspicion. Numbers are working hypotheses, refined as the world reveals itself.

Where it fails

Revising the number carries political cost. Analysts pad. Controllers stall. The forecast becomes a commitment to defend rather than a model of the future.

No software fixes this. No vendor sells it. No transformation programme has it as a deliverable.

An organisational posture

It is, however, the single most important precondition for everything else in this series. Layered architecture matters. Driver-based models matter. AI matters. Real-time data matters.

But none of it matters if the culture treats every revised forecast as a confession of failure.

Top-tier agile finance is not a software state. It is an organisational posture, and the Wednesday Test is the simplest way to know whether you have it.

This concludes the series. Thank you for reading, and thank you to the friends and colleagues whose conversations, over recent months, these six posts have tried to capture.

Pass the Wednesday Test

A board-grade answer to an unscheduled question, that same day: confidence intervals, lineage, second-order effects and all. The architecture for it is what we're building with Novi; the posture is yours to set. Join early access to follow the work.