<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>Singular State</title>
  <link>https:&#x2F;&#x2F;singular-state.com</link>
  <description>Advanced technical expertise for feasibility, prototyping and modernization. We build the working pilot and ramp up your team to take it forward.</description>
  <language>en-US</language>
  <atom:link href="https://singular-state.com/topics/capability/rss.xml" rel="self" type="application/rss+xml"/>
  <item>
    <title>Sometimes the correct answer is never to transfer</title>
    <link>https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;sometimes-never-transfer&#x2F;</link>
    <guid isPermaLink="true">https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;sometimes-never-transfer&#x2F;</guid>
    <pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate>
    <description>The structure assumes handover is the goal. Where the receiving organisation has no path to the capability, forcing a transfer produces an orphan with an owner&#x27;s name on it.</description>
  </item>
  <item>
    <title>The receiving team is the deliverable</title>
    <link>https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;the-receiving-team-is-the-deliverable&#x2F;</link>
    <guid isPermaLink="true">https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;the-receiving-team-is-the-deliverable&#x2F;</guid>
    <pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate>
    <description>Invert the frame: the software is the byproduct and the capability is the product. Every practice that eases transfer is a training programme with an artifact attached.</description>
  </item>
</channel>
</rss>
