Second and Third Order Thinking for Leaders

In checkers, a novice thinks one move at a time – if I move here, the next move is obvious. In chess, a grandmaster sees further, asking “and then what?” several moves deep, anticipating how the board, and the opponent will respond. That same gap separates first level thinking from second level thinking, and it is one of the most important distinctions we can apply as leaders and decision-makers in our business.

First level thinking is fast and simple. It looks at a problem, proposes the obvious fix, and stops there. Second & third level thinking asks what happens after that first reaction, and then what happens after that. It treats decisions not as isolated events, but as moves within a system that will respond, adapt, and sometimes push back in ways the first move never anticipated. The real edge in any competitive field comes not from seeing the obvious outcome everyone sees, but from seeing the second, third, and even fourth order effects that most people miss.

Here is a good example: when a highway gets clogged with traffic, the first-level fix seems obvious – add more lanes. So, the state spends years and millions widening the road. Traffic improves, briefly. The new capacity makes the commute easier, so more people choose that route, move further out, or stop carpooling. Within a few years, the wider highway is just as congested, only now it serves more cars across a larger footprint. The fix did not solve congestion. It just rebuilt the congestion at a larger scale.

Our industry rewards this same forward thinking and punishes the lack of it. Consider our bidding…pricing aggressively to win a job feels like a win, but if the margin doesn’t account for material escalations or subcontractor reliability, that “win” can become a strained budget and a project team fighting from behind for the next year. The first order result was a signed contract. The second and third order results determine whether it was actually good for us.

But the place this matters most is not in our numbers. It is in our relationships, both inside and outside the company, and it is here that construction minds are most prone to first level thinking. We are trained to solve the problem directly in front of us – the schedule, the scope, the cost. That training is valuable, but it can also give us blinders. We push a trade partner past their limit to save a week, win the day, and lose the relationship we’ll need on the next ten jobs when their best crews go to someone else first. We delay an honest conversation with a struggling employee because it’s uncomfortable, and a fixable issue becomes a resignation or a culture problem months later. We promote someone into leadership because they are the best individual performer, without asking whether they can develop others. We fill a seat today while leaving ourselves short a real leader three years from now. In each case, the first order move felt efficient. The real cost showed up later in trust we cannot easily rebuild and turnover we did not have to create.

Building this discipline does not require you to be psychic. It requires a habit: before committing to a decision, ask “and then what?” at least twice. What is the immediate result? What does that cause to happen next? And after that? This applies whether we are pricing a bid, negotiating a change order, managing a trade partner, or deciding who leads the next project. The goal is not certainty, but a clearer map of where a decision is likely to lead, so we choose with our eyes open instead of reacting to whatever feels most urgent today.

As leaders in this organization, our job is not only to solve the problem in front of us (not just construction related), but to anticipate the problem our solution might create, and plan for it before it arrives. The leaders who consistently ask “and then what?” are the ones who protect our margins, our client and trade partner relationships, and our people, not just for the next milestone, but for the next several years. That is the difference between managing a project and leading a company.