Spotting finance problems in EOS sessions
You're not the accountant — but finance problems surface in your sessions constantly. A field guide to recognizing them, naming them well, and guiding without overstepping.
- Finance problems disguise themselves as stalled Rocks, circular Issues, and accountability gaps.
- Name the pattern as a question, not a diagnosis: "Is finance giving you a reliable monthly close?"
- The fix is almost always controller-level; the implementer's job is to help the team see it.
As an implementer or facilitator, you don't fix the books — but you're often the first person positioned to notice that finance is the real constraint on a client's traction. Naming that accurately is one of the more valuable things you can do. This is a field guide to what to listen for.
Tells during L10
- A financial measurable gets an asterisk or a "that's not really right" every week.
- A money Issue can't get solved because the team disputes the underlying number.
- The same cash or margin question resurfaces meeting after meeting.
- "Was last month profitable?" gets hedging or cross-talk.
- "Once the books are done we'll know" shows up repeatedly.
Tells during planning
- Rocks that depend on financial data slip quarter after quarter.
- Budgets get set on gut because reliable forward numbers aren't available.
- V/TO financial targets feel disconnected from any real forecast.
How to name it without overstepping
You don't need to diagnose the general ledger. Name the pattern and hand it back as a question.
"It sounds like the team doesn't fully trust these numbers. Is finance giving you a reliable monthly close?" — That single question reframes a stalled Rock or circular Issue as a finance-function problem the company can actually solve.
This works because it stays in your lane. You're not auditing their books; you're observing a pattern and connecting it to a solvable cause. Teams usually recognize it immediately, often with relief.
A simple sequence
- Notice the recurring finance-shaped friction.
- Name it as a question, not a diagnosis.
- Point to what good looks like — a reliable close, trusted measurables, reporting tied to Rocks.
- Hand off. Whether they fix it in-house or bring in help, your job was to help them see it.
For a structured way to surface this with a client, the printable Finance Readiness Check is built to run in a session.
Frequently asked
How can an EOS implementer spot a finance problem?
Watch for stalled Rocks tied to missing data, circular L10 money debates, distrusted Scorecard numbers, and an inability to confirm last month's profit. These patterns usually point to finance, not strategy.
Should an implementer fix a client's books?
No. The implementer's role is to recognize and name the pattern, then point toward what good looks like. The fix itself is controller-level work the company handles or outsources.
How do I raise a finance issue without overstepping?
Frame it as a question rather than a diagnosis — for example, "Is finance giving you a reliable monthly close?" That keeps you in your lane while surfacing the real constraint.