<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Architecture on Phillip Büchler</title><link>https://9fbf16cc.blog-6cm.pages.dev/categories/architecture/</link><description>Recent content in Architecture on Phillip Büchler</description><generator>Hugo</generator><language>en</language><copyright>&amp;copy; 2022 &lt;a href="https://philipbuechler.ch/"&gt;Fime&lt;/a&gt;</copyright><lastBuildDate>Thu, 12 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://9fbf16cc.blog-6cm.pages.dev/categories/architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>Workplace capability model</title><link>https://9fbf16cc.blog-6cm.pages.dev/architecture/capability-model/</link><pubDate>Thu, 12 Nov 2026 00:00:00 +0000</pubDate><guid>https://9fbf16cc.blog-6cm.pages.dev/architecture/capability-model/</guid><description>&lt;p&gt;The model lists what a digital workplace has to deliver, in three layers: work surfaces (what people use), access and endpoints (where people work) and the control plane (what keeps it running and under control). Business applications sit outside the boundary and connect through identity.&lt;/p&gt;
&lt;p&gt;The capabilities are vendor-neutral. The interactive version puts one product overlay on top, a Microsoft-centric estate, plus three lenses. It leaves out business applications, cost figures and any recommendation for a provider.&lt;/p&gt;</description></item><item><title>Sovereign Workplace</title><link>https://9fbf16cc.blog-6cm.pages.dev/sovereign-workplace/</link><pubDate>Fri, 06 Nov 2026 00:00:00 +0000</pubDate><guid>https://9fbf16cc.blog-6cm.pages.dev/sovereign-workplace/</guid><description>&lt;aside class="ek-alert" role="note"&gt;&lt;p&gt;This is my personal blog. At the time of writing, I work for a Microsoft partner in Switzerland but I&amp;rsquo;m not involved in its sovereignty offerings, and nothing here is a recommendation for a provider.&lt;/p&gt;
&lt;/aside&gt;

&lt;p&gt;For years I was a firm believer in the cloud-based Microsoft 365 workplace, and I bet a good part of my career on it. Digital sovereignty looked like a theoretical exercise that no real organisation could afford.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;m less sure now. Things we took for granted are being questioned, and I&amp;rsquo;m still working out what that means for the workplaces I help build. I have nothing useful to add to the geopolitical commentary.&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt; What I can do is help untangle the Microsoft 365 dependencies most organisations are tied into.&lt;/p&gt;</description></item><item><title>The AI Adoption Chasm</title><link>https://9fbf16cc.blog-6cm.pages.dev/posts/ai-adoption-chasm/</link><pubDate>Tue, 29 Sep 2026 00:00:00 +0000</pubDate><guid>https://9fbf16cc.blog-6cm.pages.dev/posts/ai-adoption-chasm/</guid><description>&lt;p&gt;Upload your CV. Now type your name, address, employment history, education and qualifications into the text boxes below.&lt;/p&gt;
&lt;p&gt;The company already has that information, but its recruitment system can&amp;rsquo;t reliably map your document onto the structure its process requires. So the applicant becomes the integration layer. You read your own CV, reconcile terminology, reformat dates and fit your experience into categories the vendor chose. The form was digitised, not removed.&lt;/p&gt;
&lt;p&gt;Most enterprise AI adoption stalls at the same point.&lt;/p&gt;</description></item></channel></rss>