<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>The Journal — Knoito</title>
    <link>https://knoito.app/blog</link>
    <atom:link href="https://knoito.app/blog/rss.xml" rel="self" type="application/rss+xml"/>
    <description>Notes on relationships, promises and preparation, from the makers of Knoito.</description>
    <language>en-us</language>
    <lastBuildDate>Mon, 05 Oct 2026 12:00:00 GMT</lastBuildDate>
    <item>
      <title>Follow-through is a leadership skill, not a personality trait</title>
      <link>https://knoito.app/blog/follow-through-is-a-leadership-skill</link>
      <guid isPermaLink="true">https://knoito.app/blog/follow-through-is-a-leadership-skill</guid>
      <pubDate>Mon, 05 Oct 2026 12:00:00 GMT</pubDate>
      <category>Follow-through</category>
      <description>The promises you make in passing shape your reputation more than the ones you make in meetings. Here&#39;s a simple way to keep both columns straight.</description>
      <content:encoded><![CDATA[<p>Ask people to describe a leader they trust and you rarely hear about strategy. You hear &quot;she always got back to me&quot; or &quot;if he said he&#39;d do it, it got done.&quot; Follow-through is how most people experience your leadership, one small promise at a time.</p>
<p>It&#39;s tempting to treat that as a trait some people have and others don&#39;t. It isn&#39;t. It&#39;s a system, and the people who seem naturally reliable have usually just built a better one.</p>
<h2 id="the-promises-that-slip-are-the-small-ones">The promises that slip are the small ones</h2>
<p>Nobody forgets the commitments made in a formal meeting with an owner and a deadline. The ones that slip are offhand: &quot;I&#39;ll send you that article.&quot; &quot;Let me introduce you to someone.&quot; &quot;I&#39;ll find out and get back to you.&quot;</p>
<p>They feel too small to write down, so they live in your head, and your head is already full. The other person remembers them precisely, because to them it wasn&#39;t small at all.</p>
<h2 id="keep-both-columns">Keep both columns</h2>
<p>Most to-do systems track what you owe. That&#39;s half the ledger. The other half is what you&#39;re owed: the feedback someone promised, the intro they offered, the decision they said they&#39;d make by Friday.</p>
<blockquote>
<p>A promise you&#39;re owed is still your problem if your work depends on it.</p>
</blockquote>
<p>Keeping both columns changes how you walk into a conversation. You can lead with what you&#39;ve done for them, and you can ask for what you need without it feeling like an ambush.</p>
<h2 id="make-it-cheap-to-capture">Make it cheap to capture</h2>
<p>The best system is the one you&#39;ll use in the thirty seconds after a meeting ends, standing in a hallway. That means one place, very little typing, and a date attached to every promise, even a rough one. &quot;Soon&quot; is not a date.</p>
<p>Review the list before you meet the person, not once a week in the abstract. A promise is most useful to remember in the moment you&#39;re about to see the person you made it to.</p>
<h2 id="when-you-39-re-late-say-so-first">When you&#39;re late, say so first</h2>
<p>You will miss some. Everyone does. The difference is who raises it. If you bring up the late item before they do, with a new date you can keep, most people will remember that you followed up, not that you were late.</p>
<p>Reliability isn&#39;t never dropping anything. It&#39;s making sure nothing you drop stays dropped.</p>
]]></content:encoded>
    </item>
    <item>
      <title>What to read in the sixty seconds before a meeting</title>
      <link>https://knoito.app/blog/sixty-seconds-before-a-meeting</link>
      <guid isPermaLink="true">https://knoito.app/blog/sixty-seconds-before-a-meeting</guid>
      <pubDate>Mon, 28 Sep 2026 12:00:00 GMT</pubDate>
      <category>Before the Meeting</category>
      <description>A three-line brief beats a three-page dossier. Here&#39;s what goes in it, and why each line earns its place.</description>
      <content:encoded><![CDATA[<p>Most meeting prep fails in one of two ways. Either there isn&#39;t any, and you spend the first five minutes reconstructing what you discussed last time, or there&#39;s too much, and the one thing that mattered is buried on page three.</p>
<p>The fix isn&#39;t more preparation. It&#39;s a smaller brief: three lines you can read in the time it takes to walk down a hallway.</p>
<h2 id="line-one-where-you-left-off">Line one: where you left off</h2>
<p>Write down the last real conversation in a single sentence. Not the meeting title — the substance. &quot;She was hiring a VP of Finance and wanted my read on two candidates&quot; tells you more than &quot;Q3 sync&quot; ever will.</p>
<p>This line does two jobs. It lets you open where the last meeting ended, which shows you were listening. And it surfaces what may have changed since: a hire made, a reorg finished, a decision taken without you.</p>
<h2 id="line-two-what-39-s-open-between-you">Line two: what&#39;s open between you</h2>
<p>List every open promise, in both directions: what you said you&#39;d do, what they said they&#39;d do, and anything that&#39;s late.</p>
<blockquote>
<p>People forgive a late memo. They don&#39;t forgive pretending it isn&#39;t late.</p>
</blockquote>
<p>If you owe something overdue, the brief is your chance to raise it before they do. Lead with it. If they owe you something, you now know whether to ask or let it ride.</p>
<h2 id="line-three-one-thing-to-ask">Line three: one thing to ask</h2>
<p>End with one question that moves things forward, ideally one that follows up on line one. &quot;Did the search close?&quot; beats &quot;How are things?&quot; because it proves the last conversation mattered to you.</p>
<p>One question, not five. The point is to start well, not to run the meeting from a script.</p>
<h2 id="make-it-a-habit">Make it a habit</h2>
<p>A brief only helps if it exists before you walk in. Write it when the meeting lands on your calendar, or block two minutes before each one. Keep the same three lines every time, so reading it becomes automatic.</p>
<p>Sixty seconds is enough. The goal isn&#39;t to know everything about the person across the table. It&#39;s to make sure they never have to remind you of the thing you already promised.</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
