How Frameworks Are Classified
The six sections tell you what a framework says. Classification helps you
find the right one. As the library grows, labels are how you filter quickly.
Every framework carries one ID and four labels.
Framework ID — its permanent name
A fixed code like FF-WC-001, read in three parts: FF (FinanceFrameworks), the Area code
(WC = Working Capital), and the sequence number within that area. IDs are permanent and
never reused, so any link, citation, or reference always points to the same framework.
Title and Description
The Title names the framework’s focus. The Description is a few sentences on the problem it
addresses, the routine it sets up, and its purpose — enough to judge a framework before
reading it in full.
The four labels each answer a different question about that framework:
Implementation Depth — “How deep into the business does this reach?”
Shows how far the framework reaches: into day-to-day execution, finance management, or
broader business decisions.
Operational: runs at the execution level.
Managerial: sits with finance management and oversight.
Strategic: informs broader business and capital decisions.
Tier — “What governance job is it doing?”
The governance maturity level.
Control: prevents a problem directly (approvals, checks, enforcement).
Monitor: gives visibility and catches issues early (tracking, reviews, exception detection).
Optimize: improves something already working (efficiency, allocation, prioritization).
Area — “Which part of finance?”
The domain the framework belongs to, and the source of its ID letters. Eight areas:
Working Capital, Profitability & Margin, Planning & Forecasting, Cost Governance,
Capital & Investment, Controls & Compliance, Mergers & Acquisitions, and
Finance Systems & Data Quality.
Outcome — “What business result does it target, and which way?”
An arrow shows whether the goal is to raise (↑) or reduce (↓) something — for example
Cash visibility↑, Cash leakage↓, Capital allocation effectiveness↑, Compliance risk↓,
Cost overrun↓, Data reliability↑, Decision cycle time↓. A framework can target more than one.
This lets you start from a goal and find every framework built to deliver it.
How Each Framework Is Structured
A framework isn’t an article or an opinion piece. It’s a practical tool with a fixed shape:
every framework answers the same six questions, in the same order. Skip one and it’s incomplete
— like a recipe that lists ingredients but never says what to do with them.
1. Scope / Trigger — “When does this apply to me?”
The situation that makes the framework relevant — the signal that says use me now.
A tool you don’t know when to reach for is one you’ll never use. You should be able to read this
and immediately know whether it’s your situation.
2. Failure Mode — “What actually goes wrong if I ignore this?”
The specific, concrete damage when the problem is left unmanaged — not “things get bad.”
People act when the cost is clear. Example: in a late-payment framework, money you’ve already
earned sits in customers’ accounts instead of yours. The business looks profitable on paper
while quietly running out of cash.
3. Control Rule + Owner — “What’s the fix, and who owns it?”
The rule that prevents the failure, plus the one person accountable. A rule with no owner
doesn’t get followed — “someone should chase late payments” means nobody does, while
“the Controller reviews all overdue invoices every Friday” gets done. One rule, one name.
4. Minimum Viable Implementation — “What’s the simplest version I can start today?”
The smallest version that still works — no new software, no new hires, no waiting. Most businesses
don’t have large finance teams, and a framework that assumes they do gets ignored. Example: not a system,
just a weekly spreadsheet of overdue invoices and a 30-minute Friday review with one person assigned to
chase each.
5. Impact Logic / Cost of Inaction — “Why is this worth my time?”
What you gain by fixing it or lose by ignoring it, tied to something that genuinely matters:
cash, cost, risk, or time. The numbers aren’t universal — you apply your own volumes, margins,
and rates to estimate the impact in your environment.
6. When It Stops Working — “When will I outgrow this?”
The honest limit — the point where the framework is no longer enough. No tool fits forever,
and naming the expiry date upfront protects you from the most expensive mistake: trusting a
control long after it has quietly stopped working.