How Silver Lake Financial Group dismantled five layers of hierarchy and rebuilt around intelligence
On April 2, 2026, Jack Dorsey announced that Block had restructured away from traditional hierarchy toward what he called a discipline-driven, intelligence-supported organization. He did not release a framework. He did not publish a playbook. He made a personnel change that made the old structure impossible to sustain.
Signal #121 captured this as the opening move of a broader pattern: the hierarchy-to-intelligence transition in financial services organizations. This piece builds out what that transition looks like in practice — not at Block, but at a company more representative of the mid-market fintech operator reading this publication.
Meet Silver Lake Financial Group. A fictitious regional consumer lender — $1.2B portfolio, 380 employees, Columbus Ohio, 12 years old, grown through acquisition. IBM i core. Profitable. Tired.
Dorsey did not deploy AI tools. He removed the structural conditions that made coordination layers necessary. Block's hierarchy existed — like all hierarchies — to manage information flow. Information needed to travel up, get interpreted, get routed, and travel back down. That travel was the job of middle management.
When intelligence infrastructure absorbs the information routing function, the management layer has no remaining purpose. Dorsey understood this and acted accordingly. The org didn't go flat. It became accountability-centric: discipline leads who own outcomes, workers who exercise judgment, and agents who handle everything in between.
The key distinction for the IBM i and fintech operator: this is not an automation story. It's an organizational architecture story. The question is not "which jobs can AI do?" The question is "which structures exist only because we lacked a coordination layer — and what replaces them when that layer arrives?"
Silver Lake's pre-migration structure. 380 employees. 12 middle management roles. The coordination layer — layers 2 and 3 — exists entirely to manage information flow that no system was equipped to handle automatically.
Post-migration structure. 290 human employees (not reduction — redeployment). 5 Discipline Leads with full outcome ownership. 7 agents as the intelligence layer. 3 tiers instead of 5.
Each agent was not deployed to replace a person. It was deployed to absorb a function that consumed human time without requiring human judgment. The displacement was structural, not individual.
| Agent | Function | What It Displaced | What Humans Now Do |
|---|---|---|---|
| Covenant | Loan Agreement Integrity | Processor Leads — document review, condition tracking, exception queuing | Credit Discipline Lead reviews exceptions flagged by Covenant; no manual queue management |
| Harbor | Applicant Onboarding Coordination | Loan Operations Manager — intake routing, status updates, handoff orchestration | Ops Discipline Lead sets onboarding policy; Harbor executes it |
| Archer | Underwriting Decision Support | Senior Underwriters — data aggregation, policy checks, risk scoring summaries | Underwriters make final credit decisions; Archer eliminates prep work |
| Cashflow | Payment & Servicing Coordination | Servicing Manager + Payment Ops supervisory layer | Servicing Lead owns exception resolution and escalation policy |
| Chronicle | Audit Trail & Compliance Documentation | Compliance Analysts — log maintenance, reg-change tracking, exam prep | Compliance Lead interprets findings; does not manage documentation labor |
| Sentinel | Portfolio Risk Monitoring | Collections Supervisor — delinquency tracking, early warning, escalation routing | Servicing Lead receives Sentinel's risk surface; decides intervention strategy |
| Compass | Portfolio Analytics & Decisioning | Ad hoc analyst requests, report compilation, board-level data prep | CEO + Discipline Leads receive live intelligence; no report cycle |
Silver Lake's leadership made a deliberate choice: no involuntary separations in Phase 1. This was not sentimentality. It was sequencing. The agents needed to be calibrated against real workflow — and the people who held institutional knowledge of that workflow were essential to calibration. Loan processors who had spent years routing exceptions became the people who trained Covenant to recognize them. Collections supervisors who had spent years escalating risk became the people who tuned Sentinel's thresholds.
This is the part that Dorsey's announcement made easy to miss. The org restructure at Block was not a headcount story. It was a role-redefinition story. The question Silver Lake asked every affected employee was not "should we eliminate your job?" It was "what judgment have you been unable to exercise because your job was full of coordination work?"
By month six, Silver Lake had 84 former coordination-layer employees in expanded judgment roles. Eighteen had left. Fourteen had been promoted into Discipline Lead track positions. The org was smaller in headcount. It was significantly larger in productive judgment capacity.
The question Silver Lake's CCO asked in month three was the right one: "If Sentinel surfaces a risk and the Servicing Discipline Lead makes a judgment call — who owns that decision, and is it documented in a form that survives a regulatory exam?"
This is the failure mode of agentic migration done without a governance layer. The coordination overhead disappears. The audit trail disappears with it. Regulators don't care about your org chart — they care about demonstrable, documented decision accountability. In the old structure, the Compliance Manager owned that paper trail. In the new structure, who owns it?
Silver Lake's answer was Chronicle — not as an audit bot, but as the institutional memory layer that made the flat structure defensible. Every agent action, every Discipline Lead decision, every exception resolution is timestamped, attributed, and retrievable. The CCO's job shifted from managing documentation labor to interpreting what the documentation reveals.
Agentic infrastructure without a governance layer doesn't reduce compliance risk. It obscures it. The coordination overhead that disappeared also contained — imperfectly, expensively — the organization's institutional memory. That memory must be rebuilt at the intelligence layer before the hierarchy layer is removed, not after.
Silver Lake ran its core lending workflow on an IBM i platform for nine of its twelve years. The migration to agentic didn't require replacing the platform. It required exposing the platform's logic to an intelligence layer that could act on it. Archer reads underwriting policy from the same RPG-based decision tables that underwriters have been consulting for a decade. Chronicle logs to the same DB2 audit tables that the Compliance Manager used to export manually every quarter.
The platform was not the barrier. The org structure was the barrier. The IBM i shop that reads this piece and concludes "we need to modernize our platform before we can do this" has misread the lesson. The question is not "is our technology ready?" The question is "have we mapped the coordination tax — and do we have the governance infrastructure to survive its removal?"