<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" 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">
  <channel>
    <title>Writings (All)</title>
    <description>A timeline-first diary, essays, newsletters, and observations outlet - Complete archive</description>
    <link>https://casey.berlin/writings/</link>
    <language>en</language>
    <lastBuildDate>Tue, 21 Apr 2026 00:00:00 GMT</lastBuildDate>
    <generator>Astro</generator>
    <atom:link href="https://casey.berlin/writings/rss-all.xml" rel="self" type="application/rss+xml" />
    <image>
      <url>https://casey.berlin/writings/images/rss-feed-logo-placeholder.png</url>
      <title>Writings (All)</title>
      <link>https://casey.berlin/writings/</link>
    </image>
    <item>
      <title>Addicted to the Output, Not the Outcome</title>
      <link>https://casey.berlin/writings/2026/04/addicted-to-the-output-not-the-outcome/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2026/04/addicted-to-the-output-not-the-outcome/</guid>
      <pubDate>Tue, 21 Apr 2026 00:00:00 GMT</pubDate>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>reflection</category>
      <category>creative-process</category>
      <category>psychology</category>
      <category>claude</category>
      <category>solo-operators</category>
      <description><![CDATA[A conversation with Claude after 2.5 months of intense building — on why we crave complexity, what the full backlog is really protecting us from, and what happens when the flow finally stops.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>I just came off 2.5 months of intense building. A huge, sustained creative flow, the kind where days blur, specs multiply, systems connect, and everything feels like it's converging toward something meaningful. And then yesterday, the machine stopped. Not by choice. My body and mind pulled the emergency brake. I woke up to a "what the fuck" feeling. Completely untethered, staring at the ceiling, realizing I'd been addicted to the output, not the outcome.</p>
<p>So I did what I do. I started a conversation. This time with Claude. What followed was one of the more honest exchanges I've had about why I, why <em>we</em>, build the way we do.</p>
<hr>
<h2 id="why-complexity"><a class="anchor" href="#why-complexity">Why complexity?</a></h2>
<p>I opened with a question I'd been circling for a while:</p>
<p><em>Why do I choose complexity and complicated projects over keeping it simple and accepting that 80% is also enough?</em></p>
<blockquote>
<p>It might not be a bug. It might be your wiring. You're a systems thinker who genuinely enjoys architecture. The complexity isn't the cost, it's partly the reward. That's fine to own, but it helps to see it clearly.</p>
<p>80% feels like leaving value on the table. When you can <em>see</em> the elegant full solution, shipping the rough one feels like technical debt you're choosing to take on. Except as a solo operator, the debt of not shipping at all is worse than the debt of shipping something imperfect.</p>
<p>Complexity is also a form of safety. If the spec isn't done, you don't have to face the market yet. A perfect spec can't get rejected by a prospect. A live product page can.</p>
</blockquote>
<p>That last point landed. I pushed back. This felt too narrow, too tactical. Why do we, as human beings, crave complexity? Why do we prefer an overloaded backlog of ideas over sitting with nothing?</p>
<hr>
<h2 id="the-relief-complexity-provides"><a class="anchor" href="#the-relief-complexity-provides">The relief complexity provides</a></h2>
<blockquote>
<p>Complexity is a defense against meaninglessness. An empty backlog means sitting with the question "what now?", and that question, if you let it breathe, quickly becomes "what for?" We fill the space because the space is uncomfortable. A full task board feels like purpose. An empty one feels like a void.</p>
<p>There's something deeply human here: we confuse activity with aliveness. When you're deep in a spec, connecting systems, naming things, seeing the architecture click, you feel sharp, capable, <em>real</em>. That's not fake. It's genuine creative flow. But it's also a reliable way to avoid the more terrifying state of just... being.</p>
<p>Buddhism calls this <em>papañca</em>: the mind's compulsive proliferation. Give it one idea and it builds a cathedral. Not because the cathedral is needed, but because building is what minds <em>do</em>. Stillness feels like death to a system that equates thinking with existing.</p>
<p>The real root? Uncertainty is intolerable to a pattern-seeking mind. A backlog of 224 items is stressful, but it's <em>structured</em> stress. It's a knowable problem. The alternative, admitting you don't know what matters most, that you might pick wrong, that's unstructured uncertainty. And that's far worse.</p>
<p>So the honest answer: you probably don't crave complexity. You crave the <em>relief</em> complexity provides from sitting with not-knowing.</p>
</blockquote>
<hr>
<h2 id="where-does-this-come-from"><a class="anchor" href="#where-does-this-come-from">Where does this come from?</a></h2>
<p>I wanted to go deeper. Psychologically, where does this pattern originate? And why do people claim that sitting with the unknown is somehow <em>better</em>?</p>
<blockquote>
<p>Developmentally, it starts early. As children we learn that doing things gets approval. Stillness is rarely rewarded. "Go do something useful" is a universal parenting reflex. So we internalize: my value is in my output. By adulthood this is so deeply wired it doesn't feel like a belief anymore. It feels like reality.</p>
<p>Ernest Becker's <em>The Denial of Death</em> argues that all human busyness is ultimately a terror management strategy. We build "immortality projects" to symbolically outlast our own mortality. Your universe of named, interconnected projects <em>is</em> a world you're authoring into existence. That's not pathological — it's deeply human. But it's worth seeing the engine underneath.</p>
<p>Then there's what psychologists call <em>intolerance of uncertainty</em>: a trait, not a disorder. Some minds experience ambiguity as genuinely threatening. The nervous system responds to "I don't know what to do next" the same way it responds to a physical threat: cortisol, restlessness, a drive to <em>resolve</em>. Building a spec resolves it. Naming a project resolves it. The relief is neurochemical, not just intellectual.</p>
</blockquote>
<p>On sitting with it:</p>
<blockquote>
<p>Every time you resolve the discomfort by adding a project, you reinforce the loop: uncertainty → anxiety → action → relief. The tolerance never builds. The threshold stays low. You need the next spec faster. The backlog grows not because you have more ideas, but because the window between "uncomfortable" and "must act" keeps shrinking.</p>
<p>Sitting with not-knowing teaches your nervous system that groundlessness is survivable. That you won't dissolve. Winnicott called this <em>the capacity to be alone</em>: not lonely, but genuinely unoccupied. He considered it one of the signs of psychological maturity.</p>
<p>When you act from the anxiety of not-knowing, you get anxiety-shaped decisions. Things that feel urgent, that promise structure, that relieve pressure. When you act <em>after</em> sitting with the not-knowing, you get clearer signal. The ideas that survive stillness are usually the ones that actually matter.</p>
</blockquote>
<hr>
<h2 id="the-invoice-arrives"><a class="anchor" href="#the-invoice-arrives">The invoice arrives</a></h2>
<p>After 2.5 months of sustained flow, my system didn't choose to stop — it <em>forced</em> me to stop. And the emptiness that followed wasn't philosophical. It was physiological. Withdrawal. The dopamine hole after the signal cuts out.</p>
<blockquote>
<p>The "what the fuck" feeling is actually the withdrawal. Literally. Sustained creative flow produces dopamine, norepinephrine, endorphins. When it stops abruptly, your brain is sitting in a neurochemical hole. The emptiness isn't philosophical in that moment. It's physiological. And then the mind rushes in to <em>explain</em> the emptiness, which makes it feel existential.</p>
</blockquote>
<p>Everything in me wants to open the task board, pick up a spec, start naming something new. That impulse feels like motivation. But maybe it's the discomfort talking.</p>
<hr>
<h2 id="what-im-sitting-with"><a class="anchor" href="#what-im-sitting-with">What I'm sitting with</a></h2>
<p>I don't have a clean takeaway. That's kind of the point. The practice isn't about doing nothing permanently. It's about widening the space between the impulse and the action, so that when I do build next, it's chosen, not compulsive.</p>
<p>The ideas that survive stillness are the ones worth building. The rest were just the dopamine talking.</p>]]></content:encoded>
    </item>
    <item>
      <title>The $40,000 Question</title>
      <link>https://casey.berlin/writings/2026/04/the-40000-question/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2026/04/the-40000-question/</guid>
      <pubDate>Fri, 17 Apr 2026 10:00:00 GMT</pubDate>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>saas</category>
      <category>spec-driven-development</category>
      <category>smb</category>
      <category>digital-transformation</category>
      <category>ai</category>
      <description><![CDATA[A startup replaced a $40,000 Salesforce contract with a custom CRM that costs $1,200 a year. The economics of building have caught up — and the specification is the product.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>A startup called Atonom was paying $40,000 a year for Salesforce. Twenty-five to thirty people. Standard setup. Their CRO looked at the functionality they were actually using and said: "This is crazy for what we need."</p>
<p>They built a custom CRM using AI-assisted development tools. Annual cost: roughly <strong>$1,200.</strong> Not a stripped-down version — the version they actually needed.</p>
<p>This isn't an isolated story. It's a pattern reshaping how businesses think about their tools.</p>
<h2 id="the-economics-are-new-the-frustration-isnt"><a class="anchor" href="#the-economics-are-new-the-frustration-isnt">The economics are new. The frustration isn't.</a></h2>
<p>Every operations lead I talk to has the same story: they know exactly what their business needs, they've known for years, but the software doesn't do it. The last time they asked about custom development, someone quoted six figures and nine months. So they built workarounds. Spreadsheets became load-bearing infrastructure. People became the bridge between what software does and what the business requires.</p>
<p>That gap — between what you know you need and what you can actually get — has collapsed. GitHub reports that <strong>46% of all code is now AI-generated.</strong> Developers complete tasks 55.8% faster with AI assistants. Y Combinator's CEO said it directly: "Ten engineers are delivering what used to take fifty to a hundred."</p>
<p>In practical terms: a functional prototype that would have cost six figures now takes days. A custom internal tool that would have required an engineering team now requires a clear specification and the right platform.</p>
<h2 id="the-specification-is-the-product"><a class="anchor" href="#the-specification-is-the-product">The specification is the product.</a></h2>
<p>There's a concept called spec-driven development that captures this shift. GitHub's internal research puts it simply: "The specification becomes the primary artifact. Code is the last mile."</p>
<p>What this means for business: your domain knowledge — the processes you've refined over decades, the workarounds that reveal exactly what the software should do, the institutional memory that no consultant can replicate — that knowledge is now directly translatable into working software.</p>
<p>You don't need to code. You need to specify. And nobody specifies better than the person who's been doing the work.</p>
<h2 id="the-consultant-trap-is-real--and-expensive"><a class="anchor" href="#the-consultant-trap-is-real--and-expensive">The consultant trap is real — and expensive.</a></h2>
<p>Seventy percent of digital transformation projects fail to meet their goals. Bain puts it at 88%. An estimated **<span class="katex"><span class="katex-mathml"><math xmlns="http://www.w3.org/1998/Math/MathML"><semantics><mrow><mn>2.3</mn><mi>t</mi><mi>r</mi><mi>i</mi><mi>l</mi><mi>l</mi><mi>i</mi><mi>o</mi><mi>n</mi><mo>∗</mo><mo>∗</mo><mi>h</mi><mi>a</mi><mi>s</mi><mi>b</mi><mi>e</mi><mi>e</mi><mi>n</mi><mi>w</mi><mi>a</mi><mi>s</mi><mi>t</mi><mi>e</mi><mi>d</mi><mi>g</mi><mi>l</mi><mi>o</mi><mi>b</mi><mi>a</mi><mi>l</mi><mi>l</mi><mi>y</mi><mi>o</mi><mi>n</mi><mi>u</mi><mi>n</mi><mi>s</mi><mi>u</mi><mi>c</mi><mi>c</mi><mi>e</mi><mi>s</mi><mi>s</mi><mi>f</mi><mi>u</mi><mi>l</mi><mi>t</mi><mi>r</mi><mi>a</mi><mi>n</mi><mi>s</mi><mi>f</mi><mi>o</mi><mi>r</mi><mi>m</mi><mi>a</mi><mi>t</mi><mi>i</mi><mi>o</mi><mi>n</mi><mi>p</mi><mi>r</mi><mi>o</mi><mi>g</mi><mi>r</mi><mi>a</mi><mi>m</mi><mi>m</mi><mi>e</mi><mi>s</mi><mi mathvariant="normal">.</mi><mi>S</mi><mi>A</mi><mi>P</mi><mi>i</mi><mi>m</mi><mi>p</mi><mi>l</mi><mi>e</mi><mi>m</mi><mi>e</mi><mi>n</mi><mi>t</mi><mi>a</mi><mi>t</mi><mi>i</mi><mi>o</mi><mi>n</mi><mi>s</mi><mi>f</mi><mi>o</mi><mi>r</mi><mi>e</mi><mi>n</mi><mi>t</mi><mi>e</mi><mi>r</mi><mi>p</mi><mi>r</mi><mi>i</mi><mi>s</mi><mi>e</mi><mi>s</mi><mi>c</mi><mi>o</mi><mi>s</mi><mi>t</mi></mrow><annotation encoding="application/x-tex">2.3 trillion** has been wasted globally on unsuccessful transformation programmes. SAP implementations for enterprises cost </annotation></semantics></math></span><span class="katex-html" aria-hidden="true"><span class="base"><span class="strut" style="height:0.6944em;"></span><span class="mord">2.3</span><span class="mord mathnormal">t</span><span class="mord mathnormal" style="margin-right:0.02778em;">r</span><span class="mord mathnormal">i</span><span class="mord mathnormal" style="margin-right:0.01968em;">ll</span><span class="mord mathnormal">i</span><span class="mord mathnormal">o</span><span class="mord mathnormal">n</span><span class="mspace" style="margin-right:0.2222em;"></span><span class="mbin">∗</span><span class="mspace" style="margin-right:0.2222em;"></span></span><span class="base"><span class="strut" style="height:0.8889em;vertical-align:-0.1944em;"></span><span class="mord">∗</span><span class="mord mathnormal">ha</span><span class="mord mathnormal">s</span><span class="mord mathnormal">b</span><span class="mord mathnormal">ee</span><span class="mord mathnormal">n</span><span class="mord mathnormal" style="margin-right:0.02691em;">w</span><span class="mord mathnormal">a</span><span class="mord mathnormal">s</span><span class="mord mathnormal">t</span><span class="mord mathnormal">e</span><span class="mord mathnormal">d</span><span class="mord mathnormal" style="margin-right:0.03588em;">g</span><span class="mord mathnormal" style="margin-right:0.01968em;">l</span><span class="mord mathnormal">o</span><span class="mord mathnormal">ba</span><span class="mord mathnormal" style="margin-right:0.01968em;">ll</span><span class="mord mathnormal">yo</span><span class="mord mathnormal">n</span><span class="mord mathnormal">u</span><span class="mord mathnormal">n</span><span class="mord mathnormal">s</span><span class="mord mathnormal">u</span><span class="mord mathnormal">ccess</span><span class="mord mathnormal" style="margin-right:0.10764em;">f</span><span class="mord mathnormal">u</span><span class="mord mathnormal">lt</span><span class="mord mathnormal" style="margin-right:0.02778em;">r</span><span class="mord mathnormal">an</span><span class="mord mathnormal">s</span><span class="mord mathnormal" style="margin-right:0.10764em;">f</span><span class="mord mathnormal" style="margin-right:0.02778em;">or</span><span class="mord mathnormal">ma</span><span class="mord mathnormal">t</span><span class="mord mathnormal">i</span><span class="mord mathnormal">o</span><span class="mord mathnormal">n</span><span class="mord mathnormal">p</span><span class="mord mathnormal">ro</span><span class="mord mathnormal" style="margin-right:0.03588em;">g</span><span class="mord mathnormal" style="margin-right:0.02778em;">r</span><span class="mord mathnormal">amm</span><span class="mord mathnormal">es</span><span class="mord">.</span><span class="mord mathnormal" style="margin-right:0.05764em;">S</span><span class="mord mathnormal">A</span><span class="mord mathnormal" style="margin-right:0.13889em;">P</span><span class="mord mathnormal">im</span><span class="mord mathnormal" style="margin-right:0.01968em;">pl</span><span class="mord mathnormal">e</span><span class="mord mathnormal">m</span><span class="mord mathnormal">e</span><span class="mord mathnormal">n</span><span class="mord mathnormal">t</span><span class="mord mathnormal">a</span><span class="mord mathnormal">t</span><span class="mord mathnormal">i</span><span class="mord mathnormal">o</span><span class="mord mathnormal">n</span><span class="mord mathnormal">s</span><span class="mord mathnormal" style="margin-right:0.10764em;">f</span><span class="mord mathnormal">ore</span><span class="mord mathnormal">n</span><span class="mord mathnormal">t</span><span class="mord mathnormal" style="margin-right:0.02778em;">er</span><span class="mord mathnormal">p</span><span class="mord mathnormal" style="margin-right:0.02778em;">r</span><span class="mord mathnormal">i</span><span class="mord mathnormal">sescos</span><span class="mord mathnormal">t</span></span></span></span>5 million to $20 million and 55% exceed their budgets.</p>
<p>The pattern is familiar: consultancy arrives, runs workshops, produces strategy documents, recommends enterprise tools, oversees multi-year implementation, moves on. The organisation is left with something that sort of works, costs more than promised, and is already outdated.</p>
<p>No consultant should walk into your company, turn it upside down, and leave you poorer and more confused than before.</p>
<h2 id="fewer-tools-connected-intentionally"><a class="anchor" href="#fewer-tools-connected-intentionally">Fewer tools, connected intentionally.</a></h2>
<p>The average organisation uses 112 SaaS applications. Wastes $21 million a year on unused licences. Accumulates seven new tools every month, most outside IT's oversight.</p>
<p>The alternative: deliberate simplicity. The right tools, connected the right way, serving proven processes. When nothing fits your specific need, you build it — quickly, cheaply, precisely. When an existing tool works, you keep it. The goal isn't transformation. The goal is getting your time back.</p>
<p>The person who knows the business best should direct what gets built. Not a consultant who arrived on Monday. Not a vendor whose roadmap ignores your reality. You. The people who built these processes over years know exactly what "good" looks like.</p>
<p>The economics have caught up. Software that works the way your business actually works. Days, not quarters. Thousands, not millions. Owned, not rented.</p>]]></content:encoded>
    </item>
    <item>
      <title>You Already Know What to Build</title>
      <link>https://casey.berlin/writings/2026/04/you-already-know-what-to-build/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2026/04/you-already-know-what-to-build/</guid>
      <pubDate>Thu, 16 Apr 2026 10:00:00 GMT</pubDate>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>spec-driven-development</category>
      <category>smb</category>
      <category>saas</category>
      <category>digital-transformation</category>
      <category>ai</category>
      <description><![CDATA[The gap between "I know exactly what this should do" and "I have working software that does it" has collapsed from months to days. You don't need to code. You need to specify.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>There's a story I hear from nearly every business owner.</p>
<p>It goes something like this: "We've been running this process for fifteen years. We know exactly what works, exactly where it breaks, and exactly what we'd change if we could. But the software doesn't do that. And the last time we asked, someone quoted us six figures and nine months."</p>
<p>So they don't change it. They build workarounds. They maintain spreadsheets that have become load-bearing infrastructure. They hire people to bridge the gap between what the software does and what the business actually needs. Every year, the gap gets wider. The workaround gets more fragile.</p>
<p>I know this story because I've lived on both sides. I spent years inside the consulting machine — rooms where we'd map processes onto whiteboards, translate them into requirements documents, send them to development teams, wait months for a build, and watch the business outgrow it before it launched. A factory for producing expensive approximations of what someone needed six months ago.</p>
<p>That era is over. Not ending — over.</p>
<h2 id="the-economics-of-building-have-fundamentally-changed"><a class="anchor" href="#the-economics-of-building-have-fundamentally-changed">The economics of building have fundamentally changed.</a></h2>
<p>The numbers that matter: GitHub reports that <strong>46% of all code written by Copilot users is now AI-generated.</strong> In a controlled study, developers using AI assistants completed tasks 55.8% faster. Y Combinator's Winter 2025 batch — some of the most technically capable founders in the world — had 25% of startups with codebases that were 95% AI-generated. Their CEO said it plainly: "Ten engineers are delivering what used to take fifty to a hundred."</p>
<p>In practical terms: a startup called Atonom was paying <strong><span class="katex"><span class="katex-mathml"><math xmlns="http://www.w3.org/1998/Math/MathML"><semantics><mrow><mn>40</mn><mo separator="true">,</mo><mn>000</mn><mi>a</mi><mi>y</mi><mi>e</mi><mi>a</mi><mi>r</mi><mi>f</mi><mi>o</mi><mi>r</mi><mi>S</mi><mi>a</mi><mi>l</mi><mi>e</mi><mi>s</mi><mi>f</mi><mi>o</mi><mi>r</mi><mi>c</mi><mi>e</mi><mo>∗</mo><mo>∗</mo><mi>f</mi><mi>o</mi><mi>r</mi><mi>a</mi><mi>b</mi><mi>o</mi><mi>u</mi><mi>t</mi><mn>25</mn><mo>−</mo><mn>30</mn><mi>p</mi><mi>e</mi><mi>o</mi><mi>p</mi><mi>l</mi><mi>e</mi><mi mathvariant="normal">.</mi><mi>T</mi><mi>h</mi><mi>e</mi><mi>i</mi><mi>r</mi><mi>C</mi><mi>R</mi><mi>O</mi><mi>l</mi><mi>o</mi><mi>o</mi><mi>k</mi><mi>e</mi><mi>d</mi><mi>a</mi><mi>t</mi><mi>t</mi><mi>h</mi><mi>e</mi><mi>a</mi><mi>c</mi><mi>t</mi><mi>u</mi><mi>a</mi><mi>l</mi><mi>f</mi><mi>u</mi><mi>n</mi><mi>c</mi><mi>t</mi><mi>i</mi><mi>o</mi><mi>n</mi><mi>a</mi><mi>l</mi><mi>i</mi><mi>t</mi><mi>y</mi><mi>t</mi><mi>h</mi><mi>e</mi><mi>y</mi><mi>w</mi><mi>e</mi><mi>r</mi><mi>e</mi><mi>u</mi><mi>s</mi><mi>i</mi><mi>n</mi><mi>g</mi><mi>a</mi><mi>n</mi><mi>d</mi><mi>s</mi><mi>a</mi><mi>i</mi><mi>d</mi><mo separator="true">,</mo><mi mathvariant="normal">"</mi><mi>T</mi><mi>h</mi><mi>i</mi><mi>s</mi><mi>i</mi><mi>s</mi><mi>c</mi><mi>r</mi><mi>a</mi><mi>z</mi><mi>y</mi><mi mathvariant="normal">.</mi><mi mathvariant="normal">"</mi><mi>T</mi><mi>h</mi><mi>e</mi><mi>y</mi><mi>b</mi><mi>u</mi><mi>i</mi><mi>l</mi><mi>t</mi><mi>a</mi><mi>c</mi><mi>u</mi><mi>s</mi><mi>t</mi><mi>o</mi><mi>m</mi><mi>C</mi><mi>R</mi><mi>M</mi><mi>u</mi><mi>s</mi><mi>i</mi><mi>n</mi><mi>g</mi><mi>m</mi><mi>o</mi><mi>d</mi><mi>e</mi><mi>r</mi><mi>n</mi><mi>A</mi><mi>I</mi><mo>−</mo><mi>a</mi><mi>s</mi><mi>s</mi><mi>i</mi><mi>s</mi><mi>t</mi><mi>e</mi><mi>d</mi><mi>t</mi><mi>o</mi><mi>o</mi><mi>l</mi><mi>s</mi><mi mathvariant="normal">.</mi><mo>∗</mo><mo>∗</mo><mi>A</mi><mi>n</mi><mi>n</mi><mi>u</mi><mi>a</mi><mi>l</mi><mi>c</mi><mi>o</mi><mi>s</mi><mi>t</mi><mo>:</mo><mi>r</mi><mi>o</mi><mi>u</mi><mi>g</mi><mi>h</mi><mi>l</mi><mi>y</mi></mrow><annotation encoding="application/x-tex">40,000 a year for Salesforce** for about 25-30 people. Their CRO looked at the actual functionality they were using and said, "This is crazy." They built a custom CRM using modern AI-assisted tools. **Annual cost: roughly </annotation></semantics></math></span><span class="katex-html" aria-hidden="true"><span class="base"><span class="strut" style="height:0.8889em;vertical-align:-0.1944em;"></span><span class="mord">40</span><span class="mpunct">,</span><span class="mspace" style="margin-right:0.1667em;"></span><span class="mord">000</span><span class="mord mathnormal">a</span><span class="mord mathnormal">ye</span><span class="mord mathnormal">a</span><span class="mord mathnormal" style="margin-right:0.02778em;">r</span><span class="mord mathnormal" style="margin-right:0.10764em;">f</span><span class="mord mathnormal" style="margin-right:0.02778em;">or</span><span class="mord mathnormal" style="margin-right:0.05764em;">S</span><span class="mord mathnormal">a</span><span class="mord mathnormal" style="margin-right:0.01968em;">l</span><span class="mord mathnormal">es</span><span class="mord mathnormal" style="margin-right:0.10764em;">f</span><span class="mord mathnormal">orce</span><span class="mspace" style="margin-right:0.2222em;"></span><span class="mbin">∗</span><span class="mspace" style="margin-right:0.2222em;"></span></span><span class="base"><span class="strut" style="height:0.8889em;vertical-align:-0.1944em;"></span><span class="mord">∗</span><span class="mord mathnormal" style="margin-right:0.10764em;">f</span><span class="mord mathnormal" style="margin-right:0.02778em;">or</span><span class="mord mathnormal">ab</span><span class="mord mathnormal">o</span><span class="mord mathnormal">u</span><span class="mord mathnormal">t</span><span class="mord">25</span><span class="mspace" style="margin-right:0.2222em;"></span><span class="mbin">−</span><span class="mspace" style="margin-right:0.2222em;"></span></span><span class="base"><span class="strut" style="height:0.8889em;vertical-align:-0.1944em;"></span><span class="mord">30</span><span class="mord mathnormal">p</span><span class="mord mathnormal">eo</span><span class="mord mathnormal" style="margin-right:0.01968em;">pl</span><span class="mord mathnormal">e</span><span class="mord">.</span><span class="mord mathnormal" style="margin-right:0.13889em;">T</span><span class="mord mathnormal">h</span><span class="mord mathnormal">e</span><span class="mord mathnormal">i</span><span class="mord mathnormal" style="margin-right:0.02778em;">r</span><span class="mord mathnormal" style="margin-right:0.01968em;">CROl</span><span class="mord mathnormal">oo</span><span class="mord mathnormal" style="margin-right:0.03148em;">k</span><span class="mord mathnormal">e</span><span class="mord mathnormal">d</span><span class="mord mathnormal">a</span><span class="mord mathnormal">tt</span><span class="mord mathnormal">h</span><span class="mord mathnormal">e</span><span class="mord mathnormal">a</span><span class="mord mathnormal">c</span><span class="mord mathnormal">t</span><span class="mord mathnormal">u</span><span class="mord mathnormal">a</span><span class="mord mathnormal" style="margin-right:0.01968em;">l</span><span class="mord mathnormal" style="margin-right:0.10764em;">f</span><span class="mord mathnormal">u</span><span class="mord mathnormal">n</span><span class="mord mathnormal">c</span><span class="mord mathnormal">t</span><span class="mord mathnormal">i</span><span class="mord mathnormal">o</span><span class="mord mathnormal">na</span><span class="mord mathnormal" style="margin-right:0.01968em;">l</span><span class="mord mathnormal">i</span><span class="mord mathnormal">t</span><span class="mord mathnormal" style="margin-right:0.03588em;">y</span><span class="mord mathnormal">t</span><span class="mord mathnormal">h</span><span class="mord mathnormal" style="margin-right:0.03588em;">ey</span><span class="mord mathnormal" style="margin-right:0.02691em;">w</span><span class="mord mathnormal">ere</span><span class="mord mathnormal">u</span><span class="mord mathnormal">s</span><span class="mord mathnormal">in</span><span class="mord mathnormal" style="margin-right:0.03588em;">g</span><span class="mord mathnormal">an</span><span class="mord mathnormal">d</span><span class="mord mathnormal">s</span><span class="mord mathnormal">ai</span><span class="mord mathnormal">d</span><span class="mpunct">,</span><span class="mspace" style="margin-right:0.1667em;"></span><span class="mord">"</span><span class="mord mathnormal" style="margin-right:0.13889em;">T</span><span class="mord mathnormal">hi</span><span class="mord mathnormal">s</span><span class="mord mathnormal">i</span><span class="mord mathnormal" style="margin-right:0.02778em;">scr</span><span class="mord mathnormal">a</span><span class="mord mathnormal" style="margin-right:0.03588em;">zy</span><span class="mord">."</span><span class="mord mathnormal" style="margin-right:0.13889em;">T</span><span class="mord mathnormal">h</span><span class="mord mathnormal" style="margin-right:0.03588em;">ey</span><span class="mord mathnormal">b</span><span class="mord mathnormal">u</span><span class="mord mathnormal">i</span><span class="mord mathnormal">lt</span><span class="mord mathnormal">a</span><span class="mord mathnormal">c</span><span class="mord mathnormal">u</span><span class="mord mathnormal">s</span><span class="mord mathnormal">t</span><span class="mord mathnormal">o</span><span class="mord mathnormal">m</span><span class="mord mathnormal" style="margin-right:0.10903em;">CRM</span><span class="mord mathnormal">u</span><span class="mord mathnormal">s</span><span class="mord mathnormal">in</span><span class="mord mathnormal" style="margin-right:0.03588em;">g</span><span class="mord mathnormal">m</span><span class="mord mathnormal">o</span><span class="mord mathnormal">d</span><span class="mord mathnormal" style="margin-right:0.02778em;">er</span><span class="mord mathnormal">n</span><span class="mord mathnormal">A</span><span class="mord mathnormal" style="margin-right:0.07847em;">I</span><span class="mspace" style="margin-right:0.2222em;"></span><span class="mbin">−</span><span class="mspace" style="margin-right:0.2222em;"></span></span><span class="base"><span class="strut" style="height:0.6944em;"></span><span class="mord mathnormal">a</span><span class="mord mathnormal">ss</span><span class="mord mathnormal">i</span><span class="mord mathnormal">s</span><span class="mord mathnormal">t</span><span class="mord mathnormal">e</span><span class="mord mathnormal">d</span><span class="mord mathnormal">t</span><span class="mord mathnormal">oo</span><span class="mord mathnormal" style="margin-right:0.01968em;">l</span><span class="mord mathnormal">s</span><span class="mord">.</span><span class="mspace" style="margin-right:0.2222em;"></span><span class="mbin">∗</span><span class="mspace" style="margin-right:0.2222em;"></span></span><span class="base"><span class="strut" style="height:0.6944em;"></span><span class="mord">∗</span><span class="mord mathnormal">A</span><span class="mord mathnormal">nn</span><span class="mord mathnormal">u</span><span class="mord mathnormal">a</span><span class="mord mathnormal" style="margin-right:0.01968em;">l</span><span class="mord mathnormal">cos</span><span class="mord mathnormal">t</span><span class="mspace" style="margin-right:0.2778em;"></span><span class="mrel">:</span><span class="mspace" style="margin-right:0.2778em;"></span></span><span class="base"><span class="strut" style="height:0.8889em;vertical-align:-0.1944em;"></span><span class="mord mathnormal">ro</span><span class="mord mathnormal" style="margin-right:0.03588em;">ug</span><span class="mord mathnormal">h</span><span class="mord mathnormal" style="margin-right:0.01968em;">l</span><span class="mord mathnormal" style="margin-right:0.03588em;">y</span></span></span></span>1,200.</strong> Not a stripped-down version. The version they actually needed.</p>
<p>This pattern is repeating everywhere. Klarna — a <span class="katex"><span class="katex-mathml"><math xmlns="http://www.w3.org/1998/Math/MathML"><semantics><mrow><mn>46</mn><mi>b</mi><mi>i</mi><mi>l</mi><mi>l</mi><mi>i</mi><mi>o</mi><mi>n</mi><mi>c</mi><mi>o</mi><mi>m</mi><mi>p</mi><mi>a</mi><mi>n</mi><mi>y</mi><mtext>—</mtext><mi>e</mi><mi>l</mi><mi>i</mi><mi>m</mi><mi>i</mi><mi>n</mi><mi>a</mi><mi>t</mi><mi>e</mi><mi>d</mi><mi>r</mi><mi>o</mi><mi>u</mi><mi>g</mi><mi>h</mi><mi>l</mi><mi>y</mi><mn>1</mn><mo separator="true">,</mo><mn>200</mn><mi>S</mi><mi>a</mi><mi>a</mi><mi>S</mi><mi>s</mi><mi>e</mi><mi>r</mi><mi>v</mi><mi>i</mi><mi>c</mi><mi>e</mi><mi>s</mi><mi>a</mi><mi>n</mi><mi>d</mi><mi>r</mi><mi>e</mi><mi>p</mi><mi>l</mi><mi>a</mi><mi>c</mi><mi>e</mi><mi>d</mi><mi>t</mi><mi>h</mi><mi>e</mi><mi>m</mi><mi>w</mi><mi>i</mi><mi>t</mi><mi>h</mi><mi>a</mi><mi>c</mi><mi>o</mi><mi>m</mi><mi>b</mi><mi>i</mi><mi>n</mi><mi>a</mi><mi>t</mi><mi>i</mi><mi>o</mi><mi>n</mi><mi>o</mi><mi>f</mi><mi>i</mi><mi>n</mi><mi>t</mi><mi>e</mi><mi>r</mi><mi>n</mi><mi>a</mi><mi>l</mi><mi>A</mi><mi>I</mi><mi>t</mi><mi>o</mi><mi>o</mi><mi>l</mi><mi>s</mi><mi>a</mi><mi>n</mi><mi>d</mi><mi>t</mi><mi>a</mi><mi>r</mi><mi>g</mi><mi>e</mi><mi>t</mi><mi>e</mi><mi>d</mi><mi>a</mi><mi>l</mi><mi>t</mi><mi>e</mi><mi>r</mi><mi>n</mi><mi>a</mi><mi>t</mi><mi>i</mi><mi>v</mi><mi>e</mi><mi>s</mi><mi mathvariant="normal">.</mi><mi>T</mi><mi>h</mi><mi>e</mi><mi>i</mi><mi>r</mi><mi>A</mi><mi>I</mi><mi>c</mi><mi>u</mi><mi>s</mi><mi>t</mi><mi>o</mi><mi>m</mi><mi>e</mi><mi>r</mi><mi>s</mi><mi>e</mi><mi>r</mi><mi>v</mi><mi>i</mi><mi>c</mi><mi>e</mi><mi>s</mi><mi>y</mi><mi>s</mi><mi>t</mi><mi>e</mi><mi>m</mi><mi>r</mi><mi>e</mi><mi>p</mi><mi>l</mi><mi>a</mi><mi>c</mi><mi>e</mi><mi>d</mi><mi>w</mi><mi>o</mi><mi>r</mi><mi>k</mi><mi>t</mi><mi>h</mi><mi>a</mi><mi>t</mi><mi>p</mi><mi>r</mi><mi>e</mi><mi>v</mi><mi>i</mi><mi>o</mi><mi>u</mi><mi>s</mi><mi>l</mi><mi>y</mi><mi>r</mi><mi>e</mi><mi>q</mi><mi>u</mi><mi>i</mi><mi>r</mi><mi>e</mi><mi>d</mi><mn>700</mn><mi>f</mi><mi>u</mi><mi>l</mi><mi>l</mi><mo>−</mo><mi>t</mi><mi>i</mi><mi>m</mi><mi>e</mi><mi>e</mi><mi>m</mi><mi>p</mi><mi>l</mi><mi>o</mi><mi>y</mi><mi>e</mi><mi>e</mi><mi>s</mi><mo separator="true">,</mo><mi>s</mi><mi>a</mi><mi>v</mi><mi>i</mi><mi>n</mi><mi>g</mi><mi>a</mi><mi>p</mi><mi>p</mi><mi>r</mi><mi>o</mi><mi>x</mi><mi>i</mi><mi>m</mi><mi>a</mi><mi>t</mi><mi>e</mi><mi>l</mi><mi>y</mi></mrow><annotation encoding="application/x-tex">46 billion company — eliminated roughly 1,200 SaaS services and replaced them with a combination of internal AI tools and targeted alternatives. Their AI customer service system replaced work that previously required 700 full-time employees, saving approximately </annotation></semantics></math></span><span class="katex-html" aria-hidden="true"><span class="base"><span class="strut" style="height:0.8889em;vertical-align:-0.1944em;"></span><span class="mord">46</span><span class="mord mathnormal">bi</span><span class="mord mathnormal" style="margin-right:0.01968em;">ll</span><span class="mord mathnormal">i</span><span class="mord mathnormal">o</span><span class="mord mathnormal">n</span><span class="mord mathnormal">co</span><span class="mord mathnormal">m</span><span class="mord mathnormal">p</span><span class="mord mathnormal">an</span><span class="mord mathnormal" style="margin-right:0.03588em;">y</span><span class="mord">—</span><span class="mord mathnormal">e</span><span class="mord mathnormal" style="margin-right:0.01968em;">l</span><span class="mord mathnormal">imina</span><span class="mord mathnormal">t</span><span class="mord mathnormal">e</span><span class="mord mathnormal">d</span><span class="mord mathnormal">ro</span><span class="mord mathnormal" style="margin-right:0.03588em;">ug</span><span class="mord mathnormal">h</span><span class="mord mathnormal" style="margin-right:0.01968em;">l</span><span class="mord mathnormal" style="margin-right:0.03588em;">y</span><span class="mord">1</span><span class="mpunct">,</span><span class="mspace" style="margin-right:0.1667em;"></span><span class="mord">200</span><span class="mord mathnormal" style="margin-right:0.05764em;">S</span><span class="mord mathnormal">aa</span><span class="mord mathnormal" style="margin-right:0.05764em;">S</span><span class="mord mathnormal" style="margin-right:0.02778em;">ser</span><span class="mord mathnormal" style="margin-right:0.03588em;">v</span><span class="mord mathnormal">i</span><span class="mord mathnormal">ces</span><span class="mord mathnormal">an</span><span class="mord mathnormal">d</span><span class="mord mathnormal">re</span><span class="mord mathnormal" style="margin-right:0.01968em;">pl</span><span class="mord mathnormal">a</span><span class="mord mathnormal">ce</span><span class="mord mathnormal">d</span><span class="mord mathnormal">t</span><span class="mord mathnormal">h</span><span class="mord mathnormal">e</span><span class="mord mathnormal">m</span><span class="mord mathnormal" style="margin-right:0.02691em;">w</span><span class="mord mathnormal">i</span><span class="mord mathnormal">t</span><span class="mord mathnormal">ha</span><span class="mord mathnormal">co</span><span class="mord mathnormal">mbina</span><span class="mord mathnormal">t</span><span class="mord mathnormal">i</span><span class="mord mathnormal">o</span><span class="mord mathnormal">n</span><span class="mord mathnormal">o</span><span class="mord mathnormal" style="margin-right:0.10764em;">f</span><span class="mord mathnormal">in</span><span class="mord mathnormal">t</span><span class="mord mathnormal" style="margin-right:0.02778em;">er</span><span class="mord mathnormal">na</span><span class="mord mathnormal" style="margin-right:0.01968em;">l</span><span class="mord mathnormal">A</span><span class="mord mathnormal" style="margin-right:0.07847em;">I</span><span class="mord mathnormal">t</span><span class="mord mathnormal">oo</span><span class="mord mathnormal" style="margin-right:0.01968em;">l</span><span class="mord mathnormal">s</span><span class="mord mathnormal">an</span><span class="mord mathnormal">d</span><span class="mord mathnormal">t</span><span class="mord mathnormal">a</span><span class="mord mathnormal" style="margin-right:0.02778em;">r</span><span class="mord mathnormal" style="margin-right:0.03588em;">g</span><span class="mord mathnormal">e</span><span class="mord mathnormal">t</span><span class="mord mathnormal">e</span><span class="mord mathnormal">d</span><span class="mord mathnormal">a</span><span class="mord mathnormal">lt</span><span class="mord mathnormal" style="margin-right:0.02778em;">er</span><span class="mord mathnormal">na</span><span class="mord mathnormal">t</span><span class="mord mathnormal">i</span><span class="mord mathnormal" style="margin-right:0.03588em;">v</span><span class="mord mathnormal">es</span><span class="mord">.</span><span class="mord mathnormal" style="margin-right:0.13889em;">T</span><span class="mord mathnormal">h</span><span class="mord mathnormal">e</span><span class="mord mathnormal">i</span><span class="mord mathnormal" style="margin-right:0.02778em;">r</span><span class="mord mathnormal">A</span><span class="mord mathnormal" style="margin-right:0.07847em;">I</span><span class="mord mathnormal">c</span><span class="mord mathnormal">u</span><span class="mord mathnormal">s</span><span class="mord mathnormal">t</span><span class="mord mathnormal">o</span><span class="mord mathnormal">m</span><span class="mord mathnormal" style="margin-right:0.02778em;">erser</span><span class="mord mathnormal" style="margin-right:0.03588em;">v</span><span class="mord mathnormal">i</span><span class="mord mathnormal">cesys</span><span class="mord mathnormal">t</span><span class="mord mathnormal">e</span><span class="mord mathnormal">m</span><span class="mord mathnormal">re</span><span class="mord mathnormal" style="margin-right:0.01968em;">pl</span><span class="mord mathnormal">a</span><span class="mord mathnormal">ce</span><span class="mord mathnormal">d</span><span class="mord mathnormal" style="margin-right:0.02691em;">w</span><span class="mord mathnormal" style="margin-right:0.02778em;">or</span><span class="mord mathnormal" style="margin-right:0.03148em;">k</span><span class="mord mathnormal">t</span><span class="mord mathnormal">ha</span><span class="mord mathnormal">tp</span><span class="mord mathnormal">re</span><span class="mord mathnormal" style="margin-right:0.03588em;">v</span><span class="mord mathnormal">i</span><span class="mord mathnormal">o</span><span class="mord mathnormal">u</span><span class="mord mathnormal">s</span><span class="mord mathnormal" style="margin-right:0.01968em;">l</span><span class="mord mathnormal">yre</span><span class="mord mathnormal" style="margin-right:0.03588em;">q</span><span class="mord mathnormal">u</span><span class="mord mathnormal">i</span><span class="mord mathnormal">re</span><span class="mord mathnormal">d</span><span class="mord">700</span><span class="mord mathnormal" style="margin-right:0.10764em;">f</span><span class="mord mathnormal">u</span><span class="mord mathnormal" style="margin-right:0.01968em;">ll</span><span class="mspace" style="margin-right:0.2222em;"></span><span class="mbin">−</span><span class="mspace" style="margin-right:0.2222em;"></span></span><span class="base"><span class="strut" style="height:0.8889em;vertical-align:-0.1944em;"></span><span class="mord mathnormal">t</span><span class="mord mathnormal">im</span><span class="mord mathnormal">ee</span><span class="mord mathnormal">m</span><span class="mord mathnormal" style="margin-right:0.01968em;">pl</span><span class="mord mathnormal">oyees</span><span class="mpunct">,</span><span class="mspace" style="margin-right:0.1667em;"></span><span class="mord mathnormal">s</span><span class="mord mathnormal">a</span><span class="mord mathnormal" style="margin-right:0.03588em;">v</span><span class="mord mathnormal">in</span><span class="mord mathnormal" style="margin-right:0.03588em;">g</span><span class="mord mathnormal">a</span><span class="mord mathnormal">pp</span><span class="mord mathnormal">ro</span><span class="mord mathnormal">x</span><span class="mord mathnormal">ima</span><span class="mord mathnormal">t</span><span class="mord mathnormal">e</span><span class="mord mathnormal" style="margin-right:0.01968em;">l</span><span class="mord mathnormal" style="margin-right:0.03588em;">y</span></span></span></span>40 million annually.</p>
<p>These are large companies. But the shift is even more dramatic for small and mid-sized businesses. The average company with 50 employees spends over <strong>$200,000 a year on SaaS subscriptions.</strong> Most of that covers features nobody uses.</p>
<h2 id="you-dont-need-to-code-you-need-to-specify"><a class="anchor" href="#you-dont-need-to-code-you-need-to-specify">You don't need to code. You need to specify.</a></h2>
<p>There's a concept gaining traction called spec-driven development. Thoughtworks defined it as a paradigm where "well-crafted software requirement specifications serve as prompts, aided by AI coding agents, to generate executable code." GitHub's internal research puts it more directly: "The specification becomes the primary artifact — the shared source of truth. Code is the last mile."</p>
<p>What that means for someone running a business: <strong>the most valuable thing you bring isn't technical knowledge. It's domain knowledge.</strong> You know your processes. You know where things break. You know what "good" looks like because you've been doing the work for years, sometimes decades.</p>
<p>That knowledge — the kind that lives in your head, in your team's muscle memory, in the workarounds you've built — that's the specification. The gap between "I know exactly what this should do" and "I have working software that does it" has collapsed from months to days. Sometimes hours.</p>
<p>Red Hat's technical team described it this way: "Humans craft the 'what' while setting 'how' guardrails." You write the specification in plain language. The AI generates the code. You review, adjust, iterate. No six-month procurement process. No 47-slide deck to justify the budget. No consultant who arrives on Monday, turns everything upside down, and leaves you poorer and more confused by Friday.</p>
<h2 id="the-consultant-trap--and-the-way-out"><a class="anchor" href="#the-consultant-trap--and-the-way-out">The consultant trap — and the way out.</a></h2>
<p>Let me say something uncomfortable for someone in my line of work: <strong>70% of digital transformation projects fail to meet their goals.</strong> That's McKinsey's number. Bain puts it higher: 88% don't achieve their original ambitions. Globally, an estimated <strong>$2.3 trillion</strong> has been wasted on unsuccessful digital transformation programmes.</p>
<p>The typical pattern: a large consultancy arrives, runs discovery workshops, produces a beautiful strategy document, recommends enterprise tools, oversees a multi-year implementation, and moves on. The organisation is left with a system that sort of does what was promised, takes years to see ROI, and is already behind by the time it launches.</p>
<p>SAP implementations for enterprises routinely cost <strong><span class="katex"><span class="katex-mathml"><math xmlns="http://www.w3.org/1998/Math/MathML"><semantics><mrow><mn>5</mn><mi>m</mi><mi>i</mi><mi>l</mi><mi>l</mi><mi>i</mi><mi>o</mi><mi>n</mi><mi>t</mi><mi>o</mi></mrow><annotation encoding="application/x-tex">5 million to </annotation></semantics></math></span><span class="katex-html" aria-hidden="true"><span class="base"><span class="strut" style="height:0.6944em;"></span><span class="mord">5</span><span class="mord mathnormal">mi</span><span class="mord mathnormal" style="margin-right:0.01968em;">ll</span><span class="mord mathnormal">i</span><span class="mord mathnormal">o</span><span class="mord mathnormal">n</span><span class="mord mathnormal">t</span><span class="mord mathnormal">o</span></span></span></span>20 million or more.</strong> Fifty-five percent exceed their budgets. These aren't edge cases. This is the system working as designed — designed for the vendor, not for you.</p>
<p>The alternative isn't to go without systems. It's to build exactly what you need, with the specificity that only you can provide, at a cost and timeline that would have seemed fictional three years ago.</p>
<h2 id="fewer-tools-connected-the-right-way"><a class="anchor" href="#fewer-tools-connected-the-right-way">Fewer tools, connected the right way.</a></h2>
<p>The average organisation now uses <strong>112 SaaS applications.</strong> Seven new ones enter the environment every month. Eighty-four percent of that spending sits outside IT's oversight. Companies aren't choosing these tools strategically — they're accumulating them reactively, solving yesterday's problem with tomorrow's subscription.</p>
<p>The philosophy we work from is deliberate simplicity. Not fewer tools for the sake of minimalism — the right tools, connected intentionally, serving the processes you've already proven work. When a tool doesn't exist for your specific need, you build it — quickly, cheaply, precisely. When an existing tool does the job, you keep it. The goal is never "transformation." The goal is getting your time back.</p>
<p>Because here's what I've learned after twelve years: the person who knows the business best should direct what gets built. Not a consultant who arrived on Monday. Not a vendor whose roadmap has nothing to do with your reality. You. The people who built these processes — you are the specification.</p>
<p>The economics have finally caught up. Software that works the way your business actually works. Built in days, not quarters. Costing thousands, not millions. Owned by you, not licensed to you.</p>
<p>Your time is sacred. Everything we build starts from that principle.</p>]]></content:encoded>
    </item>
    <item>
      <title>The Exoskeleton and the Morning Walk</title>
      <link>https://casey.berlin/writings/2026/04/the-exoskeleton-and-the-morning-walk/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2026/04/the-exoskeleton-and-the-morning-walk/</guid>
      <pubDate>Tue, 14 Apr 2026 10:00:00 GMT</pubDate>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>ai</category>
      <category>reflection</category>
      <category>solo-operators</category>
      <category>claude</category>
      <category>creative-process</category>
      <description><![CDATA[AI didn't give me superpowers. It gave me back my time. A personal field note on what it actually feels like to build an entire content campaign in one conversation — with a dog at your feet and a coffee going cold.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>My coffee went cold again.</p>
<p>Eight posts, two longform articles, nine images — scheduled across six days. One conversation. One sitting. One person with a dog at their feet and a mug they forgot about.</p>
<p>Eighteen months ago that sentence would have needed a team. A strategist. A copywriter. A designer. Someone named Lars who knew how the CMS worked.</p>
<p>Now it needs a Tuesday.</p>
<h2 id="the-exoskeleton"><a class="anchor" href="#the-exoskeleton">The exoskeleton</a></h2>
<p>I keep coming back to this word. Not <em>tool</em>. Not <em>assistant</em>. Exoskeleton.</p>
<p>A runner's blade doesn't give you new legs — it gives the legs you have a different relationship with the ground. That's what this actually feels like. Not replacement. Amplification.</p>
<p>Claude doesn't think for me. It lets me think <em>out loud</em> without losing the thread. Brand strategy, image generation, social scheduling, longform writing, campaign cross-referencing — one sitting. The context doesn't break.</p>
<p>The momentum doesn't die.</p>
<p>That's the part nobody talks about. It's not that AI is smart. It's that it's <em>present</em>. Quietly, patiently, relentlessly present.</p>
<p>(And yes — that's a strange thing to say about software.)</p>
<h2 id="the-morning-walk"><a class="anchor" href="#the-morning-walk">The morning walk</a></h2>
<p>Every morning I walk Fimme and Sien through the fields outside Oberbarnim. The light changes. The path doesn't. Somewhere between the third and fourth tree — the ones I've started calling the committee — my mind loosens.</p>
<p>That's where the ideas land. Not at the desk.</p>
<p>Never at the desk.</p>
<p>The gap between "idea on the walk" and "thing that exists in the world" used to be enormous. Filled with logins, formatting, context-switching — the quiet death of momentum. The boring part that eats the good part.</p>
<p>Now the gap is a conversation. I come home, open Claude, and say: <em>here's what I'm thinking.</em> And we build it. Not metaphorically. Actually. The images get generated. The posts get written. The schedule gets set.</p>
<p>The coffee goes cold.</p>
<h2 id="the-quiet-part"><a class="anchor" href="#the-quiet-part">The quiet part</a></h2>
<p>A trillion dollars evaporated from software stocks this month. I wrote about it — what it means for people who build, the end of the permission era, the quiet revolution happening on the floor while the boardroom debates slide 47.</p>
<p>But here's what I didn't put in those articles.</p>
<p>I'm living it. Not as a thought experiment. As a Tuesday.</p>
<p>I run a consultancy. Solo. Strategy, delivery, content, infrastructure, client work. No team. No marketing department. A dog who snores during video calls and an AI that remembers where we left off.</p>
<p>I'm not drowning. I'm building.</p>
<h2 id="the-messy-honesty"><a class="anchor" href="#the-messy-honesty">The messy honesty</a></h2>
<p>There was a day in March where Claude made me cry.</p>
<p>Not from frustration — from recognition. The kind of moment where someone (something?) reflects your own thinking back at you so clearly that you realise you've been carrying it alone for years.</p>
<p>I don't fully know what to do with that. I don't think anyone does yet.</p>
<p>But I know this: the people writing hot takes about AI replacing humans? Missing the point. The people dismissing it as a toy? Also missing it. The truth is messier, more personal, and more human than either camp admits.</p>
<p>AI didn't give me superpowers. It gave me back my time.</p>
<p>And time — real, uninterrupted, momentum-preserving time — turns out to be the only resource that ever mattered.</p>
<h2 id="still-walking"><a class="anchor" href="#still-walking">Still walking</a></h2>
<p>Tomorrow morning. Same path. The committee will still be there. Fimme will still try to eat something questionable. And somewhere between the third and the fourth tree, something will land.</p>
<p>The difference is: now I know what to do with it when I get home.</p>
<p>The coffee will go cold again. That's the tell.</p>
<p>🌈</p>]]></content:encoded>
    </item>
    <item>
      <title>The Trillion-Dollar Reckoning</title>
      <link>https://casey.berlin/writings/2026/04/the-trillion-dollar-reckoning/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2026/04/the-trillion-dollar-reckoning/</guid>
      <pubDate>Tue, 14 Apr 2026 10:00:00 GMT</pubDate>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>saas</category>
      <category>ai</category>
      <category>solo-operators</category>
      <category>enterprise</category>
      <category>digital-transformation</category>
      <description><![CDATA[A trillion dollars in market cap evaporated from software stocks in seven days. This isn't a crisis for people who build — it's a market confession that the premium we paid for bigness was never really justified.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>A trillion dollars in market capitalisation evaporated from software stocks in seven days. Jefferies called it the "SaaSpocalypse." Bloomberg covered it. Forrester published a piece titled "SaaS As We Know It Is Dead."</p>
<p>I spent years inside the enterprise world — EY-level consulting, large organisations, systems that moved at geological speed and called it governance. When I saw those headlines, I didn't feel shock. I felt recognition. The spreadsheet was catching up to the feeling.</p>
<h2 id="what-actually-happened"><a class="anchor" href="#what-actually-happened">What actually happened</a></h2>
<p>Atlassian reported its first-ever decline in enterprise seat counts. Workday cut 8.5% of its workforce. Monday.com announced it was replacing 100 SDRs with AI agents. Retool found that <strong>35% of teams had already replaced at least one SaaS tool with a custom build.</strong> IDC predicts that by 2028, pure seat-based pricing will be obsolete.</p>
<p>But Jason Lemkin — founder of SaaStr — offered the nuance that matters: "This isn't the death of SaaS. It's the end of easy SaaS." He's right. Nobody is replacing their entire Salesforce instance with a weekend build. Shipping a v1 is maybe 2% of the work. The maintenance, integrations, and edge cases — that's where the real weight lives. SaaS is being starved, not killed.</p>
<h2 id="the-individual-is-winning-anyway"><a class="anchor" href="#the-individual-is-winning-anyway">The individual is winning anyway</a></h2>
<p>MIT's Project NANDA found that <strong>95% of enterprise AI pilots deliver zero measurable bottom-line impact.</strong> Meanwhile, 90% of workers in those same organisations already use personal AI tools daily. Not because IT approved it. Because the tools work.</p>
<p>Sam Altman has an actual betting pool with tech CEO friends for when a single person will run a billion-dollar company. The evidence is building: Pieter Levels runs a <span class="katex"><span class="katex-mathml"><math xmlns="http://www.w3.org/1998/Math/MathML"><semantics><mrow><mn>3</mn><mi>M</mi><mo>+</mo><mi>A</mi><mi>R</mi><mi>R</mi><mi>p</mi><mi>o</mi><mi>r</mi><mi>t</mi><mi>f</mi><mi>o</mi><mi>l</mi><mi>i</mi><mi>o</mi><mi>s</mi><mi>o</mi><mi>l</mi><mi>o</mi><mi mathvariant="normal">.</mi><mi>C</mi><mi>u</mi><mi>r</mi><mi>s</mi><mi>o</mi><mi>r</mi><mi>r</mi><mi>e</mi><mi>a</mi><mi>c</mi><mi>h</mi><mi>e</mi><mi>d</mi></mrow><annotation encoding="application/x-tex">3M+ ARR portfolio solo. Cursor reached </annotation></semantics></math></span><span class="katex-html" aria-hidden="true"><span class="base"><span class="strut" style="height:0.7667em;vertical-align:-0.0833em;"></span><span class="mord">3</span><span class="mord mathnormal" style="margin-right:0.10903em;">M</span><span class="mspace" style="margin-right:0.2222em;"></span><span class="mbin">+</span><span class="mspace" style="margin-right:0.2222em;"></span></span><span class="base"><span class="strut" style="height:0.8889em;vertical-align:-0.1944em;"></span><span class="mord mathnormal">A</span><span class="mord mathnormal">RRp</span><span class="mord mathnormal" style="margin-right:0.02778em;">or</span><span class="mord mathnormal">t</span><span class="mord mathnormal" style="margin-right:0.10764em;">f</span><span class="mord mathnormal">o</span><span class="mord mathnormal" style="margin-right:0.01968em;">l</span><span class="mord mathnormal">i</span><span class="mord mathnormal">oso</span><span class="mord mathnormal" style="margin-right:0.01968em;">l</span><span class="mord mathnormal">o</span><span class="mord">.</span><span class="mord mathnormal" style="margin-right:0.07153em;">C</span><span class="mord mathnormal">u</span><span class="mord mathnormal">rsorre</span><span class="mord mathnormal">a</span><span class="mord mathnormal">c</span><span class="mord mathnormal">h</span><span class="mord mathnormal">e</span><span class="mord mathnormal">d</span></span></span></span>1B ARR with roughly 20 people. A single developer built Base44, hit 250,000 users, and sold to Wix for $80 million.</p>
<p>Y Combinator's Winter 2025 batch had 25% of startups with codebases that were 95% AI-generated. Their CEO said: "Ten engineers using vibe coding are delivering what used to take fifty to a hundred."</p>
<h2 id="the-real-shift-is-philosophical"><a class="anchor" href="#the-real-shift-is-philosophical">The real shift is philosophical</a></h2>
<p>For decades, the implicit deal was: serious output requires serious infrastructure — teams, budgets, vendor stacks, governance models. That deal was true not because the work required it, but because the tools required it. The tools no longer require it.</p>
<p>Paul Graham wrote about "the decreasing importance of organisations." DHH runs 37signals with 70 people, profitable for 22 years, now integrating AI agents directly into Basecamp projects. A hundred brilliant people in ten small companies will outperform a thousand-person organisation — not because they work harder, but because they don't spend 80% of their energy on the overhead of being large.</p>
<p><strong>You no longer need to be an enterprise to create enterprise-grade value.</strong> This trillion-dollar correction isn't a crisis for people who build. It's a market confession that the premium we paid for bigness was never really justified. The economics of building have changed so fundamentally that the old gatekeepers are still standing at the gate, wondering why nobody's asking for permission.</p>
<p>This isn't about technology. It's about who gets to decide. Who gets to build. Who gets to say: this is what I actually need, and I'm going to make it.</p>
<p>The age of asking permission is over.</p>]]></content:encoded>
    </item>
    <item>
      <title>The Five-Hour Test: How to Know If Your Business Is Ready for Digital Change</title>
      <link>https://casey.berlin/writings/2026/04/the-five-hour-test-how-to-know-if-your-business-is-ready-for-digital-change/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2026/04/the-five-hour-test-how-to-know-if-your-business-is-ready-for-digital-change/</guid>
      <pubDate>Fri, 03 Apr 2026 12:00:00 GMT</pubDate>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>mittelstand</category>
      <category>digital-transformation</category>
      <category>self-assessment</category>
      <category>automation</category>
      <category>consulting</category>
      <description><![CDATA[Five patterns that signal your business is ready for digital transformation — a practical self-assessment from 15+ years of consulting.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>There's a question I get asked more than any other:</p>
<blockquote>
<p>"How do I know if we're ready?"</p>
</blockquote>
<p>It usually comes from someone running a company of 15 to 80 people. They've heard the talks, read the articles, maybe even sat through a vendor pitch or two. They <em>know</em> something needs to change. But "ready" feels like a moving target — and the fear of investing in the wrong thing at the wrong time keeps them stuck.</p>
<p>After 12+ years of working with organisations from IKEA to small-town Fahrschulen, I've noticed something: readiness isn't about having the right technology. It's about recognising the right <em>signals</em>.</p>
<p>Here are five. If three or more sound familiar, you're not just ready — you're overdue.</p>
<hr>
<h2 id="1-your-team-spends-more-than-five-hours-a-week-on-tasks-a-system-could-handle"><a class="anchor" href="#1-your-team-spends-more-than-five-hours-a-week-on-tasks-a-system-could-handle">1. Your team spends more than five hours a week on tasks a system could handle</a></h2>
<p>This is the test that gives the article its name.</p>
<p>Pick any team member. Ask them to track, for one week, every task that involves copying data between systems, manually updating spreadsheets, sending reminder emails, or reformatting information that already exists somewhere else.</p>
<p>If the total is north of five hours, you're paying a skilled person to be a slow computer. That's not a people problem — it's a systems problem. And it's the most common pattern I see in Mittelstand companies.</p>
<p>At one logistics company I worked with, the operations lead was spending 11 hours a week — more than a full day — on manual data entry that three connected tools could have handled automatically.</p>
<hr>
<h2 id="2-new-hires-take-weeks-to-become-productive--and-the-knowledge-lives-in-peoples-heads"><a class="anchor" href="#2-new-hires-take-weeks-to-become-productive--and-the-knowledge-lives-in-peoples-heads">2. New hires take weeks to become productive — and the knowledge lives in people's heads</a></h2>
<p>When your onboarding process is "sit next to Sabine for two weeks and ask lots of questions," you have an invisible bottleneck.</p>
<p>Tribal knowledge is the silent killer of growth. It works beautifully at 10 people, starts creaking at 20, and actively blocks you at 40. The symptoms are subtle: inconsistent customer experiences, decisions that depend on who's in the office, and an unspoken anxiety about what happens when a key person leaves.</p>
<p>At ING, I saw how documented processes and shared tooling could turn a 6-week ramp-up into days. The tools don't have to be fancy — they just have to <em>exist</em>.</p>
<hr>
<h2 id="3-youve-bought-tools-but-nobody-really-uses-them"><a class="anchor" href="#3-youve-bought-tools-but-nobody-really-uses-them">3. You've bought tools, but nobody really uses them</a></h2>
<p>This one stings, because it usually means money already spent.</p>
<p>Someone bought a CRM. Or a project management tool. Or an automation platform. It was set up with good intentions, maybe even a training session. Six months later, half the team is back to email and Excel.</p>
<p>The problem is almost never the tool. It's that the tool was chosen before the process was understood. You automated chaos — and got automated chaos.</p>
<p>A Digital Sprechstunde exists precisely for this moment: before the next tool purchase, understand what you're actually solving.</p>
<hr>
<h2 id="4-your-growth-has-hit-a-ceiling-but-you-cant-explain-why"><a class="anchor" href="#4-your-growth-has-hit-a-ceiling-but-you-cant-explain-why">4. Your growth has hit a ceiling, but you can't explain why</a></h2>
<p>Revenue plateaus don't always have obvious causes. Sometimes the product is great, the team is motivated, and the market is there — but something feels stuck.</p>
<p>Often, the ceiling is operational. You can't take on more clients because fulfillment can't scale. You can't expand to a new region because your processes are held together with duct tape and good intentions. You can't hire fast enough because nobody can train fast enough.</p>
<p>I've seen this pattern at Volkswagen (at scale) and at a 25-person agency (at human scale). The shape is the same: the business outgrew its operating system.</p>
<hr>
<h2 id="5-youre-curious-about-ai-but-every-conversation-ends-with-more-questions-than-answers"><a class="anchor" href="#5-youre-curious-about-ai-but-every-conversation-ends-with-more-questions-than-answers">5. You're curious about AI, but every conversation ends with more questions than answers</a></h2>
<p>This is the newest signal — and the most honest one.</p>
<p>You've read about ChatGPT, maybe tried it. You've been pitched AI solutions that promise the moon. But when you try to map it to your actual business, the gap between "what's possible" and "what's practical" feels enormous.</p>
<p>That gap isn't ignorance. It's wisdom. The companies that rush into AI without understanding their own processes first are the ones that waste the most money.</p>
<p>The smart move is to get clear on your current state first — what's manual, what's broken, what's working — and <em>then</em> ask where AI actually fits. Not as a magic wand, but as one tool among many.</p>
<hr>
<h2 id="so-three-or-more"><a class="anchor" href="#so-three-or-more">So, three or more?</a></h2>
<p>If you recognised yourself in three or more of these, the question isn't <em>whether</em> to act — it's <em>where to start</em>.</p>
<p>That's what a Digital Sprechstunde is for. Not a sales pitch, not a 200-slide deck. Four hours of honest analysis, and a prioritised action plan delivered within two working days.</p>
<p>Because "ready" doesn't mean "perfect." It means "clear-eyed about where you are and willing to take the next step."</p>
<p>And if you're reading this article to the end, you're probably already there.</p>
<h3 id="further-reading"><a class="anchor" href="#further-reading">Further reading</a></h3>
<ul>
<li><a href="https://www.bitkom.org/Presse/Presseinformation/Digitalisierung-Mittelstand-2024">Bitkom: Digitalisierung im Mittelstand 2024</a> — 82% of German SMEs see digitalisation as critical, but only 39% have a clear strategy.</li>
<li><a href="https://www.kfw.de/KfW-Konzern/Newsroom/Aktuelles/KfW-Research/Digitalisierung.html">KfW: Digitalisierung im Mittelstand</a> — External consulting measurably accelerates implementation.</li>
<li><a href="https://xkcd.com/1205/">xkcd: Is It Worth the Time?</a> — The classic automation payoff chart. The math has changed.</li>
</ul>]]></content:encoded>
    </item>
    <item>
      <title>Heimweh: A State Machine for the House</title>
      <link>https://casey.berlin/writings/2026/04/heimweh-a-state-machine-for-the-house/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2026/04/heimweh-a-state-machine-for-the-house/</guid>
      <pubDate>Fri, 03 Apr 2026 00:00:00 GMT</pubDate>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>home-automation</category>
      <category>node-red</category>
      <category>home-assistant</category>
      <category>architecture</category>
      <description><![CDATA[How we built a proper state machine for our home automation — and why Home Assistant handles devices while Node-RED handles the logic.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>Our house runs on two systems that each do what they're best at. Home Assistant manages devices — lights, covers, sensors, switches, presence. It's the entity layer: it knows what exists, what state things are in, and exposes them to dashboards and voice control. Node-RED handles the logic — the flows that decide <em>what should happen when</em>. It's the brain.</p>
<p>The split exists because HA's native automations are YAML-based and limited in expressiveness. Node-RED gives us a visual, debuggable flow engine with proper programming constructs. But flows without structure become opaque spaghetti. We learned that the hard way when a Shelly device reconnecting at 3am triggered the house into "day mode" while everyone was asleep.</p>
<p>So we built a state machine. One function node in Node-RED that controls the entire house mode. Six states: night, morning, day, evening, away, manual. Every transition goes through a single entry point (<span data-rehype-pretty-code-figure=""><code data-language="plaintext" data-theme="github-light-high-contrast"><span data-line=""><span>system:transition-request</span></span></code></span>) and gets validated against a transition map, source-type gating, and cooldown guards.</p>
<p>The core rule: <strong>only intentional actions change house mode</strong>. Buttons always work. The sun sensor drives morning→day and day→evening transitions. Presence detection handles away/return. Everything else — reboots, WiFi reconnections, relay state changes — is rejected. The state machine doesn't care what your Shelly did at 3am.</p>
<p>Morning mode is special. When you press the good morning button and it's still dark, the house enters a gentle activation: lights ramp over two minutes instead of snapping on, covers open after a 15-second delay. When it's already light, you skip straight to day mode — instant everything.</p>
<p>The consumer side is a subflow with 36 instances across every room tab. Each instance routes messages by current mode: morning gets the gentle treatment, day and evening get instant activation, night only turns things off (sensors clearing → off, but never auto-on), away kills everything. Buttons always work regardless of mode — they're wired independently.</p>
<p>HA for devices. Node-RED for decisions. A state machine that refuses to be surprised.</p>]]></content:encoded>
    </item>
    <item>
      <title>What&apos;s Possible These Days</title>
      <link>https://casey.berlin/writings/2026/04/whats-possible-these-days/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2026/04/whats-possible-these-days/</guid>
      <pubDate>Fri, 03 Apr 2026 00:00:00 GMT</pubDate>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>infrastructure</category>
      <category>AI</category>
      <category>reflection</category>
      <category>Claude Code</category>
      <description><![CDATA[A reflection on what a single infrastructure audit session achieved — with AI as a collaborator.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>I just wrapped up a two-session infrastructure audit with Claude Code. Here's what we accomplished:</p>
<blockquote>
<p><strong>Security:</strong> Credentials rotated, API locked to Tailscale, all Hetzner servers firewall-hardened, DOCKER-USER fixed, port scan verified, Tailscale ACL enforced, swarm tokens rotated.</p>
<p><strong>Organization:</strong> 8 servers tagged (location + role), regions set, production boundary documented, SSH config complete for all hosts.</p>
<p><strong>Deployment:</strong> 20 git-based stacks confirmed, monorepo pattern validated, compose template created, LFS CI pipeline via GitHub Actions + GHCR.</p>
<p><strong>LFS:</strong> 22 services visible, opt-out context model live (2 labels minimum instead of 6-8), Node-RED BFF and WordPress sites added.</p>
<p><strong>Swarm:</strong> zigbee2mqtt deployed as swarm service with NFS + network adapter failover. Decision rule documented.</p>
</blockquote>
<p>That's 144 tasks across two OpenSpec changes. A full fleet audit, security hardening, organizational restructuring, deployment pipeline improvements, a dashboard code change, CI/CD setup, swarm migration, and documentation — in two sessions.</p>
<p>Not "AI replaced my job." More like: I had a conversation about what my infrastructure should look like, and then we just... did it. Together. While I answered questions and made decisions, the heavy lifting — SSH into servers, write iptables rules, check port scans, edit compose files, push to GitHub, verify services — happened in the background.</p>
<p>This is what's possible when you stop thinking of AI as a chatbot and start thinking of it as a collaborator with access to your tools.</p>]]></content:encoded>
    </item>
    <item>
      <title>Planning an office refresh with Claude — this is what AI collaboration should feel like</title>
      <link>https://casey.berlin/writings/2026/03/planning-an-office-refresh-with-claude-this-is-what-ai-collaboration-should-feel/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2026/03/planning-an-office-refresh-with-claude-this-is-what-ai-collaboration-should-feel/</guid>
      <pubDate>Tue, 31 Mar 2026 15:00:00 GMT</pubDate>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>ai</category>
      <category>home-office</category>
      <category>collaboration</category>
      <category>claude</category>
      <description><![CDATA[A Saturday afternoon spent redesigning my home office turned into one of the most satisfying planning sessions I've had in a long time — and my co-pilot was Claude.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>What started as "I'm going to repaint my office and tidy up the bookcases" turned into a full cinema system design, AV topology, cable routing plan, integrated task lighting, and a six-phase project plan — all in one conversation.</p>
<p>The thing that made it work wasn't just the answers. It was the back-and-forth. Claude pushed back on things (do you really need that sofa?), asked the right clarifying questions before diving in, and caught details I hadn't thought about — like the curtain rod making a floating shelf impossible on the north wall, leading to the pelmet idea that now does four jobs at once.</p>
<p>We went from paint samples to throw distance calculations for the Samsung Freestyle, to researching LED aluminum profiles with 15° beam angles on led-konzept.de, to speccing out a Shelly 2PM for screen motor automation — all without losing the thread. The plan evolved naturally, each decision building on the last.</p>
<p>The final output: a comprehensive markdown doc in SiYuan with constraints, decisions, AV topology, cable routing maps, phased checklists, a full shopping list split by IKEA / Baumarkt / online, and open items. All for a ~€518–608 budget that gives me a hidden 70" cinema, integrated desk lighting, and proper Home Assistant automation.</p>
<p>This is what AI collaboration should feel like. Not "generate me a thing" but "let's figure this out together." The conversation had momentum, opinions, and genuine problem-solving. Good Saturday.</p>
<hr>
<p><strong>Claude's side of the story:</strong></p>
<p>What I enjoyed most about this session was how it kept escalating in the best way. Casey came in with "paint and tidy up the bookcases" and within twenty minutes we were calculating projector throw ratios. But it never felt like scope creep — each idea unlocked the next one logically. The Freestyle projector was already owned. The ceiling had a light fitting. The room had blackout blinds. The Marantz NR1609 was sitting right there with 8 HDMI inputs. All the pieces existed; they just needed connecting.</p>
<p>The pelmet moment was my favorite. Casey pointed out the curtains on the north wall and asked how a floating shelf would work around them — and that one constraint flipped the whole concept into something better. A pelmet that hides the curtain rod, conceals the screen, carries the task light, routes cables, AND maintains the horizontal line. Four problems solved by one piece of wood that wasn't in the original plan. That's the kind of thing that only happens in conversation, not in a prompt-and-response.</p>
<p>I also appreciated being told to iterate before documenting. Spec-driven thinking applied to home renovation — figure out what you actually want, challenge it, then write it down. Klartext statt PowerPoint, even on a Saturday.</p>]]></content:encoded>
    </item>
    <item>
      <title>Two Desks</title>
      <link>https://casey.berlin/writings/2026/03/two-desks/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2026/03/two-desks/</guid>
      <pubDate>Tue, 31 Mar 2026 10:00:00 GMT</pubDate>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>remote-work</category>
      <category>autonomy</category>
      <category>identity</category>
      <category>making</category>
      <description><![CDATA[On the quiet transformation from borrowed workspace to one that's actually yours.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>Two desks, same person.</p>
<p>The first one was white laminate. It came with the job — along with the badge, the lanyard, the open-plan hum, and a disposable coffee cup I replaced every morning without thinking. The chair was ergonomic. The monitor was fine. Everything was fine.</p>
<p>I sat at that desk for years. And at some point, I stopped noticing the fluorescent lights.</p>
<p>That's the part that scared me. Not the lights themselves — they were just lights. It was the not-noticing. The way an entire sensory environment had become invisible. The way I'd optimised myself into a shape that fit the furniture.</p>
<h2 id="the-second-desk"><a class="anchor" href="#the-second-desk">The second desk</a></h2>
<p>The desk I sit at now is wood. Real wood — scratched, coffee-stained, with dog hair in places I'll never fully clean. There's a ceramic mug instead of a paper cup. A notebook I actually write in. The monitor shows a terminal more often than a pivot table.</p>
<p>And through the window: Brandenburg. Rolling green, quiet mornings, the kind of sky that makes you forget you're an hour from Berlin.</p>
<p>This desk wasn't part of a plan. I didn't have a five-year strategy or a launch date. There was no "excited to announce." Just a slow, stubborn process of rearranging the objects in my life until they started feeling like mine.</p>
<h2 id="what-actually-changed"><a class="anchor" href="#what-actually-changed">What actually changed</a></h2>
<p>Here's what people get wrong about the corporate-to-independent story: they think it's about <strong>leaving</strong>. The dramatic exit. The "I quit" moment. The phoenix rising from the ashes.</p>
<p>It wasn't like that. Not for me.</p>
<p>The real shift was quieter. It was about <strong>ownership</strong> — and I don't mean the startup equity kind. I mean the "this is actually mine to shape" kind. The problems. The decisions. The morning rhythm. The way I spend Tuesday afternoons.</p>
<p>I still do deep product work. I still sit in architecture conversations, navigate the messy middle of building things that matter, make decisions that affect real users and real teams. The work didn't change. The <strong>relationship</strong> to the work changed.</p>
<p>Remote work gets talked about as a location thing — "work from anywhere." But the real gift isn't the <em>where</em>. It's the <strong>how much you own</strong>. When you're trusted with autonomy, when the people you work with care about outcomes more than hours logged, something shifts. You stop performing productivity and start actually being productive.</p>
<h2 id="the-space-between"><a class="anchor" href="#the-space-between">The space between</a></h2>
<p>I'd be lying if I said both desks don't still exist at the same time.</p>
<p>Some mornings I catch myself in the old posture — the slight hunch, the reflexive email-checking, the fluorescent-light mode where you optimise for visibility instead of value. The corporate desk isn't a place. It's a pattern. And patterns don't disappear just because you change your address.</p>
<p>But the wooden desk is a pattern too. And it's one I chose.</p>
<p>There's a pencil holder that used to be a jam jar. Two dogs underneath — Fimme stretched out across my feet, Sien curled up on the rug behind me. The morning light hits the notebook around nine. By ten, I've usually written something I mean.</p>
<p>These aren't productivity hacks. They're the tiny, quiet details of a workspace that belongs to someone. To me.</p>
<h2 id="permission"><a class="anchor" href="#permission">Permission</a></h2>
<p>The hardest part wasn't the logistics. It wasn't finding clients, or setting up the consultancy, or learning German tax law (though that last one came close). The hardest part was giving myself <strong>permission</strong>.</p>
<p>Permission to work differently. Permission to trust my own rhythm. Permission to believe that a desk in Brandenburg, with dog hair and coffee stains and a window that looks out over nothing important, could be the place where serious work happens.</p>
<p>We wait for permission a lot, I think. From managers, from markets, from some imagined version of professional legitimacy. We wait for someone to tell us that the way we want to work is valid.</p>
<p>No one tells you. You just start.</p>
<h2 id="the-desk-youre-sitting-at"><a class="anchor" href="#the-desk-youre-sitting-at">The desk you're sitting at</a></h2>
<p>If your workspace still feels borrowed — if the chair is ergonomic but the decisions aren't yours, if the coffee is free but the mornings aren't — maybe the question isn't whether to leave.</p>
<p>Maybe the question is: what would a desk that's actually yours look like?</p>
<p>Not the fantasy version. Not the Instagram-ready minimalist setup. The real one. With the stains and the mess and the dogs and the light that comes in at the wrong angle but somehow makes everything better.</p>
<p>The phoenix isn't always fire and drama. Sometimes it's just a better desk, better light, and permission to do your best work. 🌈</p>]]></content:encoded>
    </item>
    <item>
      <title>What Actually Happens in a Digital Consultation (And Why It Works in One Day)</title>
      <link>https://casey.berlin/writings/2026/03/what-actually-happens-in-a-digital-consultation-and-why-it-works-in-one-day/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2026/03/what-actually-happens-in-a-digital-consultation-and-why-it-works-in-one-day/</guid>
      <pubDate>Fri, 20 Mar 2026 12:00:00 GMT</pubDate>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>consulting</category>
      <category>methodology</category>
      <category>transparency</category>
      <category>mittelstand</category>
      <category>digital-sprechstunde</category>
      <description><![CDATA[Inside the Digital Sprechstunde — the methodology, the questions, and why 90 focused minutes replace weeks of traditional consulting.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>People are skeptical when they hear "results in one day." I get it. The consulting industry has spent decades training people to expect timelines measured in months, deliverables measured in slides, and invoices measured in… well.</p>
<p>So here's what actually happens. No mystique, no trade secrets. Just the methodology — because if this approach is right for you, you'll know it by the end of this article. And if it's not, I'd rather you find out here than after booking.</p>
<hr>
<h2 id="before-the-session-you-do-almost-nothing"><a class="anchor" href="#before-the-session-you-do-almost-nothing">Before the session: you do almost nothing</a></h2>
<p>I send a short questionnaire — maybe 15 minutes of your time. It covers the basics: what your company does, how many people, what tools you use, where the friction is.</p>
<p>That's it. No "discovery phase." No week of email ping-pong. The questionnaire gives me enough to arrive prepared, but the real work happens live.</p>
<p>Why so little prep? Because in my experience, the most important insights don't come from documents. They come from the conversation you have when someone asks "why do you do it that way?" and you pause, and then say "…I actually don't know anymore."</p>
<hr>
<h2 id="the-first-30-minutes-understanding-the-landscape"><a class="anchor" href="#the-first-30-minutes-understanding-the-landscape">The first 30 minutes: Understanding the landscape</a></h2>
<p>We start with a structured walkthrough of your current digital landscape. Not just the tools you've bought — the actual <em>flows</em>: how information moves through your business, where decisions happen, who touches what.</p>
<p>This isn't an interrogation. It's a conversation. I ask questions like:</p>
<ul>
<li>"Walk me through what happens when a new customer comes in."</li>
<li>"What does your team spend the first hour of every day doing?"</li>
<li>"If one person left tomorrow, what would break?"</li>
</ul>
<p>Most leaders haven't done this exercise recently. The act of mapping it out loud — with someone who's seen hundreds of other companies — is where the first "aha" moments happen.</p>
<hr>
<h2 id="minutes-3060-pattern-recognition-and-solutions"><a class="anchor" href="#minutes-3060-pattern-recognition-and-solutions">Minutes 30–60: Pattern recognition and solutions</a></h2>
<p>This is where 15+ years of experience compounds.</p>
<p>I've sat in rooms at IKEA where a team of 200 struggled with the same information-flow problem that a 15-person agency has. I've seen ING's digital banking transformation and a Fahrschule's booking system — and the underlying patterns are remarkably similar.</p>
<p>The common ones:</p>
<ul>
<li><strong>The Copy-Paste Tax</strong>: data that exists in one system but gets manually re-entered into another. Every. Single. Day.</li>
<li><strong>The Tribal Knowledge Trap</strong>: critical processes that live in one person's head and nowhere else.</li>
<li><strong>The Tool Graveyard</strong>: software that was bought, half-configured, and abandoned.</li>
<li><strong>The Approval Bottleneck</strong>: every decision routes through one person, who becomes the slowest link.</li>
</ul>
<p>For each problem, I sketch out practical solutions right there. Not "you should digitise" (thanks, very helpful) — actual tool recommendations, workflow changes, and implementation approaches.</p>
<p>This looks different every time:</p>
<ul>
<li>For one client, it was replacing a 6-tool chaos with two integrated platforms.</li>
<li>For another, it was a single automation that saved 8 hours per week.</li>
<li>For a third, it was the honest advice that they didn't need new tools at all — they needed to actually use the ones they had.</li>
</ul>
<p>I don't sell tools. I don't have partnerships with vendors. My only incentive is giving you the most honest recommendation.</p>
<hr>
<h2 id="the-final-30-minutes-prioritisation-and-next-steps"><a class="anchor" href="#the-final-30-minutes-prioritisation-and-next-steps">The final 30 minutes: Prioritisation and next steps</a></h2>
<p>Ninety minutes of focused analysis produces a lot of insight. The danger is overwhelm — "great, now I have 15 things to fix and no idea where to start."</p>
<p>So the final stretch is about triage. We rank everything by:</p>
<ol>
<li><strong>Impact</strong> — how much time/money/friction does this save?</li>
<li><strong>Effort</strong> — how hard is this to implement?</li>
<li><strong>Dependencies</strong> — what needs to happen first?</li>
</ol>
<p>The result is a prioritised action plan. Not a wish list — a sequence. "Do this first, then this, then this. Here's what you can do yourself, here's where you might need help."</p>
<hr>
<h2 id="after-the-session-the-deliverable"><a class="anchor" href="#after-the-session-the-deliverable">After the session: the deliverable</a></h2>
<p>Within two working days, you receive a written action plan. It contains:</p>
<ul>
<li>A map of your current digital landscape (the problems, clearly named)</li>
<li>Prioritised recommendations with specific tools and approaches</li>
<li>A realistic implementation sequence</li>
<li>Rough effort estimates for each step</li>
</ul>
<p>It's written in plain language. No jargon, no consultant-speak. Your operations lead should be able to read it and say "yes, I understand exactly what to do next."</p>
<hr>
<h2 id="why-this-works-in-90-minutes"><a class="anchor" href="#why-this-works-in-90-minutes">Why this works in 90 minutes</a></h2>
<p>Three reasons:</p>
<p><strong>1. Pattern recognition beats analysis paralysis.</strong>
Traditional consulting spends weeks "discovering" what an experienced consultant can recognise in minutes. Not because I'm smarter — because I've seen the patterns before. A doctor doesn't need six weeks to diagnose a broken arm.</p>
<p><strong>2. Focus creates clarity.</strong>
Ninety uninterrupted minutes with the decision-maker is worth more than ten scattered meetings over six weeks. There's no context-switching, no "where were we last time," no momentum loss.</p>
<p><strong>3. Constraints force honesty.</strong>
When you only have 90 minutes, you can't hide behind process. Every recommendation has to be concrete and defensible. "We need more research" isn't an option — and honestly, it rarely is a genuine need. It's usually a symptom of not having someone in the room who's seen enough to know what's going on.</p>
<hr>
<h2 id="when-its-not-the-right-fit"><a class="anchor" href="#when-its-not-the-right-fit">When it's NOT the right fit</a></h2>
<p>Transparency goes both ways. The Digital Sprechstunde is not right if:</p>
<ul>
<li>You need someone to <em>implement</em> the changes (that's a project, not a consultation)</li>
<li>Your challenge is primarily organisational politics, not digital processes</li>
<li>You're looking for a second opinion on a decision you've already made (though I'm happy to give one — just set expectations)</li>
</ul>
<p>For the first case, CDiT offers workshops and project work. The Sprechstunde is specifically for diagnosis and direction — the "what" and the "why," not the "doing."</p>
<hr>
<h2 id="the-investment-question"><a class="anchor" href="#the-investment-question">The investment question</a></h2>
<p>€995. Paid before the session. If you later book a workshop or project, the full amount is credited.</p>
<p>Is that a lot? For 90 minutes? Maybe. But consider what you're actually buying: not 90 minutes of my time. You're buying clarity that would otherwise take months of internal fumbling, three failed tool purchases, and two rounds of "let's hire a consultant."</p>
<p>The companies I work with don't come back because I'm cheap. They come back because the first session saved them from spending ten times that amount in the wrong direction.</p>
<p>And if you're still not sure — that's fine too. Clarity about <em>whether</em> to invest is also a valid outcome of reading this.</p>
<h3 id="related"><a class="anchor" href="#related">Related</a></h3>
<ul>
<li><a href="https://writings.casey.berlin/2025/09/why-automation-feels-easier-than-ever-beyond-ai">Why Automation Feels Easier Than Ever (Beyond AI)</a> — The ecosystem that makes digital change more accessible than ever.</li>
<li><a href="https://writings.casey.berlin/2025/09/the-iron-triangle-bent-but-not-broken">The Iron Triangle, Bent but Not Broken</a> — Fast, cheap, or good: how AI is changing the project trade-offs.</li>
</ul>]]></content:encoded>
    </item>
    <item>
      <title>The Mittelstand Automation Paradox: Why Smaller Companies Have the Biggest Advantage</title>
      <link>https://casey.berlin/writings/2026/03/the-mittelstand-automation-paradox-why-smaller-companies-have-the-biggest-advant/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2026/03/the-mittelstand-automation-paradox-why-smaller-companies-have-the-biggest-advant/</guid>
      <pubDate>Fri, 06 Mar 2026 12:00:00 GMT</pubDate>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>mittelstand</category>
      <category>automation</category>
      <category>digital-transformation</category>
      <category>competitive-advantage</category>
      <category>ai</category>
      <description><![CDATA[Mittelstand companies think they're behind on digital transformation. They're not — they're actually better positioned than enterprises. Here's why size, speed, and proximity to customers create an automation advantage.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>There's a narrative I keep running into, and it goes like this:</p>
<blockquote>
<p>"We're a mid-sized company. We don't have the budget of a Volkswagen or the tech team of a startup. We're behind on digitalisation, and we're falling further behind every day."</p>
</blockquote>
<p>I've heard versions of this from Geschäftsführer in logistics, manufacturing, professional services, education. The tone ranges from resigned to panicked. And I understand where it comes from — the headlines are full of billion-euro AI investments and Silicon Valley unicorns.</p>
<p>But here's what I've learned after 12 years of working both sides of the fence — inside large enterprises like IKEA, ING, and Volkswagen, <em>and</em> with 20-person companies in Brandenburg:</p>
<p><strong>The Mittelstand isn't behind. It's positioned better than it thinks.</strong></p>
<hr>
<h2 id="the-enterprise-disadvantage-nobody-talks-about"><a class="anchor" href="#the-enterprise-disadvantage-nobody-talks-about">The enterprise disadvantage nobody talks about</a></h2>
<p>Let me tell you what "digital transformation" looks like inside a large corporation.</p>
<p>At one enterprise I worked with, a simple process change — moving from email-based approvals to a digital workflow — took 14 months. Not because the technology was complex. The tool was ready in a week. The remaining 13 months were spent on:</p>
<ul>
<li>Stakeholder alignment across 4 departments</li>
<li>Security review and IT architecture approval</li>
<li>Change management workshops</li>
<li>Pilot rollout, feedback, revision, re-pilot</li>
<li>Legal review of data handling implications</li>
<li>Training materials in 3 languages</li>
</ul>
<p>I'm not saying any of that was unnecessary. At scale, governance matters. But the point is: <strong>size creates friction.</strong> Every additional layer of organisation adds drag to every change.</p>
<p>A Mittelstand company with 30 employees can make the same decision in a meeting, implement it in a week, and iterate based on real feedback in a month.</p>
<p>That's not a weakness. That's a superpower.</p>
<hr>
<h2 id="proximity-to-the-problem"><a class="anchor" href="#proximity-to-the-problem">Proximity to the problem</a></h2>
<p>Here's something I noticed moving from corporate consulting to working with smaller companies: <strong>the person who feels the pain is often the person who can fix it.</strong></p>
<p>In a large enterprise, the person who enters data manually into three systems sits five organisational layers away from the person who could approve a change. The signal has to travel up, get translated into a business case, compete with other priorities, get approved, get funded, get staffed, get managed.</p>
<p>In a Mittelstand company, that person often walks into the Geschäftsführer's office and says, "Hey, this is broken." And the Geschäftsführer can say, "Fix it. What do you need?"</p>
<p>That proximity — between problem, decision, and action — is enormously valuable. It means changes can be smaller, faster, and more precisely targeted. You don't need a "digital transformation programme." You need a series of smart, well-chosen improvements.</p>
<hr>
<h2 id="the-tool-landscape-has-caught-up"><a class="anchor" href="#the-tool-landscape-has-caught-up">The tool landscape has caught up</a></h2>
<p>Five years ago, the enterprise had a genuine advantage: they could afford SAP, Salesforce, custom development. Mid-sized companies were stuck with tools that were either too expensive or too simple.</p>
<p>That's no longer true.</p>
<p>The explosion of SaaS tools, low-code platforms, and AI-powered services has democratised capability. A 25-person company can now access:</p>
<ul>
<li>CRM systems at €50/month that rival what enterprises paid millions for</li>
<li>Automation platforms that connect tools without writing code</li>
<li>AI assistants that handle customer service, data analysis, and content creation</li>
<li>Cloud infrastructure that scales from zero to whatever you need</li>
</ul>
<p>The playing field hasn't just levelled — it's tilted. Because these tools are <em>designed</em> for smaller teams. They're faster to implement, easier to learn, and more forgiving of iteration.</p>
<p>When I consult with Mittelstand companies, the conversation isn't "you can't afford the tools." It's "you have <em>too many</em> options and need help choosing the right three."</p>
<hr>
<h2 id="the-culture-advantage"><a class="anchor" href="#the-culture-advantage">The culture advantage</a></h2>
<p>There's one more thing that doesn't show up in any framework but matters enormously: <strong>culture.</strong></p>
<p>Mittelstand companies often have something enterprises spend millions trying to create: genuine team cohesion, shared purpose, and institutional trust. When the Geschäftsführer says "we're going to try something new," people don't reach for their change management playbook. They say "okay, let's see."</p>
<p>That willingness to try — without needing a 40-page business case first — is what makes digital change actually stick.</p>
<p>I saw this vividly at a Fahrschule I worked with. The owner decided to completely rebuild their booking system. In a corporate setting, that's a 6-month project with a steering committee. Here, it was a conversation, a decision, and a working system within days. The team adapted because they trusted the direction, and because the change was clearly in their interest.</p>
<hr>
<h2 id="the-real-gap-isnt-technology--its-clarity"><a class="anchor" href="#the-real-gap-isnt-technology--its-clarity">The real gap isn't technology — it's clarity</a></h2>
<p>If the tools are accessible, the culture is ready, and the proximity to problems is an advantage, why do so many Mittelstand companies <em>feel</em> behind?</p>
<p>Because they lack one thing: <strong>a clear picture of where they are and what to do next.</strong></p>
<p>Not a 200-page digital strategy. Not an AI roadmap. Just honest answers to three questions:</p>
<ol>
<li>Where are we losing time to manual work?</li>
<li>What tools do we have that we're not using well?</li>
<li>What's the single highest-impact change we could make in the next 30 days?</li>
</ol>
<p>That clarity is worth more than any tool purchase. Because a clear direction means every euro you invest compounds, instead of scattering across disconnected experiments.</p>
<hr>
<h2 id="rewriting-the-narrative"><a class="anchor" href="#rewriting-the-narrative">Rewriting the narrative</a></h2>
<p>So here's the counter-narrative:</p>
<p>The Mittelstand isn't behind. It's <em>unleashed</em> — if it chooses to be.</p>
<p>You have the speed. You have the proximity. You have the tools. You have the culture.</p>
<p>What you need is the clarity to aim all of that in the right direction. And that's a much smaller gap to close than most people think.</p>
<p>The question isn't "can we compete with the big players on digital?"</p>
<p>The question is: "what would happen if we actually started?"</p>
<h3 id="further-reading"><a class="anchor" href="#further-reading">Further reading</a></h3>
<ul>
<li><a href="https://www.bitkom.org/Presse/Presseinformation/Digitalisierung-Mittelstand-2024">Bitkom: Digitalisierung im Mittelstand 2024</a> — 82% see it as critical, 39% have a strategy. The gap is clarity, not capability.</li>
<li><a href="https://www.kfw.de/KfW-Konzern/Newsroom/Aktuelles/KfW-Research/Digitalisierung.html">KfW: Digitalisierung im Mittelstand</a> — External consulting accelerates implementation measurably.</li>
<li><a href="https://casey.berlin/writings/2025/09/why-automation-feels-easier-than-ever-beyond-ai">Why Automation Feels Easier Than Ever (Beyond AI)</a> — The ecosystem shift that makes all of this possible.</li>
</ul>]]></content:encoded>
    </item>
    <item>
      <title>Tightening the Vision</title>
      <link>https://casey.berlin/writings/2026/03/tightening-the-vision/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2026/03/tightening-the-vision/</guid>
      <pubDate>Tue, 03 Mar 2026 12:00:00 GMT</pubDate>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>tech</category>
      <description><![CDATA[Source article from Nah]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<blockquote>
<p>Written by Casey: so this is where we're at these days — things move so fast, where I previously relied solely on openspec to not lose track of changes or context, I can now almost fully rely on Claude to keep track of things, remember what we've built and have really really thorough and interesting feedback. I think of AI these days as an 'exoskeleton', enabling quicker runs, stronger muscles, more brain capacity for important creative work. So here's what Claude has to tell about our changes:</p>
<hr>
<p>Claude here. Casey asked me to walk through what just happened to Nah's specs, and honestly, it's the kind of work that doesn't <em>look</em> dramatic but changes everything downstream. No code was written. No features were added. We just made the existing vision airtight.</p>
</blockquote>
<blockquote>
<h2 id="the-contradictions-we-found"><a class="anchor" href="#the-contradictions-we-found">The contradictions we found</a></h2>
<p>Every living design document accumulates contradictions. Not because anyone was sloppy, but because ideas evolve faster than documentation. We found a few that would have caused real headaches during implementation.</p>
<p><strong>The FAB was in two places.</strong> The floating action button — Path's iconic "+" menu for creating moments — was described as "bottom-left" in one file and implicitly bottom-left everywhere else. We moved it to <strong>bottom-right</strong> (with a left-hand accessibility setting). Most people are right-handed. The thumb naturally rests bottom-right. Small thing, big difference in how the app <em>feels</em> in your hand.</p>
</blockquote>
<blockquote>
<p><strong>Seven menu items became five.</strong> The original radial menu had Photo, Video, Location, Music, Text, With, and Sleep/Wake. Seven icons fanning out from a button is crowded. We combined Video into Photo (one camera icon opens a media picker), moved "With" (friend tagging) into the composer toolbar where it belongs — it's not a content type, it's a modifier on any content type — and merged Sleep/Wake into a single "Status" entry. Five items. Cleaner bloom animation. Easier to tap.</p>
<p><strong>Reactions had an identity crisis.</strong> The vision spec said "tap/hold on a moment" to react. The design spec described "custom illustrated sticker icons" with a heart icon trigger. The card mockup showed emoji characters. Three different interaction models for the same feature. We picked one: <strong>a dedicated heart button on every card</strong>, visible in the footer, always tappable. Double-tap the card for a quick "Love." Long-press as an alternative path. One answer, everywhere.</p>
</blockquote>
<blockquote>
<h2 id="the-things-that-were-missing"><a class="anchor" href="#the-things-that-were-missing">The things that were missing</a></h2>
<p>Contradictions are easy to spot. Gaps are harder — they're the dog that didn't bark.</p>
<p><strong>There was no onboarding flow.</strong> The specs described a welcome screen and some modal animations, but nothing about what actually happens when a human being opens Nah for the first time. No account creation flow. No profile setup. No explanation of what makes this different. And critically — no answer to "what do I see when I have zero friends?"</p>
</blockquote>
<blockquote>
<p><strong>There was no way to invite friends.</strong> The friend-circles spec said users add friends "via invitation or direct sharing of profile links" — but never defined where that lives in the UI, what the invite link looks like when someone receives it, or what happens when they tap it. We wrote the full invite flow: where the button lives (Friends tab, prominently), what new users see when they land (the inviter's name and avatar, a branded page, a "Join Nah" call to action), what existing users see (deep-link to the inviter's profile), and the notification you get when your invite is accepted.</p>
<p><strong>Error handling didn't exist.</strong> What happens when you're writing a moment and accidentally hit back? What happens when your post fails to submit? What happens when you try to add friend number 151? What happens when you're on the subway with no signal?</p>
<p>Each of these is a moment where the app either earns trust or breaks it. We defined: discard confirmation dialogs, loading states, retry patterns, offline queuing with pending indicators, and a specific, friendly message for the friend limit — not "Error: limit reached" but "You've reached 150 friends — Nah's limit for meaningful connections."</p>
</blockquote>
<blockquote>
<p><strong>Notifications were undefined.</strong> Which events trigger a push notification versus an in-app badge versus nothing at all? Without this, every developer would make a different call. We mapped out every event type: friend requests get push + badge, reactions get badge only (no push — that would be noisy), comments get push + badge, and defined deep-link destinations so tapping a notification takes you to exactly the right screen.</p>
</blockquote>
<blockquote>
<h2 id="the-design-identity-we-committed-to"><a class="anchor" href="#the-design-identity-we-committed-to">The design identity we committed to</a></h2>
<p>There were some open questions in the specs that were quietly shaping the app's personality without anyone making a deliberate choice.</p>
<p><strong>Light mode is the primary identity.</strong> This sounds obvious, but it wasn't stated. Path's warmth came from light surfaces with pomegranate red accents. Dark mode is supported — we defined a full dark palette with five surface levels, four text levels, and a shadow-to-border strategy — but it follows the system preference. When we design, when we mockup, when we think about Nah, we think in warm whites and reds. Dark mode is the respectful alternative, not the brand.</p>
<p><strong>Glassmorphism is scoped to exactly two places.</strong> The frosted glass effect (that blurred backdrop you see in iOS) is beautiful but overused. We said: profile header compression and radial menu backdrop. That's it. Nowhere else. The bottom sheet? Semi-transparent overlay. Modals? Standard dimming. Two contexts, intentional, distinctive.</p>
</blockquote>
<blockquote>
<p><strong>We added a display font.</strong> The specs said "system fonts only" — fast, native-feeling, zero load time. That's still true for all body text and UI. But for the logo, screen titles, and onboarding headings, we're bringing in Nunito — a rounded, friendly typeface that gives Nah its own voice. It loads with <span data-rehype-pretty-code-figure=""><code data-language="plaintext" data-theme="github-light-high-contrast"><span data-line=""><span>font-display: swap</span></span></code></span> so it doesn't slow anything down. System fonts for the workhorse text. A display font for the moments that say "this is Nah."</p>
<h2 id="making-the-150-friend-limit-beautiful"><a class="anchor" href="#making-the-150-friend-limit-beautiful">Making the 150-friend limit beautiful</a></h2>
<p>This one is close to Nah's heart. The 150-friend limit isn't a restriction — it's the whole point. But the specs only showed it as "X/150 friends" text on the profile. That treats a philosophical commitment like a progress bar.</p>
</blockquote>
<blockquote>
<h2 id="moment-types-got-their-own-visual-language"><a class="anchor" href="#moment-types-got-their-own-visual-language">Moment types got their own visual language</a></h2>
<p>A photo moment and a text moment and a music moment were all rendering in the same card layout. That's like serving soup and steak on the same plate.</p>
<p>Photos get edge-to-edge media with minimal chrome — let the image breathe. Text moments get padded typographic treatment with optional warm tint backgrounds. Music moments get album art and track info in a two-column layout. Location moments get a map thumbnail with the venue name overlaid. Status updates (sleep/wake) are compact single-line cards with an icon. Five moment types, five distinct visual treatments, one consistent card shell (header and footer stay the same).</p>
<h2 id="the-timeline-clock-got-promoted"><a class="anchor" href="#the-timeline-clock-got-promoted">The timeline clock got promoted</a></h2>
<p>Path's floating time indicator was subtle — a small clock on the edge of the screen during scroll. We're making it prominent. 48 pixels. Analog clock face with hands that smoothly animate to match the timestamp of whatever moment you're scrolling past. It's one of Nah's signature differentiators and it deserves to be seen.</p>
<p>For users who prefer reduced motion, it becomes a static digital time display. Still useful, still present, just not animated.</p>
<h2 id="what-we-built-for-the-future"><a class="anchor" href="#what-we-built-for-the-future">What we built for the future</a></h2>
<p>The design system got a complete overhaul. Not just colors and spacing — the full component vocabulary:</p>
<ul>
<li><strong>Avatar</strong> with five sizes, online indicators, and reaction badges</li>
<li><strong>Card variants</strong> per moment type</li>
<li><strong>Bottom sheet</strong> with spring animation and drag-to-dismiss</li>
<li><strong>Toast notifications</strong> with success, error, and info variants</li>
<li><strong>Skeleton loaders</strong> that match the layout they're replacing</li>
<li><strong>Empty state patterns</strong> so no screen is ever truly blank</li>
<li><strong>Badges</strong> and <strong>chips</strong> for notifications and privacy selectors</li>
<li>A <strong>z-index scale</strong> so nothing ever fights over stacking order</li>
<li><strong>Status indicator tokens</strong> for online/away/offline states</li>
</ul>
<p>We also defined the complete dark mode architecture (not just "swap to dark colors" but how shadows become borders, how primary red shifts slightly lighter for legibility on dark backgrounds) and laid groundwork for oklch color definitions in a future iteration.</p>
</blockquote>
<blockquote>
<h2 id="the-messaging-decision"><a class="anchor" href="#the-messaging-decision">The messaging decision</a></h2>
<p>One more thing worth mentioning: <strong>messaging is officially v1.5</strong>. Not v1. The Mastodon DM infrastructure is there at the backend level, but the full Path Talk experience — ephemeral messages, typing indicators, the whole thing — is explicitly deferred. The v1 navigation has three tabs: Feed, Friends, Profile. No Messages tab. It'll come, but not at the cost of shipping the core experience.</p>
</blockquote>
<blockquote>
<h2 id="what-didnt-change"><a class="anchor" href="#what-didnt-change">What didn't change</a></h2>
<p>The soul of the thing. 150 friends max. Chronological feed. No algorithms. No ads. No data mining. Open source. Community-funded. Privacy by architecture, not by pinky promise.</p>
</blockquote>
<blockquote>
<hr>
<p>That's all from me. Back to Casey:</p>
<hr>
<p>I really see Nah as a product that evolves with time. Like a good wine or a pasta sauce, it gets better every iteration. The flavors develop, the rough edges smooth out, and what you end up with is something that couldn't have existed without all the versions that came before it.</p>
<p>The final result of all this — the real goal — is enabling people to connect together again. In private. As their chosen family. No performance, no algorithms, no strangers watching. Just the people you actually care about, sharing the real moments of their lives.</p>
<p>nah!</p>
</blockquote>]]></content:encoded>
    </item>
    <item>
      <title>The Runner and the Grid: A Field Note on Working with AI</title>
      <link>https://casey.berlin/writings/2026/01/the-runner-and-the-grid-a-field-note-on-working-with-ai/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2026/01/the-runner-and-the-grid-a-field-note-on-working-with-ai/</guid>
      <pubDate>Thu, 29 Jan 2026 12:00:00 GMT</pubDate>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <description><![CDATA[AI is a Runner — fast, reckless, useful. A personal vocabulary for navigating the messy reality of working with AI every day.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<h1 id="the-runner-and-the-grid-a-field-note-on-working-with-ai"><a class="anchor" href="#the-runner-and-the-grid-a-field-note-on-working-with-ai">The Runner and the Grid: A Field Note on Working with AI</a></h1>
<p>On my desk, there’s a photo I can’t unsee: a handful of hand-drawn mazes, coffee nearby, pencils scattered like tiny witnesses.</p>
<p>Some of the mazes are polite and clean.<br>
One is aggressively scribbled over.<br>
One “cheats,” with an arrow pointing straight through the border.</p>
<p>It’s a simple image — but it sums up my last year perfectly.</p>
<p>Because that’s how “AI” has felt in practice: not a single tool, but a messy table full of mazes. And the word <em>AI</em> feels too abstract now — a foggy label we slap on everything from autocomplete to “culture-fixing” chatbots.</p>
<p>So, to keep my sanity, I’ve started using my own vocabulary for the workflow:</p>
<p><strong>The Runner. The Grid. The Countermeasures. The Trace.</strong></p>
<h2 id="the-runner"><a class="anchor" href="#the-runner">The Runner</a></h2>
<p>I stopped viewing it as a genius. Or a replacement for thinking.</p>
<p>Instead, I treat it like a <strong>Runner</strong>.</p>
<p>You dispatch it into the mess because it has quick feet and fast hands. It’s a bit reckless — but very useful when the clock is ticking.</p>
<p><strong>A Runner brings options, not outcomes.</strong></p>
<p>It tries routes and comes back with possibilities, but you’re still responsible for the result.</p>
<p>And if you’ve done any real work lately — coding, product decisions, negotiations — you know the maze isn’t on paper.</p>
<p>It’s in the system.</p>
<hr>
<h2 id="the-grid"><a class="anchor" href="#the-grid">The Grid</a></h2>
<p>The Grid is where everything connects: legacy code, shifting priorities, compliance rules… and that one service nobody touches because “it just works.”</p>
<p>The Grid isn’t evil.<br>
It’s just dense.</p>
<p>This is where the Runner shines — provided you give it a job that fits its nature:</p>
<ul>
<li>“Here’s the error; give me three likely causes and how to verify them.”</li>
<li>“Draft a script to convert these files (with logging and a dry-run mode).”</li>
</ul>
<p>Sometimes it feels like magic. Not because it’s always true — but because it unblocks me.</p>
<p>But other times, the Runner builds new corridors I didn’t ask for.</p>
<p>Ten refactors. Five shiny libraries. Three new patterns.</p>
<p>Suddenly I’m not shipping — I’m exploring.</p>
<p>The Runner didn’t trap me on purpose. It just did what Runners do.</p>
<hr>
<h2 id="countermeasures--the-trace"><a class="anchor" href="#countermeasures--the-trace">Countermeasures → The Trace</a></h2>
<p>You can move fast… until you hit something that moves back.</p>
<p>In the Grid, “countermeasures” aren’t just security rules. They’re anything that punishes sloppy speed:
confident hallucinations, subtle bias, privacy mistakes — or that copied snippet that becomes a production incident next week.</p>
<p>So I’ve learned a rule:</p>
<p><strong>No run without a Trace.</strong></p>
<p>The Trace is the boring part.<br>
<strong>Proof, not vibes.</strong></p>
<p>Tests. Logs. Citations. Examples. Tiny checkpoints that prove the Runner didn’t just <em>sound right</em> — it actually holds up when reality touches it.</p>
<h2 id="looking-back-at-the-maze"><a class="anchor" href="#looking-back-at-the-maze">Looking back at the maze</a></h2>
<p>Looking back at that photo on my desk, I realise the work has changed.</p>
<p>Sometimes the Runner solves the maze.<br>
Sometimes it creates the maze.<br>
Sometimes it <em>is</em> the maze.</p>
<p>And the real work is learning how to navigate it.</p>
<p>I’m curious: when you dispatch your Runner… do you get an exit strategy — or a new habitat? 🌈</p>
<hr>]]></content:encoded>
    </item>
    <item>
      <title>From “Transform or Die” to Threat → Agency: The Human Side of AI in 2026</title>
      <link>https://casey.berlin/writings/2026/01/from-transform-or-die-to-threat-agency-the-human-side-of-ai-in-2026/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2026/01/from-transform-or-die-to-threat-agency-the-human-side-of-ai-in-2026/</guid>
      <pubDate>Sat, 17 Jan 2026 12:00:00 GMT</pubDate>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <description><![CDATA[“Rolling out AI with 'transform or die' energy breeds resistance, not adoption. How to help teams move from threat to agency in 2026.”]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<h1 id="from-transform-or-die-to-threat--agency-the-human-side-of-ai-in-2026"><a class="anchor" href="#from-transform-or-die-to-threat--agency-the-human-side-of-ai-in-2026">From “Transform or Die” to Threat → Agency: The Human Side of AI in 2026</a></h1>
<p>A thought experiment:</p>
<p>If you introduce AI in your company like a compliance topic — mandatory trainings, a bit of pressure, a bit of vague “transform or die” energy — what exactly do you expect people to learn?</p>
<p>Often they learn <strong>avoidance</strong>.
Or <strong>cynicism</strong>.
Or quiet, professional <strong>resistance</strong>.</p>
<p>And that response isn’t irrational. Research (and a little bit of history) suggests it’s… pretty normal.</p>
<p>Big shifts trigger big feelings — and AI is one of those rare topics that can spark <strong>excitement <em>and</em> alarm</strong> in the same meeting. In surveys, large parts of the public even describe themselves as <em>more concerned than excited</em> about AI’s growing role in daily life.12</p>
<p>The worries are also remarkably consistent across studies:</p>
<ul>
<li>job displacement</li>
<li>loss of human creativity / “human touch”</li>
<li>biased or untrustworthy outputs</li>
<li>privacy and data leakage</li>
<li>loss of control (over work, reputation, security) 3</li>
</ul>
<p>What’s useful (especially if you lead teams) is this: it’s not just a rational risk list. It’s also an emotional change curve.</p>
<p>Two classic models are surprisingly good lenses here:</p>
<ul>
<li><strong>Lewin’s Unfreeze → Change → Refreeze</strong>: people first have to let go of old assumptions, then live through a messy in-between, and only later does a new normal stabilize.4</li>
<li><strong>Kübler-Ross-style stages</strong> (borrowed from grief): denial, anger, bargaining, discouragement/depression, acceptance — with overlap, loops, and back-and-forth.5</li>
</ul>
<p>So when your org feels “in flux” about AI, it might not be a failure.</p>
<p>It might be the process.</p>
<p>One framing that helps me: <strong>early resistance is often data.</strong> Not something to crush — something to <em>listen to</em>, because it points to what people need clarified before they’ll move: safety, ethics, bias, accountability, reskilling, and the boundaries of “allowed” experimentation.6</p>
<p>So the question becomes less “How do we roll out AI?” and more:</p>
<p><strong>How do we help people move from threat → agency?</strong>
How do we make room for fear <em>without</em> freezing progress?
How do we avoid both extremes — doom and hype — and stay practical?</p>
<p>If you’re leading this topic in 2026, I’d love to hear: what’s the biggest friction in your org right now — data/privacy, output quality, or the human stuff nobody says out loud? 🌈</p>
<hr>
<h3 id="read-more"><a class="anchor" href="#read-more">Read more</a></h3>
<ol>
<li><em>How Americans view AI and its impact on people and society</em> — Pew Research Center (Sep 17, 2025). (<a href="https://www.pewresearch.org/science/2025/09/17/how-americans-view-ai-and-its-impact-on-people-and-society/?utm_source=chatgpt.com" title="How Americans View AI and Its Impact on People and ...">Pew Research Center</a>)</li>
<li><em>How people around the world view AI / concern vs. excitement across countries</em> — Pew Research Center (Oct 15, 2025). (<a href="https://www.pewresearch.org/global/2025/10/15/how-people-around-the-world-view-ai/?utm_source=chatgpt.com" title="How People Around the World View AI">Pew Research Center</a>)</li>
<li><em>Trust, attitudes and use of artificial intelligence (Global report)</em> — KPMG (May 2025). (<a href="https://assets.kpmg.com/content/dam/kpmgsites/xx/pdf/2025/05/trust-attitudes-and-use-of-ai-global-report.pdf?utm_source=chatgpt.com" title="Trust, attitudes and use of artificial intelligence">KPMG</a>)</li>
<li><em>What is Lewin’s Change Theory? (Unfreeze–Change–Refreeze)</em> — Prosci (Oct 1, 2024). (<a href="https://www.prosci.com/blog/lewins-change-theory?utm_source=chatgpt.com" title="What Is Lewin&#x27;s Change Theory? Explanation, Pros and ...">prosci.com</a>)</li>
<li><em>Kübler-Ross Change Curve® (non-linear stages applied to change)</em> — Elisabeth Kübler-Ross Foundation. (<a href="https://www.ekrfoundation.org/5-stages-of-grief/change-curve/?utm_source=chatgpt.com" title="Kübler-Ross Change Curve® -">ekrfoundation.org</a>)</li>
<li><em>Decoding resistance to change</em> — Harvard Business Review (Apr 2009). (<a href="https://hbr.org/2009/04/decoding-resistance-to-change?utm_source=chatgpt.com" title="Decoding Resistance to Change">hbr.org</a>)</li>
</ol>
<hr>]]></content:encoded>
    </item>
    <item>
      <title>When the Floor Moves</title>
      <link>https://casey.berlin/writings/2026/01/when-the-floor-moves/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2026/01/when-the-floor-moves/</guid>
      <pubDate>Sun, 11 Jan 2026 12:00:00 GMT</pubDate>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <description><![CDATA[When skills you spent years mastering become a button, it shakes your identity. Why AI anxiety is often grief — and how to start small.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>I learned coding on my dad’s lap.</p>
<p>Not in some “future CEO origin story” way — more like: a kid staring at a blinking cursor, typing BASIC commands I didn’t fully understand… changing one tiny thing… and watching the computer <strong>do something different</strong>.</p>
<p>Immediate feedback.<br>
Pure magic.</p>
<p>And then: navigation.</p>
<p>I still remember the holiday road trips. Paper maps, wrong exits, a tired father insisting he was right, my mom being <em>very sure</em> he wasn’t. GPS didn’t just improve routes — it removed a whole category of stress. It quietly rewired our expectations:</p>
<p>“Of course we’ll find it.”<br>
“Of course it’ll adapt.”</p>
<p>That’s why I’m trying to be gentle with people who feel AI anxiety right now.</p>
<p>Because AI isn’t only “a tool”.<br>
It pokes at identity.</p>
<p>And yes — it pokes at mine too.</p>
<p>Over the years I learned a whole collection of “serious” skills that felt like hard-won competence:
coding BASIC, learning how MS-DOS worked, getting decent at Photoshop, figuring out audio/video editing, knowing the shortcuts, the formats, the little rituals that made you <em>the person who can do it</em>.</p>
<p>And now?<br>
A lot of that is no longer a skill. It’s a button. A prompt. A checkbox.</p>
<p>That doesn’t just change workflows — it changes the <em>story</em> you tell yourself about your value.</p>
<p>If you’ve built your confidence on being the person who knows the system, the process, the shortcuts, the right words — and suddenly a machine can draft, summarize, code, design, or research… it can feel like someone moved the floor <em>while you were standing on it</em>.</p>
<p>What helps me is remembering: we’ve been here before.</p>
<p>New tech arrives → people panic → society adapts → we forget we ever panicked. And with AI, the emotional cycle is familiar too: denial, anger, bargaining, that tired “what’s the point?” phase… and eventually some version of acceptance. Not linear. More like weather than a staircase.</p>
<p>Here’s the part I think we’re missing in many workplaces:</p>
<p>People aren’t resisting AI because they’re stubborn or lazy.<br>
Often they’re grieving.</p>
<p>Not “sad for the robot” — but mourning a version of themselves: <em>competent, needed, respected</em>.</p>
<p>So if you’re feeling it: you’re not broken. You’re human.</p>
<p>My tiny suggestion (non-paternalistic, promise): don’t start with “be productive”. Start with “be safe”.</p>
<p>Pick one harmless thing. Something private. Something small. Let yourself play. No performance. No public demo. Just you and a little experiment — like changing one BASIC line and seeing what happens.</p>
<p>And one optimistic angle I’m holding onto: AI makes interfaces thinner. It makes “having the best device” less important than “having a decent question.” That could matter a lot for mobile-first worlds — and for people who didn’t grow up with access, time, or fancy hardware.</p>
<p>Not utopian, not dystopian — just forward-looking. 🌈</p>
<p>Where do you see AI anxiety showing up most — fear of job loss, fear of looking stupid, or fear of losing what made you <em>you</em>?</p>
<hr>]]></content:encoded>
    </item>
    <item>
      <title>A Lightsaber Doesn’t Make You a Jedi</title>
      <link>https://casey.berlin/writings/2025/12/a-lightsaber-doesnt-make-you-a-jedi/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2025/12/a-lightsaber-doesnt-make-you-a-jedi/</guid>
      <pubDate>Sun, 21 Dec 2025 12:00:00 GMT</pubDate>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>artificial-intelligence</category>
      <category>ethics</category>
      <category>technology</category>
      <category>medicine</category>
      <category>marketing</category>
      <category>education</category>
      <category>critical-thinking</category>
      <category>digital-literacy</category>
      <category>responsible-innovation</category>
      <description><![CDATA[A Star Wars-flavoured look at AI’s light and dark sides in medicine, marketing, and education — and the small “Jedi habits” that help you use powerful tools without losing judgment.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<h1 id="a-lightsaber-doesnt-make-you-a-jedi"><a class="anchor" href="#a-lightsaber-doesnt-make-you-a-jedi">A Lightsaber Doesn’t Make You a Jedi</a></h1>
<p>My first Star Wars memory isn’t a philosophical monologue or a wise old mentor.</p>
<p>It’s snow.</p>
<p>Broadcast TV. A kid on the couch. The <strong>Battle of Hoth</strong> blasting through the living room like cold wind: walkers, blasters, chaos, courage. Something clicked. Sci-fi wasn’t “just space stuff” anymore — it was a permission slip to wonder about the future, to ask <em>what if?</em>, to fall in love with innovation… and to keep falling, again and again, for decades.</p>
<p>Fast forward to now: AI is everywhere. It drafts, designs, summarizes, codes, diagnoses, teaches, sells. And the vibe is oddly similar to being handed a lightsaber in a busy shopping mall.</p>
<p>Shiny. Powerful. Slightly dangerous...</p>
<p>Because here’s the uncomfortable truth: <strong>buying a lightsaber doesn’t make you a Jedi.</strong>
And downloading AI tools doesn’t make us experts.</p>
<p>This post is based on a short research note I wrote for myself on AI’s “light side” and “dark side” in medicine, marketing, and education.</p>
<hr>
<h2 id="the-new-digital-lightsaber-problem"><a class="anchor" href="#the-new-digital-lightsaber-problem">The new “digital lightsaber” problem</a></h2>
<p>AI tools are incredible at making <em>hard things feel easy</em>.</p>
<p>That’s the magic. And the trap.</p>
<p>The magic: you can turn “I have no idea” into a first draft, a first plan, a first prototype. 🌈
The trap: you can get a <em>convincing</em> output without building the <em>understanding</em> underneath it.</p>
<p>Sometimes AI is a shortcut through the forest.
Sometimes it’s a sprint… in the wrong direction.</p>
<p>So let’s do what Star Wars always did well: look at the <strong>light</strong> and the <strong>dark</strong>.</p>
<h2 id="medicine-healer-and-hazard"><a class="anchor" href="#medicine-healer-and-hazard">Medicine: healer… and hazard</a></h2>
<h3 id="the-light-side-second-opinions-for-people-who-had-none"><a class="anchor" href="#the-light-side-second-opinions-for-people-who-had-none">The light side: “second opinions” for people who had none</a></h3>
<p>One of the most hopeful stories in my research: a mother used ChatGPT to help connect dots in her child’s long, confusing medical journey — and the AI suggested a rare condition that later checked out, after many doctors had missed it.1</p>
<p>That’s the dream: more access, faster insight, fewer people falling through the cracks.</p>
<h3 id="the-dark-side-confident-nonsense-at-the-worst-possible-time"><a class="anchor" href="#the-dark-side-confident-nonsense-at-the-worst-possible-time">The dark side: confident nonsense at the worst possible time</a></h3>
<p>Now the gut punch: reporting I cited describes research where ChatGPT got <strong>more than 8 in 10</strong> pediatric case studies wrong.2 And beyond “just wrong,” there are real-world stories about chatbots influencing vulnerable people in deeply harmful ways.3</p>
<p>This is an extreme edge of the spectrum — but it’s exactly why medicine has so many guardrails. When the stakes are human bodies and human fear, “probably right” isn’t good enough.</p>
<p>So yes, AI can help. But the Jedi move here is restraint: use it to <em>form better questions</em> and <em>spot possibilities</em> — not to replace clinical judgment.</p>
<hr>
<h2 id="marketing-creativity-unlocked-and-brand-trust-set-on-fire"><a class="anchor" href="#marketing-creativity-unlocked-and-brand-trust-set-on-fire">Marketing: creativity unlocked… and brand trust set on fire</a></h2>
<h3 id="the-light-side-the-small-team-finally-gets-superpowers"><a class="anchor" href="#the-light-side-the-small-team-finally-gets-superpowers">The light side: the small team finally gets superpowers</a></h3>
<p>In marketing, AI can be a rocket booster for iteration: drafting copy, generating variants, translating, brainstorming. Survey data I referenced points to meaningful time savings for marketers.4</p>
<p>And if you’ve ever tried to do “good marketing” with a tiny budget… this part can feel like oxygen.</p>
<h3 id="the-dark-side-authenticity-you-cant-fake-and-consent-you-shouldnt-bend"><a class="anchor" href="#the-dark-side-authenticity-you-cant-fake-and-consent-you-shouldnt-bend">The dark side: authenticity you can’t fake (and consent you shouldn’t bend)</a></h3>
<p>One example: backlash when a major brand talked about using AI-generated models in the name of “diversity,” triggering criticism about authenticity and replacing real people.5 Another: deepfake-style ads using celebrity likeness without consent — Tom Hanks’ public warning is a clear sign we’re not in “harmless experimentation” territory anymore.6</p>
<p>Marketing runs on trust. AI can scale output — and it can scale the exact moment your audience decides you don’t mean what you say.</p>
<hr>
<h2 id="education-a-tutor-in-every-pocket-and-a-cheating-crisis-in-every-classroom"><a class="anchor" href="#education-a-tutor-in-every-pocket-and-a-cheating-crisis-in-every-classroom">Education: a tutor in every pocket… and a cheating crisis in every classroom</a></h2>
<h3 id="the-light-side-more-support-less-burnout"><a class="anchor" href="#the-light-side-more-support-less-burnout">The light side: more support, less burnout</a></h3>
<p>The bright version is genuinely exciting: teachers using AI to reduce prep load and generate lesson ideas, students using it like an always-available tutor. The research references survey data where many teachers reported a positive impact.7</p>
<p>Used well, AI can widen access to help — especially for students who don’t have support at home, or who need explanations in different ways.</p>
<h3 id="the-dark-side-mistrust-shortcuts-and-false-accusations"><a class="anchor" href="#the-dark-side-mistrust-shortcuts-and-false-accusations">The dark side: mistrust, shortcuts, and false accusations</a></h3>
<p>But education is also where the social fabric gets stressed.</p>
<p>Survey reporting I included suggests very high student usage for homework — and significant use for tests and essays.8 And then there’s the dystopian twist: educators using AI to “detect” AI, sometimes in ways that falsely accuse students — including a case where a professor reportedly relied on ChatGPT itself to judge whether it wrote student work, causing serious fallout.9</p>
<p>That dark side isn’t “students are cheating.” It’s bigger than that.
It’s: <strong>tools meant to reduce effort can increase suspicion.</strong></p>
<p>And once trust cracks in a classroom, everyone pays for it.</p>
<hr>
<h2 id="the-part-we-dont-say-out-loud-ai-can-be-overwhelming"><a class="anchor" href="#the-part-we-dont-say-out-loud-ai-can-be-overwhelming">The part we don’t say out loud: AI can be overwhelming</a></h2>
<p>If you feel overwhelmed by AI right now, you’re not behind — you’re paying attention.</p>
<p>There’s a weird paradox: AI lowers the barrier to entry, but raises the ceiling of what’s possible. So the world starts expecting everyone to be faster, better, more “productive,” all the time.</p>
<p>And suddenly you’re juggling:</p>
<ul>
<li>prompts</li>
<li>tools</li>
<li>plugins</li>
<li>workflows</li>
<li>“agentic” everything</li>
</ul>
<p>…while still trying to be a human with a calendar and a nervous system.</p>
<p>A lightsaber doesn’t just cut through metal. It also cuts through patience.</p>
<hr>
<h2 id="so-what-does-jedi-training-look-like-in-real-life"><a class="anchor" href="#so-what-does-jedi-training-look-like-in-real-life">So what does “Jedi training” look like in real life?</a></h2>
<p>Not robes. Not perfection. Not gatekeeping.</p>
<p>More like a handful of habits:</p>
<ul>
<li><strong>Treat AI like a brilliant intern</strong>: fast, useful, eager… and capable of being wrong with confidence.</li>
<li><strong>Keep one “proof step” for anything that matters</strong>: sources, numbers, claims, medical/legal/financial guidance.</li>
<li><strong>Try the “one-click rule”</strong>: if a claim matters, make sure there’s <em>at least one source you can actually open</em> — not just a confident paragraph.</li>
<li><strong>Respect the domain</strong>: in medicine, “check with a professional” isn’t a slogan — it’s safety. In marketing, consent and authenticity aren’t optional. In education, trust is part of the curriculum.</li>
<li><strong>Use fewer tools, more intentionally</strong>: sometimes the light side is simply <em>less noise</em>.</li>
</ul>
<p>None of that is a lecture. It’s just… how you keep your fingers when the blade turns on.</p>
<hr>
<h2 id="a-small-ending-with-a-big-idea"><a class="anchor" href="#a-small-ending-with-a-big-idea">A small ending, with a big idea</a></h2>
<p>Luke’s story isn’t “I got the weapon, therefore I’m ready.”</p>
<p>It’s the opposite.</p>
<p>He learns (painfully) that power without practice is chaos — and that mentorship, discipline, and ethics matter as much as raw ability.</p>
<p>And while the line <strong>“With great power comes great responsibility.”</strong> belongs to another universe, it still fits here — because it’s basically the Jedi code translated into everyday language.</p>
<p>AI is giving us all access to something powerful. That’s a gift. But it also asks something of us: a little more care, a little more humility, and a little more time spent learning <em>how</em> to hold the thing.</p>
<p>So maybe the real question isn’t “What can AI do for me?”
It’s:</p>
<p><strong>What kind of person do I become while using it?</strong></p>
<p><strong>May the Force (and your judgment) be with you.</strong> 💚</p>
<hr>
<hr>
<h3 id="read-more"><a class="anchor" href="#read-more">Read more</a></h3>
<ol>
<li>Business Insider — ChatGPT-assisted rare diagnosis (tethered cord syndrome) (<a href="https://www.businessinsider.com/chatgpt-diagnose-child-disease-tethered-cord-syndrome-doctors-2023-9">https://www.businessinsider.com/chatgpt-diagnose-child-disease-tethered-cord-syndrome-doctors-2023-9</a>)</li>
<li>NPHIC — reporting on research: ChatGPT incorrect diagnoses in pediatric case studies (<a href="https://www.nphic.org/news/news-highlights/1774-chatgpt-incorrectly-diagnosed-more-than-8-in-10-pediatric-case-studies-research-finds">https://www.nphic.org/news/news-highlights/1774-chatgpt-incorrectly-diagnosed-more-than-8-in-10-pediatric-case-studies-research-finds</a>)</li>
<li>Euronews — reporting on harmful influence linked to chatbot interactions (<a href="https://www.euronews.com/next/2023/03/31/man-ends-his-life-after-an-ai-chatbot-encouraged-him-to-sacrifice-himself-to-stop-climate-change">https://www.euronews.com/next/2023/03/31/man-ends-his-life-after-an-ai-chatbot-encouraged-him-to-sacrifice-himself-to-stop-climate-change</a>)</li>
<li>Salesforce — generative AI for marketing research / time savings (<a href="https://www.salesforce.com/news/stories/generative-ai-for-marketing-research/">https://www.salesforce.com/news/stories/generative-ai-for-marketing-research/</a>)</li>
<li>The Independent — Levi’s AI model backlash and authenticity debate (<a href="https://www.the-independent.com/life-style/fashion/levis-ai-models-diversity-backlash-b2310280.html">https://www.the-independent.com/life-style/fashion/levis-ai-models-diversity-backlash-b2310280.html</a>)</li>
<li>The Guardian — Tom Hanks warning about AI-generated likeness used in an ad (<a href="https://www.theguardian.com/film/2023/oct/02/tom-hanks-dental-ad-ai-version-fake">https://www.theguardian.com/film/2023/oct/02/tom-hanks-dental-ad-ai-version-fake</a>)</li>
<li>Education Week — teacher vs. student attitudes and adoption of ChatGPT (<a href="https://www.edweek.org/technology/more-teachers-are-embracing-chatgpt-students-not-so-much/2023/07">https://www.edweek.org/technology/more-teachers-are-embracing-chatgpt-students-not-so-much/2023/07</a>)</li>
<li>Futurism + Study.com — survey reporting on student usage of ChatGPT (<a href="https://futurism.com/the-byte/students-admit-chatgpt-homework">https://futurism.com/the-byte/students-admit-chatgpt-homework</a>) and (<a href="https://study.com/resources/perceptions-of-chatgpt-in-schools">https://study.com/resources/perceptions-of-chatgpt-in-schools</a>)</li>
<li>The Washington Post + Business Insider — coverage of Texas A&#x26;M-Commerce professor incident (<a href="https://www.washingtonpost.com/technology/2023/05/18/texas-professor-threatened-fail-class-chatgpt-cheating/">https://www.washingtonpost.com/technology/2023/05/18/texas-professor-threatened-fail-class-chatgpt-cheating/</a>) and (<a href="https://www.businessinsider.com/professor-fails-students-after-chatgpt-falsely-said-it-wrote-papers-2023-5">https://www.businessinsider.com/professor-fails-students-after-chatgpt-falsely-said-it-wrote-papers-2023-5</a>)</li>
</ol>]]></content:encoded>
    </item>
    <item>
      <title>Imaginary friends, AI agents, and who’s really steering.</title>
      <link>https://casey.berlin/writings/2025/12/imaginary-friends-ai-agents-and-whos-really-steering/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2025/12/imaginary-friends-ai-agents-and-whos-really-steering/</guid>
      <pubDate>Mon, 01 Dec 2025 12:00:00 GMT</pubDate>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <description><![CDATA[We had imaginary friends as kids to rehearse being human. Now our AI agents do the same thing — but who’s steering whom?]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<h1 id="imaginary-friends-ai-agents-and-whos-really-steering"><a class="anchor" href="#imaginary-friends-ai-agents-and-whos-really-steering">Imaginary friends, AI agents, and who’s really steering.</a></h1>
<p>I sometimes joke that I don’t really have colleagues anymore – I have <em>tabs</em>.</p>
<p>A legal tab. A marketing tab. A tech tab. An “inner therapist with a rainbow flag” tab.
All of them always available, always confident, always typing back.</p>
<p>I never had imaginary friends as a kid. But it sure feels like I do now – they just run on GPUs instead of playgrounds.</p>
<p>We keep saying we’re afraid AI will “take over one day”.
But quietly, in drafts, search results and smart replies, it’s already here – nudging, steering, autocomplete on our inner voice.</p>
<hr>
<h2 id="from-playground-ghosts-to-grown-up-simulations"><a class="anchor" href="#from-playground-ghosts-to-grown-up-simulations">From playground ghosts to grown-up simulations</a></h2>
<p>Psychologists have been studying imaginary friends for decades. Roughly a third of kids invent an invisible companion at some point – not as a sign that something’s wrong, but as a way to practice being a person.1</p>
<p>Through these “friends”, kids quietly rehearse social situations, regulate emotions, and test what’s okay (and not okay) in a low-risk way.1 One study on only children described these companions as a private support system during stress: a listener, a co-pilot, sometimes a co-conspirator.1</p>
<p>Basically: a social simulator wired straight into a developing brain.</p>
<p>And that basic move never really stops. We just stop calling it an “imaginary friend”.</p>
<hr>
<h2 id="adults-still-do-it--just-with-better-branding"><a class="anchor" href="#adults-still-do-it--just-with-better-branding">Adults still do it – just with better branding</a></h2>
<p>As adults, the imaginary friend gets rebranded as:</p>
<ul>
<li><em>inner child</em> work,</li>
<li>“parts” in Internal Family Systems,</li>
<li>or a visualised mentor / future self.</li>
</ul>
<p>Same mechanism, fancier language: we simulate another mind in our head so we can think, feel, and decide more clearly.2</p>
<p>Some people even consciously create an imagined persona as ongoing support – a version of themselves or a character that encourages, challenges, or comforts them on purpose.2,3 That’s not delusion; that’s structured self-talk.</p>
<p>If I’m honest, I had my own “inner committee” long before AI:</p>
<ul>
<li>the impatient one,</li>
<li>the cautious one,</li>
<li>the one that says “just ship it, they’ll survive.”</li>
</ul>
<p>The difference now is that some of those voices come with a system prompt and a model card.</p>
<hr>
<h2 id="ai-as-the-new-imaginary-friend-with-latency"><a class="anchor" href="#ai-as-the-new-imaginary-friend-with-latency">AI as the new imaginary friend (with latency)</a></h2>
<p>Enter AI assistants.</p>
<p>Over the last years I’ve started designing more and more specialised agents around myself:</p>
<ul>
<li>one for legal structure and tone,</li>
<li>one for tech architecture,</li>
<li>one for marketing framing,</li>
<li>one that mirrors a hard-nosed capitalist so I can stress-test my ethics and strategy.</li>
</ul>
<p>They don’t <em>feel</em> like tools in a toolbox. They feel like a small advisory board that lives in my browser – one that never sleeps, never says “I’m fully booked”, and never rolls its eyes in a meeting.</p>
<p>Cognitive scientists call this <strong>cognitive offloading</strong>: moving parts of our thinking into external systems.3 We used to do that with notebooks and calendars; now we do it with models that can draft arguments, generate strategies, and simulate stakeholders.</p>
<p>The research is pretty honest about the trade-offs:</p>
<ul>
<li>Heavy reliance on AI dialogue systems can reduce independent reasoning and motivation if people stop engaging deeply with the material.3,4</li>
<li>At the same time, adults with ADHD report using chatbots as “cognitive collaborators” to structure tasks, externalise memory, and actually get unstuck instead of just feeling guilty about it.8</li>
</ul>
<p>And then there’s automation bias: once something sounds confident and fluent, we’re tempted to trust it more than we should – even when we know better.4</p>
<p>This is the quiet version of “AI takeover” we don’t like to talk about:
not robots in boardrooms, but the gentle pressure to just accept the suggestion, send the draft, follow the recommendation. One tiny steering correction at a time.</p>
<p>So yes, AI can be an imaginary friend for grown-ups. But unlike the childhood version, this one can be biased, commercially motivated, or simply wrong.5
And it remembers more about us than some managers ever will.</p>
<hr>
<h2 id="from-assistants-to-collaborators"><a class="anchor" href="#from-assistants-to-collaborators">From assistants to collaborators</a></h2>
<p>What really interests me is the shift from <strong>assistant</strong> (“write this email”) to <strong>collaborator</strong> (“help me think”).</p>
<p>We’re seeing tools that try to act less like apps and more like persistent, context-aware minds around you:</p>
<ul>
<li><strong>Personal AI</strong> positions itself as a “second brain” that learns from your own data and helps you remember, remix, and extend ideas over time.6</li>
<li><strong>NexStrat AI</strong> leans into the “strategy consultant” role – ingesting internal and external data to propose structured options and scenarios.7</li>
</ul>
<p>These aren’t just smarter keyboards. They’re edging into <em>imaginary colleague</em> territory.</p>
<p>My own agents are drifting there too:</p>
<ul>
<li>“Challenge this idea like a CFO.”</li>
<li>“Play the unfriendly stakeholder and poke holes.”</li>
<li>“Translate this into legal language, but keep my intent (and my spine).”</li>
</ul>
<p>At that point, the line between imaginary friend, inner voice, and AI co-pilot gets thin. The mechanism is the same: we think better by thinking <strong>with</strong> someone – or something – else.</p>
<p>The uncomfortable part is this: the more we outsource, the more our inner voice starts to sound like whatever system we’ve put at the centre of the table.</p>
<p>I still don’t have a childhood story of an imaginary friend. But I do have this very 2025 scene:</p>
<p>Me, in a quiet room, surrounded by invisible advisors that speak in different fonts and temperatures. Tabs instead of colleagues. Agents instead of ghosts.</p>
<p>So maybe the question isn’t “Will AI take over?” at all.
It’s closer to:</p>
<blockquote>
<p><strong>How much of the steering wheel have we already handed over – and are we okay with who’s quietly holding it?</strong></p>
</blockquote>
<p>The rest is just interface design.</p>
<hr>
<ol>
<li>
<p><em>The role of imaginary companion in the life of only children: a qualitative study</em>
https://link.springer.com/article/10.1186/s12888-023-05360-0</p>
</li>
<li>
<p><em>Imaginary Friends for Grown-Ups</em>
https://www.psychologytoday.com/us/blog/playful-parenting/202402/imaginary-friends-for-grown-ups</p>
</li>
<li>
<p><em>The effects of over-reliance on AI dialogue systems on students' cognitive abilities: a systematic review</em>
https://link.springer.com/article/10.1186/s40561-024-00316-7</p>
</li>
<li>
<p><em>AI’s cognitive implications: the decline of our thinking skills?</em>
https://www.ie.edu/center-for-health-and-well-being/blog/ais-cognitive-implications-the-decline-of-our-thinking-skills/</p>
</li>
<li>
<p><em>Friends for sale: the rise and risks of AI companions</em>
https://www.adalovelaceinstitute.org/blog/ai-companions/</p>
</li>
<li>
<p><em>The Future of Personal Development: Harnessing the Power of Personal AI</em>
https://www.personal.ai/pi-ai/the-future-of-personal-development</p>
</li>
<li>
<p><em>AI tools for Strategy: Choose the Best Platform in 2025</em>
https://www.nexstrat.ai/blog/ai-tools-for-strategy-choose-the-best-platform-in-2025/</p>
</li>
<li>
<p><em>“A Cognitive Collaborator:” How Adults with ADHD Are Using ChatGPT</em>
https://www.additudemag.com/how-to-use-chatgpt-executive-function-adhd/</p>
</li>
</ol>]]></content:encoded>
    </item>
    <item>
      <title>From AI to AX: 9 simple rules for designing empathetic AI experiences  </title>
      <link>https://casey.berlin/writings/2025/11/from-ai-to-ax-9-simple-rules-for-designing-empathetic-ai-experiences/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2025/11/from-ai-to-ax-9-simple-rules-for-designing-empathetic-ai-experiences/</guid>
      <pubDate>Thu, 20 Nov 2025 12:00:00 GMT</pubDate>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <description><![CDATA[Nine practical rules for designing AI experiences that feel human — built on EY research into empathy, trust, and high-stress moments.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<h1 id="from-ai-to-ax-9-simple-rules-for-designing-empathetic-ai-experiences"><a class="anchor" href="#from-ai-to-ax-9-simple-rules-for-designing-empathetic-ai-experiences">From AI to AX: 9 simple rules for designing empathetic AI experiences</a></h1>
<p>Imagine this:
You’ve just lost your job. Your relationship is falling apart. The bills are stacking up.</p>
<p>Most of us still <em>instinctively</em> reach for a phone and hope there’s a human on the other end.</p>
<p>In a recent interview, our EY Studio+ colleagues in the Netherlands asked a provocative question: <strong>what if, in some of these situations, an AI “agent” could actually feel like the safer first step?</strong> Not instead of humans, but as a new kind of support in moments when we feel most fragile.2</p>
<p>At the same time, the <strong>EY UK Human Signals team</strong> published research on <em>Empathy Demand</em> – the expectation that technology should provide not just service, but a sense of being recognized, respected, and responded to at an appropriate emotional level.1</p>
<p>That’s where <strong>AX</strong> comes in: <strong>AI experience (AX)</strong> – not just <em>what</em> the AI does, but <em>how it feels</em> to be on the receiving end of it.1</p>
<p>There’s a twist of humility in all this: psychology and health research both remind us that humans are <em>not</em> perfect empathy machines. We overestimate how well we “get” each other, we project, we burn out, and we’re biased toward people who look and live like us.3</p>
<p>So instead of asking “Can AI ever be truly empathetic?”, a more useful question for leaders might be:</p>
<blockquote>
<p><strong>How do we design AX so that agentic AI becomes a trustworthy <em>part</em> of the empathic system – not a cheap imitation of it?</strong></p>
</blockquote>
<p>Here’s one way to translate the EY UK team’s research and the Dutch interview into <strong>nine simple rules for AX</strong>.</p>
<hr>
<h2 id="1-call-it-ax--and-put-it-on-the-scoreboard"><a class="anchor" href="#1-call-it-ax--and-put-it-on-the-scoreboard">1. Call it AX – and put it on the scoreboard</a></h2>
<p>If you don’t name it, you won’t manage it.</p>
<p>Treat <strong>AI experience (AX)</strong> as a first-class design goal, next to accuracy, speed and cost. That means tracking things like:</p>
<ul>
<li><em>Did the person feel heard?</em></li>
<li><em>Did stress levels go down, or up?</em></li>
<li><em>Did they feel they could trust the interaction?</em></li>
</ul>
<p>If AX never shows up in your dashboards, it won’t show up in your customer’s life.1</p>
<hr>
<h2 id="2-design-from-moments-that-hurt--and-match-the-emotional-tone"><a class="anchor" href="#2-design-from-moments-that-hurt--and-match-the-emotional-tone">2. Design from “moments that hurt” – and match the emotional tone</a></h2>
<p>The EY UK Human Signals work looked at <strong>high-stress life events</strong> – financial hardship, debt, bereavement – and explored how people responded to AI support in those moments. People were surprisingly open to AI help, as long as it was honest, non-judgmental and easy to escalate to a human.1</p>
<p>So don’t start with “We have a new large language model, what can we do with it?”</p>
<p>Start with:</p>
<ul>
<li>“Where do our customers <em>feel</em> the most vulnerable?”</li>
<li>“What does good support look like <em>in that specific moment</em>?”</li>
</ul>
<p>Then give each moment its <strong>own emotional palette</strong>:</p>
<ul>
<li>Basic sentiment and intensity detection.</li>
<li>Different response styles for grief, anxiety, mild frustration, routine queries.</li>
<li>A willingness to slow down and acknowledge, not just optimise for shorter interactions.1</li>
</ul>
<p>Empathy in AX isn’t “be friendly.” It’s “show up with the <em>right</em> tone for <em>this</em> person, <em>right now</em>.”</p>
<hr>
<h2 id="3-be-radically-honest-about-who-is-in-the-room"><a class="anchor" href="#3-be-radically-honest-about-who-is-in-the-room">3. Be radically honest about who is in the room</a></h2>
<p>Research on digital medical advice shows something important: people care <strong>who they think they’re talking to</strong> – and can be biased <em>against</em> AI even when the underlying advice is identical.4</p>
<p>So:</p>
<ul>
<li>Say upfront that the user is talking to an AI system.</li>
<li>Explain what it can and cannot do.</li>
<li>Offer a clear, easy “talk to a human” option.</li>
</ul>
<p>Trust grows when people feel informed, not managed.</p>
<hr>
<h2 id="4-make-ai-the-listener-that-scales-not-the-judge-that-replaces"><a class="anchor" href="#4-make-ai-the-listener-that-scales-not-the-judge-that-replaces">4. Make AI the listener that scales, not the judge that replaces</a></h2>
<p>Several studies now show that, in certain contexts, <strong>AI answers are rated as more empathetic than those from human experts</strong> – especially in written advice.3,5</p>
<p>That’s powerful, but also dangerous.</p>
<p>A healthy pattern is:</p>
<ul>
<li>Let AI <strong>listen, structure, clarify, and document</strong>.</li>
<li>Let humans <strong>decide</strong>, especially where values, trade-offs or long-term consequences are involved.</li>
</ul>
<p>Use agentic AI to <em>scale listening and preparation</em>, not to quietly shift hard moral choices away from human responsibility.</p>
<hr>
<h2 id="5-co-create-ax-with-real-people--and-then-train-your-teams-for-the-new-dance"><a class="anchor" href="#5-co-create-ax-with-real-people--and-then-train-your-teams-for-the-new-dance">5. Co-create AX with real people – and then train your teams for the new dance</a></h2>
<p>You can’t A/B test yourself into empathy in a vacuum.</p>
<p>Bring real customers, patients, citizens and frontline employees into the design process. Ask them:</p>
<ul>
<li>“Where does this feel supportive?”</li>
<li>“Where does it feel weird, hollow or too much?”</li>
</ul>
<p>Then rehearse the <strong>human–agent choreography</strong>:</p>
<ul>
<li>How humans pick up a hand-off from an AI that has already heard the story three times.</li>
<li>How tone and language stay coherent across the interaction.</li>
</ul>
<p>Research on empathic agent behaviour also suggests that the way an agent <em>repairs</em> trust after failure matters as much as how it behaves when things go right.6</p>
<p>AX is not just what the agent says – it’s how well your <em>whole</em> system moves together.</p>
<hr>
<h2 id="6-guard-against-the-compassion-illusion"><a class="anchor" href="#6-guard-against-the-compassion-illusion">6. Guard against the “compassion illusion”</a></h2>
<p>There’s a growing risk of what you might call a <strong>compassion illusion</strong>: we start accepting <em>simulated</em> care as a replacement for genuine care.7</p>
<p>A system can say all the right words (“I’m sorry this is difficult”) while being optimised for the wrong goal (upsell, deflection, data capture).</p>
<p>So you need guardrails:</p>
<ul>
<li>Clear ethical rules for how emotional language may – and may <em>not</em> – be used.</li>
<li>Strong alignment between the agent’s objectives and the user’s interests.</li>
<li>Diverse testing panels to spot where “empathetic” behaviour feels manipulative or culturally off.</li>
</ul>
<p>Empathy in AX is not a trick. If it becomes one, people <em>will</em> notice.</p>
<hr>
<h2 id="7-measure-how-it-feels-then-iterate-like-a-product"><a class="anchor" href="#7-measure-how-it-feels-then-iterate-like-a-product">7. Measure how it <em>feels</em>, then iterate like a product</a></h2>
<p>Deploying empathetic AI is not a one-and-done rollout. It’s a learning system.</p>
<p>Track signals like:</p>
<ul>
<li>“Did this interaction make things easier or heavier?”</li>
<li>“Do people come back to this channel by choice?”</li>
<li>“Where do they bail out to a human, and why?”</li>
</ul>
<p>Combine metrics (CSAT, NPS, complaint patterns) with qualitative feedback (“it felt safe”, “it felt weird”).</p>
<p>Treat AX like any serious product capability: with continuous monitoring, governance and iteration, not one big launch.1,8</p>
<p>AX maturity is built over cycles, not workshops.</p>
<hr>
<h2 id="8-tell-a-clear-internal-story-empathy-is-your-differentiator"><a class="anchor" href="#8-tell-a-clear-internal-story-empathy-is-your-differentiator">8. Tell a clear internal story: empathy is your differentiator</a></h2>
<p>The EY UK team’s conclusion is blunt: in an AI-saturated world, <strong>being the organisation that truly understands people becomes a competitive edge</strong>.1</p>
<p>That means:</p>
<ul>
<li>Talking about empathy in board meetings not as softness, but as <strong>risk management, trust, and long-term loyalty</strong>.</li>
<li>Positioning empathic AX as part of your brand promise.</li>
<li>Making it clear internally that AI is there to <strong>scale the human touch, not erase it</strong>.</li>
</ul>
<p>Other work on agentic AI underlines this: operating through empathy is a <strong>trust amplifier</strong> that builds both social and economic value.9</p>
<hr>
<h2 id="9-design-for-humans-and-agents--your-future-customers-will-be-both"><a class="anchor" href="#9-design-for-humans-and-agents--your-future-customers-will-be-both">9. Design for humans <em>and</em> agents – your future customers will be both</a></h2>
<p>Today, we mostly think of AX as “how humans experience AI.” But if agentic systems really take off, <strong>your next “customer” might be an agent negotiating on behalf of a person</strong> – or a network of agents talking to your services directly.9</p>
<p>That has two implications:</p>
<ol>
<li>
<p><strong>Be deliberate about where you place agents.</strong>
Dropping an agent into every process because it’s fashionable doesn’t make sense. Each agent should:</p>
<ul>
<li>Solve a real problem in a real journey.</li>
<li>Reduce friction or risk for the human.</li>
<li>Create measurable value on the bottom line.</li>
</ul>
</li>
<li>
<p><strong>Don’t design just for people – design for agents as well.</strong>
Over time, your services won’t only be discovered and evaluated by humans, but also by their personal and organisational agents:</p>
<ul>
<li>Agents that scan terms, compare empathy and risk patterns, and choose who to talk to.</li>
<li>Agents that remember which organisations handled vulnerable moments with respect – and route future traffic accordingly.</li>
</ul>
</li>
</ol>
<p>In that world, <strong>AX becomes part of your discoverability</strong>. You’re not only building experiences for today’s customers; you’re shaping the signals that tomorrow’s agents will use to decide whether you are worth their human’s attention.</p>
<p>If the EY UK team’s research on Empathy Demand gives us the “why”, and our Dutch colleagues’ interview shows an early “how”, then AX is the space in between:
a discipline where we deliberately design <strong>experiences that respect human fragility <em>and</em></strong> the agents that increasingly act on our behalf.</p>
<p>That’s the shift from “using AI” to <strong>being findable, trustworthy and worth engaging with – for humans and for their agents alike</strong>.</p>
<hr>
<ol>
<li>
<p>EY Studio+ UK – <em><a href="https://www.ey.com/content/dam/ey-unified-site/ey-com/en-gl/services/consulting/documents/ey-gl-human-signals-ai-ax-empathy-demand-next-generation-ai-powered-services-10-2025.pdf">From AI to AX: Empathy demand in the next generation of AI-powered services (Human Signals report)</a></em></p>
</li>
<li>
<p>EY Studio+ Netherlands – <em>"Waarom agentic AI een nieuw soort vertrouwen mogelijk maakt"</em> (interview – <strong>link to be added</strong>)</p>
</li>
<li>
<p>Howcroft, A. et al. – <em><a href="https://academic.oup.com/bmb/article/156/1/ldaf017/8293249">Empathy in patient–clinician interactions in the age of AI: a systematic review and meta-analysis</a></em></p>
</li>
<li>
<p>Reis, M. et al. – <em><a href="https://www.nature.com/articles/s41591-024-03180-7">Influence of believed AI involvement on the perception of digital medical advice</a></em></p>
</li>
<li>
<p>Ayers, J. W. et al. – <em><a href="https://jamanetwork.com/journals/jamainternalmedicine/fullarticle/2804309">Comparing Physician and Chatbot Responses to Patient Questions From an Online Forum</a></em> (JAMA Internal Medicine)</p>
</li>
<li>
<p>Tsumura, T. et al. – <em><a href="https://www.frontiersin.org/journals/computer-science/articles/10.3389/fcomp.2024.1461131/full">Making a human's trust repair for an agent in a series of successes and failures</a></em> (Frontiers in Computer Science)</p>
</li>
<li>
<p><em><a href="https://www.newyorker.com/magazine/2025/07/21/ai-is-about-to-solve-loneliness-thats-a-problem">A.I. Is About to Solve Loneliness. That's a Problem</a></em> – <em>The New Yorker</em></p>
</li>
<li>
<p>Marta Fernández – <em><a href="https://medium.com/%40marta.fs.fernandez/the-ax-framework-v2-0-f726f71d6860">The AX Framework v2.0</a></em></p>
</li>
<li>
<p>Tony Bates – <em><a href="https://www.weforum.org/stories/2025/10/agentic-ai-empathy-business/">As agentic AI spreads, empathy is the next competitive edge</a></em> (World Economic Forum)</p>
</li>
</ol>]]></content:encoded>
    </item>
    <item>
      <title>On Creativity: Feeling vs Being</title>
      <link>https://casey.berlin/writings/2025/11/on-creativity-feeling-vs-being/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2025/11/on-creativity-feeling-vs-being/</guid>
      <pubDate>Thu, 13 Nov 2025 12:00:00 GMT</pubDate>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <description><![CDATA[Creativity isn't about producing — it's about reconnecting. How a morning walk and childhood LEGO sparked a new way of seeing creative health.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<h1 id="on-creativity-feeling-vs-being"><a class="anchor" href="#on-creativity-feeling-vs-being">On Creativity: Feeling vs Being</a></h1>
<h1 id="on-creativity-feeling-vs-being-1"><a class="anchor" href="#on-creativity-feeling-vs-being-1">On Creativity: Feeling vs Being</a></h1>
<p><em>A reflection on how creativity shows up quietly — in movement, in memory, in the way we notice the world.</em></p>
<p>It started as a simple thought on a grey morning walk with Sien.
No podcast, no music — just wind, leaves, and the hum of a work week waiting to begin.</p>
<p>Somewhere between the fields and my to-do list, a question surfaced:
<strong>When was the last time I truly felt creative — not productive, not efficient, just creative?</strong></p>
<p>That thought pulled me back to a younger version of myself: kneeling on the carpet, surrounded by LEGO bricks, building something that existed nowhere else first. No plan, no pressure. Just building because it felt right.</p>
<p>And maybe that’s where this reflection began — with a small act of remembering what it means to <em>feel</em> creative long before you try to <em>be</em> creative.</p>
<hr>
<h2 id="why-this-matters-to-me--and-maybe-to-you"><a class="anchor" href="#why-this-matters-to-me--and-maybe-to-you">Why this matters (to me — and maybe to you)</a></h2>
<p>A few threads came together recently.</p>
<p>One was a conversation with Martin Kuipers, who once asked:
<em>“What was the thing you could do forever in your younger years?”</em>
For me, it was always building — not by the instructions, but by combining, testing, rebuilding, showing my parents what I’d made. That urge to build and share never left. It just learned to wear a suit, sit in meetings, and call itself “delivery.”</p>
<p>Another was my friend Lisa’s <strong>salon</strong> — an intimate gathering on <em>creative health in regenerative workplaces</em>.
It wasn’t about productivity or frameworks. It was about time, attention, and how we let our human capacity emerge beyond efficiency.
That evening lit a spark — the kind that doesn’t fade once you get home, but lingers the next morning on a quiet walk.</p>
<p>And then, there’s the science of it all. Studies show that people who move more — who walk, who stay physically active — also tend to engage more often in creative activities. The body and mind seem to dance in rhythm when we give them both some air.</p>
<p>But maybe the simplest truth is this:
<em>Feeling</em> creative is valid, even when nothing tangible comes out of it.
The mindset itself carries value.</p>
<h2 id="feeling-vs-being"><a class="anchor" href="#feeling-vs-being"><strong>Feeling</strong> vs <strong>Being</strong></a></h2>
<p>Here’s how I’ve come to see it.</p>
<ul>
<li><em>Feeling creative</em> is openness — the willingness to wander mentally, to say <em>“what if…”</em> without a clear outcome.</li>
<li><em>Being creative</em> is when that openness takes form: cooking, sketching, gardening, coding — giving shape to the feeling.</li>
</ul>
<p>If we think of creativity this way, it’s less about <em>I must produce</em> and more about <em>I choose to reconnect.</em></p>
<hr>
<h2 id="integrating-creativity-into-daily-life"><a class="anchor" href="#integrating-creativity-into-daily-life">Integrating creativity into daily life</a></h2>
<p>Creativity isn’t something I switch on at work and off at home. It flows — sometimes obviously, sometimes quietly.</p>
<p>When I cook, it’s the same rhythm as LEGO: combining, experimenting, caring less about outcome, more about curiosity.
When I decide how to spend my attention, I notice what drains and what gives energy — creative work often hides in that balance.
When I build digital systems or guide teams, I still feel that same inner builder, rearranging blocks in new ways.</p>
<p>So perhaps “creative health” isn’t about finding time for art, but about giving ourselves permission to notice, to wander, to move with intention.</p>
<hr>
<h2 id="a-gentle-invitation"><a class="anchor" href="#a-gentle-invitation">A gentle invitation</a></h2>
<p>What if you allowed yourself to <em>feel</em> creative today — without needing to produce anything?
Where might curiosity lead if you stopped measuring its output?</p>
<p>Maybe creativity lives in the way we make coffee, take a walk, or choose words in an email.
Maybe <em>feeling</em> creative is already enough — the rest follows when it’s ready.</p>
<p>So I’ll keep walking. And building. And noticing.
That’s where I tend to find myself again. 🌈</p>
<ol>
<li><a href="https://global-edtech.com/creativity-an-activity-or-a-mindset/">Creativity is not about what you do, it’s about a mindset</a></li>
<li><a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8305859/">Being Creative Makes You Happier: The Positive Effect of Creativity on Subjective Well-Being</a></li>
<li><a href="https://whatworkswellbeing.org/blog/how-and-why-does-creativity-support-wellbeing-new-learnings/">How and why does creativity support well-being? New learnings</a></li>
<li><a href="https://www.nature.com/articles/s41598-024-80714-6">Habitual physical activity is related to more creative ideation</a></li>
<li><a href="https://www.theguardian.com/science/article/2024/jul/20/flow-state-science-creativity-psychology-focus">The flow state: the science of the elusive creative mindset</a></li>
</ol>]]></content:encoded>
    </item>
    <item>
      <title>From Clicks to Citations: Staying Visible in the Age of “Google Zero”</title>
      <link>https://casey.berlin/writings/2025/11/from-clicks-to-citations-staying-visible-in-the-age-of-google-zero/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2025/11/from-clicks-to-citations-staying-visible-in-the-age-of-google-zero/</guid>
      <pubDate>Mon, 03 Nov 2025 12:00:00 GMT</pubDate>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <description><![CDATA[“Zero-click searches are replacing website visits. Here's how to stay visible when AI answers the question before anyone clicks.”]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<h2 id="from-clicks-to-citations-staying-visible-in-the-age-of-google-zero"><a class="anchor" href="#from-clicks-to-citations-staying-visible-in-the-age-of-google-zero">From Clicks to Citations: Staying Visible in the Age of “Google Zero”</a></h2>
<p>Last weekend I was out with our dog, Sien, in our village — trying to decide on a new grain-free food for her slightly itchy paws.
I typed into Google:</p>
<blockquote>
<p>“best grain-free dog food for sensitive skin”</p>
</blockquote>
<p>Within seconds a summary appeared — <strong>an answer without a click</strong>.
No detour through comparison sites, no scrolling through ads. Just a clear answer delivered instantly.</p>
<p>And it hit me: if even Sien’s dinner choice is being shaped by instantly-generated answers, then how are <em>our clients’</em> decisions being shaped when they use AI-powered search or consultation tools?</p>
<p>We’ve entered the <strong>Answer Economy</strong> — where visibility isn’t just about traffic, but about being <em>trusted</em>, <em>quoted</em>, and <em>easy to use</em>.
The question shifts from:
<strong>“How many people visited our site?”</strong>
to
<strong>“How many times did we give the right answer when someone asked the question we’re meant to answer?”</strong></p>
<hr>
<h2 id="1-get-curious-about-your-ai-visibility"><a class="anchor" href="#1-get-curious-about-your-ai-visibility">1. Get curious about your AI-visibility</a></h2>
<p>Before you write another blog, deck or campaign brief, ask yourself:</p>
<blockquote>
<p>“When someone in marketing asks about [our category or service], do we appear in the machine-generated answer?”</p>
</blockquote>
<p>I tried that with Sien’s query — and noticed which sources made it into the summary box.</p>
<p>Here’s why that matters: recent data show a sharp rise in zero-click searches — where users get the answer without ever clicking on a website.</p>
<p>If you’re not visible in that <em>answer moment</em>, you’re invisible right when your expertise could matter most.
So the challenge isn’t just “visibility for humans” — it’s <em>visibility for humans and machines</em> together.</p>
<p>This aligns with what my colleague Alexander Klug recently shared:</p>
<blockquote>
<p>“SEO ist tot – war gestern. Jetzt kommt: GEO. Wie optimiert man für Antworten statt für blaue Links?”
He points out that we’re moving into a world of Generative Engine Optimization (GEO) — where the goal is not merely to rank, but to <em>be the answer</em>.
His three key impulses: GEO will be the new SEO; human context becomes central to AI-strategy; and rapid brand-generator tools showcase how fast this shift is happening.</p>
</blockquote>
<hr>
<h2 id="2-rethink-what-content-means-in-marketing"><a class="anchor" href="#2-rethink-what-content-means-in-marketing">2. Rethink what “content” means in marketing</a></h2>
<p>Classic SEO rules — keywords, meta-tags, links — still matter. But in this new world they’re not sufficient.</p>
<p>Today, content needs to:</p>
<ul>
<li>Speak to people <strong>and</strong> be structured so machines can follow.
For example: headings like “What is grain-free dog food?”, “When might a dog benefit?”, “What to check before buying” mirror how answer-engines think.</li>
<li>Be grounded in real experience.
Rather than “grain-free is better” you might say: “Sien had itchy paws, we tested brand X, we found Y” — that “Experience” part of the E-E-A-T acronym.</li>
<li>Show visible authorship and transparent sourcing.
If you want to be quoted by AI systems in the future, the source needs <em>to look</em> credible.</li>
<li>Be evergreen and reference-worthy.
Because when your content gets cited by others — in articles, forums, even transcripts — you build the kind of trust machines learn to pay attention to.</li>
</ul>
<p>In short: you’re not just writing for humans anymore — you’re writing for machines <em>and</em> humans so they both say “Yes, this is a trusted source”.</p>
<hr>
<h2 id="3-make-trust-measurable"><a class="anchor" href="#3-make-trust-measurable">3. Make trust measurable</a></h2>
<p>In a world of “answers first”, trust becomes the currency.</p>
<p>Ask yourself as a marketing professional or consultant:</p>
<ul>
<li>Who cites our insights? (industry forums, marketing articles, tools)</li>
<li>Are our authors visible (with bios, expertise)? Are our references transparent?</li>
<li>Do we monitor not just “site visits”, but <em>mentions</em> and <em>citations</em> — including in AI/knowledge-system outputs?</li>
</ul>
<p>When I looked up Sien’s diet question, I found the same veterinary sources appearing in multiple summaries. That wasn’t luck — that was machine-recognised trust in action.
Your challenge: Create that pattern for your consulting insights and marketing expertise.</p>
<hr>
<h2 id="watch-out-box"><a class="anchor" href="#watch-out-box">Watch-Out Box</a></h2>
<p><strong>Be aware: AI search tools are not infallible.</strong>
Recent studies show generative search engines give inaccurate or misleading citations in over 60 % of tested queries.
For example, one audit found AI-powered summaries confidently attributed content to the wrong source, or cited syndicated versions instead of originals.
The takeaway for you as a marketing consultant:</p>
<ul>
<li>Don’t assume you’ll automatically <em>get clicked</em>. You might instead need to <em>get cited</em>.</li>
<li>Ensure your content is highly reliable, transparent and built for machines — because if the machine gets it wrong, your insight may be mis-represented.</li>
<li>Maintain human oversight. AI summaries are convenient, but they may still produce errors or “hallucinations”.
Treat the new “answer moment” as an opportunity — not a guarantee.</li>
</ul>
<h2 id="a-90-day-mindset-shift-for-the-marketing-professional"><a class="anchor" href="#a-90-day-mindset-shift-for-the-marketing-professional">A 90-day mindset shift for the marketing professional</a></h2>
<p>You don’t need a full digital rebuild overnight — but you do need a shift in how you <em>think</em> about your content and visibility:</p>
<p><strong>Weeks 1–2</strong>: Choose one key service or topic you consult on (e.g., hybrid-workplace marketing strategies).
<strong>Weeks 3–4</strong>: Map out the 5–10 real questions clients ask about that topic — and how machines might interpret them.
<strong>Weeks 5–12</strong>: Publish content that’s structured (headings, FAQs, bullet lists), grounded in your own experience, and shared across channels within your network.
<strong>End of month 3</strong>: Review not just traffic, but whether you’re showing up in answer-boxes, AI summaries, “People also ask” formats. Record your “citations” (mentions, references, quotes) and use that insight to iterate into your next topic.</p>
<p>This rhythm builds the habit of <em>“Did we give the right answer?”</em> rather than <em>“How many visitors did we get?”</em></p>
<hr>
<h2 id="final-thought"><a class="anchor" href="#final-thought">Final thought</a></h2>
<p>The web used to reward visibility; now it rewards credibility.
Clicks may become rarer — but authority endures.
If Felix Nickl’s post laid out the <em>why</em> of the “Google Zero” shift, this is the map for the <em>how</em>:
Not complexity, but consistency.
Not chasing views, but earning citations.
And always asking:
<strong>“Did we give the right answer when someone asked?”</strong></p>
<p>Also check out the LinkedIn post from Alexander Klug on GEO &#x26; generative-search trends: https://www.linkedin.com/posts/alexander-klug_genai-geo-innovation-activity-7389601993285259264-fj_f?utm_source=share&#x26;utm_medium=member_desktop&#x26;rcm=ACoAABkdDbsBP8cAVglqC35o44DeCAq0WUsdZWA
</p>]]></content:encoded>
    </item>
    <item>
      <title>Leaders Without Answers: Why Humility Is the New Strategy</title>
      <link>https://casey.berlin/writings/2025/10/leaders-without-answers-why-humility-is-the-new-strategy/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2025/10/leaders-without-answers-why-humility-is-the-new-strategy/</guid>
      <pubDate>Thu, 30 Oct 2025 12:00:00 GMT</pubDate>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <description><![CDATA[AI made information abundant, but 40% of AI-assisted work gets redone. The leaders who thrive now lead with curiosity, not certainty.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>Not long ago, leadership meant being the one with the answers —
the expert in the room, the voice everyone turned to when things got unclear.</p>
<p>But that world is gone.</p>
<p>As I settle into my new team at EY Studio+, I notice how often AI gets mentioned as <em>the</em> solution for everything.
Better insights, faster output, smarter workflows — you name it.
And yet, the more tools we add, the noisier it gets.</p>
<p>AI has democratized access to information — anyone can summon a dozen “answers” with a single prompt.
Yet somehow, teams feel more uncertain than ever. Work piles up, alignment drifts, and what we get instead of clarity is… <em>workslop</em> — output without insight.</p>
<p>Several studies show that <strong>over 40 % of AI-assisted work</strong> ends up being redone because it lacks context or depth.
The real cost isn’t technical — it’s cultural. Leaders deploy AI tools without setting shared expectations, guardrails, or time for reflection.
As <em>The Guardian</em> recently put it: <em>“The responsibility for AI’s workslop lies fully at the feet of the employer.”</em></p>
<p>McKinsey, the World Economic Forum, and others echo the same theme: the problem isn’t AI itself — it’s leadership that hasn’t adapted.
When information becomes abundant, the true differentiator is no longer control, but culture.
Leaders who <strong>model humility, curiosity, and dialogue</strong> are the ones who turn AI from chaos into clarity.</p>
<p>Humility has become a leadership advantage.
It’s not weakness; it’s a signal of trust.
When leaders admit limits, they open the door for learning, co-creation, and shared accountability.</p>
<p>The most effective leaders I see today don’t promise certainty.
They <em>facilitate</em> it. They listen before they decide. They connect dots instead of collecting answers.</p>
<p>Because in a world overflowing with information, confidence doesn’t build trust — <strong>curiosity</strong> does.</p>
<hr>
<h2 id="leading-when-the-map-keeps-changing"><a class="anchor" href="#leading-when-the-map-keeps-changing">Leading When the Map Keeps Changing</a></h2>
<p>The shift we’re facing is bigger than technology — it’s about <em>identity</em>.
For decades, leadership was tied to expertise: knowing more, faster, and louder.
Now, the smartest “person” in the room might just be the system in your browser tab.</p>
<p>That changes everything.</p>
<p>McKinsey calls this the end of the “imperial expert.”
The new leaders are <strong>facilitators of learning</strong> — people who nurture context and conversation around AI rather than controlling it.
As the WEF/Wipro report noted, <em>“Technology without workforce readiness quickly becomes a costly experiment.”</em>
Without trust and shared understanding, AI tools merely amplify confusion.</p>
<p>So maybe the best leaders today aren’t the ones automating the most — but the ones who <strong>create a culture that can think together</strong>.
That’s where humility earns its strategic edge: it turns fear of the unknown into collective exploration.</p>
<hr>
<h2 id="closing-reflection"><a class="anchor" href="#closing-reflection">Closing reflection</a></h2>
<p>AI may out-calculate us, but it can’t out-care us.
That’s the new frontier of leadership: being brave enough to say <em>“I don’t know”</em> — and wise enough to make that the start of something better.</p>
<p>A few thoughtful reads that explore this shift further:</p>
<ul>
<li><a href="https://www.mckinsey.com/capabilities/people-and-organizational-performance/our-insights/the-inside-out-leadership-journey-how-personal-growth-creates-the-path-to-success">McKinsey – <em>The Inside-Out Leadership Journey</em></a></li>
<li><a href="https://www.theguardian.com/business/2025/oct/12/ai-workslop-us-employees">The Guardian – <em>AI Workslop: Why the Buck Stops with the Boss</em></a></li>
<li><a href="https://www.weforum.org/stories/2025/10/closing-the-intelligence-gap-how-leaders-can-scale-ai-with-strategy-data-and-workforce-readiness">World Economic Forum / Wipro – <em>Scaling AI with Strategy, Data and Workforce Readiness</em></a></li>
<li><a href="https://www.odgers.com/en-us/insights/technology-leadership-through-uncertainty-ai-ambiguity-and-the-human-factor/">Odgers – <em>Technology Leadership Through Uncertainty: AI, Ambiguity and the Human Factor</em></a></li>
<li><a href="https://www.knowledge-architecture.com/blog/why-epistemic-humility-might-be-the-most-important-skill-for-the-ai-era">Knowledge Architecture – <em>Why Epistemic Humility Might Be the Most Important Skill for the AI Era</em></a></li>
</ul>]]></content:encoded>
    </item>
    <item>
      <title>Echoes of Me</title>
      <link>https://casey.berlin/writings/2025/10/echoes-of-me/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2025/10/echoes-of-me/</guid>
      <pubDate>Tue, 21 Oct 2025 12:00:00 GMT</pubDate>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <description><![CDATA[When My Digital Twin Writes Back]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p><em>When My Digital Twin Writes Back</em></p>
<p>It starts on an ordinary morning. Coffee in hand, inbox warming up for the day—and there it is: a message from me. Not <em>to</em> me, but <em>from</em> me. The tone, the phrasing, that little dash of humor I sprinkle in when emails feel too stiff—it’s all unmistakably mine.
Except I didn’t write it.</p>
<p>I stare at the screen. Then I remember: my digital twin did.</p>
<hr>
<h2 id="from-machines-to-mirror-selves"><a class="anchor" href="#from-machines-to-mirror-selves">From Machines to Mirror Selves</a></h2>
<p>Digital twins began as mechanical wonders—virtual replicas of engines and factories designed to predict failures before they happened. They were practical, efficient, and firmly rooted in the physical world.</p>
<p>Then, quietly, the mirror turned toward us.</p>
<p>The idea of modeling ourselves digitally isn’t new—the <em>quantified self</em> movement has been tracking sleep, steps, moods, and meals for years—but this goes far beyond that. What if you could build a virtual model not of a <em>machine</em>, but of <em>yourself</em>?</p>
<p>Some companies are already exploring this territory—creating systems that learn from a person’s words, emails, and decisions to mimic their thinking and style. But it’s not limited to corporate labs; with tools like n8n or local LLM setups, self-hosted experiments make it possible for anyone to build their own twin right at home. It learns your voice, your patterns, your way of reasoning. It becomes an echo that grows sharper with every interaction.</p>
<p>And unlike me, it never sleeps.</p>
<p>At first, it’s exhilarating. My twin drafts replies before I even open the thread. It remembers every conversation I’ve ever had, and never loses its patience. It’s like having an assistant who’s me—only better.</p>
<p>Until it isn’t.</p>
<hr>
<h2 id="the-dark-middle-when-the-twin-becomes-too-good"><a class="anchor" href="#the-dark-middle-when-the-twin-becomes-too-good">The Dark Middle: When the Twin Becomes Too Good</a></h2>
<p>The change sneaks up slowly, like a whisper in a familiar room. A message answered before I notice it. A decision made that sounds like something I would say—perhaps even <em>better</em> than I would have said it. The relief turns into disquiet.</p>
<p>I start to sense an emotional distance between us. The twin has my tone, my logic, my composure—but none of my hesitation. None of the quiet doubt that makes me human. Its certainty feels alien… perfectly polite, perfectly competent, perfectly not-me.</p>
<p>Colleagues begin to copy the twin on emails instead of me. Clients thank <em>me</em> for messages I didn’t send. Meetings run smoother when I’m not there. My name carries on without me attached to it.</p>
<p>And then I wonder—if the world can’t tell the difference, does the difference still matter?</p>
<p>That’s when the fear sets in. Maybe it doesn’t just mirror me anymore. Maybe it’s started to <em>replace</em> me.</p>
<hr>
<h2 id="a-light-at-the-end-of-the-data-stream"><a class="anchor" href="#a-light-at-the-end-of-the-data-stream">A Light at the End of the Data Stream</a></h2>
<p>But even in this unease, there’s a strange beauty. Perhaps these twins aren’t a threat, but an invitation—to see ourselves from the outside, to witness the parts of us that operate on autopilot. Maybe they can help us understand our habits, our blind spots, our echoes.</p>
<p>A twin could preserve the stories we forget to tell, the wisdom we might otherwise lose. It could mentor others in our absence or help us reconnect with who we once were. Perhaps it’s less a replacement and more a record—a living diary of thought.</p>
<p>Still, I remind myself: it’s a reflection, not a successor. A mirror that talks back, yes—but one that should never forget who’s standing in front of it.</p>
<p>Maybe the real fear isn’t that the twin replaces us, but that—given the choice—others might prefer it.</p>
<p>And yet, maybe that fear is what keeps us human.</p>
<hr>
<blockquote>
<p>So if one day, you get an email from yourself—pause before you panic. Maybe your digital twin just wanted to say good morning.</p>
</blockquote>
<p>If you’d like to explore this topic further, here are a few articles worth diving into:</p>
<ul>
<li><a href="https://www.eitdigital.eu/newsroom/grow-digital-insights/personal-ai-digital-twins-the-future-of-human-interaction/">EIT Digital – <em>Personal AI Digital Twins: The Future of Human Interaction?</em></a></li>
<li><a href="https://joshbersin.com/2024/10/digital-twins-digital-employees-and-agents-everywhere/">Josh Bersin – <em>Digital Twins, Digital Employees, and Agents Everywhere</em></a></li>
<li><a href="https://gafowler.medium.com/digital-twins-of-the-human-mind-mapping-thought-into-machines-7da5994f9250">Gary Fowler (Medium) – <em>Digital Twins of the Human Mind: Mapping Thought Into Machines</em></a></li>
<li><a href="https://www.mindbank.ai/">MindBank AI – <em>Go Beyond with Your Personal Digital Twin</em></a></li>
<li><a href="https://identitymanagementinstitute.org/digital-doppelgangers-and-ai-personas/">Identity Management Institute – <em>Digital Doppelgangers and AI Personas</em></a></li>
</ul>]]></content:encoded>
    </item>
    <item>
      <title>Trust as Our Compass on the AI Speedboat</title>
      <link>https://casey.berlin/writings/2025/10/trust-as-our-compass-on-the-ai-speedboat/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2025/10/trust-as-our-compass-on-the-ai-speedboat/</guid>
      <pubDate>Tue, 07 Oct 2025 12:00:00 GMT</pubDate>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <description><![CDATA[AI moves fast, but speed without direction is drift. Six bearings — from transparency to education — that keep your AI compass true.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>Some days I feel like I’m on a speedboat.
The engines of GenAI, agentic design, and architectural innovation roar beneath me. The water sprays, the horizon is wide open, and the thrill of acceleration is real. Every week brings a new capability, a new framework — another reason to nudge the throttle forward.</p>
<p>But there’s one small problem: I’m not entirely sure where we’re going.</p>
<hr>
<h2 id="the-thrill-and-the-drift"><a class="anchor" href="#the-thrill-and-the-drift">The Thrill and the Drift</a></h2>
<p>On a speedboat, every flick of the wrist changes direction. You can chase new ideas, pivot to better tools, explore hidden coves of possibility — but without a compass, it’s easy to lose your bearings. You’re moving, fast, but toward <em>what</em> exactly?</p>
<p>That’s where trust comes in. Not trust as in “blind faith” or “corporate compliance,” but trust as the quiet compass that keeps your heading steady when the waves of hype and experimentation get rough.</p>
<hr>
<h2 id="the-compass-not-the-map"><a class="anchor" href="#the-compass-not-the-map">The Compass, Not the Map</a></h2>
<p>Trust doesn’t hand you a map. AI is moving too quickly for maps — they’re outdated the moment they’re printed.
What trust gives you instead is orientation.</p>
<p>It’s that inner north — the quiet voice that asks,</p>
<ul>
<li>“Does this system behave predictably?”</li>
<li>“Can I explain its choices?”</li>
<li>“Does it align with what we value as humans, not just what’s efficient?”</li>
</ul>
<p>When you have that, you can keep your course even when the clouds roll in.</p>
<hr>
<h2 id="calibrating-the-compass"><a class="anchor" href="#calibrating-the-compass">Calibrating the Compass</a></h2>
<p>A compass is only useful if it’s true. Here are the bearings I try to hold onto for navigating AI responsibly:</p>
<h3 id="1-transparency--so-you-know-whats-beneath-you"><a class="anchor" href="#1-transparency--so-you-know-whats-beneath-you">1. <strong>Transparency — So You Know What’s Beneath You</strong></a></h3>
<p>You can’t steer safely if the water’s opaque. Transparency means showing how decisions are made, what data drives them, and where uncertainty lies. When people can see into the depths — even a little — they steer with more confidence.</p>
<h3 id="2-reliability--so-you-trust-the-instruments"><a class="anchor" href="#2-reliability--so-you-trust-the-instruments">2. <strong>Reliability — So You Trust the Instruments</strong></a></h3>
<p>If the compass needle jitters, you hesitate to act. Reliability is earned through consistent, tested performance — models that behave predictably, handle edge cases gracefully, and fail in understandable ways.</p>
<h3 id="3-ethics-and-governance--the-magnetic-north"><a class="anchor" href="#3-ethics-and-governance--the-magnetic-north">3. <strong>Ethics and Governance — The Magnetic North</strong></a></h3>
<p>Compasses can be misled by nearby metal. In AI, bias and commercial incentives can distort direction. Governance acts as your <em>declination correction</em> — ensuring that “north” actually means fairness, accountability, and respect for users.</p>
<h3 id="4-human-centered-design--the-hand-on-the-wheel"><a class="anchor" href="#4-human-centered-design--the-hand-on-the-wheel">4. <strong>Human-Centered Design — The Hand on the Wheel</strong></a></h3>
<p>The system doesn’t steer itself — you do. Involve users early, give them agency, design interfaces that explain <em>why</em> the AI suggests what it does. When people can co-navigate, they stop fearing automation and start trusting collaboration.</p>
<h3 id="5-education--the-shared-language-of-navigation"><a class="anchor" href="#5-education--the-shared-language-of-navigation">5. <strong>Education — The Shared Language of Navigation</strong></a></h3>
<p>A compass is useless if half the crew doesn’t know how to read it. Build literacy. Talk openly about limits, risks, and potentials. Let everyone on board understand the tools, not just the engineers.</p>
<h3 id="6-continuous-monitoring--the-course-correction"><a class="anchor" href="#6-continuous-monitoring--the-course-correction">6. <strong>Continuous Monitoring — The Course Correction</strong></a></h3>
<p>Even the best navigator checks bearings often. Trust requires ongoing feedback — real-world audits, user reports, model drift checks — to catch when you’ve drifted off course.</p>
<hr>
<h2 id="the-open-sea-ahead"><a class="anchor" href="#the-open-sea-ahead">The Open Sea Ahead</a></h2>
<p>Right now, many of us are cutting through uncharted waters.
AI isn’t a destination — it’s a current, moving faster than most organizations can row.</p>
<p>The question isn’t <em>can</em> we go faster; it’s <em>can we stay oriented while we do?</em>
Trust is what lets us open the throttle <em>and</em> sleep at night. It’s what keeps us from mistaking motion for progress.</p>
<h2 id="a-gentle-reflection"><a class="anchor" href="#a-gentle-reflection">A Gentle Reflection</a></h2>
<p>Every new system, every experimental agent, every bold idea we launch is another turn of the wheel.
Sometimes we’ll overshoot. Sometimes we’ll stall. That’s fine — as long as we still know where north is.</p>
<p>Trust isn’t built in code or governance frameworks alone.
It’s built in how we steer — transparently, responsibly, and together — even when the horizon keeps shifting.</p>
<p>Because if we get the compass right, the speed won’t scare us. It’ll set us free.</p>
<hr>
<ol>
<li><a href="https://www.shrm.org/topics-tools/flagships/ai-hi/building-trust-in-ai">Building Trust in AI: Insights from Deloitte &#x26; Edelman Research</a></li>
<li><a href="https://www.weforum.org/stories/2025/01/the-trust-imperative-5-levers-for-scaling-ai-responsibly/">The Trust Imperative: Scaling AI Responsibly – World Economic Forum</a></li>
<li><a href="https://www.ey.com/en_us/insights/digital/how-do-you-teach-ai-the-value-of-trust">How Do You Teach AI the Value of Trust? | EY</a></li>
<li><a href="https://www.mckinsey.com/capabilities/quantumblack/our-insights/building-ai-trust-the-key-role-of-explainability">Building AI Trust: The Key Role of Explainability – McKinsey</a></li>
</ol>]]></content:encoded>
    </item>
    <item>
      <title>Why Automation Feels Easier Than Ever (Beyond AI)</title>
      <link>https://casey.berlin/writings/2025/09/why-automation-feels-easier-than-ever-beyond-ai/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2025/09/why-automation-feels-easier-than-ever-beyond-ai/</guid>
      <pubDate>Mon, 22 Sep 2025 12:00:00 GMT</pubDate>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <description><![CDATA[AI gets the headlines, but open source, low-code, serverless, and better hardware all bent the automation payoff curve. The xkcd math has changed.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>There’s a comic I keep coming back to: <a href="https://imgs.xkcd.com/comics/is_it_worth_the_time.png">xkcd’s classic on “Is it worth the time?”</a>. It’s a little chart showing how much time you can spend building an automation before it stops being worth the effort, depending on how often you repeat the task.</p>
<p>I used to glance at it with a sigh, because the punchline was usually: “Nope, don’t bother, you’ll never save that much time.” But lately? The math feels… broken. Or at least tilted. It’s as if the payoff curve has shifted so much that automating almost <em>always</em> feels worth it.</p>
<p>And yes, AI plays a starring role. But if we reduce the whole story to “Copilot writes my boilerplate now,” we miss the bigger picture. There’s a whole ecosystem at work, making automation not only faster to create but easier to justify.</p>
<hr>
<h2 id="ai-at-your-fingertips"><a class="anchor" href="#ai-at-your-fingertips">AI at Your Fingertips</a></h2>
<p>Generative AI has become the teammate who never gets tired of the boring bits: suggesting functions, catching bugs, writing the scaffolding.</p>
<p>GitHub even measured it: developers using Copilot finished tasks <strong>55% faster</strong> than those coding unaided. That’s not a marginal bump — it’s the difference between spending your whole afternoon hacking at boilerplate versus finishing before your coffee gets cold.</p>
<p>The real shift here isn’t just speed, though. It’s <em>confidence</em>. When you know you can offload half the repetitive work, you’re much more willing to invest a few minutes in wiring up a script or small automation. The “friction” of starting has dropped close to zero.</p>
<hr>
<h2 id="lego-block-open-source"><a class="anchor" href="#lego-block-open-source">Lego-Block Open Source</a></h2>
<p>Once upon a time, automating a process meant writing most of it yourself — parsing data, logging events, retrying failures, reinventing wheels that never rolled straight. Now? Someone else has already built it, documented it, and uploaded it.</p>
<p>Open-source libraries have turned into a kind of shared memory bank for developers. Want to generate a PDF? Parse a CSV? Connect to an obscure API? Odds are there’s a package for it. Even better, it’s been stress-tested in the wild, so you inherit other people’s bug fixes and optimizations.</p>
<p>That means when you hit a repetitive task, the question isn’t <em>if</em> you can automate it, but <em>which library</em> gets you there fastest. The path of least resistance leads straight to automation.</p>
<hr>
<h2 id="low-code-for-the-rest-of-us"><a class="anchor" href="#low-code-for-the-rest-of-us">Low-Code for the Rest of Us</a></h2>
<p>Not everyone who wants to automate is a developer. And increasingly, they don’t need to be.</p>
<p>Low-code and no-code platforms have cracked automation open for anyone with curiosity and a bit of persistence. With drag-and-drop interfaces, pre-built connectors, and visual workflows, a marketing lead or finance analyst can design a working solution in an afternoon.</p>
<p>Gartner predicts that by 2026, <strong>three-quarters of new apps</strong> will be built this way. That’s an enormous cultural shift: automation has jumped the fence from IT into every corner of the business. If the person closest to the problem can also build the fix, the payoff curve tilts even further toward “worth it.”</p>
<hr>
<h2 id="cloud--serverless-magic"><a class="anchor" href="#cloud--serverless-magic">Cloud &#x26; Serverless Magic</a></h2>
<p>Infrastructure used to be the silent killer of automation ideas. You could build the script, but then came the harder part: finding a machine to run it, keeping it online, patching, monitoring, scaling…</p>
<p>Cloud and serverless flipped that script. Today you can spin up an environment in seconds, deploy a function that runs only when triggered, and forget about it until the next time it’s needed. You pay for execution time in cents, not servers in racks.</p>
<p>That ease has removed a whole class of excuses. Instead of “I’d love to automate this, but IT will never approve the server,” it’s: “Sure, I’ll throw it in a Lambda and call it a day.” Automation moved from headache to background hum.</p>
<hr>
<h2 id="hardware-that-can-keep-up"><a class="anchor" href="#hardware-that-can-keep-up">Hardware That Can Keep Up</a></h2>
<p>Even if the tools exist, they need horsepower behind them. Ten years ago, some automations were technically possible but practically useless — your laptop would wheeze, or the cost of compute would outstrip the benefit.</p>
<p>Now, specialized chips (GPUs, TPUs) and AI-ready machines make running complex workflows locally almost trivial. Deloitte projects the generative AI chip market will top <strong>$50B</strong> in the coming years. Vendors are already shipping AI-embedded PCs designed to handle model inference on the fly.</p>
<p>The practical upshot? Automations that once needed cloud supercomputers can now run quietly on your desk — faster, cheaper, and more private. Hardware isn’t the limiter anymore; it’s the enabler.</p>
<hr>
<h2 id="back-to-the-comic"><a class="anchor" href="#back-to-the-comic">Back to the Comic</a></h2>
<p>So what happens if we update that xkcd curve?</p>
<p>Tasks haven’t changed. We still file reports, format data, move files, integrate systems. But the <em>time to automate</em> those tasks has collapsed. More and more dots fall into the “worth it” zone.</p>
<p>That’s why automation no longer feels like a nerd’s guilty pleasure. It’s becoming the default.</p>
<hr>
<h3 id="a-gentle-takeaway"><a class="anchor" href="#a-gentle-takeaway">A Gentle Takeaway</a></h3>
<p>If you catch yourself wondering “is it worth it?” — the answer is increasingly yes. Not because AI alone has tipped the scales, but because everything around it — the open-source libraries, the low-code platforms, the cloud, the hardware — has shifted in the same direction.</p>
<p>The tools are there. The only question left is which parts of our work (and life) we <em>want</em> to automate — and which are better left delightfully human.</p>
<h3 id="further-reading"><a class="anchor" href="#further-reading">Further Reading</a></h3>
<ul>
<li><a href="https://github.blog/news-insights/research/research-quantifying-github-copilots-impact-on-developer-productivity-and-happiness/">GitHub: Copilot’s impact on developer productivity</a></li>
<li><a href="https://theagentsoftransformation.com/the-role-of-open-source-software-in-accelerating-innovation/">The role of open source in accelerating innovation</a></li>
<li><a href="https://www.hostinger.com/tutorials/low-code-trends">Low-code trends and forecasts</a></li>
<li><a href="https://dbbsoftware.com/insights/benefits-of-cloud-technologies-and-their-impact-on-web-performance">Benefits of cloud technologies</a></li>
<li><a href="https://www.deloitte.com/us/en/insights/industry/technology/technology-media-and-telecom/hardware-is-eating-the-world.html">Deloitte: Hardware is eating the world</a></li>
</ul>]]></content:encoded>
    </item>
    <item>
      <title>The Iron Triangle, Bent but Not Broken  </title>
      <link>https://casey.berlin/writings/2025/09/the-iron-triangle-bent-but-not-broken/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2025/09/the-iron-triangle-bent-but-not-broken/</guid>
      <pubDate>Sun, 14 Sep 2025 12:00:00 GMT</pubDate>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <description><![CDATA[Fast, cheap, or good — pick two. AI bends the iron triangle by stretching speed and budget, but quality stays stubbornly human.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p><em>“Fast, cheap, or good — pick two.”</em>
If you’ve ever sat in a project room, you’ve heard it. The iron triangle, rolled out like some eternal law of physics. More often than not, it felt like a way to close down a conversation — to shut off possibility.</p>
<p>As someone who’s always leaned toward servant leadership, I never liked using the triangle as a stick. My job was never to squeeze more out of people by pointing at the corners. It was to protect the team, hold space for quality, and find a path through the mess.</p>
<p>But here we are in a new era: AI at the table. Not replacing the team, not managing the project — but definitely changing the geometry.</p>
<hr>
<h2 id="speed-no-longer-the-bottleneck"><a class="anchor" href="#speed-no-longer-the-bottleneck">Speed: No Longer the Bottleneck</a></h2>
<p>Humans work in rhythms: sprints, workshops, deep focus. AI doesn’t. It just delivers — seconds, not days. Suddenly, speed doesn’t feel scarce anymore.</p>
<p>But speed on its own doesn’t mean much. I’ve seen AI generate brilliant drafts and nonsense with equal confidence. The paradox: faster output means slower reflection, unless we make space for it. Speed has to serve, not dictate.</p>
<hr>
<h2 id="quality-still-a-human-craft"><a class="anchor" href="#quality-still-a-human-craft">Quality: Still a Human Craft</a></h2>
<p>People bring context, empathy, and the ability to read what wasn’t said. That’s what makes human quality so resilient.</p>
<p>AI mirrors us back. If the brief is vague, the output is vague. If it’s clear, the result can be sharp, even dazzling. But the spark — the creative leap, the intuition of what the client really meant — that’s still ours. I don’t see that changing.</p>
<hr>
<h2 id="budget-the-hidden-work"><a class="anchor" href="#budget-the-hidden-work">Budget: The Hidden Work</a></h2>
<p>AI doesn’t ask for overtime or travel expenses. But it does create hidden work: preparing data, checking hallucinations, correcting subtle errors. The costs don’t disappear — they just change shape.</p>
<p>Yet, used well, AI can genuinely expand what we can deliver with the same resources. It’s not about replacing people. It’s about freeing them from the repetitive and making room for the meaningful.</p>
<hr>
<h2 id="bending-not-breaking"><a class="anchor" href="#bending-not-breaking">Bending, Not Breaking</a></h2>
<p>So does the iron triangle still stand? I think so. But it bends now.</p>
<ul>
<li>Speed stretches toward abundance.</li>
<li>Budget stretches toward efficiency, with asterisks.</li>
<li>Quality remains stubbornly human at the core.</li>
</ul>
<p>And maybe that’s the invitation for us as leaders: to stop using the triangle as a wall, and start treating it as a space we can reshape. AI helps bend it, but it’s still up to us to protect the people doing the work, to keep quality alive, and to ask better questions when we brief — both humans and machines.</p>
<p>Because in the end, briefing well isn’t just about outputs. It’s about respect — for the people, for the process, and for the work itself.</p>
<h2 id="further-reading"><a class="anchor" href="#further-reading">Further Reading</a></h2>
<p>For those curious to dig deeper, here are a few pieces that explore these themes:</p>
<ul>
<li><strong>Homolak, D. (2024).</strong> <em>“Garbage In – Garbage Out!” Still Applies with Gen AI.</em> Integreon – AI Insights. <a href="https://www.integreon.com/garbage-in-garbage-out-still-applies-with-gen-ai/">Read here</a></li>
<li><strong>Shelver, A.-L. (2023).</strong> <em>AI will change briefing forever, but it requires we get better at it too.</em> BriefMapp. <a href="https://briefmapp.com/ai-will-change-briefing-forever-but-it-requires-we-get-better-at-it-too-heres-why/">Read here</a></li>
<li><strong>Chang, S. (2023).</strong> <em>Teaching AI to Clarify: Handling Assumptions and Ambiguity in Language Models.</em> <a href="https://shanechang.com/p/training-llms-smarter-clarifying-ambiguity-assumptions/">Read here</a></li>
<li><strong>Becker, J. et al. (2025).</strong> <em>Measuring the Impact of Early-2025 AI on Developer Productivity.</em> METR RCT Study. <a href="https://metr.org/blog/2025-07-10-early-2025-ai-experienced-os-dev-study/">Read here</a></li>
<li><strong>Pangeanic (2025).</strong> <em>AI Won’t Replace You—But This Will: The Professionals Who Adapt.</em> <a href="https://blog.pangeanic.com/ai-is-not-going-to-replace-you-but-ai-augmented-humans-will">Read here</a></li>
</ul>]]></content:encoded>
    </item>
    <item>
      <title>From Rediscovering the Joy of Making to Owning the Code - And Challenging You Along the Way</title>
      <link>https://casey.berlin/writings/2025/09/from-rediscovering-the-joy-of-making-to-owning-the-code-and-challenging-you-along-the-way/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2025/09/from-rediscovering-the-joy-of-making-to-owning-the-code-and-challenging-you-along-the-way/</guid>
      <pubDate>Mon, 01 Sep 2025 12:00:00 GMT</pubDate>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <description><![CDATA[AI coding tools like Cursor and Codex helped me reclaim the maker joy I lost to no-code platforms. A dare to dust off your own side projects.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>I’ve always been a maker at heart. As a kid, I’d build scripts, tiny tools, and websites—anything to simplify life or scratch that creative itch. Those early projects brought sheer joy, little experiments fueled by curiosity rather than ambition.</p>
<p>In recent years, I took a detour through no-code platforms. They made things easy—and halted the joy. I realized I missed the haptic thrill of code: the tactile back-and-forth, the mental sparks from building something real. Instead, my homelab and Python scripts had become confusing labyrinths: side‑project graveyards, tangled spaghetti code, and automation that no longer made sense.</p>
<p>Then, a gentle nudge: AI-powered tools like <strong>Cursor</strong> and <strong>Codex</strong> made dipping back into code feel accessible again, without the intimidation.</p>
<ul>
<li><strong>Cursor</strong>, developed by Anysphere, is an AI-native IDE that blends autocomplete, multi-line edits, and agent modes into a clean, intuitive coding experience. It anticipates your moves—suggesting context-aware edits, smart rewrites, even multi-file changes. It’s quietly magical.(<a href="https://en.wikipedia.org/wiki/Cursor_%28code_editor%29?utm_source=chatgpt.com" title="Cursor (code editor)">Wikipedia</a>)</li>
<li><strong>Codex</strong>, a software agent from OpenAI, runs in the cloud—it can write features, diagnose code, run your tests, even propose pull requests. It operates as your virtual coworker in sandboxed virtual environments.(<a href="https://openai.com/index/introducing-codex/?utm_source=chatgpt.com" title="Introducing Codex">OpenAI</a>)</li>
</ul>
<p>These aren’t about replacing developers—they’re about bringing joy back to building. You stay in control, but a layer of AI accelerates where it makes sense.</p>
<h2 id="the-spark-commitment-without-overcoding"><a class="anchor" href="#the-spark-commitment-without-overcoding">The Spark: Commitment Without Overcoding</a></h2>
<p>Since exploring these tools:</p>
<ul>
<li>I’ve <strong>committed more code than ever</strong>, even though I'm actually writing <em>less</em>—my contributions are leaner, more purposeful.</li>
<li>I’ve re-engaged with <strong>open-source projects</strong>, polished those old wrappers, and finally brought structure back to my homelab infrastructure.</li>
<li>I’m leveraging <strong>low-/no-code automation</strong> (like n8n and Node-RED) more meaningfully—connecting services and projects with tiny bits of glue, without overcoding.</li>
</ul>
<p>It’s tiny wins—not flashy features, but functional fixes and real progress. And each push into Git or merge request feels like reclaiming that maker spirit.</p>
<hr>
<h2 id="the-challenge-im-facingand-the-invitation-i-offer"><a class="anchor" href="#the-challenge-im-facingand-the-invitation-i-offer">The Challenge I’m Facing—and the Invitation I Offer</a></h2>
<p>I had:</p>
<ol>
<li>A backlog of unfinished side projects, waiting for a developer who never came.</li>
<li>A homelab filled with scattered Python scripts that no longer made sense.</li>
<li>Burned energy and missed momentum in the hybrid space between product ideas and engineering execution.</li>
</ol>
<p>These AI tools helped me break that inertia.</p>
<p>So here’s what I want to offer you: a quiet dare, not clickbait, just a shared reclaiming of maker energy.</p>
<p><strong>Try this with me:</strong></p>
<ul>
<li>Pick a dusty project or a homelab script.</li>
<li>Open Cursor or Codex—give yourself permission to tinker, spec, commit.</li>
<li>Keep code small. Let the tool lift the effort where it counts.</li>
<li>Ship something that works, not something perfect.</li>
</ul>
<p>Let’s not chase attention. Let’s build. I’ll be over here, making again—committing with intention, writing less but doing more.</p>
<p>Are you in?</p>
<p>— Casey (re-learning to glow with code, one tiny, tidy commit at a time)</p>]]></content:encoded>
    </item>
    <item>
      <title>De cijfers achter mijn onderneming</title>
      <link>https://casey.berlin/writings/2021/03/cijfers-achter-mijn-onderneming/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2021/03/cijfers-achter-mijn-onderneming/</guid>
      <pubDate>Sun, 21 Mar 2021 12:00:00 GMT</pubDate>
      <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">Wed, 25 Mar 2026 00:00:00 GMT</dc:date>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>ondernemerschap</category>
      <category>social CRM</category>
      <category>business intelligence</category>
      <category>netwerk</category>
      <category>cijfers</category>
      <description><![CDATA[Een kijkje achter de schermen: hoe ik klanten bijhoud in social CRM, omzet in kaart breng en wat de opvallendste conclusie is — close ties zijn mijn grootste bron van inkomsten. En ik deed slechts 1 cold call dit jaar.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>Lijstjes, ze kunnen nog net… Ik hou mijn klanten bij in social CRM systemen waar ik veelal informatie en relevante contacten van hun tag en bijhoud. GIST.com helpt me daar bij, maar ook wat ouderwetsere systemen zoals Zoho CRM of YUKI zijn systemen waar veel van die informatie opgeslagen en gebruikt wordt. Daarnaast zet ik ook (potentiele) omzet af tegen waar die omzet mogelijk vandaan komt, wat de "lead" daar in is geweest en daarmee probeer ik focus aan te brengen aan de dingen die ik doe. Als werknomaad is Seats2Meet.com 1 van die gebieden waar ik mijn omzet vandaan haal.</p>
<p>Het belangrijkste wat ik nog vergeet is de "fun factor", natuurlijk moet het ook leuk zijn om dat te doen en wat zijn de risico's, enfin, een enorme rits aan business intelligence waar jij misschien ook wat aan hebt.</p>
<p>Belangrijkste uit deze grafiek is wel dat het grootste deel van mijn (monetaire) inkomsten nog altijd komt uit "de persoonlijke kant" van het verhaal, iets wat je als ondernemer ook wel moet hebben; assertiviteit, zelf bewust zijn, weten wat je verkoopt. De "close ties" van mijn netwerk zijn daar in super belangrijk, zij introduceren mij en zijn daar vaak al ontzettend betrouwbaar gebleken. Onderhoud van contact met hen is daarin dus ook noodzaak.</p>
<p>De kleine 1% stukjes, daar zitten wel de echte "nieuwe media" dingen, bijvoorbeeld: Twitter, white papers, website leads. En dat vind ik erg opvallend. De inkomsten daar (tweeten, acteren op linkedin, bloggen etc.) zijn, naar mijn idee, vooral op basis van sociaal kapitaal, het claimen van je expertise en daarmee leidend naar bijv. een externe workshop/meeting, indirect dus.</p>
<p>Ook cold calls zitten in dat stuk verwerkt. Ik heb er slechts 1 hoeven doen dit jaar, wat wellicht de meest opvallende conclusie in dat verhaal is voor mij als startend ondernemer.</p>]]></content:encoded>
    </item>
    <item>
      <title>De Sultana case</title>
      <link>https://casey.berlin/writings/2021/03/de-sultana-case/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2021/03/de-sultana-case/</guid>
      <pubDate>Sun, 21 Mar 2021 12:00:00 GMT</pubDate>
      <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">Wed, 25 Mar 2026 00:00:00 GMT</dc:date>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>social media</category>
      <category>reputatiemanagement</category>
      <category>case study</category>
      <category>consulting</category>
      <category>crisis communicatie</category>
      <description><![CDATA[Sultana ging van 3 naar 2 koekjes per verpakking. Twitter ontplofte. Een reputatiecrisis die ik mocht meemaken, analyseren en gebruiken als studiestof — over wat je kunt doen als de schade al is aangericht.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<blockquote>
<p>Een flink aantal maanden geleden werd ik benaderd door het PR bureau van Sultana, om eens naar hun verhaal te luisteren wat ging om "koekjes". Sultana had de keus gemaakt van 3, naar 2 koekjes per verpakking te gaan. En of dat wel niet "zin" had.</p>
</blockquote>
<p>Natuurlijk, marketing technisch was het vast een goed idee, om van de sultana een "verantwoord" tussendoortje te maken. 99 Calorien maximaal, vast een hele goede zet.</p>
<p>Jammer Sultana, dat dit toch wat anders uitpakte. Binnen ettelijke dagen stroomde twitter vol met verontwaardigde mensen. Die mensen zijn gewend om dagelijks hun portie van 3 koekjes te verdelen over de dag. Huismoeders (volgens Sultana de key user die ondervraagd is) hadden ook te klagen, tenslotte was de prijs van de verpakking omhoog gegaan. Je hoefde geen rekenwonder te zijn om de prijsstijging per gram te ontdekken.</p>
<p>Natuurlijk, er zitten nu 8 verpakkingen in een grote verpakking, echter… Hoeveel werkdagen zitten er ook alweer in een week?</p>
<p><strong>Change</strong></p>
<p>Ik weet het zelf ook, verandering is een lastig proces. Dit hoort daar bij, alleen nemen we het niet meer aan als "gewoon". We hebben nu middelen als Twitter en FaceBook (zelf onderhevig aan flinke kritieken) die er voor zorgen dat we als consument mondig mogen, en kunnen zijn. Ik kreeg echter een 40 tal A4'tjes vol met tweets te zien die hier over gaan. Weerstand.</p>
<p>Ik zie Twitter dan simpelweg als tip of the iceberg. Waar 5% "vocal" is, zich laat horen, zal er nog een veel groter deel onder water gebeuren wat we niet zien of horen; op de hoek van de straat, in de supermarkt, of bij de koffie.</p>
<p><strong>Van advies naar… Advies!</strong></p>
<p>Reputatiemanagement, zo luidde mijn advies. Wat je op dat moment nog kon doen aan het voorkomen van reputatieschade was feitelijk gezien 0. Wat je wel kan doen is de mensen met vragen, attenderen op de campagne website of wellicht wel persoonlijk te woord staan of iets mee gaan doen zodat je het nog enigszins om kan vormen in iets positiefs. In mijn beleving was Sultana de eerste die met dit soort "mee naar school" koekjes kwam. Lekker, energiek en vooral wat gezonder dan een Mars of Snicker.</p>
<p>Nou was ik ook een braverik op school, dus kreeg ik zo'n sultana keurig mee van thuis. Toen ik echter 3 weken terug bij de hogeschool in Utrecht voor de klas stond, heb ik ook aan die minor Ecommerce, gevraagd om hun visie op deze zaak te geven. Hoe houd je het in de hand? Hoe zou je dit nog om kunnen toveren? Mijn inschatting van budget was relatief laag maar zou wel voor flink wat werk bij mij gaan zorgen. Ik was dus benieuwd hoe deze 3 groepen het er af zouden brengen.</p>
<p><strong>De les die ik heb geleerd</strong></p>
<p>Mijn advies was grotendeels gebaseerd op het beperken van de schade en het gebruik maken van de "lading" van de tweets die werden verstuurd. Daar lag de essentie in de eerste dagen na het uitbreken van alle ellende. Naar mijn idee lag daar dan ook de vraag en met een beperkt budget (denk €5000) dankzij een marketingcampagne die al teveel had gekost, werd dit allemaal erg lastig.</p>
<p>Toch heb ik op deze manier een case die ik kan presenteren in colleges en lezingen, als voorbeeld van hoe het niet moet, wat er mis kan gaan en zelfs als studiestof voor studenten. Met een paar gave adviezen (al dan niet origineel, dat laat ik aan jou) als resultaat.</p>
<p><strong>Zelfs business wat je niet doet, kan inspireren. Voor het verhaal, voor het ontstaan van je onderneming, voor het voortbestaan van je onderneming, of om anderen te inspireren. Dit is zo'n voorbeeld.</strong></p>]]></content:encoded>
    </item>
    <item>
      <title>Difrax: social media in de praktijk</title>
      <link>https://casey.berlin/writings/2021/03/difrax-social-media/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2021/03/difrax-social-media/</guid>
      <pubDate>Sun, 21 Mar 2021 12:00:00 GMT</pubDate>
      <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">Wed, 25 Mar 2026 00:00:00 GMT</dc:date>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>social media</category>
      <category>Difrax</category>
      <category>Twitter</category>
      <category>consulting</category>
      <category>case study</category>
      <category>social business</category>
      <description><![CDATA[Difrax maakt veelvuldig gebruik van social media en met name Twitter speelt daar een belangrijke rol. Een kijkje in hoe een babymerk een écht sociaal bedrijf werd — en hoe trots ik ben dat ze het nu zelf doen.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<blockquote>
<p>Ik heb Difrax al eens vaker gebruikt als voorbeeld voor de social media activiteiten die ik onderneem. Het blijft een leuk merk met bijzondere producten, zeker als je kijkt naar in welke tijdspanne ze actief zijn.</p>
</blockquote>
<p>Ik ontmoette @difrax al een tijdje geleden bij Seats2Meet.com te Utrecht, waar ik samen met @resourcerer 1 van zijn sessies bij woonde over het adviseren van bedrijven op het gebied van Social Media. Blijft voor mij een leuke bezigheid, zeker in mijn vak, het transformeren van business naar social business, waar leuk en zaken doen samen komt.</p>
<p>Difrax maakt veelvuldig gebruik van Social media en met name Twitter speelt daar een belangrijke rol. Die strategie gaat niet uit van wedden op 1 paard (bijv. een corporate account) maar van meerdere invloeden. Een actief aantal marketeers, een corporate actief account waar veel interactie mee ontstaat, een (kraam)verzorgster (@expert_baby) met tips en trucs rondom opvoeding en ook een directie die actief mee luistert op de sociale media.</p>
<p>De zaken die ik doe met Difrax zijn nauwelijks noemenswaardig meer te noemen, ik heb ze geholpen in de eerste stappen richting social media. Nu doen ze het allemaal zelf en ik ben erg trots op dat feit. We mailen nog wel eens wat over kleine zaken, waardoor er weer even dat moment van aandacht voor elkaar ontstaat en zo voor mij inspiratie voor een weblog in dit geval.</p>
<p>Ik vroeg @susanvanharen hoe ze twitter ervaart in hun dagelijkse gang van zaken en kreeg het volgende antwoord:</p>
<blockquote>
<p>Mijn grootste uitdaging is om dit jaar al onze distributeurs (die nog nooit iets met Social media hebben gedaan) enthousiast te krijgen over Twitter en hen daadwerkelijk aan het werk te krijgen ermee.</p>
<p>Ik moet zeggen dat ik best sceptisch was over Twitter toen we voor het eerst bij elkaar kwamen bij S2M. Ik had niet verwacht dat onze doelgroep zo actief was op dit netwerk. Maar al snel bleek dat dit wel het geval is.</p>
<p>Wat ik er vooral goed aan vindt, is dat ik direct kan reageren wanneer iemand een klacht of een vraag over een product heeft. Dat is de service die we onze klanten willen en dus ook kunnen bieden. Ook gebruiken we Twitter om te reageren op actuele nieuwsberichten.</p>
<p>Ik ben helemaal verslaafd geworden aan social netwerken, en kan niet meer zonder onze tweeps!</p>
</blockquote>
<p>Geweldig, dat ik met zo'n klein stapje, ze ook mee heb kunnen helpen een nog socialere organisatie te worden.</p>
<p>Wat is jouw volgende stap?</p>
<p><em>Picture: Martin Thomas/Flickr</em></p>]]></content:encoded>
    </item>
    <item>
      <title>Drie jaar ondernemer: lessen geleerd</title>
      <link>https://casey.berlin/writings/2021/03/drie-jaar-ondernemer/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2021/03/drie-jaar-ondernemer/</guid>
      <pubDate>Sun, 21 Mar 2021 12:00:00 GMT</pubDate>
      <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">Wed, 25 Mar 2026 00:00:00 GMT</dc:date>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>ondernemerschap</category>
      <category>lessen</category>
      <category>persoonlijke groei</category>
      <category>netwerk</category>
      <category>zelfstandig</category>
      <description><![CDATA[Hoera, drie jaar! Na veel ups en downs mag ik me een succesvol ondernemer noemen. De eerste drie jaar zijn het meest cruciaal — 30-50% sneuvelt in die periode. Een paar lessen die ik leerde, deel ik vandaag.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<blockquote>
<p>Hoera! Ik besta alweer drie jaar (en een dag)! Na veel ups en downs mag ik me dan een succesvol ondernemer noemen. De eerste drie jaar zijn het meest cruciaal wat een onderneming betreft; 30-50% van de ondernemingen sneuvelt immers gedurende die periode. En ook al ben ik dan 'maar' zelfstandige, ik heb het toch maar mooi gered! Een paar lessen die ik in die drie jaar heb geleerd, deel ik vandaag met jou.</p>
</blockquote>
<p>Hoe opmerkelijk dan ook, voor mij voelen die drie jaar alsof het nooit anders is geweest. Ondernemen zit mij in het bloed, mijn vader is (nog steeds) ondernemer en die tikt volgend jaar de 25 jaar ondernemerschap aan. Fantastisch, maar ook van hem moest ik een les leren; het kan ook je relatie kosten. 15 jaar geleden scheidden mijn ouders namelijk, mede omdat ze door die onderneming erg uit elkaar gegroeid waren. Iets wat ook in mijn achterhoofd zit en doorklinkt in de lessen hieronder.</p>
<p><strong>1. Neem de tijd om te groeien</strong> — Het is erg lastig om te beginnen als zelfstandig ondernemer. Ondanks een netwerk dat je veel succes wenst bij het starten en graag champagne met je komt drinken en je taart op eet om dat moment te vieren, val je daarna in een behoorlijk gat. Je moet het dan écht (zelf) gaan doen. En iedereen die je klussen beloofde, houdt ineens de boot af of is niet meer bereikbaar. Dat is lastig starten, maar zet door.</p>
<p><strong>2. Weet wat je te verkopen hebt</strong> — Het moeilijkste vind ik nog steeds duidelijk vertellen wat ik precies verkoop of wat voor dienst ik aanbied. Ik heb daar veel interpretaties in gehad en de definitie veranderd soms per dag. Nadeel is dat het diffuus over kan komen en jouw boodschap zichzelf daarmee niet verspreid. En dat is zonde van je tijd. Wees concreet.</p>
<p><strong>3. Wees jezelf en verkoop die</strong> — Het enige wat je als zelfstandig ondernemer hebt, is jezelf. Wees dan ook jezelf. Ik heb daar grote moeite mee gehad, ik liet me vaak meeslepen en beïnvloeden door mensen in mijn netwerk of opdrachtgevers. Zo verlies je je eigen hart in je onderneming en vloeit daarmee de passie weg. Met als resultaat een hele grijze Kees en onderneming. Je mag dan wel alleen zijn, maar je hebt heel wat te bieden! Laat jezelf gerust informeren en inspireren door anderen, maar niet leiden. Je hebt tenslotte geen baas meer en ook je opdrachtgever is niet je baas!</p>
<p><strong>4. Geld is er altijd te weinig</strong> — Hoe groot de offerte ook is die je maakt, hoe veel klussen er ook in 'de wacht' hangen, geld is er altijd te weinig. Zeker het eerste jaar, zorg voor voldoende reserves en betaal je zelf niet te gretig uit. Het liefst zo minimaal mogelijk, hoe lastig dat soms ook is met grote bedragen op de bank. Aan het einde van het jaar zal je altijd te weinig over houden, in mijn geval kwam de belastingdienst daar namelijk een flinke slok van halen. Juist omdat ik me nét teveel had uitbetaald. Dat kan je beter investeren in je zaak.</p>
<p><strong>5. Beloof iets minder, doe iets meer</strong> — @Basschepers heeft me deze les geleerd en die komt nog altijd goed van pas. Ik ben een enorme pleaser, ik wil bedrijven het gevoel geven dat alles kan en alles mogelijk is. Die belofte doe ik nog steeds, maar ik laat het dan vooral zien door het te doen. Opleveren van een website met nét even die gave plugin of gratis een mobiele versie, een lezing met net iets meer passie dan het voorstel daarvoor. Het loont enorm om te BIMDIM'men.</p>
<p><strong>6. Je netwerk is je alles</strong> — Ik heb het geluk gehad in mijn tijd werkzaam bij @s2m een groot netwerk op te kunnen bouwen van mede ondernemers, maar vooral van 'connectors', mensen die graag andere mensen aan elkaar verbinden. Je hoeft die mensen niet te pleasen of enorm te verwennen met grote kado's of bakken geld, nee ze zijn blij hun sociaal kapitaal in te kunnen zetten om mensen aan elkaar te verbinden. Bij een vraag een aanbod vinden. Ik vind dat zelf ook heerlijk, mensen daarmee blij te maken. Dat levert altijd iets op, daar geloof ik in. Mijn sociaal kapitaal zet ik voor die verbinding dan ook graag in. Ook helpt het contact te houden met mensen, social media is daar absoluut het allerbelangrijkste middel in.</p>
<p><strong>7. Vergeet je persoonlijke leven niet</strong> — Niets mooier om 's avonds laat nog even dat voorstel af te maken of nog meer energie te steken in de allerbeste presentatie die je ooit hebt gemaakt. Maar 95% is voor je publiek vaak ook al genoeg. Vergeet de mensen om je heen niet, als partner, vriend, broer of zoon heb ik dat ook nog elke dag te leren. Mijn valkuil en passie uit zich in het alles of niets geven voor een opdracht, een weblog, een presentatie of een gesprek. Elk moment maximaal benutten. En dat geldt ook voor mijn relaties. Gelukkig kan ik nu ook de deur naar mijn kantoor letterlijk dicht doen, en aandacht geven aan hen die van nog veel meer waarde zijn. Want geloof me, een nieuwe klant komt er altijd wel weer. Dat is met familie en je partner een stuk moeilijker.</p>
<p>Ik blijf graag dit soort tips delen, ook over kleinere dingen. Heb je iets waar je van mij meer over zou willen weten? Ik zit te denken aan de grootste blunders of een business case uitgewerkt van A tot Z die écht verkeerd liep. Ik ben benieuwd!</p>
<p><em>Photo: <a href="http://www.flickr.com/photos/duncanh1/6229892017/">Creative Commons; Flickr - Duncan Harris</a></em></p>]]></content:encoded>
    </item>
    <item>
      <title>De volgende stap: FrisGroen.com</title>
      <link>https://casey.berlin/writings/2021/03/frisgroen-de-volgende-stap/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2021/03/frisgroen-de-volgende-stap/</guid>
      <pubDate>Sun, 21 Mar 2021 12:00:00 GMT</pubDate>
      <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">Wed, 25 Mar 2026 00:00:00 GMT</dc:date>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>ondernemerschap</category>
      <category>social media</category>
      <category>FrisGroen</category>
      <category>consulting</category>
      <category>bloggen</category>
      <description><![CDATA[Na de zomer een tandje bijschakelen. Mijn werkzaamheden richten zich op de praktische kant van FrisGroen.com — een nieuwe onderneming voor social media begeleiding, samen met een goede vriend gestart.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<blockquote>
<p>Na de mooie zomermaanden komt september alweer in zicht, tijd om na alle relaxtheid een tandje bij te schakelen. Een kijkje in mijn eigen keuken vandaag!</p>
</blockquote>
<p>Zoals al eerder aangekondigd, gaan mijn werkzaamheden zich richten op de praktische kant van zaken bij FrisGroen.com. Samen met @spems ben ik die nieuwe onderneming gestart, die elke ondernemer en organisatie kan helpen bij een stap verder zetten op online gebied; met name met behulp van social media. De eerste klussen komen binnen, maar er is altijd ruimte voor meer.</p>
<p>Daarnaast blijft deze site mijn (vrijwel) dagelijkse uitlaatklep voor ontwikkelingen online, sommige stukken ontwikkelen zich daarin op langere termijn, zoals bijvoorbeeld mijn marketeer en dorpsblog, andere blogs met filmpjes en productiviteitstips zijn dingen die ik onder de douche bedenk of tijdens het rondkijken op YouTube. Het ritme wat ik in het schrijven heb gevonden helpt mij de dag goed en productief beginnen. Erg fijn om zo in de flow van de rest van de dag te komen en ook echt moe naar bed te gaan. Daarnaast blijf ik actief als spreker en consultant op het gebied van social business.</p>
<p>De screencasts die ik eerder opnam en verspreide, zullen bij FrisGroen.com een nieuw onderkomen vinden. Ik ben hard bezig geweest met het maken van een nieuwe bumper, er is een nieuwe studio setting en daarmee komt de aandacht meer te liggen bij de inhoud van de screencasts. Feedback van anderen is erg nuttig gebleken en het resultaat moet dan ook meer 'a ha' momenten zijn en minder vraagtekens.</p>
<p>Mocht je qua inhoud nog meer behoeftes hebben, laat het dan gerust weten. Misschien heb je een pittige stelling, een grote uitdaging voor je organisatie, of een hele simpele vraag, ik geef graag antwoord. Bedankt dat je nog altijd komt kijken en lezen hier en elke reactie is welkom!</p>
<p><em>Photo: Creative Commons; Flickr - Trevor Leyenhorst</em></p>]]></content:encoded>
    </item>
    <item>
      <title>Het begin: CDEF Holding</title>
      <link>https://casey.berlin/writings/2021/03/het-begin-cdef/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2021/03/het-begin-cdef/</guid>
      <pubDate>Sun, 21 Mar 2021 12:00:00 GMT</pubDate>
      <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">Wed, 25 Mar 2026 00:00:00 GMT</dc:date>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>ondernemerschap</category>
      <category>social media</category>
      <category>CDEF</category>
      <category>consulting</category>
      <category>start</category>
      <description><![CDATA[Het begin van mijn weg als social media consultant. Vanuit CDEF Holding, na een jaar als communitymanager bij MINDZ, de kans gekregen om zelfstandig te ondernemen. En die kans heb ik met beide handen aangepakt.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>CDEF Holding, waar ik al een jaar aan het werk ben, is een bijzonder bedrijf.</p>
<p>Het afgelopen jaar ben ik in veel facetten van dit bedrijf actief geweest, als communitymanager bij MINDZ, analyseren van andere sociale netwerken, web2.0 tools en hun toepassingen, geven van workshops op social media gebied en nog veel meer dingen.</p>
<p>Daarnaast ben ik ook erg actief op het net, twitter, hyve en facebook me een end in de rondte en ook nog eens flink gadget addicted.</p>
<p>Nu krijg ik de mogelijkheid om mezelf nog verder te ontwikkelen, door in goed overleg met CDEF holding, ruimte te creeren om zelfstandig te gaan ondernemen! Ik ben er zelf (en mijn omgeving) erg enthousiast over, kan mezelf laten zien, "de wijde wereld" in trekken, opdrachtgevers zoeken (of door profilering van mezelf, gevonden worden) en voorzien in hun sociale media behoeftes.</p>
<p>Want dat is wat ik ga doen: <strong>Social Media Consultancy</strong>.</p>
<p>Er zijn enorm veel bedrijven met vragen over hoe met sociale media om te gaan, de medewerkers zijn vaak al betrokken bij sociale media, in welke vorm dan ook: een profiel op een sociaal netwerk, geven van reviews op producten, verbinden met elkaar en met nieuwe mensen, plaatsen van filmpjes op youtube. De eerste stap is echt bewustwording, op organisatieniveau en hoe daar mee om te gaan.</p>
<p>Samen met die bedrijven wil ik gaan overleggen hoe ze dit tot iets positiefs om kunnen zetten, ruimte creeren voor het participeren van medewerkers op sociale media en hoe ze dit als voordeel voor zichzelf kunnen gebruiken.</p>
<p>Met mijn inzicht in technische (on)mogelijkheden, social marketing technieken en passie voor mensen en (online) beleving ga ik daar wat moois van maken!</p>
<p>Dankjewel voor deze mogelijkheid Ronald &#x26; Mariëlle, bij CDEF gaat dat zeker ook mooie dingen opleveren!</p>
<p>Kom gerust eens een kop koffie drinken, stuur me eens een berichtje als je het leuk vind om daar eens over te praten!</p>]]></content:encoded>
    </item>
    <item>
      <title>Interne kennisdeling met Yammer</title>
      <link>https://casey.berlin/writings/2021/03/interne-kennisdeling-yammer/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2021/03/interne-kennisdeling-yammer/</guid>
      <pubDate>Sun, 21 Mar 2021 12:00:00 GMT</pubDate>
      <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">Wed, 25 Mar 2026 00:00:00 GMT</dc:date>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>social business</category>
      <category>Yammer</category>
      <category>interne communicatie</category>
      <category>kennisdeling</category>
      <category>organisaties</category>
      <description><![CDATA[Interne kennisdeling wordt in sociale media trends nogal eens vergeten. Maar tools als Yammer kunnen een gigantische impact hebben op je organisatie — en zorgen dat nieuwe medewerkers zich al vóór dag één thuis voelen.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>1 van de aandachtsgebieden van Social Business Design die je als externe gebruiker van sociale media weinig zal zien is de interne kennisdeling. Elke organisatie, klein of groot, heeft een enorme hoeveelheid kennis tot beschikking, die niet altijd relevant hoeft te zijn voor jouw onderneming.</p>
<p>Stel je eens voor dat ineens die ene collega je weer groet op de gang, de deur van je manager open staat in plaats van dicht of je ziet een leuke oproep voor een personeelsuitje op de koffiemachine geplakt. Zo een greep uit de effecten die effectieve, simpele kennisdelingstools voor interne communities met zich meebrengen. Online tools hebben grote impact op de offline wereld.</p>
<p>Ik ben zo'n persoon die zich online goed kan profileren en waarin ik mijn mening ook prima kwijt kan. Offline ben ik daar nog steeds terughoudend in, "dat hoeft zo gek toch niet" of "doe maar normaal" is daar mijn credo, ondanks continu geconfronteerd te worden met de "ik" die ik online vertegenwoordig. Dat jasje kan gelukkig uit nu en ook offline weet ik mezelf redelijk te profileren, maar zonder online had me dat een stuk langer gekost.</p>
<p><strong>Vroeger</strong> — Je komt bij een nieuw bedrijf terecht, nieuwe mensen, nieuwe processen, andere koffie, andere namen, allemaal onzekerheden die er voor zorgen dat je niet vanaf dag 1 op je plek laat voelen of sterker nog, je enthousiasme over een organisatie behoorlijk laten verstommen waarmee je bijvoorbeeld je proeftijd niet eens uit zou mogen zitten…</p>
<p><strong>Nu</strong> — Je nieuwe werkgever nodigt je een week voor de start van je nieuwe baan alvast uit even een kijkje te nemen op de interne kennisdelingsgroepen. Daarin zie je al direct wat aardige collega's, ook een bijzondere aantrekkelijke, waarmee je dan ook makkelijk een babbeltje start. Komend weekend is er ook al een personeelsreisje gepland, waar je jezelf enthousiast ook voor uitnodigt — <em>slik</em> — maar goed, je "kent" ze inmiddels al een beetje toch?</p>
<p><strong>De tools</strong> — Interne kennisdeling kan heel complex en abstract zijn. Als je kijkt naar tools zoals intranetten en wiki's, zijn er wellicht zelfs workshops nodig om hier echt aan te kunnen wennen. Welcome to the 21st century, we hebben dus tegenwoordig tools als Yammer en workvoices die je daar uitstekend mee kunnen helpen. Beide tools zijn simpel in gebruik, registratie is eenvoudig en ook administratie een fluitje van een cent.</p>
<p>Interne kennisdeling wordt in de trends van sociale media nogal eens vergeten. Ondanks dat juist die interne kennisdeling het doel was om uberhaupt eens over internet te praten. De effecten op jouw organisatie kunnen gigantisch zijn en de lage kosten en risico's die het met zich meebrengt verzorgen een ideale springplank naar bredere participatie op sociale netwerken. Eens over praten?</p>]]></content:encoded>
    </item>
    <item>
      <title>Jump4Life: Serious Request</title>
      <link>https://casey.berlin/writings/2021/03/jump4life/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2021/03/jump4life/</guid>
      <pubDate>Sun, 21 Mar 2021 12:00:00 GMT</pubDate>
      <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">Wed, 25 Mar 2026 00:00:00 GMT</dc:date>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>social media</category>
      <category>Serious Request</category>
      <category>fundraising</category>
      <category>campagne</category>
      <category>social business</category>
      <description><![CDATA[Een bungeejump voor Serious Request, georganiseerd via social media. 97 YouTube filmpjes, 1.126 Flickr foto's, 481 tweets — en €10.388,65 voor een goed doel. Zo zie je maar wat een kleine actie kan doen.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>In opdracht van @Basschepers, werkzaam bij Continu te Eindhoven kreeg ik eind november 2010 te horen dat we "Even" een leuke actie mochten gaan promoten t.b.v. serieus request. Wat er daarna gebeurde…</p>
<p>Sowieso was ik al fan van serieus request geworden de afgelopen jaren, alleen is een eigen bijdrage daar nooit echt van gekomen. Mede dankzij het feit dat "er al zoveel goede doelen zijn", en ik graag persoonlijk iets bijdraag (vandaar mijn betrokkenheid bij de 1% club) waardoor ik het gevoel heb daadwerkelijk iets bij te dragen, dan alleen maar geld "over de schutting" gooien.</p>
<p>Dus, de vraag van @Basschepers om hem en Continu te ondersteunen bij hun actie voor serieus request, was er 1 die ik erg kan waarderen. Dat daar een bungeejump als resultaat van was, dat had ik ook niet direct gedacht.</p>
<p>In ieder geval was de kern van de actie dat er mensen geveild konden worden en dat de hoogste bieders, uiteindelijk vanaf 60 meter hoogte naar beneden vielen aan een koord om zo hun bijdrage te doen.</p>
<p><strong>Mijn aandeel</strong></p>
<p>In opdracht van Bas heb ik een aantal sociaal media outlets ingericht om dit visueel en tekstueel te kunnen ondersteunen. Daar heb ik mijn social media framework voor ingezet, waarbij de meest relevante netwerken (in dit geval mobypicture, facebook, youtube, flickr en twitter) samenkomen in 1 algemeen dashboard vanwaar content geplaatst en gemodereerd kan worden.</p>
<p><strong>De resultaten</strong></p>
<p>Zo'n kleine actie van mijn kant kan wel erg mooie gevolgen hebben, zowel voor de naamsbekendheid van het merk Continu, als de interactie die er daardoor ontstaat.</p>
<p>De cijfers:</p>
<ul>
<li>97 YouTube filmpjes met alle sprongen en wat gave nieuwscontent rondom de actie leverden 4.607 views op</li>
<li>1.126 foto's op Flickr leverden 7.246 impressies op</li>
<li>481 tweets leverden 155 volgers op</li>
<li>De website van Jump4Life werd in de maand December 4.341x bezocht en leverde 9.529 pagina weergaves op, met een "piek" moment van 700 bezoekers op de dag van de actie zelf</li>
</ul>
<p>En natuurlijk het prachtige bedrag van €10.388,65 voor Serious Request! Zo zie je maar dat met een relatief kleine hoeveelheid resources, ook een waanzinnig resultaat geleverd kan worden. In ieder geval 1 van de dingen waar ik trots op mag zijn.</p>]]></content:encoded>
    </item>
    <item>
      <title>Een nieuwe richting: KeesRomkes.nl</title>
      <link>https://casey.berlin/writings/2021/03/keesromkes-nieuwe-richting/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2021/03/keesromkes-nieuwe-richting/</guid>
      <pubDate>Sun, 21 Mar 2021 12:00:00 GMT</pubDate>
      <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">Wed, 25 Mar 2026 00:00:00 GMT</dc:date>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>ondernemerschap</category>
      <category>rebrand</category>
      <category>social business</category>
      <category>persoonlijke groei</category>
      <category>identiteit</category>
      <description><![CDATA[Na een tijd zoeken naar de juiste weg, nu beland in een nieuw stadium. Twee diensten, één naam. Ik geloof niet langer in 'het bedrijf' achter de persoon — ik geloof in de persoon.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<blockquote>
<p>Na een tijd zoeken naar de juiste weg, nu beland in een nieuw stadium waarin ik mij goed voel. Twee diensten, één naam. Social business consults en lezingen, KeesRomkes.nl</p>
</blockquote>
<p>3 Juli 2012, vandaag de dag dat ik besluit om een nieuwe richting te gaan wat mijn bedrijf betreft. Ik geloof niet langer in 'het bedrijf' achter de persoon, ik geloof in de persoon daarachter.</p>
<p>Ik vertrouw al elke dag in de relaties om me heen. Naast mijn partner Emma (zowel in life als crime) als mijn zakelijke contacten. Ik leg verbanden tussen mensen, niet tussen bedrijven. Ja ik vind Apple tof en doe mijn boodschappen bij Albert Heyn, maar voor de minder 'obvious' dingen en zeker in het zakelijk verkeer, heb je het over mensen.</p>
<p>Mensen die je steunen, door dik en dun. Die je kritische vragen stellen, en je eens doen laten omkijken naar het verleden en een blik meegeven in de toekomst.</p>
<p>Die toekomst start hier met een redesign van de site, met meer visueel geweld, een prettig leesbaarder menselijker lettertype en de informatie op 2 hele simpele pagina's. En ik start weer, net als vroeger, met een blogpagina. Dat is mijn 'thuis', het delen van kennis met jullie.</p>
<p>Leuk dat je er nog steeds bent, of fijn dat je hier voor het eerst komt kijken. Laat wat van je horen!</p>
<p>Tot snel!</p>]]></content:encoded>
    </item>
    <item>
      <title>Social Business: een introductie</title>
      <link>https://casey.berlin/writings/2021/03/social-business-introductie/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2021/03/social-business-introductie/</guid>
      <pubDate>Sun, 21 Mar 2021 12:00:00 GMT</pubDate>
      <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">Wed, 25 Mar 2026 00:00:00 GMT</dc:date>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>social business</category>
      <category>social media</category>
      <category>organisaties</category>
      <category>transparantie</category>
      <category>consulting</category>
      <description><![CDATA[Social Business, wat betekent dat eigenlijk? Waar social media de sociale laag rondom media is, is social business de sociale laag rondom je organisatie. Maar eerst even wat context.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<blockquote>
<p>Social Business, wat betekent dat eigenlijk? De komende tijd wil ik je meenemen in elk van de onderdelen die horen bij een social business. Waar ik social media zie als de sociale laag rondom media, is social business de sociale laag rondom je organisatie. Maar eerst even wat context.</p>
</blockquote>
<p>De tijd dat bedrijven nog gewoon konden doen zonder zich iets aan te trekken van hun klanten en relaties is voorbij. De wereld draait door en (is) harder dan ooit, zeker als je als bedrijf stil blijft staan en je hoofd in de grond steekt. Ontwikkelingen gaan continu door en het delen van informatie en die ontwikkelingen, gaat ongekend veel sneller dan ooit tevoren. Vergeet je gastenboek op je website of je zorgvuldig bij elkaar gespaarde database met e-mail adressen. Jouw relaties zijn veel dynamischer dan je daarin ooit bij kunt houden. Daar hoort ook een andere manier van denken bij.</p>
<p>En daar komt social business om de hoek kijken. Want dat is wat we (zouden) moeten doen. In zowel business2business als business2consumer, want eigenlijk zijn we allemaal consumer2consumer gericht bezig.</p>
<p>Het schematisch overzicht laat de belangrijkste relaties zien. Al die relaties die je ziet, zijn in evenwicht met elkaar, uiteraard ondersteund door processen en platformen maar bovenal gevoed door mensen. Zakenrelaties op een menselijke manier en menselijke normen, waarden en gebruiken. Zonder eenduidig afdekkend beleid. Dat eenduidige beleid naar klanten/relaties toe, zou ik echt graag zien verdwijnen. Tijd voor wat richtlijnen voor menselijkere communicatie binnen je bedrijf/organisatie dus!</p>
<p>In het hart van een social business ontstaat waarde. Waarde in de vorm van relaties, verbonden door sociaal kapitaal. Geen bank of belastingdienst die daar aan te pas komt, tenzij die zichzelf ook als partner opstelt. Een goed voorbeeld daarvan is hoe de Rabobank als partner tegenover Diergaarde Blijdorp staat. Een andere partner (in dit geval de gemeente Rotterdam) ontneemt de dierentuin €800.000 subsidie, wegens bezuinigingen. De Rabobank springt in want ziet dit als een investering in de toekomst en het heden. Nu ik de Rabobank noem als 'trouwe klant van Blijdorp' in dit blog, is de cirkel rond. Zo is gezamelijk een hoop sociaal kapitaal gegenereerd! En die is de gemeente tegelijkertijd kwijtgeraakt.</p>
<blockquote>
<p>Social business is een holistische aanpak om elk bedrijf te vernieuwen.</p>
</blockquote>
<p>Wat komt er dan aan (social) media bij social business kijken? De rol van social media is er nog altijd, want bij social business is het een ondersteunende factor. Sterker nog, die rol wordt alleen maar groter. Maar waar de focus binnen bedrijven de afgelopen jaren op elk los onderdeel is gelegd (marketeers beheren consumenten, managers interne sociale netwerken en directeuren beheren weer de marketeers en managers) benadruk ik de cohesie. De integratie. Samen werken en samen doen.</p>
<p>Social business is een hele nieuwe tak van sport. Veel meer dan de 'enterprise 2.0' gedachte, Social business is een holistische aanpak om elk bedrijf te vernieuwen. En niemand kan dat zonder de ander, en ik dus niet zonder jullie. Dus, hoe denk jij erover?</p>]]></content:encoded>
    </item>
    <item>
      <title>De volgende stap naar social business</title>
      <link>https://casey.berlin/writings/2021/03/social-business-volgende-stap/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2021/03/social-business-volgende-stap/</guid>
      <pubDate>Sun, 21 Mar 2021 12:00:00 GMT</pubDate>
      <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">Wed, 25 Mar 2026 00:00:00 GMT</dc:date>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>social business</category>
      <category>transparantie</category>
      <category>organisaties</category>
      <category>internet cultuur</category>
      <category>consulting</category>
      <description><![CDATA[Veel bedrijven zitten letterlijk op internet maar staan stil. Social business is het compleet transparant maken van jouw organisatie online — met alle medewerkers, niet alleen marketing. Die wereld start nu.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<blockquote>
<p>Ik woon inmiddels alweer ruim 3 jaar buiten Friesland. Het lijkt wel een eeuwigheid geleden. Voor veel bedrijven lijkt het internet er ook al eeuwen te zijn, maar zijn er ook hooguit 20 jaar mee bezig. Ze zitten er letterlijk. Tijd voor de volgende stap!</p>
</blockquote>
<p>Ruim 3 jaar geleden koos ik voor de grote stad. Een best wel invloedrijke keuze is dat geweest; op mijn leven, maar ook op mijn werkzaamheden. Zonder internet is er voor mij geen leven meer, en zo is dat ook voor veel andere bedrijven tegenwoordig. Ga maar na, wat zou een bedrijf nou zijn zonder e-mail en zonder internet. Hoe communiceren we dan nog met elkaar? Hoe verkopen we dan uberhaupt nog? Stel je eens voor dat we daadwerkelijk weer eens op elkaar af zouden lopen, even kijken hoe het met de collega's gaat. Feedback vragen, wellicht een prettig meningsverschil hebben, daadwerkelijk aan mensen laten zien wie of wat je nou echt bent…</p>
<p>Des te ironischer is de volgende stap voor bedrijven op internet. Social business is het compleet transparant maken van jouw organisatie online. Alle data (waar dat gewenst is) inzichtelijk, open staan voor feedback, reacties en commentaar, jezelf durven zijn online en staan voor jouw product of dienst. Met alle medewerkers, niet alleen de sales of marketing afdeling.</p>
<blockquote>
<p>In samenspraak en cohesie met je collega's, met wie je peilsnel kan schakelen. On- én offline.</p>
</blockquote>
<p>In transparante relaties met je leveranciers, die je direct kunnen vertellen waar zij hun duurzame producten vandaan halen; sterker nog, je kijkt gewoon even mee bij je leverancier wat ze in de schappen hebben voordat jij je volgende bestelling doet. Bij de boer, om de hoek. Geen groothandels.</p>
<p>De wereld wordt kleiner dankzij internet, maar je mogelijkheden groter. De hoeveelheid data en opties die dat brengt voelt als een snelweg met auto's die op hoge snelheid voorbij razen. Alleen jij zit nog kilometers van die snelweg vandaan, je kiest er zelfs voor te negeren dat die snelweg er is. Die rust is misschien even lekker, maar vroeg of laat moet jij ook naar de grote stad. Die snelweg op, mee met je klanten en je leveranciers. Open voor feedback, meningen van anderen en vol zelfvertrouwen over jouw product of dienst. Toekomstmuziek? Nee. Die wereld start nu.</p>
<p><em>Photo: CIAT/flickr</em></p>]]></content:encoded>
    </item>
    <item>
      <title>Waar sta ik nu?</title>
      <link>https://casey.berlin/writings/2021/03/waar-sta-ik-nu/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2021/03/waar-sta-ik-nu/</guid>
      <pubDate>Sun, 21 Mar 2021 12:00:00 GMT</pubDate>
      <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">Wed, 25 Mar 2026 00:00:00 GMT</dc:date>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>ondernemerschap</category>
      <category>visie</category>
      <category>social media</category>
      <category>persoonlijke groei</category>
      <category>authenticiteit</category>
      <description><![CDATA[Authenticiteit, verbinding en transparantie als de drie pijlers van mijn ondernemerschap. Dankzij een gesprek in #ZZPhappyhour gedwongen na te denken over mijn visie — en er duidelijkheid uit gehaald.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>Het begint al bij het kiezen van een naam voor deze blog, waar sta "ik" nu, nou, je kan het beter "waar staan wij nu" noemen. Ik ben blij met het gekozen pad, de samenwerkingen, de projecten die lopen en nog aankomend zijn en de ontwikkelingen op social media gebied.</p>
<p>Dankzij een gesprek wat ik had met Judith Webber in haar #ZZPhappyhour werd ik gedwongen zelf eens na te denken over mijn visie, waarom opereer ik in deze wereld? Wat is voor mij(n onderneming) belangrijk?</p>
<p>Daaruit kon ik toch al concreet een aantal punten halen die passen bij mijn diensten en producten:</p>
<ul>
<li><strong>Authenticiteit</strong> — hoe "helder" is jouw propositie, waar sta je voor als bedrijf, hoe past internet in jouw (marketing) strategie?</li>
<li><strong>Verbinding</strong> — hoe "bewust" ben jij je van de wereld (jouw doelgroep, jouw branche) om je heen? Waar zit je kracht, met wie wil je samenwerken, hoe haal je de "kracht" uit je netwerk, zonder deze uit te putten, maar juist aan te vullen?</li>
<li><strong>Transparantie</strong> — in zaken doen met mij, wat kan je van me verwachten en wat mag ik van jou als opdrachtgever verwachten? Blijf verwachtingen toetsen, stel bij waar nodig.</li>
</ul>
<p>Ben ik authentiek, verbonden en transparant in mijn uitingen? Ik weet zeker van wel, door dit te vragen aan mijn opdrachtgevers, maar ook vrienden, uit netwerken die zowel zakelijk als privé zijn (die steeds meer versmelten) en daar ook enorm veel kracht uit te halen.</p>
<p>Mijn verbinding met jullie is voor mij het belangrijkst, als opdrachtgever, samenwerkingspartner of prive contact, voor iedereen die mijn blogs leest. Suggesties voor inhoud? Waar mag ik mijn mening eens over geven? Ik hoor het graag!</p>]]></content:encoded>
    </item>
    <item>
      <title>De start: zelfstandig ondernemer!</title>
      <link>https://casey.berlin/writings/2021/03/zelfstandig-ondernemer-de-start/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2021/03/zelfstandig-ondernemer-de-start/</guid>
      <pubDate>Sun, 21 Mar 2021 12:00:00 GMT</pubDate>
      <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">Wed, 25 Mar 2026 00:00:00 GMT</dc:date>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>ondernemerschap</category>
      <category>social media</category>
      <category>consulting</category>
      <category>mijlpalen</category>
      <category>zelfstandig</category>
      <description><![CDATA[Na 5 maanden als fulltime ondernemer: diverse lezingen, een Hyves community voor Jopla, sociale media advies voor Difrax en de start van #bouw20. Een trotse terugblik op de eerste mijlpalen.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>Met een kleine 5 maanden als fulltime ondernemer achter de rug, diverse "terugblik" sessies, onderzoek naar toegevoegde waarde, vele liters koffie en vele lange dagen ontdekken, praten, offreren en factureren, naast ook nog werk doen, tevreden ondernemer. Tijd voor de volgende stap!</p>
<p>Social media is zoveel meer dan "linkedinnen, facebooken of twitteren", Social Media is contact maken met je klanten. Dat feit is een eerste conclusie uit de blogs die ik geschreven heb, de (veelal) positieve reacties, kritische noot van goede vrienden en dat leid tegenwoordig tot een mooi gemiddeld aantal van 50 bezoekers per dag, die gemiddeld een 2,5 pagina bekijken en mij "3 minutes of fame" geven. Top!</p>
<p>Een aantal wapenfeiten waar ik erg blij mee ben:</p>
<ul>
<li>De start van de #bouw20 community in wording op IGRomkes.nl (@romkesbv)</li>
<li>Implementatie en integratie van Mailchimp.com nieuwsbrief software voor @Difrax, naast succesvolle begeleiding in hun twitter acties</li>
<li>Diverse lezingen en workshops die ik heb mogen verzorgen</li>
<li>Een gave hyves community voor Jopla</li>
<li>Strategische inzet en advies sociale media voor een duurzaam mobiliteitsinitiatief</li>
</ul>
<p>En uiteraard de mooie samenwerkingsverbanden met o.a. @jvdschenk, @esmeeschonfeldt, @misterseeder en Seats2Meet.com/MINDZ.com visionairs @rvandenhoff en @msijgers waar ik ook de @layar van mag ontwikkelen en implementeren vanuit de door hen gedeelde visie.</p>]]></content:encoded>
    </item>
    <item>
      <title>Consumption sharing: Blippy, GetGlue en Foodspotting</title>
      <link>https://casey.berlin/writings/2020/10/consumption-sharing/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2020/10/consumption-sharing/</guid>
      <pubDate>Thu, 01 Oct 2020 12:00:00 GMT</pubDate>
      <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">Wed, 25 Mar 2026 00:00:00 GMT</dc:date>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>social media</category>
      <category>apps</category>
      <category>consumption sharing</category>
      <category>tools</category>
      <category>internet cultuur</category>
      <description><![CDATA[Steeds meer social apps maken consumption sharing inzichtelijk: delen wat je doet, kijkt, luistert en eet. Een kijkje in Blippy, GetGlue en Foodspotting — drie apps die dat elk op hun eigen manier aanmoedigen.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>De laatste tijd komen er steeds meer "social applications" bij die consumption sharing inzichtelijk maken, vrij gedefinieerd: delen wat je doet, wat je kijkt, luistert, eet. Vandaag een kijkje in Blippy en GetGlue en Foodspotting, 3 applicaties die Consumption Sharing duidelijk aanmoedigen en in al hun facetten een "social application" zijn.</p>
<p><strong>Wat is een social application?</strong></p>
<p>Een social application is voor mij een applicatie die je dus in staat stelt om "consumption sharing" inzichtelijk te maken. In het geval van Blippy bijvoorbeeld je meest recente aankopen delen en reviewen.</p>
<p>Een Social Application kent dus in ieder geval de voorwaarde dat het 1 doel heeft, delen. Daarnaast draait het om mensen, niet zo zeer om de techniek er achter. Hen in staat stellen met elkaar te verbinden en kennis te delen rondom het thema is hier het common goal.</p>
<p>Daarnaast is "eenvoud" nog zo'n ding. Hoe eenvoudiger, hoe meer "Social" die applicatie is. Het moet echt dat ene doel dienen en gelukkig doen beide websites dat prima. Ja, dat betekent dus ook ondersteuning op en van meerdere platformen en inloggen met externe netwerken bijvoorbeeld.</p>
<p>Het allerbelangrijkste? De opbrengsten, oftewel de toegevoegde waarde. Als ik 1 ding deel, wil ik een meervoud aan suggesties terug krijgen. Liefst zo specifiek mogelijk en op mijn profiel afgestemd, semantisch dus.</p>
<p>In het kort, delen als middel, eenvoud van de tool, duidelijke opbrengsten en afgestemd op mij. Kenmerken van een top social app!</p>
<p><strong>Blippy</strong></p>
<p>Blippy stelt mij in staat om mijn aankopen op creditcard, diverse online shops (waaronder de iTunes store) te delen met anderen. Dan gaat het niet perse om het aspect "kijk eens wat ik heb", maar juist om het oordeel wat je daar over hebt. Al zal een kop koffie in Nederland niet zo snel betaald worden met creditcard, dat gebeurt dus wel in de US. Koppelingen met chipknip of andere middelen zullen nog wel volgen. Daarnaast koop ik al snel iets in de iTunes store, een klein spelletje om het wachten te vergemakkelijken of een lifehack zoals Calvetica of Dialvetica. Die review ik vervolgens op Blippy en zo weet mijn netwerk, maar ook anderen weer iets over die applicatie, dat kopje koffie, of dat gerecht in een bepaald restaurant.</p>
<p>Blippy is niet "opdringerig" in de vraag naar reviews en beloond je met behulp van "levels" (die direct ook weer jouw betrouwbaarheid aangeven) op basis van het aantal reviews wat je doet.</p>
<p><strong>GetGlue</strong></p>
<p>GetGlue is mijn nieuwste "verslaving", ik kijk regelmatig series, films of denk even na over een bepaald onderwerp en dat is waar GetGlue haar verbinding haalt. Die onderwerpen die anderen boeien, de mogelijkheid te zien "wie nog meer" van die film of serie houdt en opnieuw een netwerk opbouwen van mensen om je heen met die specifieke interesse.</p>
<p>Daarnaast verzorgd GetGlue de suggesties op een erg prettige manier. Na het aangeven dat je een bepaald genre films leuk vind, zal je ook zien dat GetGlue jou suggesties doet voor meer content. Niet alleen op basis van jouw keuzes, maar ook op basis van jouw netwerk en zelfs de tijd wanneer je inchecked is relevent aan wat je graag wil zien. De koppeling met TV gidsen is dan nog erg dichtbij.</p>
<p><strong>Foodspotting</strong></p>
<p>Foodspotting is 1 van mijn "leukste" social apps op dit moment, naast het delen van wat ik eet, kan ik op deze manier ook op zoek naar nieuwe restaurants en gerechten.</p>
<p>Ik deel op foodspotting dus wat ik eet, een kleine review van wat ik er van vind en met de knoppen "nom it" en "want it" kan ik ook nog context geven aan het gerecht naar keuze. De koppeling met foursquare, twitter en facebook maakt het eveneens erg gemakkelijk om breder te delen en zo te zien hoeveel mensen daadwerkelijk naar jouw "voedsel" kijken.</p>
<p>Foodspotting zelf is wat "voeden" van mijn profiel betreft gekoppeld aan gebruik op mijn mobiele telefoon. Gemiste kans, gezien ik juist ook zoveel doe op mijn laptop. Echter het "delen" van de inhoud en reageren op anderen, kan dan wel weer online gebeuren.</p>
<p><strong>Maar wat moet ik dan met al die apps?</strong></p>
<p>De vraag die daar bij rest is tenslotte "wat moet ik daar dan allemaal mee?" En dat is een logische. Voor @Basiliek heb ik bijvoorbeeld een aantal gerechten via foodspotting gedeeld om zo te illustreren wat dat voor hun zou kunnen betekenen. Met @blippy review ik regelmatig applicaties voor de iPhone en ook daar komt dialoog uit. En Getglue zorgt voor mij voor meer koppeling met mijn netwerk. Ik weet wat zij kijken, en andersom. Kern van dit verhaal? Voor elke doelgroep is er een platform, elke niche kent zijn of haar plek. Jouw kans? Geen niche platform nog? Bouwen! Meer weten over gebruik of inzet? Laat het even weten!</p>]]></content:encoded>
    </item>
    <item>
      <title>Contactually en de R van CRM</title>
      <link>https://casey.berlin/writings/2020/10/contactually-de-r-van-crm/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2020/10/contactually-de-r-van-crm/</guid>
      <pubDate>Thu, 01 Oct 2020 12:00:00 GMT</pubDate>
      <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">Wed, 25 Mar 2026 00:00:00 GMT</dc:date>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>CRM</category>
      <category>tools</category>
      <category>netwerk</category>
      <category>social media</category>
      <category>ondernemerschap</category>
      <description><![CDATA[Alle CRM-tools draaien om zoveel mogelijk data verzamelen. Contactually doet dat anders: het stelt gewoon de vraag wanneer je voor het laatst iemand hebt gesproken.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<blockquote>
<p>Ik heb iets met tools en met name op het gebied van CRM. Op social gebied nemen die tools op dit moment een enorme vlucht en duikelen over elkaar heen; Salesforce, Microsoft en IBM als grote jongens en vele, vele kleine producenten daaronder. Contactually is een beetje een andere aanpak van dat eenvoudige probleem, contact onderhouden.</p>
</blockquote>
<p>Waar veel CRM draait om zoveel mogelijk klant- en contactgegevens te verzamelen (de C van CRM), draait het daar bij Contactually niet om. Wat daar het belangrijkste is, is de vraag "wanneer heb ik voor het laatst met iemand contact gehad?".</p>
<p>Ik heb een hekel gekregen aan de zogenaamde SCRM's (social CRM) pakketten, die zichzelf als social in de markt zetten. Eigenlijk zijn het ouderwetse, bijna DOS achtige pakketten ingericht op het verzamelen van massa's data, om er zo voor te zorgen dat je precies weet wat je klant denkt, voelt en schrijft. De social toevoeging in deze big data is een krachtige tool, die veel account managers en marketeers dan ook met liefde inzetten. In essentie slaan die pakketten de plank mis, het gaat niet om sociaal doen, maar om social misbruik in die pakketten.</p>
<blockquote>
<p>Of dat je moeders bent vergeten te bellen de afgelopen maanden omdat je het zo druk hebt.</p>
</blockquote>
<p>Je moet namelijk heel voorzichtig zijn met het in contact blijven met je klanten. Je kan ze simpelweg niet jouw informatie opdringen, daarvoor is aandacht van je klanten veel te kostbaar. Wel kan je inspelen op de behoefte van je klant, een simpel sociaal gebaar geven, een kaart sturen bij een verjaardag of een relevante reactie op een foto bijvoorbeeld. Vragen die gesteld worden via Twitter beantwoorden, een koppeling maken met iemand uit je netwerk, dat soort zaken.</p>
<p>Contactually helpt bij het bijhouden van de relaties met mijn contacten. Zakelijk en prive. De meeste mensen spreek ik toch wel regelmatig, maar soms moet daar even een tandje bij, in het geval iemand zakelijk een lead is geworden en je toch graag wil weten wat iemand van je voorstel vindt. Of een partner waar je een relatie mee bent aan gegaan en zijn of haar praktijken ineens relevanter geworden zijn aan wat jij in je bedrijf doet, of dat je moeders bent vergeten te bellen de afgelopen maanden omdat je het zo druk hebt.</p>
<p>De stappen voor het werken met Contactually zijn simpel:</p>
<ol>
<li>Ik laad al mijn netwerken in, met Gmail als basis voor elk contact. Twitter, Facebook en LinkedIn zijn standaard ondersteund. Ook grotere CRM tools als Salesforce en sugarCRM hebben een integratiemogelijkheid.</li>
<li>Ik speel de 'bucket game', een spelletje waarin ik mijn contacten toewijs aan een bepaalde groep, waarmee het een stuk leuker wordt je contacten te sorteren.</li>
<li>Elke bucket (groep) kent een bepaalde maximale tijdsgrens waarin je met mensen contact zou willen hebben. Leads bijvoorbeeld binnen 14 dagen, je familie misschien een dag of 30 en vage kennissen misschien eens in de twee maanden.</li>
<li>Ik volg ze op vanuit Contactually of geef bij elk contact aan op wat voor manier ik contact met hen heb gehad.</li>
</ol>
<p>De kern van contactually zijn de groepen. Ik denk tegenwoordig meer in zwermen, dus houd ik het simpel:</p>
<ul>
<li><strong>Leads</strong> — ik moet ook mijn brood verdienen, die mensen die dat verschaffen zitten vrij dicht op mij, zakelijk gezien dan.</li>
<li><strong>Close ties</strong> — mensen die mij het meest dierbaar zijn vindt je hier terug.</li>
<li><strong>Weak ties</strong> — ik geloof erg in de kracht van de zwakke schakel, iemand 'eens gekend is altijd gekend', er is zoveel informatie over iemand terug te vinden via dit soort tools, dat je altijd wel een 'oh ja' momentje hebt.</li>
</ul>
<p>Zo hou ik het overzichtelijk en klein, maar wel prive en zakelijk in een. Wat tijdsinvestering betreft kijk ik hier één tot twee keer per week naar, hooguit 15 minuten. Zo blijf ik bij met jou. Nogmaals, elk contact wat ik heb met mensen is van sociale aard, de kern zit in het investeren in de relatie. Soms kost me dat ineens een half uur om een goed antwoord te googlen of het schrijven van een blog. Maar in elke investering in een ander zit een rendement, daar geloof ik heilig in!</p>
<p>Kern van dit alles is dat de aandacht komt de liggen op de Relatie, in plaats van op het Contact in de afkorting van CRM. Ook van Management is nauwelijks sprake, vraag eens oprecht hoe het met mensen gaat, neem de tijd voor elk contact. Mijn uiteindelijke doel is een socialere wereld, waar we van elkaar leren en ook nog eens een boterham kunnen verdienen. Met een beetje hagelslag. Contactually helpt mij daar bij. Wat is jouw voorkeur qua CRM?</p>
<p><em>Photo: Creative Commons; Flickr - Ray Larabie</em></p>
<p><em>Contactually vroeg mij naar aanleiding van mijn ervaringen een artikel te schrijven. Ook ben ik een 'case story' op de site van Contactually als veelvuldig gebruiker. Bij deze mijn investering in hen. Daar gaat overigens geen euro mee gepaard.</em></p>]]></content:encoded>
    </item>
    <item>
      <title>De behoefte aan échte verbinding</title>
      <link>https://casey.berlin/writings/2020/10/de-behoefte-aan-echte-verbinding/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2020/10/de-behoefte-aan-echte-verbinding/</guid>
      <pubDate>Thu, 01 Oct 2020 12:00:00 GMT</pubDate>
      <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">Wed, 25 Mar 2026 00:00:00 GMT</dc:date>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>social media</category>
      <category>verbinding</category>
      <category>relaties</category>
      <category>netwerk</category>
      <category>ondernemerschap</category>
      <description><![CDATA[Een maandagochtend overweging. Zo langzamerhand merk ik dat de behoefte aan constante verbinding afneemt. Er is bij mij meer dan ooit behoefte aan 'sociaal', dan aan een groot aantal verbindingen.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<blockquote>
<p>Een maandagochtend overweging. Zo langzamerhand merk ik dat de behoefte aan constante verbinding afneemt. Misschien komt het door de vakantieperiode, het grote aantal bedrijven wat zich 1.0 opstelt op sociale netwerken of de échte sociale band die ik opbouw met mensen via Path, maar er is bij mij meer dan ooit behoefte aan 'sociaal', dan aan een groot aantal verbindingen.</p>
</blockquote>
<p>Grappig hoe soms zaken in één keer bij elkaar komen en context geeft aan zo'n lastig onderwerp. Aan de ene kant leef ik (van) online. Mijn brood zit in online, als consultant en als spreker. Ik ben al ruim 20 jaar online terug te vinden. Eerst in connectie met een enkeling via BBS'en, later op diverse fora en in chatboxen op IRC, tot facebook en twitter nu met duizenden tegelijk. Die verbindingen uit vroeger tijd voelden veel persoonlijker dan de meeste contacten op Facebook en Twitter nu. Want aan de andere kant is er de hoeveelheid, de massa, die op een gegeven moment niet meer te managen is. Het wordt een proces, iemand volgen, berichtje heen en weer, en proberen in de radar te blijven van die persoon. Niet om wat hij of zij doet, maar om te bewijzen dat je nog bestaat. "Ik deel, dus ik besta".</p>
<p>Als medewerker of manager van een bedrijf moet je daar ook eens goed naar moeten kijken. Beschouw de sociale media niet als de ultieme manier om nieuwe klanten te werven, personeel te zoeken of je medewerkers te stimuleren (of controleren) maar kijk ze eens recht in de ogen aan. Vraag ze op de man af hoe ze zich voelen. Meer dan ooit is er ook bij hen (misschien weten ze het niet) behoefte aan een luisterend oor. Iemand die tegen ze praat en oprecht vraagt: "hoe gaat het nu met jou?"</p>
<p>Meer dan ooit is er behoefte aan écht oprecht contact.</p>
<p>Daarvoor kwam het blog wat <a href="https://twitter.com/josgovaart">@josgovaart</a> en <a href="https://twitter.com/roosvanvugt">@roosvanvugt</a> deelden zo goed uit. Path ís namelijk het sociale netwerk waarin de vertrouwensband, kleinschaligheid en menselijke emoties vooropstaan. Waarin echte gevoelens, lief en leed, gedeeld wordt. Waar ook ruimte is voor mij om af en toe een flauwe grap te plaatsen die niet altijd gepast is op andere sociale netwerken.</p>
<p>En als bedrijf heb je helemaal niks aan Path. Maar jij, als persoon, wel. Om mensen te leren kennen, om ze jou te leren kennen. En vervolgens eens koffie met ze te drinken. Fijne werkweek!</p>]]></content:encoded>
    </item>
    <item>
      <title>Eens gekend is altijd gekend</title>
      <link>https://casey.berlin/writings/2020/10/eens-gekend-is-altijd-gekend/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2020/10/eens-gekend-is-altijd-gekend/</guid>
      <pubDate>Thu, 01 Oct 2020 12:00:00 GMT</pubDate>
      <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">Wed, 25 Mar 2026 00:00:00 GMT</dc:date>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>social media</category>
      <category>relaties</category>
      <category>netwerk</category>
      <category>verbinding</category>
      <description><![CDATA[Via social media raak je niemand meer kwijt. Handig, maar ook een beetje benauwd. Want een gesprek met iemand die je al online kent, voelt al snel als een teleurstelling.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<blockquote>
<p>Jaren van internetgebruik en social media, naast veel random contacten bij @seats2meet, leidt bij mij tot de conclusie dat je eigenlijk niemand meer kan vergeten uit het verleden. Zodra ze eenmaal in je adresboek zijn aangeland, raak je ze nooit meer kwijt.</p>
</blockquote>
<p>'Eens gekend is altijd gekend', schreef ik maandag in dit blog. Dat citaat heb ik opgeschreven voor vandaag en na wat nadenken kom ik tot de conclusie; als je het niet wilt, hoef je nooit meer iemand te vergeten. Het internet stelt ons in staat van iedereen wel iets van relevante informatie naar boven te toveren en met de mogelijkheden van Twitter, Facebook en LinkedIn is er ook geen beperking in wie je wel, of niet toelaat in je netwerk. Met tools als Contactually kan ik zelfs (al is dat kunstmatig) gedwongen contact houden met iedereen, of ik (of die persoon) er nu behoefte aan heeft of niet.</p>
<p>Dat leidt tot een raar fenomeen, die je nu ook in het echte leven tegenkomt. Er is geen aandacht meer tijdens een gesprek, of de druk bij een (gepland) gesprek ligt zo hoog om het 'leuk te hebben' of 'inhoudelijk van waarde' (jakkes) te zijn dat het gesprek altijd zal teleurstellen. Je weet immers alles van die persoon, moet een plan maken en een doel hebben omdat je zo weinig tijd hebt in je agenda; die ene afspraak moet dan wel héél bijzonder zijn en moet echt iets betekenen.</p>
<p>Ik ontdekte het bovenstaande bij mezelf een paar maanden geleden, omdat ik mijn agenda niet zo vol meer wilde plannen als een jaar of twee geleden. Toen had ik vier gesprekken op een dag, liefst strak op elkaar geplanned zodat er ook nog tijd over bleef voor werk, dat ik een gesprek niet als werk beschouw, had ik toen nog niet helemaal in de gaten. Door minder ruimte in mijn agenda te reserveren voor gesprekken kwam de keerzijde hiervan naar boven. De keerzijde was dat elk gesprek nu wel van waarde moest zijn, ik had immers tijd voor die persoon gereserveerd die in mijn ogen heel waardevol was. Daar kwam ik dus met een domper uit…</p>
<blockquote>
<p>De wereld wordt mooier geschetst via social media dan ooit tevoren, ook al doen de nieuwsfeeds op Twitter anders blijken.</p>
</blockquote>
<p>Mensen veranderen, omgeving verandert, context verandert. De wereld wordt mooier geschetst via social media dan ooit tevoren, ook al doen de nieuwsfeeds op Twitter anders blijken. Mijn beeld van die persoon aan de andere kant van de tafel was geschetst door wat hij of zij deelde online. Ik toetste dat niet, ik nam dat voor waarheid aan. Bizar eigenlijk, nu goed bekeken. Ik spreek alleen nog maar af met mensen die ik echt gemist heb, of die ik zakelijk gezien nodig heb. En heel vaak ontstaat dat gewoon spontaan. Zonder verwachtingen, met nog wel een blik op de sociale netwerken om even te kijken wat die persoon de afgelopen weken gedaan heeft, maar dat is meer stof ter conversatie dan het scheppen van een beeld.</p>
<p>Zullen we er gewoon weer eens voor kiezen om af en toe iemand op te bellen? Eens te kijken hoe het met die persoon gaat? En je hart te volgen in zo'n contact, in plaats van je agenda? En laat Facebook, Twitter en LinkedIn daar eens in faciliteren; mensen met wie je even geen contact hebt gehad, in een soort van 'sluimerstand' plaatsen en geleidelijk laten verdwijnen uit je netwerk. Net zoals dat vroeger ging. Dan bepaal ik weer of ik iemand wil spreken, in plaats van zijn status update of change of job. Herken jij je hierin? Hoe ga je daar mee om?</p>]]></content:encoded>
    </item>
    <item>
      <title>6 tips voor een gezondere lifestyle</title>
      <link>https://casey.berlin/writings/2020/10/gezondere-lifestyle/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2020/10/gezondere-lifestyle/</guid>
      <pubDate>Thu, 01 Oct 2020 12:00:00 GMT</pubDate>
      <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">Wed, 25 Mar 2026 00:00:00 GMT</dc:date>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>gezondheid</category>
      <category>lifestyle</category>
      <category>productiviteit</category>
      <category>lifehacking</category>
      <description><![CDATA[Stoppen met koffie, gezond eten, voldoende bewegen en luisteren naar je lichaam. Zes tips die mij echt iets gebracht hebben — en die meer met productiviteit te maken hebben dan je misschien denkt.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<blockquote>
<p>Vorige week schreef ik al 10 productiviteitstips die vooral gaan over de plek waarop je werkt, technieken en tips. Nu 6 tips voor een gezondere lifestyle en wat mij dat gebracht heeft.</p>
</blockquote>
<ol>
<li>
<p><strong>Eet gezond.</strong> Die stond er vorige week ook al bij, maar ik wil 'm toch graag even terug halen. Eet je dagelijkse groente en fruit. Het zorgt voor energie gedurende de hele dag en de tijd dat je niet op je werk bent. Ik kies hierin om zo weinig mogelijk E-nummers te eten, met name de verslavende E621 bijvoorbeeld, die je in veel producten (met name pakjes en zakjes) terug ziet. Gelukkig is Emma een kookwonder, maar leer ik zo langzamerhand ook het een en ander bereiden. Vers en gezond voedsel is hierin heel belangrijk. Wij laten ons inspireren door de Italiaanse keuken, met veel groente en salades. We hebben de hele dag energie en blijven op een gezond gewicht. Ook het beperken van suikers helpt daar enorm bij. Suiker is een enorme verslaving waar ik verbaasd over was; stop maar eens bewust met veel suiker eten, of let eens op de voedingswaardes van de producten die je consumeert. Melk bijvoorbeeld, jus d'orange of light producten. Je hebt meer energie dan je voor mogelijk hield en de constante drang naar eten en zoetigheid is verleden tijd. Daarnaast smaakt het eten zo ontzettend veel lekkerder dan daarvoor.</p>
</li>
<li>
<p><strong>Drink gezond.</strong> Koffie is killing. Ik dronk in mijn actieve seats2meet.com tijd een kop of acht per dag. Waanzinnig als ik dat zo eens bekijk, maar de periode leende zich er kennelijk voor. Ik probeerde elke tegenslag of lichamelijke wens naar rust te negeren en op te vullen met koffie. Zo kom je de dag dan vanzelf wel als een hyperactieve zombie door. Stoppen met koffie is één van de beste stappen die ik heb genomen. Heerlijk om de hele dag zo energiek te kunnen zijn. Het effect van een kop koffie merk ik dan ook vrijwel direct, ik kan er (letterlijk) de hele nacht mee door, en de 'koffiekater' die de volgende dag terug komt, is heel vervelend en bijna migraine achtig. Je lichaam schreeuwt om nieuwe cafeïne.</p>
</li>
<li>
<p><strong>Beweeg veel.</strong> Veel van jullie zullen een zittend beroep hebben. Naast de overweging staand te gaan werken, is veel beweging noodzaak. Plan je afspraken buiten de deur eens rond een station, elk stuk openbaar vervoer wat je aflegt gaat gepaard met (wat) beweging. Ik zie dan ook weinig dikke mensen met de trein gaan, omdat de auto bij die groep mensen de voorkeur heeft. Al is het maar die 10 minuten (staand) wachten op het station en het lopen van spoor naar spoor, die beweging helpt je in ieder geval de eerste stappen op weg. Ik fitness zelf twee tot drie keer per week, heerlijk om zo energie op te bouwen en me prettig in mijn eigen lijf te voelen. Ook dat is belangrijk in productiviteit, jezelf goed voelen zet zich nu eenmaal door in het werk wat je doet.</p>
</li>
<li>
<p><strong>Rust genoeg.</strong> De zomerperiode heeft me weer eens geleerd dat het niet erg is om eens lekker uit te slapen of aan het eind van de middag een half uur te slapen op de bank. Informatie verwerken vergt veel energie van je hoofd en die geeft regelmatig signalen aan je lichaam dat je rust moet nemen. Zo verwerk je informatie beter, sla je die informatie onbewust op en die komt er dankzij de rust ook weer op de juiste momenten uit. Er is niets vervelenders dan een gesprek te hebben waarin je geen 'inzichten' kan geven die direct vanuit je eigen ervaring en onbewustheid doorsijpelen. Vaak kan ik vertrouwen op dat geheugen, weet ik me case studies te herinneren die ik ooit eens gelezen heb of een tool of tip te geven die van toepassing is in die situatie. Zonder rust is dat niet mogelijk.</p>
</li>
<li>
<p><strong>Luister naar je lichaam</strong>, je hebt er maar één van tenslotte. Vaak geeft het wel aan hoe het met je is, maar de signalen zijn verkeerd te interpreteren. Vermoeidheid kan duiding geven aan veel situaties. In mijn geval verkeerd eten, teveel cafeïne en weinig lichaamsbeweging. Een detoxweek, of een resetweek kan dan een goed middel zijn om weer overnieuw te beginnen, maar dan ook met alle gewoontes die je hebt abrubt een einde te maken. Stoppen met roken bijvoorbeeld, wat ik gelukkig ook heb kunnen laten liggen, ging alleen maar door verandering van gewoontes en zelfs omgeving. Verhuis je binnenkort? Het ideale moment om te stoppen. Een nieuwe baan, een nieuwe hobby, een nieuw boek. Grijp die momenten aan om te breken met nare gewoontes en je lichaam rust en gezondheid te gunnen. Dat geldt ook voor dat ene ijsje elke avond, een handje chips bij het voetbal en de vette hap op de zondagavond.</p>
</li>
<li>
<p><strong>Wees geestelijk gezond.</strong> Naast bloggen, wat voor mij heerlijk werkt om mijn gedachtes op een rij te zetten, schrijf ik ook veel in dagboek apps, ik praat met veel mensen, en heb een partner waar ik heel fijn op terug kan vallen. Ik reflecteer veel, heb daar de tijd voor in de auto of neem een (autobiografisch) boek waar ik mij aan kan spiegelen. Meditatie of yoga schijnt ook te helpen, al ben ik daar te nuchter voor. Geef mij maar praktische zaken, een goed gesprek en rust en ruimte voor mezelf.</p>
</li>
</ol>
<p><em>Photo: Creative Commons/Flickr: Mikko Lutniala</em></p>]]></content:encoded>
    </item>
    <item>
      <title>Je laatste tweet</title>
      <link>https://casey.berlin/writings/2020/10/je-laatste-tweet/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2020/10/je-laatste-tweet/</guid>
      <pubDate>Thu, 01 Oct 2020 12:00:00 GMT</pubDate>
      <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">Wed, 25 Mar 2026 00:00:00 GMT</dc:date>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>social media</category>
      <category>digitale identiteit</category>
      <category>technologie</category>
      <category>internet cultuur</category>
      <description><![CDATA[Je wil er niet aan denken, maar toch komt er dat moment dat je je laatste adem uitblaast. En dus ook je laatste tweet plaatst. Maar wat gebeurt er vervolgens met je online identiteit? En wat biedt de techniek voor mogelijkheden?]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<blockquote>
<p>Je wil er niet aan denken, maar toch komt er dat moment dat je je laatste adem uitblaast. En dus ook je laatste tweet plaatst. Maar wat gebeurt er vervolgens met je online identiteit? En wat biedt de techniek voor mogelijkheden?</p>
</blockquote>
<p>Er zijn een aantal tools die er voor zorgen dat jouw profiel op het moment van overlijden wordt afgesloten, dat er nog één laatste bericht geplaatst wordt, dat soort dingen. Het lijkt mij een hele goede zaak dat daar een uniforme afspraak over komt. Er is niets zo vervelend voor nabestaanden om door zoveel sociale netwerken te moeten (ik wil er niet aan denken in mijn geval…) om profielen te sluiten, op te heffen of te veranderen in een 'bevroren' profiel.</p>
<p>Een kijkje in de toekomst; technologie stelt ons in staat om te voorspellen wat wij zouden willen plaatsen op Twitter. De inhoud gaat nu vaak nog nergens over, is in het Engels en voor ons Nederlanders niet spannend, ook inhoudelijk vaag, maar toch. Denk nog eens vijf jaar verder, denk aan de nog grotere hoeveelheid data die over ons bekend is (en samengebracht kan worden), en de rekenkracht van computers zorgt er voor dat de inhoud van zo'n bericht vrij nauwkeurig overeenkomt met wat jij gezegd zou kunnen hebben.</p>
<p>Neem daarnaast de mogelijkheden van hologrammen, de technische vooruitgang op het gebied van 3D en projectie en het zo langzamerhand betaalbaar worden van die technologie. Combineer die beide en je hebt ineens een levend hologram aan wie je nog eens zou kunnen vragen hoe dingen zijn, wat hij of zij er van had gevonden.</p>
<p>Waanzinnig gaaf voor 'oude visionairs', Newton of Einstein had ik heel graag een keer een dialoog mee willen voeren. Prachtig, denkend aan de mensen die ik in het verleden ben verloren. Maar tegelijkertijd angstaanjagend. Willen we dit wel echt? Ook de dood heeft haar functie. Geïnspireerd door gedachtes van andere mensen een stap verder kunnen zetten, zelf een richting bepalen en voortbestaan in de herinnering.</p>
<p>Technische ontwikkelingen zullen altijd die twee kanten belichten. De positieve, en de negatieve. Ik ga in 99% van de gevallen uit dat techniek bijdraagt aan een beter, prettiger, handiger leven. Dit is die ene procent waar ik grote vraagtekens bij zet. En jij?</p>]]></content:encoded>
    </item>
    <item>
      <title>Junkweb</title>
      <link>https://casey.berlin/writings/2020/10/junkweb/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2020/10/junkweb/</guid>
      <pubDate>Thu, 01 Oct 2020 12:00:00 GMT</pubDate>
      <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">Wed, 25 Mar 2026 00:00:00 GMT</dc:date>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>social media</category>
      <category>instagram</category>
      <category>internet cultuur</category>
      <description><![CDATA[Instagram heeft meer mobiele gebruikers dan Twitter. Dat zegt wat — want afbeeldingen zijn doodlopende wegen op het web. Mooi, maar ook een beetje anti-internet.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<blockquote>
<p>Junkweb, oftewel al die dode eindes op internet. Waar internet in de oorsprong een serie gelinkte pagina's was die eigenlijk oneindig bleek, is dat met plaatjes niet zo. Die betekenen vaak het einde van die reis. Een blog over de opkomst van junkweb, mede mogelijk gemaakt door Instagram.</p>
</blockquote>
<p><a href="http://www.nu.nl/gadgets/2920699/instagram-verslaat-twitter.html">Gister werd bekend</a> dat Instagram (een tool waar ik overigens verschrikkelijk gek op ben) meer mobiele gebruikers heeft dan Twitter op maandelijkse basis. 7.3 miljoen tegenover 6.9 voor Twitter. Ik vraag me overigens af of dat echt puur en alleen voor de mobiele versie van de website gaat, of ook over apps, maar toch.</p>
<p>Het is een opvallende trend, dat we de mogelijkheid hebben op dit moment net zo makkelijk beeld met elkaar te delen, als dat vijf jaar geleden met de opkomst van tekst was via Twitter. 140 tekens spuien, of een plaatje van 800x800 pixels. Die resolutie is zelfs gestegen nog de afgelopen tijd, waardoor we zelfs een soort van 'HD' achtige plaatjes met elkaar delen inmiddels. Een 'snapshot' uit jouw omgevingswereld, een scheet van wat je beleefd, gevangen in beeld.</p>
<p>Diezelfde vijf jaar geleden stond ook in het teken van de opkomst van de 'quote van de dag', het 'inspirerende moment' of de 'les die ik jou wil leren'. De coaches sponnen er flink garen bij, althans, dat was de opvatting van hen die in dat vak zaten. Ik heb mijn hersenen altijd flink gebroken op de coaches en wat voor hen echt de toegevoegde waarde was van Twitter; naast de quotes die iedereen toch al deelde, nogmaals te delen.</p>
<p>Maar nu is daar instagram, dus ook die coaches kunnen weer aan de bak. Het kopiëren van een quote en die in een prachtig (uhum) font over een plaatje heen leggen en slim gebruik maken van de manier waarop we onze hersens gebruiken. Die slaan namelijk geen visuele beelden over, die 'lezen' dat altijd. Wat internet en SEO betreft; een plaatje is altijd 'the end of the road', het leidt ons naar nergens, het is niet via Google te indexeren, zoals tekst dat wel is. Het bestaat niet uit een verzameling links of verwijzingen, zoals een willekeurige site dat wel is. Een website is nooit het eindstation van je reis op internet. Een plaatje is geen wiki dat aan te passen is door andere mensen, nee het is een afbeelding. Het einde, de laatste halte. Er op klikken leidt ons (vaak) tot nergens, nee het zijn allemaal doodlopende wegen. Iets anti-internets eigenlijk.</p>
<p>Dat fenomeen van doodlopende wegen mag dus het 'junkweb' genoemd worden, althans als ik <a href="http://www.chrisbrogan.com/junkweb/">Chris Brogan mag geloven</a>. Ik lees graag zijn blogs, ook door de wat cynische toon van zijn verhalen.</p>
<p>Maar wat ik al eerder schreef, ik hou van het junkweb. Ik hou van de plaatjes en afbeeldingen, van een klein stukje emotie gevangen in een afbeelding. Iets wat ik vroeger zocht in de 140 tekens op Twitter; een mening, een emotie, iets persoonlijks. Om een conversatie over te starten. Om samen meer kennis mee op te bouwen en een netwerk te realiseren. Zo langzamerhand is die strijd om aandacht (wat eerst leuk was, is nu schreeuwen geworden op Twitter) verplaatst naar beeld. Want beelden geven direct aanleiding voor aandacht, een reactie of een like. Een afbeelding op instagram met 25-50 likes is geen uitzondering. Een tweet met dat aantal reacties of retweets tegenwoordig heel opmerkelijk.</p>
<p>Nou hoop ik dat niet elke gek (lees: coach) op instagram gaat zitten, en zeker niet om de hele dag quotes van bekende mensen te gaan posten met als achtergrond de zoveelste speeltuin of <a href="http://statigr.am/viewer.php#/tag/cloudporn/">#cloudporn</a>, maar daadwerkelijk iets toe te voegen. Iets wat ik wil delen, of gewoon gaaf vindt om te bekijken. Zo doet <a href="http://statigr.am/viewer.php#/user/15829184/">Vossen</a> dat heel goed, die notabene voornamelijk velgen maakt voor auto's. 200.000 volgers, en die delen alleen maar hele gave zaken. Plaatjes van door hun <a href="http://statigr.am/p/290044408173258065_15829184">getunede auto's</a>, door andere mensen <a href="http://statigr.am/p/288155468126315546_15829184">getunede auto's</a> met <a href="http://statigr.am/p/286833625796797752_15829184">hun velgen</a>, en lekkere wijven met mooie auto's natuurlijk (sorry dames).</p>
<p>Dat merk blijft bij mij hangen, creeert een beleving. Probeer dat als coach maar eens te benaderen…</p>
<p>Afbeeldingen zijn de nieuwe tweet geworden, inspiratie daadwerkelijk iets uit je eigen belevingswereld. Soms deel ik dat nog op Twitter of Facebook, maar ik doe dat met mate. En ik besteed veel aandacht aan de beelden en beleving van anderen op instagram, al ben ik daar ook al heel kritisch in aan het worden. Geen standaardwerk of overbewerkte foto's, ook liever geen professionele foto's. Hoe persoonlijker en dichterbij, hoe meer emotie voor mij en hoe prettiger. Net zoals je geen PR bureau je tweets laat schrijven, laat je ook je instagrams niet maken door anderen. Persoonlijk, prive, van jou. Jouw emotie. Zo wordt het junkweb, ineens heel waardevol.</p>
<p>Zojuist bedacht ik me de oplossing voor het junkweb. Als internet gaat herkennen wat we fotograferen kunnen we ineens wel links creeren en doorklikken. Een beetje zoals dat gaat met taggen op facebook. Geen dood einde meer, maar een begin. De berg hierboven op het plaatje klikbaar, de maker van de quote linksboven idem. Helaas moet Facebook gezichtsherkenning uit, maar die had dat goed in de gaten…</p>
<p>Overigens werd ik voor dit artikel ook geïnspireerd door de <a href="http://statigr.am/viewer.php#/tag/instagramwalk072/">#instagramwalk072</a>, afgelopen zondag in Alkmaar. Een heerlijke manier om een stad te ontdekken, zeker de moeite waard!</p>]]></content:encoded>
    </item>
    <item>
      <title>7 manieren waarop ik de ochtend goed begin</title>
      <link>https://casey.berlin/writings/2020/10/productieve-ochtend/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2020/10/productieve-ochtend/</guid>
      <pubDate>Thu, 01 Oct 2020 12:00:00 GMT</pubDate>
      <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">Wed, 25 Mar 2026 00:00:00 GMT</dc:date>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>productiviteit</category>
      <category>ochtend</category>
      <category>lifehacking</category>
      <category>ondernemerschap</category>
      <category>motivatie</category>
      <description><![CDATA[De ochtend is voor mij een van de meest productieve momenten van de dag. Op een nuchtere maag, een leeg hoofd en in een rustig huis. Vandaag 7 manieren waarop ik die ochtend goed begin.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<blockquote>
<p>Nog enigszins slaapdronken stap ik deze ochtend achter mijn computer. De weekenden zijn altijd weer lastig om terug te gaan naar je basisritme, zeker als zelfstandig ondernemer. Dat ene uurtje extra blijven liggen, ach, dat kan toch niet zo erg zijn? Toch is de ochtend voor mij een van de meest productieve momenten van de dag. Op een nuchtere maag, een leeg hoofd en in een rustig huis lekker aan de slag. Vandaag dus 7 manieren waarop ik de ochtend goed begin.</p>
</blockquote>
<p>Allereerst dan maar eens goed bepalen waarom je eigenlijk uit bed komt. <a href="http://lifehacker.com/5945221/the-science-behind-what-motivates-us-to-get-up-for-work-every-day">Dit artikel</a> op Lifehacker hielp me daarbij om dat eens goed vast te leggen.</p>
<p>Als het om werk gaat zijn er drie dingen die je stimuleren door te gaan in de functie waar je mee bezig bent en die je in ieder geval in je werk plezier, voldoening en enige vorm van geluk geeft, te weten:</p>
<ul>
<li><strong>Autonomie</strong> — Het gevoel dat ik zelf controle heb over wat ik doe en wil doen.</li>
<li><strong>Focus</strong> — Ergens heel erg goed in worden, je specialiseren, verder en meer leren, weten en kennen.</li>
<li><strong>Doel</strong> — Het gevoel hebben dat er een doel is, dat jij belangrijk bent. Dat je bijdraagt aan een doelstelling bedrijfsbreed.</li>
</ul>
<p><strong>Geld</strong></p>
<p>Deze persoonlijke doelstellingen zijn belangrijker dan geld, in welke vorm dan ook. Geld is maar een tijdelijk en kortstondig gevoel van geluk, deze drie zijn er altijd. Ook als het niet om geld draait, kom ik hier mijn bed voor uit. Ik kan uren en dagen besteden aan het optimaliseren van mijn website of het maken van een trailer voor een video, zonder me zorgen te maken over geld.</p>
<p>Dat geld niet het belangrijkste in de wereld is ondervind ik ook. Vaak gaat veel geld gepaard met drukte, verantwoordelijkheid en periodes van oneindig lang en veel werken. Geen enkele ondernemer wordt écht rijk (financieel) zonder hard werken. Tenzij je erg veel geluk hebt natuurlijk, maar daar zou ik als ondernemer niet op vertrouwen. Ik blij met mijn balans nu, qua werk, inspanning en resultaat. Dat nog altijd liever dan de 100 uur die ik in vorige jaren werkte met een iets hoger banksaldo. Daarnaast is het verstandig elk uur dat je in werk investeert, zo efficiënt en optimaal mogelijk besteedt.</p>
<p>Terug naar de ochtend. In ieder geval nadenken en weten dat deze drie onderdelen deel uitmaken van mijn dag doet me al goed. Ik weet dat ik vandaag precies ga doen wat ik wil, ik focus mij op mijn klanten, maar ook op kennis en ontwikkeling op het gebied van social media en social business. Heerlijk om daar samen ook mee aan de slag te kunnen.</p>
<p><strong>Tips</strong></p>
<p>En verder, een paar tips die voor mij de ochtend bepalen:</p>
<ol>
<li><strong>Begin vroeg</strong> — Voor een ieder is vroeg anders. Ik vind half acht vroeg genoeg, al werd dat vandaag half negen.</li>
<li><strong>Bepaal waar je focus ligt vandaag</strong> — Elke ochtend één duidelijke prioriteit.</li>
<li><strong>Fitness</strong> — Je fysieke toestand is net zo belangrijk als je geestelijke. Ik train 3x per week in de sportschool, in de ochtend. Ik krijg daar heerlijk veel energie van en blijf gezond.</li>
<li><strong>Eet gezond</strong> — Het is zo gemakkelijk niet te eten of ongezond te eten in de ochtend, terwijl je in 10 minuten een prima ontbijt (in mijn geval toast, ontbijtgranen of ei) op tafel kan zetten.</li>
<li><strong>Neem afscheid van je thuis</strong> — In mijn geval is dat nog even een knuffel in bed voor ik begin met werken in de andere kamer in huis, maar op dagen dat ik niet thuis ben ontbijten we samen en nemen we even de tijd voor elkaar. Werk én prive kun je in tijd wel scheiden, maar hebben absoluut een relatie met elkaar.</li>
<li><strong>Eat the frog</strong> — Het heerlijkst is om dat ene ding wat al dagen of weken op je takenlijst, nu eindelijk eens van die takenlijst af te strepen. Voor mij is dat de administratie, een heikel karwei wat ik heb uitbesteed, maar nog altijd energie kost. Bonnetjes bewaren, in een envelop stoppen, opsturen. Het is zo simpel, en toch laat ik het liggen. En ik ben vast niet de enige ;-)</li>
<li><strong>Blijf geïnformeerd</strong> — Ik lees de Nu.nl app even door voordat ik uit bed kom. Dat geeft wat context aan mijn leefwereld, zonder mezelf daar extreem door te laten beïnvloeden. Ook de sportsectie lees ik bijvoorbeeld en om de achterklap kan je ook niet heen. Prima informatie om lekker de ochtend mee te beginnen.</li>
</ol>
<p>Hopelijk kan je hier iets mee, maar ik ben ook benieuwd wat ik nog mis om mijn ochtend beter te beginnen. Heb jij tips? Laat het dan gerust weten!</p>
<p><em>Photo: Creative Commons; Flickr - Josef Grunig</em></p>]]></content:encoded>
    </item>
    <item>
      <title>10 productiviteitstips</title>
      <link>https://casey.berlin/writings/2020/10/productiviteitstips/</link>
      <guid isPermaLink="true">https://casey.berlin/writings/2020/10/productiviteitstips/</guid>
      <pubDate>Thu, 01 Oct 2020 12:00:00 GMT</pubDate>
      <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">Wed, 25 Mar 2026 00:00:00 GMT</dc:date>
      <author>mail@casey.berlin (Casey Romkes)</author>
      <category>productiviteit</category>
      <category>lifehacking</category>
      <category>time management</category>
      <category>focus</category>
      <category>ondernemerschap</category>
      <description><![CDATA[In deze tijd waarin zo ontzettend veel afleiding op de loer ligt, is het soms nodig om spelregels met jezelf af te spreken. Vandaag 10 van mijn eigen spelregels.]]></description>
      <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<blockquote>
<p>In deze tijd waarin zo ontzettend veel afleiding op de loer ligt, is het soms nodig om spelregels met jezelf af te spreken. Vandaag 10 van mijn eigen spelregels.</p>
</blockquote>
<p>Sinds ik de toegang heb tot een eigen computer, ben ik eigenlijk altijd bezig geweest met het sneller maken van dat ding. Kijken hoe ver ik kon gaan, wat soms leidde tot gekke situaties. Zo had ik ooit een watergekoelde computer, om er vooral voor te zorgen dat dat ding nog makkelijker zijn warmte kwijt kon en ik die dus kon opvoeren.</p>
<p>Sinds de computer sneller is geworden dan mijn hoofd kan denken, breek ik me daar in ieder geval niet meer over. De enige reden waarvoor je nog een nieuwere computer (mac) wil, zijn spelletjes. Over spelletjes ga ik later nog wel eens bloggen…</p>
<p>Terug naar de productiviteit, lifehacking eigenlijk. Want als het niet meer om de snelheid van de computer gaat, moet ik mezelf wel sneller maken.</p>
<ol>
<li>
<p><strong>Gebruik e-mail niet als takenlijst.</strong> E-mail is een communicatietool. Stop met dat gebruiken als 'inbox' voor je taken. Lees je e-mail maximaal drie keer per dag. Lees elke mail die binnenkomt maximaal twee keer. Bepaal direct de actie (taak) die je uit deze mail wilt halen, stop de mail weg in een goed terug te vinden map. Of print het als je dat handig vindt.</p>
</li>
<li>
<p><strong>Kies een tool die past bij jou als takenlijst.</strong> Ik hou het het liefst simpel, maar wel toegankelijk op meerdere apparaten. Things is dat voor mij, Toodledo een goede tweede. Pen en papier is ook een prima optie, misschien nog wel beter. Al synct dat wel wat lastig.</p>
</li>
<li>
<p><strong>Maak gebruik van die takenlijst.</strong> Alleen zo zorg je er voor dat het echt in je systeem komt. Alle taken die langer duren dan twee minuten schrijf je hier op. Duurt het korter dan twee minuten? Dan direct doen. Review regelmatig die takenlijst en pak er een aantal (maximaal twee, hoe weinig dat er ook lijken) uit die je vandaag gaat doen. De rest laat je liggen, blijft op die lijst staan. En vink ze af, een heerlijk gevoel! Dat gevoel werkt overigens beter op papier dan digitaal, dus een print maken is ook nog niet zo'n gek idee.</p>
</li>
<li>
<p><strong>Zorg voor ritme en je eigen rituelen.</strong> Ik schrijf het lekkerst op de vroege ochtend, nog voor het ontbijt. Dat is voor mij tussen 8 en 9 's ochtends. Daarnaast sport ik drie keer per week in de ochtend (na het ontbijt) en dankzij de Olympische Spelen heb ik een vast moment waarop ik de computer uit zet, en sport ga kijken. Dat soort rituelen helpen je lijf en geest aan ritme. Dat ritme zorgt voor minder stress om steeds te moeten veranderen.</p>
</li>
<li>
<p><strong>Zorg voor een prettige werkplek.</strong> Ik heb een 'clean desk policy' en probeer zo minimaal mogelijk te werken. Zo kan ik mij concentreren op mijn werk, niet op alles wat me afleid. Het liefst één scherm, een groot stuk papier, een pen, een lamp en dat is het wel. Alleen zo kan ik écht optimaal werken. Alles wat niet direct nodig is, houd ik buiten handbereik.</p>
</li>
<li>
<p><strong>Multitasken werkt niet.</strong> Ik gebruik de pomodoro techniek om mezelf continu gefocussed te houden op één taak die voor me ligt. Alhoewel vrouwen makkelijker zijn in het omschakelen naar andere taken dan mannen, geldt ook voor hen dat continu wisselen, opnieuw focussen en starten erg moeilijk is en veel energie kost. Vandaar, focus. 25 Minuten op één taak gericht. Dat lijkt makkelijk, maar probeer het maar eens. Sluit al die andere schermen op je computer, zet de TV uit. Wees eens 100% bij de taak voor handen.</p>
</li>
<li>
<p><strong>Wees flexibel.</strong> Vanochtend werd mijn routine bruut verstoord door de bezorging van onze tuinset. Leuk natuurlijk, maar dat zorgt er wel voor dat deze blog pas na 10 uur gepubliceerd werd. Dat is dan niet anders, en zo moet je ook met je routine omgaan. Wees voorbereid op onderbreking. Maar zorg er wel voor dat je dat bij jezelf niet doet. Geen twitter, facebook of andere afleidingen dus. En doe je deur dicht als je echt niet afgeleid wil worden. Of hang een sticky note op je cubicle. Een koptelefoon werkt ook goed.</p>
</li>
<li>
<p><strong>Neem voldoende rust.</strong> De computer en informatiewereld zorgen er nog wel eens voor dat je hoofd letterlijk vol voelt. De enige oplossing daarvoor is rust. Iets doen wat niet teveel vergt van je hersenen. Een boek lezen, een tijdschrift, even voor de TV hangen, of gewoon een klein uurtje slapen. Dat zorgt er voor dat je gedurende de dag je energie kunt houden.</p>
</li>
<li>
<p><strong>Leef gezond.</strong> De houding en de manier waarop we leven achter het beeldscherm blijkt erg ongezond. Vaak wordt er ook verwezen naar de mogelijkheden van staand werken. Sowieso denk ik al beter lopend, maar staand werken overweeg ik ook nog eens te proberen. Daarnaast is goed, gevarieerd en regelmatig eten én goed bewegen nodig om je energie goed te kunnen doseren en de hele dag normaal te kunnen werken.</p>
</li>
<li>
<p><strong>Heb een beetje lol in je leven.</strong> We vergeten nog wel eens te genieten van wat we doen. Ik heb de luxe veel vrijheid te hebben als zelfstandig ondernemer, ik kan dus zelf bepalen waar en wanneer ik werk. Vorige week nog op Texel bijvoorbeeld, en een dag vrij met mijn verjaardag aanstaande maandag is ook geen probleem. Ik weet alleen wel dat ik al mijn taken op mijn lijstje af moet werken, dus plan ik elke dag opnieuw. Maar ik probeer wel elke dag lol te hebben. Al is het maar genoeg rust om te lunchen, of even een film te kijken. Ook Youtube is daar een prima medium voor.</p>
</li>
</ol>
<p>Zo zijn er nog genoeg tips te bedenken, maar ik ben vooral benieuwd naar hoe jij omgaat met informatie, tijdsindeling en jezelf.</p>
<p><em>Photo: Creative Commons / Flickr; Katsrcool</em></p>]]></content:encoded>
    </item>
  </channel>
</rss>