<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title><![CDATA[Quiet Cloud Rise]]></title>
  <link>https://quietcloudrise.com/</link>
  <description><![CDATA[Independent consultancy in Saga, Japan. Organisational diagnostics, strategy facilitation days and quarterly advisory for small and mid-size organisations.]]></description>
  <language>en</language>
  <atom:link href="https://quietcloudrise.com/feed.xml" rel="self" type="application/rss+xml" />
  <item>
    <title><![CDATA[Recognising organisational friction before it becomes a problem]]></title>
    <link>https://quietcloudrise.com/notes/recognising-organisational-friction-before-it-becomes-a-prob.html</link>
    <guid isPermaLink="true">https://quietcloudrise.com/notes/recognising-organisational-friction-before-it-becomes-a-prob.html</guid>
    <description><![CDATA[Organisational friction rarely announces itself. It accumulates gradually, in the form of small delays, repeated misunderstandings, and decisions that take longer than they should. By the time it is visible enough to be named as a problem, it has usually been present for a year or more. The organisations that manage it well are the ones that learn to recognise the early signals.]]></description>
    <pubDate>Thu, 08 Oct 2026 16:59:45 GMT</pubDate>
  </item>
  <item>
    <title><![CDATA[How to map decision-making in a small organisation]]></title>
    <link>https://quietcloudrise.com/notes/how-to-map-decision-making-in-small-organisations.html</link>
    <guid isPermaLink="true">https://quietcloudrise.com/notes/how-to-map-decision-making-in-small-organisations.html</guid>
    <description><![CDATA[Most organisations have an org chart. Very few have an accurate picture of how decisions actually get made. The chart shows reporting lines. It does not show who gets consulted before a decision is announced, who can quietly block something, or which decisions get made in the corridor rather than the meeting room. Mapping the real decision structure is the first thing Quiet Cloud Rise does in any diagnostic engagement, and it is something any organisation can do for itself.]]></description>
    <pubDate>Sun, 20 Sep 2026 20:06:05 GMT</pubDate>
  </item>
  <item>
    <title><![CDATA[Running a strategy day that actually produces decisions]]></title>
    <link>https://quietcloudrise.com/notes/running-a-strategy-day-that-produces-decisions.html</link>
    <guid isPermaLink="true">https://quietcloudrise.com/notes/running-a-strategy-day-that-produces-decisions.html</guid>
    <description><![CDATA[A strategy day that ends with a list of things to discuss further is not a strategy day. It is a long meeting. The difference between the two is almost entirely structural: what happens before the session, how the session itself is run, and what gets written down before everyone leaves the room.]]></description>
    <pubDate>Wed, 26 Aug 2026 12:39:01 GMT</pubDate>
  </item>
  <item>
    <title><![CDATA[When your organisation has outgrown informal coordination]]></title>
    <link>https://quietcloudrise.com/notes/when-your-organisation-has-outgrown-informal-coordination.html</link>
    <guid isPermaLink="true">https://quietcloudrise.com/notes/when-your-organisation-has-outgrown-informal-coordination.html</guid>
    <description><![CDATA[There is a size at which informal coordination works well. In a team of five or six people who sit near each other and share context, a lot can be handled by conversation. Somewhere between fifteen and thirty people, that stops being true. The conversations that used to carry the organisation start dropping things. This is not a failure of the people involved. It is a structural problem, and it has structural solutions.]]></description>
    <pubDate>Tue, 07 Jul 2026 09:22:01 GMT</pubDate>
  </item>
  <item>
    <title><![CDATA[Writing internal documents that people actually read]]></title>
    <link>https://quietcloudrise.com/notes/writing-internal-documents-people-actually-read.html</link>
    <guid isPermaLink="true">https://quietcloudrise.com/notes/writing-internal-documents-people-actually-read.html</guid>
    <description><![CDATA[Many internal documents in Japanese organisations are longer than they need to be, written in the passive voice, and structured around what the author wanted to say rather than what the reader needs to know. This is not a criticism. It reflects how most people are taught to write in professional contexts. But it produces documents that do not get read, which means the work that went into them is largely wasted.]]></description>
    <pubDate>Mon, 29 Jun 2026 16:39:18 GMT</pubDate>
  </item>
  <item>
    <title><![CDATA[A quarterly review format that works for small teams]]></title>
    <link>https://quietcloudrise.com/notes/quarterly-review-format-for-small-teams.html</link>
    <guid isPermaLink="true">https://quietcloudrise.com/notes/quarterly-review-format-for-small-teams.html</guid>
    <description><![CDATA[The quarterly review is one of the most consistently useful tools in a small organisation's calendar. It creates a regular moment to step back from daily operations, assess what has changed, and make decisions that would otherwise get deferred indefinitely. The format matters. A poorly structured quarterly review is just a long meeting. A well-structured one produces decisions that hold.]]></description>
    <pubDate>Wed, 20 May 2026 18:16:31 GMT</pubDate>
  </item>
</channel>
</rss>
