<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>Kihon Labs Research</title>
    <link>https://newsletter.kihonlabs.com/research</link>
    <description>Field research on B2B commercial systems: how they break, what the breakage costs, and what actually holds after a fix. Working notes from Kihon Labs.</description>
    <language>en</language>
    <pubDate>Thu, 01 Oct 2026 10:50:43 GMT</pubDate>
    <dc:date>2026-10-01T10:50:43Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>The question I get most: what is the Monday forecast rebuild costing us?</title>
      <link>https://newsletter.kihonlabs.com/research/the-question-i-get-most-what-is-the-monday-forecast-rebuild-costing-us</link>
      <description>&lt;p&gt;&lt;img src="https://www.kihonlabs.com/assets/newsletter/communication-coordination.png" alt="Kihon Labs daily note: communication, coordination and cooperation" width="600"&gt;&lt;/p&gt; 
&lt;p&gt;Most of the time the honest answer is not yet. Not because the number is small. Because I have not read anything yet.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;img src="https://www.kihonlabs.com/assets/newsletter/communication-coordination.png" alt="Kihon Labs daily note: communication, coordination and cooperation" width="600"&gt;&lt;/p&gt; 
&lt;p&gt;Most of the time the honest answer is not yet. Not because the number is small. Because I have not read anything yet.&lt;/p&gt; 
&lt;p&gt;I once watched a sales director answer that question in under ten seconds. He may well have been in the right order of magnitude. He also had no way to defend it when his finance director asked how he got there, and the conversation closed, the way those conversations usually close.&lt;/p&gt; 
&lt;p&gt;Here is the part the total hides. The number is not the finding. The finding is the condition that produces it, and memory is the last source for that, not the first.&lt;/p&gt; 
&lt;p&gt;What would settle it is dull work. Four weeks of calendars for the eight people who rebuild the thing, and the edit history on the stage that carries two meanings. Then each of the eight asked separately, in their own words, what their Monday actually looks like, before anyone is shown the records.&lt;/p&gt; 
&lt;p&gt;Even done properly, that establishes what those four weeks cost that team in that quarter. It is not a law about pipeline stages, and it is not your number.&lt;/p&gt; 
&lt;p&gt;So if you want the figure this week, write down first where you would go to get it. If the answer is that you would ask around, you already have your first finding.&lt;/p&gt; 
&lt;p&gt;Every day by email; the week's synthesis on Sundays at kihonlabs.com/research.&lt;/p&gt; 
&lt;p&gt;Cem Gorer, Founder of Kihon Labs&lt;br&gt;Executive DBA Candidate at EADA&lt;/p&gt;  
&lt;img src="https://track-eu1.hubspot.com/__ptq.gif?a=149259106&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fnewsletter.kihonlabs.com%2Fresearch%2Fthe-question-i-get-most-what-is-the-monday-forecast-rebuild-costing-us&amp;amp;bu=https%253A%252F%252Fnewsletter.kihonlabs.com%252Fresearch&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Daily</category>
      <pubDate>Thu, 01 Oct 2026 08:42:14 GMT</pubDate>
      <author>cemgorer@kihonlabs.com (Cem Gorer)</author>
      <guid>https://newsletter.kihonlabs.com/research/the-question-i-get-most-what-is-the-monday-forecast-rebuild-costing-us</guid>
      <dc:date>2026-10-01T08:42:14Z</dc:date>
    </item>
  </channel>
</rss>
