What you license · 05
The e2e Flow reference model, worked as BigBank
Frameworks fail at the moment someone asks “show me.” The reference model is the answer: one continuous example of value carried through every practice, record, view, and skill output, from a customer idea through strategic objectives, initiatives, value and innovation increments, features, user and technical stories, and tasks, to the verdict that confirms the investment paid off.
BigBank is the organization the example lives in. It is a worked example aggregated from more than two decades of engagements across financial services, healthcare, telecommunications, government, and retail, and it is never a client. Because the whole system is populated as BigBank, every page can be shown in full, with no redaction and nothing withheld, which is exactly what a buyer deciding on a system of record needs to see.
Why one example, all the way through
The thread is the point.
Disconnected samples teach a practice in isolation and leave the connections to the reader. The reference model carries the same thread through all of them, so the strategic objective on the roadmap is the one the initiative serves, the increment the planning event pulled is the one whose features cross the Feature Kanban, the stories in Linear are the ones those features decomposed into, and the verdict recorded after the measurement window is the one that re-orders the backlog for the next quarter. Every practice page in the PDLC points at its moment in this thread, every dashboard face reads the BigBank instrument, and every skill output in the model was produced by the skill actually running, not written to look as if it had been.
What BigBank contains
Sized like the organization that will license it.
BigBank is shaped like a technology organization of ten to fifty teams: a small set of product lines and value streams, a strategic objective set, initiatives defined to the eight-category standard, named personas who hold the decision rights on a published table, and a demonstration portfolio spread across every board state from the front door through delivered and outcome confirmed, so every view has data, aging and flow metrics read realistically, and the closed loop is visible end to end.
Depth is carried where it proves the most. At least one initiative runs all the way from strategic objective to sized stories in Linear, through a real Value Delivery Planning event with its trade-off log, a rendered roadmap with its confidence tiers, a morning read with real exceptions, and an outcome review with its verdict. The rest of the portfolio carries summary depth, which is how a real portfolio looks on any given day.
See it running
The overviews, in the order a buyer asks the questions.
Each overview is filmed against the BigBank environment and lands here as it is finished. Together they are the demonstration the working session runs live.
The front door to the intake queue
An idea arrives with its problem, intended result, and value case, moves through discovery to the Definition of Ready, and waits in a queue held to the depth the quarter can absorb.
The quarter gets committed
Value Delivery Planning on the BigBank backlog: capacity with confidence, pulls and deferrals decided in the room, and the roadmap refreshed as the close.
Objective to story in one afternoon
The Chain carries one BigBank increment from a hardened brief to specified features, sized stories in Linear, and a dated implementation plan.
The morning read and the Bridge
The Watch surfaces what is aging, blocked, or drifting with owners and next steps, and the Bridge gives leadership the same truth at its own altitude.
The loop closes
A measurement window ends, the Proof brings the promised result beside the observed one, and the recorded verdict re-orders next quarter.
What the license contains
The scaffolding your own examples progressively replace.
The reference model arrives with the system: the BigBank organization and context files, the populated Delivery OS and Linear workspaces, the PDLC estate with the worked example threaded through it, the dashboards reading the BigBank instrument, and the skill outputs that produced them. Organizations keep it as the proving ground and the sandbox where skills, dashboards, and guidance evolve without touching live work, and they replace its examples with their own as the installation takes hold. How the tiers are shaped.