<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>João Russio</title>
    <link>https://russios-blog.pages.dev/en/tags/mental-models/</link>
    <description>Writing by João Russio about software, AI, leadership, business, and life outside work.</description>
    <language>en-US</language>
    <atom:link href="https://russios-blog.pages.dev/en/tags/mental-models/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>How I use mental models to make better decisions</title>
      <link>https://russios-blog.pages.dev/en/posts/mental-models/</link>
      <pubDate>Thu, 09 Apr 2026 10:00:00 -0300</pubDate>
      <guid isPermaLink="true">https://russios-blog.pages.dev/en/posts/mental-models/</guid>
      <description>&lt;p&gt;For a while, my first response to a problem was to work harder. With simple problems, that sometimes worked. When a decision involved many variables, I would spend energy before properly understanding the problem.&lt;/p&gt;
&lt;p&gt;When I became a father and a manager, those decisions carried more weight. More people were affected by what I decided. That was when I started looking for a better way to think before acting.&lt;/p&gt;
&lt;h2 id=&#34;what-mental-models-are&#34;&gt;What mental models are&lt;/h2&gt;
&lt;p&gt;A mental model is a simplified way of understanding part of reality. Since we cannot consider every variable at once, we use models to organize information and make decisions.&lt;/p&gt;
&lt;p&gt;Inversion helps me imagine how a plan could go wrong. First principles make me examine rules I accepted without asking why. Incentives help explain behavior; systems thinking helps me see effects that only emerge later.&lt;/p&gt;
&lt;p&gt;Each model explains part of the situation. Using more than one makes me less likely to force a problem into my first interpretation of it.&lt;/p&gt;
&lt;h2 id=&#34;how-i-found-the-subject&#34;&gt;How I found the subject&lt;/h2&gt;
&lt;p&gt;I came across the concept in 2022, in a talk by Charlie Munger. The idea that stayed with me was simple: when we have few frames of reference, we try to fit every problem to the tools we already know.&lt;/p&gt;
&lt;p&gt;I then looked into Farnam Street’s material and Shane Parrish’s book &lt;em&gt;Pensamento eficaz&lt;/em&gt;. I found ways to examine assumptions, observe incentives, and think through the consequences before making a decision.&lt;/p&gt;
&lt;p&gt;Two quotes from Munger capture this well:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;ldquo;You&amp;rsquo;ve got to have multiple models, because if you have just one or two, you&amp;rsquo;ll torture reality until it fits your models.&amp;rdquo;&lt;/p&gt;&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;ldquo;I don&amp;rsquo;t think you can get worldly wisdom without 80 or 90 important models in your head.&amp;rdquo;&lt;/p&gt;&lt;/blockquote&gt;
&lt;h2 id=&#34;start-with-what-could-go-wrong&#34;&gt;Start with what could go wrong&lt;/h2&gt;
&lt;p&gt;Inversion means looking at the outcome I want to avoid before putting a plan together. Alongside thinking about how to reach the goal, I ask:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;What could make this plan fail?&lt;/li&gt;
&lt;li&gt;What assumption am I taking for granted?&lt;/li&gt;
&lt;li&gt;What cost or constraint have I left out?&lt;/li&gt;
&lt;li&gt;What decision would make the situation worse?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Doing this before implementation often reveals risks I would otherwise have discovered too late.&lt;/p&gt;
&lt;h3 id=&#34;an-example-from-work&#34;&gt;An example from work&lt;/h3&gt;
&lt;p&gt;A client kept data in several spreadsheets and wanted to automate the creation of dashboards for their own customers.&lt;/p&gt;
&lt;p&gt;Our first solution was to consolidate the files with Python, clean the data, and connect everything to Power BI. Before implementing it, I listed what might get in the way:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The spreadsheets had an unstable structure.&lt;/li&gt;
&lt;li&gt;Columns, formats, and file paths changed frequently.&lt;/li&gt;
&lt;li&gt;The dashboards could become too rigid.&lt;/li&gt;
&lt;li&gt;Each change might require work from the consultancy.&lt;/li&gt;
&lt;li&gt;The volume of data would keep growing.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;That list changed the conversation about the architecture. We began looking for a solution that would let the client create charts and expand its use without calling the consultancy for every change.&lt;/p&gt;
&lt;p&gt;The result was a system less dependent on the original spreadsheets and greater independence for the client. Examining the first proposal before writing code made a difference.&lt;/p&gt;
&lt;h2 id=&#34;ask-why-the-rule-exists&#34;&gt;Ask why the rule exists&lt;/h2&gt;
&lt;p&gt;First principles help break a problem down and examine the rules already in place. I usually start with these questions:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Why does this rule exist?&lt;/li&gt;
&lt;li&gt;What problem did it solve?&lt;/li&gt;
&lt;li&gt;Are the circumstances that led to it still the same?&lt;/li&gt;
&lt;li&gt;What is a technical constraint, and what is a process choice?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This is useful when a team keeps an old process without revisiting the reason for it. Sometimes the rule still makes sense. Sometimes the circumstances have changed and nobody has gone back to look.&lt;/p&gt;
&lt;h2 id=&#34;how-i-use-this-today&#34;&gt;How I use this today&lt;/h2&gt;
&lt;p&gt;In management, I use these models to assess priorities, incentives, bottlenecks, and operational risks. They also help me notice when a quick decision is merely pushing a problem into the future.&lt;/p&gt;
&lt;p&gt;Outside work, I use the same questions to examine my reactions, expectations, and personal decisions. The method has limits: it makes my assumptions clearer, but I still make bad decisions.&lt;/p&gt;
&lt;p&gt;What changed was the habit of revisiting the first solution. I now look for foreseeable risks and question rules that have lost their purpose more often. When I make a mistake, I have clearer criteria for understanding what happened and reconsidering the decision.&lt;/p&gt;
&lt;h2 id=&#34;references&#34;&gt;References&lt;/h2&gt;
&lt;p&gt;Books (links to the editions referenced in the original post):&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;a href=&#34;https://www.amazon.com.br/sabedoria-Charlie-Munger-Peter-Kaufman-ebook/dp/B0DTZ1JCD2&#34;&gt;&lt;em&gt;A sabedoria de Charlie Munger&lt;/em&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.amazon.com.br/Pensamento-eficaz-transformar-cotidianas-extraordin%C3%A1rios/dp/8539008122&#34;&gt;&lt;em&gt;Pensamento eficaz&lt;/em&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.amazon.com.br/Great-Mental-Models-Boxed-Set/dp/B0F5V7NJ78/&#34;&gt;&lt;em&gt;Os grandes modelos mentais&lt;/em&gt;&lt;/a&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Blog:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;a href=&#34;https://fs.blog/&#34;&gt;Farnam Street&lt;/a&gt;&lt;/li&gt;
&lt;/ol&gt;</description>
    </item>
    
  </channel>
</rss>
