A CDFI lender's CEO briefed his board on Monday using rules written before the crisis

The mechanism here is narrower than the phrase "crisis leadership" suggests. What B:Side Capital's CEO calls a code is a short set of written commitments specific enough to be violated ^[9], and that specificity is the entire engineering decision. He argues that words such as "Integrity" or "People First" sit comfortably beside almost any action, including cutting staff or going public with a grievance, which is why they cannot settle a decision under pressure ^[8]. His own line, written well before March, committed him not to soften the truth for his team in order to calm them ^[11]. That is a rule with a failure state, which is what makes it usable at speed.

The tradeoff is that a rule with a failure state also removes an option you may badly want. He writes that part of him felt he should have done more to soothe nerves, and that he chose the plain version because he believed it was the fastest route to an actual solution ^[19]. Pre-commitment is cheap to write and expensive to honor, and the bill arrives in the one hour when improvising looks reasonable.

The arithmetic explains why a pre-written rule did any work at all. The order landed on a Friday evening and the plan was owed Monday morning, the 14th to the 17th, three calendar days ^[17]; because Saturday and Sunday sat in between, that is zero business days ^[18]. No counsel opinion, no appropriations reading, and no peer benchmarking was going to arrive inside that window, so whatever deliberation the Monday plan contained had to have happened earlier.

Some readers will call this a values statement dressed in stricter grammar, told by the person whose weekend it was, in a contributor column that Entrepreneur labels as the author's own opinion ^[16]. The evidence pushes back on that in two ways. He offers a falsifiability test that does not depend on his story: run your line against the hardest situation of the last two years, and if it does not produce a clear answer, it is not specific enough yet ^[13]. He also reports studying figures from the Roman Senate and from the Depression-era Army for a book on crisis-era leadership, finding that their codes differed from each other but were written in advance of the pressure ^[10]. The account stops short of an outcome, though: it describes a strong pull toward a public fight in the weeks that followed ^[15], and it leaves open what became of the CDFI Fund or of the company ^[20]. The record here supports a claim about sequencing; a claim about survival is a separate, unanswered question.

Separating the timescales keeps this honest. He had already assumed that mission-based lenders would draw scrutiny from the newly formed Department of Government Efficiency; the surprise was that the CDFI Fund itself got named so directly ^[6]. The gap between anticipating a category of risk and pre-deciding a response is precisely where the written line was doing its work. For a board this quarter, the usable question is which responses are already authorized on paper and who is permitted to issue them without a meeting. For the same board this decade, the question is a revenue line whose existence depends on a federal program, and no code answers that one. What transfers from his weekend is the timing rather than the wording, because the writing happened while nothing was at stake, which is the only condition under which it is cheap.