INSIGHTS / THE MERIDIAN SERIES
07 / 16
Intended Enterprise State
Eighteen months ago, when your bank acquired that fintech lending platform, leadership made a specific, narrow decision: MFA stays off the acquired platform while integration finishes, but only under conditions — the gap closes by Q2, the exposure stays bounded to the loan volume the platform had at the time of the deal, and nothing about what that platform does changes in the meantime. That's not one decision. It's a decision plus everything that had to stay true for the decision to still make sense.
That whole package — the decision, its scope, its timeline, and the assumptions underneath it — is one piece of what I mean by Intended Enterprise State. It's not just "MFA is off." It's "MFA is off, on a platform doing this much loan volume, doing this kind of lending, for this long, with this fix on the way." Change any one of those pieces, and you're not looking at the same approval anymore, even if nobody edited the original memo.

Why the Whole Package Matters, Not Just the Headline
Most companies only track the headline part of a decision — "MFA is off, acceptance on file" — and lose the rest. But the rest is what actually made the decision defensible. Leadership didn't accept unlimited exposure on an unlimited platform for an unlimited time. They accepted a specific, bounded version of that risk. If the platform quietly starts doing more volume, or a different kind of lending, or the fix stalls past its deadline, the business is carrying something different from what got approved — different access controls, different loan volume, a fix that's stalled instead of on schedule — even though the paperwork never changed.
One Decision Is Only Part of the Picture
That MFA acceptance is one thread. Intended Enterprise State is the whole fabric — every decision like it, across every part of the business leadership has actually weighed in on: what you're funding, what you're staffing, what risk you've agreed to carry, what limits you've set, all of it, taken together. A single accepted risk is the easiest way to see the idea in action, but the real reference point is bigger than any one acceptance. It's the entire condition leadership has signed off on, all at once.
The Reference Point Everything Else Gets Measured Against
This is why Intended Enterprise State has to exist as its own thing, separate from whatever the business is actually running today. It's the fixed reference point — what leadership actually signed off on, in full, including every condition attached to it, across everything they've approved. Without it, you have no honest way to check whether the actual risk you're exposed to right now — the real access controls, the real volume, the real state of the fix — still matches what got approved. You'd just be comparing today's mess to your memory of a meeting eighteen months ago.
Keep that reference point clear, and the next question becomes simple to ask, even if the answer is uncomfortable: does the bank you're actually running today still match the bank leadership said yes to — not just on this one platform, but everywhere leadership has made that kind of call? That comparison — intended against current — is where the real picture starts to show up.
THE MERIDIAN SERIES
07 / 16