Second-Order Effects: What Happens After What Happens

A finance team I heard about once capped expense approvals at a lower amount specifically to reduce fraud risk. It worked, in the narrow sense it was built for. Fraud dropped, and the dashboard tracking it looked exactly the way the policy was meant to make it look. It also meant legitimate large purchases, the ones a growing team genuinely needed to keep operating, now required three extra approval steps that had not existed before. Those extra steps added roughly two weeks to anything over the new cap. Teams facing that delay, under real pressure to get equipment or services in place on time, started splitting single purchases into several smaller ones specifically to stay under the new limit and skip the wait. The first-order effect, less fraud, was real and measurable. The second-order effect, more purchase-splitting and arguably more risk overall, just in a new and far less visible shape, took longer to show up and was much harder to trace back to its actual cause once it did.

Why first-order thinking stops too soon

First-order thinking asks a single, entirely reasonable question: does this solve the problem directly in front of me. It is not wrong to ask that question, and most of the time the first-order answer is accurate as far as it goes. The expense cap really did reduce fraud, exactly as intended. The trouble is that a first-order answer describes what happens the moment a change takes effect, before anyone downstream has had time to actually live inside the new rule and adjust their own behavior around it. People are not passive once a policy changes. They respond to it, routing around friction, finding the path of least resistance, often within days of the change going live, and that response is precisely the part a first-order analysis has no way of seeing in advance.

Second-order thinking adds exactly one further question on top of the first, and that single addition does most of the real work: and then what happens, once people have had real time to live inside this change and adjust how they operate around it. Not a hypothetical worst case dreamed up for its own sake, but a genuine, specific prediction about how the people actually affected by the new rule are likely to respond to the incentive it just created, given what you already know about the pressure they are under.

A simple way to actually ask it

That conversation costs about two minutes and happens before the policy ships rather than being discovered six months later in an audit. The question is always the same shape: given the incentive this change creates, and what I already know about the pressure the affected people are under, what is the easiest way for them to respond to it, and is that response actually the one we want?

Where to stop asking

Second-order thinking has an obvious trap built into it, which is that the question and then what happens can be asked indefinitely, spiraling into third, fourth, and fifth-order speculation that becomes less reliable and more exhausting with every additional step. The useful discipline is stopping at the first genuinely plausible second-order response, the one grounded in something you already know about how the affected people actually behave under pressure, rather than chasing every theoretically possible chain of consequences to its logical end. The expense cap example only needed one extra question, what happens to a team facing a real deadline, to surface the purchase-splitting risk. It did not require modeling five further steps beyond that to be worth asking.

This is, in the end, a habit rather than a formal technique, and it is one of the cheapest habits available to a BA relative to what it protects against. Before a change ships, whether it is a policy, a new field on a form, or a process redesign, ask once what the people living inside it are actually likely to do in response, given the real pressures they are already under. Most of the time the honest answer confirms the change is fine. Occasionally it surfaces exactly the kind of quiet, expensive surprise that an audit finds eight months later, and finding it on a Thursday afternoon before the policy ships is considerably cheaper than finding it in that audit.

The hardest part of this habit is not the thinking itself, which usually takes less than a minute once you know the question to ask. The hardest part is asking it out loud in a room that already feels good about the decision it is about to make, where raising one more question can read as slowing things down or second-guessing colleagues who worked hard to get the proposal this far. It rarely needs to be framed that way. "What's the most likely thing someone does differently once this is live" is a question about the proposal's own strength, not a challenge to the people who built it, and asked in that spirit it tends to be welcomed rather than resisted, because everyone in the room would genuinely rather catch the issue now than explain it in an audit eight months later.

Tomorrow closes the week by folding everything so far, the queue, the map, the loops, the second-order question, into something that fits inside ordinary daily BA work rather than sitting apart from it as a separate analytical exercise.

Go out and be successful.

Oluwatosin Ogunkoya · Flotog BA Insights · 1:1 mentoring and coaching for BAs at every career stage · www.flotogbainsights.com

TOMORROW

Thinking in Systems as a Daily BA Habit - Folding this into ordinary requirements and process work, instead of treating it as a separate analytical exercise.