<?xml version="1.0" encoding="UTF-8"?><rss 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" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Willem van Ketwich on Medium]]></title>
        <description><![CDATA[Stories by Willem van Ketwich on Medium]]></description>
        <link>https://medium.com/@wvk?source=rss-d970ec8e6a8a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*8qao5Tbu12n13_ltd8_uAg.jpeg</url>
            <title>Stories by Willem van Ketwich on Medium</title>
            <link>https://medium.com/@wvk?source=rss-d970ec8e6a8a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 18:18:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@wvk/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Political Architect: Understanding Power, People, and Patterns in the Enterprise (with a…]]></title>
            <link>https://medium.com/@wvk/the-political-architect-understanding-power-people-and-patterns-in-the-enterprise-with-a-087e131d05b8?source=rss-d970ec8e6a8a------2</link>
            <guid isPermaLink="false">https://medium.com/p/087e131d05b8</guid>
            <dc:creator><![CDATA[Willem van Ketwich]]></dc:creator>
            <pubDate>Fri, 16 May 2025 07:26:20 GMT</pubDate>
            <atom:updated>2025-05-16T07:26:20.640Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Political Architect: Understanding Power, People, and Patterns in the Enterprise (with a Little Help from AI)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eVtMOJlfSI1LIox9YsxySw.jpeg" /></figure><p>In many ways, the role of an architect in an enterprise isn’t just to make technical decisions — it’s to influence change in systems made of people, politics, and power. The hard part? None of that is in the documentation.</p><p>You can design the cleanest architecture diagram, choose the most elegant solution, and still hit a wall — because an executive sponsor changed priorities, a mid-level manager is quietly resistant, or a senior engineer is emotionally attached to a legacy system.</p><p>That’s where being a <strong>political architect</strong> comes in. And increasingly, it’s where tools like <strong>ChatGPT</strong> are becoming surprisingly useful.</p><h3>Architecture Exists Within Power Structures</h3><p>Most of us start with a belief that the best idea should win. But in practice, architecture is shaped by:</p><ul><li>Who has budget control</li><li>Which teams are trusted</li><li>Legacy technology decisions made years ago</li><li>Organisational inertia</li></ul><p>There’s the <strong>formal org chart</strong>, and then there’s the <strong>real influence map</strong>.</p><p>Good architects learn to navigate both. In one project, I remember pushing a secure-by-default cloud architecture. It had everything — compliance, scalability, cost-efficiency. But I hadn’t considered how threatened the internal network team would feel. They weren’t consulted early, and they stalled the rollout. It was a political misstep, not a technical one.</p><blockquote><strong><em>With ChatGPT:</em></strong><em> You can simulate conversations with different stakeholders, explore their motivations, and rehearse your messaging before going in cold. I’ve used it to roleplay scenarios or prepare language that lands with execs, engineers, or security leads alike.</em></blockquote><h3>Patterns of Influence: Who Really Decides?</h3><p>Organisations often appear consensus-driven on the surface, but real decisions are made by:</p><ul><li>The <strong>shadow sponsor</strong>: someone unofficial but influential</li><li>The <strong>skeptic</strong>: who doesn’t say no, but slows everything down</li><li>The <strong>hidden decider</strong>: a quiet senior person whose opinion trumps all</li></ul><p>Spotting these patterns early is key. Influence isn’t always tied to title. Sometimes a principal engineer carries more weight than a VP because they’re the go-to person for real answers.</p><blockquote><strong><em>With ChatGPT:</em></strong><em> Try prompting it with “how do I uncover the real influencers in a meeting where the org chart doesn’t tell the whole story?” or “what are signs someone is a silent decision-maker?” The insights are a great way to sharpen your awareness going into stakeholder sessions.</em></blockquote><h3>The Hidden Risk: Technical Authority Without Architectural Range</h3><p>One of the most persistent (and under-addressed) challenges is when technically strong individuals — who are brilliant coders, troubleshooters, or system maintainers — exert <strong>outsized architectural influence</strong> without a deep understanding of architectural tradeoffs or patterns.</p><p>Their opinions often carry weight due to tenure, delivery speed, or deep domain familiarity. But without broader exposure to cross-cutting concerns like scalability, resilience, cost models, or organisational change, their technical preferences can steer decisions in a narrow direction — and that’s a governance risk.</p><blockquote><em>I’ve seen monoliths rebuilt as distributed monoliths because someone read about microservices but didn’t grasp service boundaries, observability, or data ownership patterns. I’ve also seen serverless rejected wholesale by someone worried about cold starts — in a batch processing pipeline.</em></blockquote><p>Technical expertise is essential. But <strong>architectural range</strong> — the ability to think in tradeoffs, to evaluate alternatives in context, to know when not to use a pattern — is what makes the difference between local optimisation and system-level improvement.</p><blockquote><strong><em>With ChatGPT:</em></strong><em> I’ve used GPT to introduce these colleagues to patterns gently: “What are the tradeoffs of microservices in a low-maturity engineering org?” or “Explain event-driven architecture for someone used to REST APIs.” It’s a low-friction way to expand thinking without confrontation.</em></blockquote><h3>Language, Framing, and Strategic Alignment</h3><p>If you want to get buy-in, stop talking about services and start talking about outcomes.</p><p>Framing an architecture decision around <strong>cost reduction</strong>, <strong>risk mitigation</strong>, or <strong>speed to market</strong> is much more effective than talking about container orchestration or database choices.</p><p>One mental model I use is: <em>What would this look like in a boardroom deck?</em></p><blockquote><strong><em>With ChatGPT:</em></strong><em> I often paste my architecture notes into a prompt and ask it to:<br>- </em>Summarise it in business language<br>- Reframe it as a one-pager for an executive<br>- Draft stakeholder-specific messaging (e.g., “explain this to a CISO vs. a product owner”)</blockquote><p>It’s like having a sparring partner to stress-test your message before the real conversation.</p><h3>Playing the Long Game: Trust, Timing, and Tradeoffs</h3><p>Influencing change is about timing and trust. Sometimes you <em>know</em> the org isn’t ready — not technically, but emotionally or politically.</p><p>Pushing too hard leads to rejection. Waiting too long misses the moment. The art is in recognising what tradeoffs are acceptable now to enable a better foundation later.</p><p>In one organisation, I spent months quietly building relationships before proposing a significant platform change. By the time I pitched it, the champions were already in place.</p><blockquote><strong><em>With ChatGPT:</em></strong><em> I’ve found it useful to write “retrospective-style” prompts to unpack what worked, what didn’t, and what I could’ve done differently in similar scenarios. It helps refine the approach for next time.</em></blockquote><h3>Becoming a Political Architect Without Losing Integrity</h3><p>There’s a line between navigating politics and becoming political in a negative sense.</p><p>Integrity matters. The most effective architects I’ve seen are trusted not just for their technical insight, but for their consistency, empathy, and fairness. They know when to compromise and when to hold the line.</p><p>My advice to myself (and others): Be political, but not manipulative. Be strategic, but not opaque. Let your values shape your influence, not the other way around.</p><blockquote><strong><em>With ChatGPT:</em></strong><em> You can explore ethical dilemmas through “what if” scenarios or write out your personal architectural principles and ask GPT to challenge them. It’s a surprisingly good sounding board for refining your professional compass.</em></blockquote><h3>In Closing</h3><p>Organisations are complex systems, and architecture is as much about people as it is about platforms.</p><p>If you want to be effective, you can’t just design the system — you have to design <strong>for</strong> the system. Learn how influence works. Pay attention to the culture. Understand the motivations behind resistance. And use every tool you can — including AI — to enhance your awareness, articulation, and empathy.</p><p>Because great architecture doesn’t just live in code. It lives in relationships, trust, and timing.</p><p><strong>If this resonates with you — whether you’re an architect, engineer, or change agent — follow along. I’ll be sharing more practical insights on navigating the messy, human side of architecture in the real world.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=087e131d05b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Architecting the Organisation]]></title>
            <link>https://medium.com/@wvk/architecting-the-organisation-20495996251c?source=rss-d970ec8e6a8a------2</link>
            <guid isPermaLink="false">https://medium.com/p/20495996251c</guid>
            <category><![CDATA[enterprise]]></category>
            <category><![CDATA[architecture]]></category>
            <dc:creator><![CDATA[Willem van Ketwich]]></dc:creator>
            <pubDate>Sun, 15 Jan 2023 09:47:57 GMT</pubDate>
            <atom:updated>2023-01-15T09:47:57.679Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eV-IZ7csOYSs-TbOoXyaLg.png" /><figcaption>The organisation is like a living building in many ways.</figcaption></figure><h3>Hello</h3><p>Hello, this is a first post from me on the topic of Architecture, Change, Governance, Culture and many other areas within organisations.</p><p>It will be a forum and debrief for my observations around what I see that good and bad look like, how to effect change and how to work within the existing structures and channels to achieve organisational objectives.</p><h3>Motivation</h3><p>In my current role, I work across the organisation, with stakeholders and teams in order to help them achieve goals and targets faster. This has been everything from security to cloud migration, from patterns and practices to strategic shaping and everything in-between.</p><p>Having seen and worked across many organisations, there are some obvious and some less obvious approaches to architecting the organisation I feel work better than others.</p><p>Everything is contextual, however, and so what I have seen work in some organisations may not work in others. There are always tradeoffs — time, cost, technology preference, capability, and many other factors.</p><h3>Culture</h3><p>I am fascinated by people — how they come together, how they interact, what motivates them and the decisions they make within the organisational context. There is a strong bias in my analysis towards the psychology, dynamics and politics that are often at play.</p><p>This is a deep topic and I look forward to venturing into it in more detail. It defines everything from leadership down to high-performing teams, staff longevity and ultimately Return on Investment to shareholders.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=20495996251c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>