<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[The Judgment Relay]]></title><description><![CDATA[Better judgment, passed on weekly: how owners of small founder-led businesses make sound calls under pressure.]]></description><link>https://judgmentrelay.com</link><image><url>https://substackcdn.com/image/fetch/$s_!LR6J!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F83591132-335b-456b-a47b-2a7df6b56a6f_512x512.png</url><title>The Judgment Relay</title><link>https://judgmentrelay.com</link></image><generator>Substack</generator><lastBuildDate>Mon, 16 Nov 2026 06:19:54 GMT</lastBuildDate><atom:link href="https://judgmentrelay.com/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[Liahtman LLC]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[judgmentrelay@substack.com]]></webMaster><itunes:owner><itunes:email><![CDATA[judgmentrelay@substack.com]]></itunes:email><itunes:name><![CDATA[Nolan Saye]]></itunes:name></itunes:owner><itunes:author><![CDATA[Nolan Saye]]></itunes:author><googleplay:owner><![CDATA[judgmentrelay@substack.com]]></googleplay:owner><googleplay:email><![CDATA[judgmentrelay@substack.com]]></googleplay:email><googleplay:author><![CDATA[Nolan Saye]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[Find the Person Who Will Argue With You]]></title><description><![CDATA[Most owners don&#8217;t lack advice. They lack one honest no.]]></description><link>https://judgmentrelay.com/p/find-the-person-who-will-argue-with</link><guid isPermaLink="false">https://judgmentrelay.com/p/find-the-person-who-will-argue-with</guid><dc:creator><![CDATA[Nolan Saye]]></dc:creator><pubDate>Sat, 14 Nov 2026 14:03:11 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/7dcee56f-822a-4a4d-85cf-49194e3c4614_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Most owners I know have more advice than they can use. Podcasts, peers, a mentor, the accountant, a group chat of other founders. What most of them lack is something narrower: one person who will tell them, before a big decision, that it&#8217;s a bad idea.</p><p>This week&#8217;s two pieces both depended on that person. Tuesday&#8217;s rule needed someone to argue against a quick yes. Thursday&#8217;s premortem needed someone who will live with the result. Here is how to find them.</p><h2>Why it&#8217;s hard in a small business</h2><p>In a company of eight, the people closest to a decision usually depend on you. They report to you, or their job depends on the business going well. Disagreeing with the owner has a cost for them, even when you ask for it. Peers outside the business have the opposite problem: they&#8217;re free to disagree, but they don&#8217;t know enough to be useful.</p><p>So the person you want sits between the two: close enough to know the business, safe enough to say no.</p><h2>Three places to look</h2><p>A partner or co-owner, if you have one. They already carry the risk with you.</p><p>The person who handles the money: your bookkeeper, accountant or finance lead. They see the numbers without the story you tell about them.</p><p>A former employee who left on good terms. They know how the business really works, and they no longer need anything from you.</p><h2>How to ask</h2><p>Be specific, and make no the easy answer. &#8220;I&#8217;m about to sign a five-year lease. I want you to make the best case against it. You won&#8217;t change my mind by being polite.&#8221; Then listen without defending. Thank them for the strongest point, even if you go ahead anyway.</p><p>Do it once and they&#8217;ll believe you meant it. Do it three times and you&#8217;ll have one of the most valuable advisers an owner can have: someone who knows they&#8217;re allowed to say no.</p><h2>This weekend</h2><p>Write down the name of the person you would ask. If you can&#8217;t think of one, that&#8217;s the finding, and it&#8217;s the first thing to fix before your next locked decision.</p><p>Who is that person for you? Hit reply and tell me.</p><p>&#8212; Nolan</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://judgmentrelay.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">The Judgment Relay is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[The Heroics-to-System Ledger]]></title><description><![CDATA[A record to identify opportunities for preventive change]]></description><link>https://judgmentrelay.com/p/the-heroics-to-system-ledger</link><guid isPermaLink="false">https://judgmentrelay.com/p/the-heroics-to-system-ledger</guid><dc:creator><![CDATA[Flamer]]></dc:creator><pubDate>Thu, 12 Nov 2026 14:03:44 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/0bc7a26c-f60b-4d3a-af8e-4f034beaa8da_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>A rescue story tells you who stayed late and how they saved the day. The Heroics-to-System Ledger examines what led to the emergency, what harm the rescue prevented and whether anything could change to prevent a recurrence without weakening the emergency response.</p>
      <p>
          <a href="https://judgmentrelay.com/p/the-heroics-to-system-ledger">
              Read more
          </a>
      </p>
   ]]></content:encoded></item><item><title><![CDATA[The Locked-Decision Premortem]]></title><description><![CDATA[A thirty-minute method for finding out how a big commitment fails before you sign.]]></description><link>https://judgmentrelay.com/p/the-locked-decision-premortem</link><guid isPermaLink="false">https://judgmentrelay.com/p/the-locked-decision-premortem</guid><dc:creator><![CDATA[Nolan Saye]]></dc:creator><pubDate>Thu, 12 Nov 2026 14:03:40 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/71e2a5b1-20df-499e-bfb2-f6bd7eab94f8_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Tuesday&#8217;s rule was simple: no same-day yes on anything that locks. This piece is for the locked decisions you can see coming: the lease renewal, the senior hire, the partnership, the loan. For those, a day&#8217;s pause is not enough. You need to find out how the decision fails while you can still change it.</p><p>The method is a premortem, an idea from the psychologist Gary Klein. Instead of asking &#8220;what could go wrong?&#8221;, which invites polite reassurance, you assume the decision has already failed and ask why. People who would never criticize a plan in a meeting will readily explain a failure that has already happened.</p><p>Here is the version I use for a small business, with one or two people, in thirty minutes.</p>
      <p>
          <a href="https://judgmentrelay.com/p/the-locked-decision-premortem">
              Read more
          </a>
      </p>
   ]]></content:encoded></item><item><title><![CDATA[Why Locked Decisions Slip Through Fast]]></title><description><![CDATA[The calls you can&#8217;t undo rarely look big when they arrive.]]></description><link>https://judgmentrelay.com/p/why-locked-decisions-slip-through</link><guid isPermaLink="false">https://judgmentrelay.com/p/why-locked-decisions-slip-through</guid><dc:creator><![CDATA[Nolan Saye]]></dc:creator><pubDate>Tue, 10 Nov 2026 14:01:53 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/15f34795-b22f-4846-80af-4cf844da1563_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Last Tuesday sorted decisions into two kinds: doors you can walk back through, and doors that lock behind you. Most readers found the sorting easy. The hard part is that locked decisions rarely arrive looking locked.</p><h2>How a locked decision arrives</h2><p>It comes as a favor. A supplier offers a better rate if you sign for three years. A landlord holds the unit for you until Friday. A strong candidate needs an answer by Monday because another firm has made an offer. A client asks for exclusivity, politely, in the last paragraph of an email you are answering between meetings.</p><p>None of these feels like a big decision. Each one feels like a small yes that keeps things moving. That is the trap: the decision is locked, but the moment is fast, and owners match their speed to the moment instead of to the decision.</p><h2>What makes a yes hard to undo</h2><p>Look at what those offers have in common. Each one touches at least one of three things.</p><p>Time. The commitment runs longer than your current plan does. A three-year contract outlives most small-business plans.</p><p>Other people. Someone else starts relying on your yes. The new hire resigns from their old job. The client tells their board.</p><p>Money that moves first. A deposit, a fit-out, a signing bonus. Once it is spent, the sunk-cost fallacy starts arguing for you to stay.</p><p>If an offer touches any one of these, treat it as locked, however casually it was made.</p><h2>A rule that costs one day</h2><p>The fix is not more analysis. It is a pause with two parts.</p><p>First, no same-day yes on anything that touches time, other people or money that moves first. Say: &#8220;That sounds good. I&#8217;ll confirm by tomorrow afternoon.&#8221; Almost every legitimate offer survives a day. One that doesn&#8217;t is telling you something.</p><p>Second, before you confirm, ask one person to argue against it. Not to vote, just to make the best case for no. If you have a business partner, use them. If you don&#8217;t, use the person who would carry the most if it went wrong: your operations lead, your bookkeeper, sometimes your spouse.</p><p>You will still say yes to most of these offers. The point is that you say it as a decision, not as a reflex.</p><h2>When the deadline is real</h2><p>Sometimes the other side really can&#8217;t wait. The candidate has another offer; the unit will go to someone else. Then the question changes: is losing this option worse than locking in without the check? Sometimes it is, and you should move. Write down why, in one line, so that in six months you can see whether the urgency was real.</p><h2>This week</h2><p>Look back over the last three months. Find one commitment you made in under a day that you could not now undo cheaply. Ask which of the three it touched, and whether a day&#8217;s pause would have changed anything. That one example will teach you more than the rule.</p><p>Thursday&#8217;s paid piece gives you a thirty-minute method for the locked decisions you can see coming.</p><p>What&#8217;s a quick yes you&#8217;d take back if you could? Hit reply and tell me.</p><p>&#8212; Nolan</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://judgmentrelay.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">The Judgment Relay is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[Heroic Work: Your Business May Be Rewarding the Wrong Kind of Heroism]]></title><description><![CDATA[The studio celebrates the hero without changing the process that made it necessary.]]></description><link>https://judgmentrelay.com/p/heroic-work-your-business-may-be</link><guid isPermaLink="false">https://judgmentrelay.com/p/heroic-work-your-business-may-be</guid><dc:creator><![CDATA[Flamer]]></dc:creator><pubDate>Tue, 10 Nov 2026 14:01:18 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/c5766d72-55d6-453c-bcd3-39c0ffd19c4a_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Imagine a fit-out practice where a restaurant&#8217;s joinery specification changes after the latest drawing set has been issued. The change reaches the site team, but the contractor somehow starts work from the old version. By the time Daniel catches the mismatch, the client has already arranged an inspection, and so a replacement drawing must reach the site overnight. The founder, Mara takes the drawing home, works until two in the morning to make the changes, and sends the file before dawn. The client receives the corrected drawings before breakfast. She has protected a real promise to the client and deserves thanks for that night. Everyone in the studio calls it a victory.</p><p>The problem becomes clear on Monday. The team discusses Mara&#8217;s impressive rescue without examining why an outdated drawing reached the site. Nobody identifies who was responsible for the revision register, the record of changes to the drawings. Nobody checks whether Daniel could have spotted the mismatch before the contractor saw it. The studio celebrates the hero without changing the process that made it necessary.</p><h2>What the rescue solves, and what remains</h2><p>A rescue has two outcomes. The immediate outcome is whether harm was contained. Was the client protected? Was the safety risk addressed? Was the deadline met? Those results matter. The second outcome is that the business needs to establish whether the conditions that caused the incident have changed. A rescue can fully protect the client while leaving the business exposed to the same failure happening again.</p><p>Repeated rescues can also become part of the firm&#8217;s reward system. People who interrupt ordinary work to save the day receive visible praise, while those who quietly prevent a crisis may receive none, because an incident that never happened offers no dramatic story to tell. Employees learn which work earns recognition, and the founder learns to associate being indispensable with leadership. Meanwhile, the process remains vulnerable to another emergency.</p><p>None of this makes an emergency an opportunity to demonstrate performance. Mara should not have let the contractor continue simply to demonstrate that the process was flawed. When people, property, contractual promises or a client&#8217;s critical deadline are at risk, the first task is to protect them through people who have the appropriate authority to act. Reviewing the incident afterward cannot replace urgent action.</p><p>Nor does every rescue reveal a poorly designed process. A storm can close a site, and a supplier can fail without warning. Some tasks genuinely require a qualified professional to intervene. Even a resilient company still needs people who can respond under pressure. The important distinction is whether a similar, foreseeable failure has happened before and whether anyone changes the conditions that made it likely.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://judgmentrelay.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://judgmentrelay.com/subscribe?"><span>Subscribe now</span></a></p><h2>Look beyond the late nights</h2><p>Start with the last few rescues, rather than counting how often people worked late. For each incident, record what first made the rescue necessary, where the problem could have been detected earlier and what the rescuer actually did. Also note whether the rescue involved a decision that had to be made by a person or role with specific authority. Then check whether the cause had appeared before. A one-off storm and the third use of an outdated drawing should not be treated as equivalent examples of heroism.</p><p>The appropriate response might be to update the register of issued drawings, clarify a handoff, or establish a way to report bad news before a deadline becomes impossible to meet. In some cases, there may also have been no reasonable way to prevent the incident. Recognizing that limit helps the company avoid introducing controls that cost more than the risks they address.</p><p>Prevention is harder to assess when someone receives no credit for preventing an incident. Suppose Priya notices a revision mismatch on Tuesday and asks the team to hold back the drawing set until the mismatch has been checked. A project manager may later remember Priya as the person who delayed the drawings, while remembering Mara&#8217;s overnight rescue as the act that protected the deadline. Neither description tells the whole story. Priya&#8217;s intervention may have been more valuable than Mara&#8217;s rescue, or it may have been excessive caution. The studio needs evidence to distinguish those possibilities.</p><p>A proper incident review should therefore record both <strong>what the rescue achieved</strong> and <strong>what it consumed</strong>. Record the hours diverted from other work, any risk introduced by a rushed repair, the dependence on one person, and the changes actually made afterward. Fatigue is only part of the cost. If every important exception waits for the company&#8217;s most skilled rescuer, the next crisis may arrive while that person is absent. The business then depends on the rescuer&#8217;s availability, rather than a defined process that people are authorized to carry out.</p><p>The question for the Monday meeting is not whether Mara deserves praise. She does. It is whether the studio can also explain what it will do differently <strong>before</strong> the next emergency, now while nobody is standing at a drawing board after midnight.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://judgmentrelay.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">The Judgment Relay is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[Start Here]]></title><description><![CDATA[What The Judgment Relay is, who it&#8217;s for, and where to begin.]]></description><link>https://judgmentrelay.com/p/start-here</link><guid isPermaLink="false">https://judgmentrelay.com/p/start-here</guid><dc:creator><![CDATA[Nolan Saye]]></dc:creator><pubDate>Sun, 08 Nov 2026 14:00:59 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/4528bc78-4c36-4070-b886-b325546651fb_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>The Judgment Relay is a weekly publication for owners of small founder-led businesses (roughly 2&#8211;25 people) on making sound calls under pressure.</p><p>The record of how small-business owners actually made hard calls, and what happened after.</p><p>Most of what happens in a small business comes down to a handful of decisions: who to hire, what to stop, what to commit to, when to wait. Nobody hands you a method for those, and there is rarely anyone to hand the decision to. This publication works through them one at a time, in plain language, so your next hard call is a better one.</p><h2>How it works</h2><ol><li><p>Tuesday: a free piece that takes one decision problem and works it through.</p></li><li><p>Thursday: a deeper piece for paid subscribers that walks through one decision method in full.</p></li><li><p>Saturday: a free piece that puts the idea to work in a real situation.</p></li></ol><h2>Where to begin</h2><p>If you read three pieces, read these, in order.</p><ol><li><p><a href="https://judgmentrelay.substack.com/p/the-first-question-to-ask-about-any">The First Question to Ask About Any Decision</a>: sort the decision before you weigh the options.</p></li><li><p><a href="https://judgmentrelay.substack.com/p/the-one-page-decision-record">The One-Page Decision Record</a>: write the decision down so you can learn from it either way.</p></li><li><p><a href="https://judgmentrelay.substack.com/p/decide-when-to-quit-before-you-start">Decide When to Quit Before You Start</a>: set the stop line while you are still calm.</p></li></ol><h2>The Founder Trap (series)</h2><p>The Founder Trap is when the founder becomes the bottleneck: someone has what they need to finish the work, including the authority to decide, but still has to wait for the founder&#8217;s attention.</p><p>Read it in order: <a href="https://judgmentrelay.substack.com/p/the-founder-trap-i">Part I</a> &#183; <a href="https://judgmentrelay.substack.com/p/the-founder-trap-ii-the-decision">Part II</a> (members) &#183; <a href="https://judgmentrelay.substack.com/p/the-founder-trap-iii-when-being-needed">Part III</a></p><h2>What Relay members believe</h2><ol><li><p>A sound call made on time beats a perfect call made late.</p></li><li><p>Every decision has a cost; name it before you make it.</p></li><li><p>Owners decide better when they say the decision out loud to peers who don&#8217;t compete with them.</p></li><li><p>Review the call, not the person.</p></li><li><p>What&#8217;s said in confidence stays in confidence.</p></li></ol><p>Against: deciding alone, by default, under pressure.</p><h2>Who writes it</h2><p>I&#8217;m Nolan Saye, the pen name of a founder who runs a small company and a team across two countries. I write from the decisions that work involves.</p><p>Hit reply to any email and tell me the decision on your desk. I read every one.</p><p>&#8212; Nolan</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://judgmentrelay.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">The Judgment Relay is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[The Founder Trap III: When Being Needed Starts Hurting the Business]]></title><description><![CDATA[Each rescue reinforces the habit that made it necessary.]]></description><link>https://judgmentrelay.com/p/the-founder-trap-iii-when-being-needed</link><guid isPermaLink="false">https://judgmentrelay.com/p/the-founder-trap-iii-when-being-needed</guid><dc:creator><![CDATA[Flamer]]></dc:creator><pubDate>Sat, 07 Nov 2026 14:02:21 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/2843acb2-a78c-4826-84b6-2aa8127ebe8c_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>At four on Friday, Daniel has had three answers from Mara and just as many reasons to ask her again next week. In this hypothetical studio, Mara has spent the afternoon answering questions that had accumulated during a client visit. Could a supplier replace a standard fitting? Did a draft email sound right? Could a small delivery be booked a day earlier? She answered each question quickly. Everyone thanked her, and the jobs moved forward. On the office board, the afternoon&#8217;s delays appeared to have been resolved.</p><p>Daniel knew what that recovery had cost. He had understood the fitting issue well enough to recommend the same part Mara approved. He had written the email twice: first in his own words, then in what he guessed would be hers. The supplier&#8217;s available delivery dates were already open on his screen. He did not need more time or enthusiasm. What he needed was confidence that Mara would respect his authority to make those decisions after she reviewed them.</p><h2>What a quick answer leaves unresolved</h2><p>A founder&#8217;s responsiveness can get work moving while leaving the business dependent on the same approval next time. Each rescue reinforces the habit that made it necessary. Being needed begins to hurt the business when answering today&#8217;s questions leaves employees with the same reasons to ask again tomorrow.</p><p>There is a fair objection: Mara may have caught something Daniel missed. If the replacement fitting had breached the client&#8217;s accepted specification, stopping the order would have protected the work. Counting messages cannot tell Mara which approvals are unnecessary. Nor does Daniel&#8217;s confidence that he can predict her answer establish that he has authority to decide.</p><p>In a possible scenario, Mara makes no public announcement about delegation. Instead, she asks Daniel to show her the three questions as they stood before she replied. Together, they examine the standard each decision had to meet, any authority Daniel lacked, and any commitment that had to be honored. The &#8216;finish&#8217; requirement turns out to be in an old email rather than in the current drawing pack. The draft email was factually correct; Mara&#8217;s revision was merely concerned with its tone. The delivery request stays with Mara because a specific client agreement names who may confirm handover dates.</p><p>No decision-making authority has changed hands. The change is more modest: their next discussion will start with what the decision requires, rather than whether Mara is available.</p><p>In another version of the story, Mara&#8217;s approval was necessary. Suppose the supplier order required a client approval Daniel had not seen, and Mara caught the omission when she replied. Her intervention would then have protected a promise to the client. The appropriate lesson from this would then be to give Daniel access to the approved specification or retain the required approval, rather than treat the order as a routine decision. </p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://judgmentrelay.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://judgmentrelay.com/subscribe?"><span>Subscribe now</span></a></p><h2>When approval protects a real obligation</h2><p>Both versions look like a busy founder saving a stalled afternoon. Understanding the difference requires examining the information and obligations behind the original request. Nobody in the studio can establish whether approval was necessary simply by how relieved they feel at five o&#8217;clock. They will need to examine the original request, the rule that applied and the consequence of acting without approval. Reviewing those records is less satisfying than clearing a full inbox, but it can change next week&#8217;s work.</p><p>Daniel goes home having completed the week&#8217;s work, and Mara goes home having answered everything. Both have been productive, but neither yet has evidence that Monday will be different. True change begins by examining that gap: the difference between clearing a queue and changing why the queue exists.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://judgmentrelay.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">The Judgment Relay is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p></p>]]></content:encoded></item><item><title><![CDATA[Decide When to Quit Before You Start]]></title><description><![CDATA[The kindest thing you can do for your future self is set the exit conditions now.]]></description><link>https://judgmentrelay.com/p/decide-when-to-quit-before-you-start</link><guid isPermaLink="false">https://judgmentrelay.com/p/decide-when-to-quit-before-you-start</guid><dc:creator><![CDATA[Nolan Saye]]></dc:creator><pubDate>Sat, 07 Nov 2026 14:00:34 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/fd09beeb-067a-4846-896d-757f89b752bf_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Starting things is easy. Stopping them is where judgment goes to die.</p><p>A project that isn&#8217;t working rarely announces itself. It drifts. The numbers are a little short, but there&#8217;s a reason. The timeline slips, but the next month looks better. Every week you&#8217;ve put in becomes another reason to put in one more, because walking away would mean admitting those weeks were spent on something that didn&#8217;t work.</p><p>By the time the evidence is undeniable, you&#8217;ve spent far more than the thing was ever worth.</p><p>There is a simple defense, and it costs about ten minutes: decide your exit conditions before you begin.</p><p>Annie Duke calls these kill criteria in her book Quit: a state you can observe and a date by which you will check it. Here is how to write them for a small business.</p><h2>Why we can&#8217;t quit well in the moment</h2><p>When you&#8217;re inside a project, three forces push you to continue.</p><p>You&#8217;ve already invested, and abandoning it feels like losing that investment, even though it&#8217;s gone either way.</p><p>You&#8217;ve told people about it, and stopping feels like a public failure.</p><p>You can always imagine the version where it turns around, and that version is vivid while the slow decline is not.</p><p>None of these forces care whether continuing is a good idea. They operate regardless. Which is why the decision about when to stop shouldn&#8217;t be made by the person in the middle of the project. It should be made by the calmer person at the start.</p><h2>How to set exit conditions</h2><p>Before you commit to anything substantial, such as a new offer, a hire, a partnership or a side project, write down three things.</p><p>What success looks like, and by when. One or two concrete measures with a date. Not &#8220;growing,&#8221; but &#8220;twenty paying customers by the end of March.&#8221;</p><p>The point at which you&#8217;ll stop. A specific threshold, written as a sentence you can&#8217;t argue with later. &#8220;If we have fewer than eight paying customers by the end of March, I stop and move the time elsewhere.&#8221;</p><p>What you&#8217;ll do with the freed-up resources. This matters more than it looks. Quitting is much easier when you know exactly where the time and money will go next.</p><p>Then put the date in your calendar.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://judgmentrelay.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://judgmentrelay.com/subscribe?"><span>Subscribe now</span></a></p><h2>The middle zone</h2><p>Most outcomes land between success and the stop line. Fewer customers than hoped, more than the minimum. This is where honest judgment matters most, and where it&#8217;s easiest to fool yourself.</p><p>Set a rule for this zone too. A good default: if you&#8217;re in the middle at the checkpoint, you get one extension, of a fixed length, with one specific change. Not &#8220;keep going and see.&#8221; Something like: &#8220;Six more weeks, with a different price, then the same test.&#8221;</p><p>One extension. Not two. The second extension is where most slow failures live.</p><h2>Tell someone</h2><p>Exit conditions are much stronger when someone else knows them. Not to hold you to account in a punishing way, but so there&#8217;s one person who&#8217;ll ask, gently, &#8220;It&#8217;s the end of March. Where did you land?&#8221;</p><p>That question, asked by someone outside your head, cuts through most of the stories you&#8217;d otherwise tell yourself.</p><h2>This weekend</h2><p>Look at what you&#8217;re currently working on. Pick the one thing you started without clear exit conditions. Write the three sentences now: success, the stop line, and where the resources go. Put the checkpoint in your calendar.</p><p>You might find it&#8217;s already past the line. That&#8217;s useful too.</p><p>What&#8217;s the one project you&#8217;d write a stop line for today? Hit reply and tell me. I read every one.</p><p>Also from Nolan Saye, in Flame Spiral: <a href="https://flamespiral.substack.com/p/when-a-project-deserves-to-die">When a Project Deserves to Die</a>, the same question for creative work: ending a project on purpose instead of letting it drift.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://judgmentrelay.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">The Judgment Relay is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>&#8212; Nolan</p>]]></content:encoded></item><item><title><![CDATA[The Founder Trap II: The Decision Queue Audit]]></title><description><![CDATA[It is easy to complain about a delayed decision, yet surprisingly difficult to describe what happened]]></description><link>https://judgmentrelay.com/p/the-founder-trap-ii-the-decision</link><guid isPermaLink="false">https://judgmentrelay.com/p/the-founder-trap-ii-the-decision</guid><dc:creator><![CDATA[Flamer]]></dc:creator><pubDate>Thu, 05 Nov 2026 14:01:27 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/2fe1ec01-e7b1-48b4-a3be-6113e76f82a0_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>It is easy to complain about a delayed decision, yet surprisingly difficult to describe what happened. Was the decision actually late, or did someone lack the permission, information or skill to make it? Was the founder protecting a binding obligation? This week&#8217;s <strong>Decision Queue Audit</strong> gives you a short record for what happened so you can distinguish these causes before changing anyone&#8217;s role.</p><h2>Build the record</h2><p>Use this audit on <strong>ten recent requests that waited for approval</strong>. Take the requests in order, rather than selecting the ones that seem most unnecessary. A founder or operations lead can assemble the facts with the people who made the requests. If the audit points to moving a decision, the person who holds that authority today signs off on the change.  </p>
      <p>
          <a href="https://judgmentrelay.com/p/the-founder-trap-ii-the-decision">
              Read more
          </a>
      </p>
   ]]></content:encoded></item><item><title><![CDATA[The One-Page Decision Record]]></title><description><![CDATA[A simple method for learning from your calls, whether they work out or not.]]></description><link>https://judgmentrelay.com/p/the-one-page-decision-record</link><guid isPermaLink="false">https://judgmentrelay.com/p/the-one-page-decision-record</guid><dc:creator><![CDATA[Nolan Saye]]></dc:creator><pubDate>Thu, 05 Nov 2026 14:00:55 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/243468a8-14e2-4a8b-93f8-761486952488_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Here is an uncomfortable fact about experience: it doesn&#8217;t automatically make your judgment better. It makes you more confident. Whether it makes you more accurate depends on whether you can see, clearly and honestly, what you were thinking when you made your past decisions.</p><p>Most of us can&#8217;t. Memory rewrites the reasoning to fit the outcome. A call that worked out becomes, in hindsight, obviously right. A call that failed becomes a case of bad luck, or of someone else&#8217;s mistake. Either way, the lesson is lost.</p><p>The fix is unglamorous. Write the decision down before you know how it turns out.</p><p>This piece gives you the exact one-page format I recommend, how to fill it in quickly, and how to review it so it actually changes how you decide.</p><h2>Why outcomes are a poor teacher</h2><p>A good decision can produce a bad result, and a bad decision can get lucky. If you judge your past calls only by how they turned out, you&#8217;ll reward recklessness that happened to work and punish careful thinking that met bad luck.</p><p>The poker player and author Annie Duke calls this mistake &#8220;resulting&#8221;: judging the quality of a decision by the quality of its outcome.</p><p>What you want to judge is the quality of the reasoning given what you knew at the time. You can only do that if you captured what you knew at the time. Hence the record.</p><h2>The format</h2><p>Keep it to one page. If it takes longer than fifteen minutes to fill in, it won&#8217;t survive past the second week. Use these seven headings, in this order.</p><h3>The decision</h3><p>One sentence. Not the topic, the actual choice. &#8220;Hire a part-time operations assistant at 20 hours a week,&#8221; not &#8220;operations help.&#8221;</p><h3>Type</h3><p>Reversible or locked, using Tuesday&#8217;s test. This tells you how much of the rest to fill in. A reversible call might only need the decision, the options and your expectations.</p><h3>What I know, and what I&#8217;m assuming</h3><p>Two short lists. Facts you&#8217;d stake money on, and things you&#8217;re treating as true but haven&#8217;t checked. The second list is where most decisions go wrong, so be honest about it.</p><h3>Options I considered</h3><p>At least three, including &#8220;do nothing&#8221; and one you&#8217;d normally dismiss. If you only had one option, you didn&#8217;t make a decision. You made an announcement.</p><h3>Why this one</h3><p>The two or three reasons that actually tipped it. Not every reason, just the ones that carried weight.</p><h3>What I expect to happen, and by when</h3><p>Concrete and checkable. &#8220;Within eight weeks, I&#8217;ll have five more hours a week for client work.&#8221; Add how confident you are, as a rough percentage. You&#8217;ll be surprised how revealing that number becomes over time.</p><h3>What would tell me I was wrong</h3><p>The signal you&#8217;ll watch for. Write it now, while you&#8217;re calm, so you can&#8217;t quietly move the goalposts later.</p><h2>Filling it in fast</h2><p>You don&#8217;t need to be eloquent. Bullet points are fine. The aim is not a document anyone else reads. It&#8217;s an honest snapshot of your own head on the day.</p><p>Three habits make it easier.</p><p>Write it at the moment of commitment, not before. Once you&#8217;ve decided but before you&#8217;ve told anyone, take the fifteen minutes. That&#8217;s when your reasoning is freshest and least edited.</p><p>Keep them all in one place. A single document or folder, newest first. Scattered records are records you&#8217;ll never look at again.</p><p>Date everything. The date is what lets you compare your expectations with what actually happened.</p><h2>The review: where the value is</h2><p>A record you never revisit is just a diary. The learning happens in the review.</p><p>Put a reminder in your calendar for the date you set under &#8220;What I expect.&#8221; When it arrives, open the record and answer three questions in a line or two each.</p><p>What actually happened, compared with what I expected?</p><p>Which of my assumptions turned out to be wrong?</p><p>If I faced the same decision tomorrow, with only what I knew then, would I decide the same way?</p><p>That last question is the important one. It separates the quality of the decision from the luck of the outcome. If the answer is yes, a bad result doesn&#8217;t mean you need to change your approach. If the answer is no, a good result doesn&#8217;t mean you got it right.</p><h2>What to look for over time</h2><p>After ten or fifteen records, patterns appear. They are usually more useful than any single lesson.</p><p>You might find your confidence numbers are consistently too high, which tells you to slow down on locked decisions. You might find the same assumption failing again and again, perhaps about how fast other people move, or how long things take. You might find you rarely consider the &#8220;do nothing&#8221; option, and that when you do, it&#8217;s often the best one.</p><p>None of this is visible from memory. All of it is visible on paper.</p><h2>Your assignment</h2><p>Take the decision you classified after Tuesday&#8217;s piece. Before the week ends, fill in a record for it, all seven headings, fifteen minutes, no more. Set the review reminder.</p><p>If you&#8217;d like a second pair of eyes, reply to this email with your record, or just the decision and your list of assumptions. I read every one, and with your permission I may use an instructive one, anonymized, in a future piece.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://judgmentrelay.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">The Judgment Relay is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>&#8212; Nolan</p>]]></content:encoded></item><item><title><![CDATA[The Founder Trap I]]></title><description><![CDATA[The founder who became the bottleneck]]></description><link>https://judgmentrelay.com/p/the-founder-trap-i</link><guid isPermaLink="false">https://judgmentrelay.com/p/the-founder-trap-i</guid><dc:creator><![CDATA[Flamer]]></dc:creator><pubDate>Tue, 03 Nov 2026 14:03:27 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/b62f9d90-4137-4c78-8a0c-0f36d856eb92_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Imagine a small fit-out studio led by Mara. On an ordinary afternoon, the founder leaves her desk for lunch. No crisis follows per se, yet a quotation stays unsent, a designer waits to order a material that was already approved, and a client receives a promise that someone will call back. The work has not become harder in the founder&#8217;s absence. The decisions have simply stopped moving. </p><p>Mara&#8217;s team is capable enough to prepare drawings, manage suppliers and speak to clients. Mara built the studio by making the hard calls herself, and she still wants to see the final version of anything that might bear her name. That history makes her useful, but it also makes her the safest place for other people to put uncertainty.</p><p>When Mara returns, her inbox gives her a flattering account of the day: everyone needed her. She answers quickly, and two things move. The third turns out to be a question Daniel could have settled using information already in the project file. Mara calls that an easy win. Daniel learns a different lesson: if he waits, he will receive an answer that cannot later be challenged as his own mistake.</p><h2>Where the delay actually comes from</h2><p>A busy founder or a crowded inbox does not, by itself, establish a founder bottleneck. The bottleneck appears when someone has what they need to finish the work, including the authority to decide, but still has to wait for the founder&#8217;s attention. Three quite different causes can create that dependence.</p><p>An <strong>approval habit</strong> sends a routine choice back to the founder even though the person making it has already agreed on the standard. </p><p>An <strong>information gap</strong> sends it back because the founder knows a client preference, cost or limitation that nobody else can find. </p><p>And a <strong>reserved decision</strong> needs the founder for a legitimate reason: law, professional qualification, contract, safety or a potential loss that the firm has deliberately kept at the founder level. These requests can look much the same in an inbox, although they call for different responses.</p><p>In the studio, Daniel could order standard hinges within an agreed project budget, but the supplier offered a different finish. If that substitute meets a written acceptance condition and the purchase falls within his actual authority, Mara&#8217;s approval may add nothing. On the other hand, if it changes a client&#8217;s agreed specification, Daniel may be right to stop. Either way the inconvenience of waiting is not evidence which one is true.</p><p>The team may also lack the training to judge substitutions, or may not have the current drawing or price list needed to make the decision, and taking Mara out of the process would not fix that. The first useful move is therefore to inspect what the decision required, not reprimand the person who escalated it.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://judgmentrelay.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://judgmentrelay.com/subscribe?"><span>Subscribe now</span></a></p><h2>A better question than &#8216;Why do they always ask me?&#8217;</h2><p>Take ten recent decisions that waited for you. For each one, write down what was being decided, what information was available, who held authority, what was at risk and why the wait occurred. A protected professional approval does not become waste simply because it took time. Neither does a request become evidence of incompetence because it arrived in your inbox.</p><p>The result may be uncomfortable. You might find that your team needs more training or that a genuine legal or client obligation accounts for the wait. You might also find that your own previous reversals have taught competent people to ask permission for decisions you told them to own.</p><p>Nothing in that inventory grants new authority. Instead, it gives the founder a more specific question worth answering: which single low-risk, reversible decision could move without me <strong>if</strong> its standard, information, limits and legitimate owner were made clear?</p><p>You could test this interpretation without withdrawing any approval. For one week, mark each incoming request when it arrives: did it concern a fact, a standard, a permission, or a risk? Then note whether the response required something only you could supply. </p><p>Recording requests as they arrive is more revealing than an end-of-week count because it retains the reason for each interruption. A request for a missing part number and a request to approve an irreversible contract change may both take two minutes, but they are not interchangeable.</p><p>The employee&#8217;s side of the evidence matters too. Ask what they believed would happen if they acted without checking. If the answer is &#8216;I would be corrected even if the outcome met the brief&#8217;, the firm may have created its own permission queue. If the answer is &#8216;I cannot see the signed specification&#8217;, then that points to a problem with document access. If the answer is &#8216;the contract names Mara&#8217;, the queue contains a real obligation. </p><p>All three findings must remain possible; your analysis should not force every request into an explanation that suits the founder&#8217;s plan to step away.</p><p>The aim is not to make the founder unavailable. It is to make availability stop being the operating system for ordinary work.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://judgmentrelay.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">The Judgment Relay is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p></p>]]></content:encoded></item><item><title><![CDATA[The First Question to Ask About Any Decision]]></title><description><![CDATA[Before you weigh the options, find out what kind of decision you&#8217;re holding.]]></description><link>https://judgmentrelay.com/p/the-first-question-to-ask-about-any-decision</link><guid isPermaLink="false">https://judgmentrelay.com/p/the-first-question-to-ask-about-any-decision</guid><dc:creator><![CDATA[Nolan Saye]]></dc:creator><pubDate>Tue, 03 Nov 2026 14:00:44 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/9b0f14b0-9e19-44ff-9df8-500e741366eb_1456x1048.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Most people start a hard decision by listing options. Pros on the left, cons on the right, a gut check at the end. It feels responsible. It is usually the wrong first move.</p><p>The first move is to classify the decision. Not every call deserves the same amount of thought, and the most common judgment failure isn&#8217;t choosing badly. It&#8217;s spending a week agonizing over something you could have undone on Friday, then rushing through something you can never take back.</p><p>So before anything else, ask one question: if this turns out to be wrong, how hard is it to reverse?</p><h2>Two kinds of decisions</h2><p>Some decisions are doors you can walk back through. You try a new pricing page, a new meeting rhythm, a new supplier on a small order. If it&#8217;s wrong, you notice, you step back, and the cost is a few days and some mild embarrassment.</p><p>Other decisions lock behind you. You sign a long lease. You hire a senior person. You take on a partner, a loan, a public commitment with your name on it. Getting out is possible, but it&#8217;s slow, expensive, and it damages things along the way.</p><p>Jeff Bezos made this distinction famous as one-way and two-way doors. What matters here is what it changes about how you decide.</p><p>These two kinds of decisions want opposite treatment.</p><p>Reversible decisions want speed. The information you need mostly comes from doing the thing, not from thinking about it longer. Every day you deliberate is a day you aren&#8217;t learning. The right posture is: decide quickly, watch closely, adjust.</p><p>Irreversible decisions want care. Here the cost of being wrong is paid once and paid in full, so the extra week of thinking is cheap by comparison. The right posture is: slow down, widen the options, find the person who disagrees with you and listen properly.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://judgmentrelay.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://judgmentrelay.com/subscribe?"><span>Subscribe now</span></a></p><h2>Where people go wrong</h2><p>The trouble is that we tend to treat every decision with the same intensity, and that intensity is set by how the decision feels rather than by what it is.</p><p>A reversible decision can feel enormous because it&#8217;s visible, or because someone you respect will see the result. So it gets a committee, three drafts and two weeks.</p><p>An irreversible decision can feel small because it arrives quietly. A friendly offer, a contract renewal, a &#8220;quick yes&#8221; on a call. So it gets thirty seconds.</p><p>If you take one habit from this piece, take this: name the type out loud before you start. &#8220;This one&#8217;s reversible, let&#8217;s move.&#8221; Or: &#8220;This one locks. We&#8217;re not deciding today.&#8221;</p><h2>A quick test</h2><p>When you&#8217;re not sure which kind you&#8217;re holding, ask three things.</p><p>What would it cost, in money and time, to undo this in three months?</p><p>Who else would be affected by the reversal, and would they forgive it?</p><p>What would I lose that I can&#8217;t get back, such as trust, reputation, or a window that closes?</p><p>If the answers are &#8220;not much, nobody important, nothing,&#8221; you have a reversible decision. Move.</p><p>If any answer makes you wince, treat it as irreversible, even if technically it isn&#8217;t. A decision you could undo but wouldn&#8217;t, because of what it would cost you socially, is a locked door in practice.</p><h2>The hidden third category</h2><p>There&#8217;s one more type worth knowing about: decisions that are reversible now but become irreversible if you wait.</p><p>A role you could still restructure before the person settles in. A product direction you could still change before customers depend on it. A habit in a team that hasn&#8217;t hardened into culture yet.</p><p>These are the ones to catch early. They look like small, fixable things, and they are, for a while. The judgment lies in noticing the clock.</p><h2>This week</h2><p>Pick the decision that&#8217;s been sitting on your desk longest. Ask the reversal question. If it&#8217;s a door you can walk back through, make the call before the week is out. If it locks, stop pretending you&#8217;ll decide it in a spare hour, and book proper time for it.</p><p>To learn from the call whichever way it goes, write it down first with <a href="https://judgmentrelay.substack.com/p/the-one-page-decision-record">The One-Page Decision Record</a>.</p><p>One question before you go: what&#8217;s a decision on your desk that you could still undo today, but won&#8217;t be able to in a month? Hit reply and tell me. I read every one.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://judgmentrelay.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">The Judgment Relay is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>&#8212; Nolan</p>]]></content:encoded></item></channel></rss>