Second-order Thinking - Mental Model

Second-order thinking is presented as a way to make better decisions by looking past the immediate result and considering what happens next. The author uses the change from Rails Meeting to Backend Meetings as an example of a decision that worked at first but created longer-term problems.

The page suggests pausing before acting, checking whether a decision is reversible, asking “And then what?” several times, and using the 10-10-10 rule to compare consequences over different time spans. It closes by saying the goal is to think about long-term impact rather than only immediate outcomes.

Reading notes

#

• Engineering managers are paid to make good decisions, and second-order thinking helped the author with that.
• The Rails Meeting became Backend Meetings, which solved the short-term problem of finding speakers.
• After a few months, the new format was harder to maintain, and the team lost a place for its own announcements.
• Second-order thinking means considering more than one immediate result of a decision.
• The author warns that rushing into action can prevent proper analysis.
• A useful check is to ask whether a decision is reversible; reversible choices can be made quickly, while difficult reversals need more time.
• Repeating “And then what?” can uncover first-, second-, and third-level consequences.
• The 10-10-10 rule asks what the consequences will be in 10 minutes, 10 months, and 10 years.
• The page says this time-based approach helps with short-term negative consequences.
• Rails Meeting was revived 22 months later, and the author says cancelling it was a mistake because the long-term consequences were not considered.
• The main point is to pause before deciding and think about long-term impact.