<?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://10d532f8.blog-6cm.pages.dev/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://10d532f8.blog-6cm.pages.dev/architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>Workplace capability model</title><link>https://10d532f8.blog-6cm.pages.dev/architecture/capability-model/</link><pubDate>Thu, 12 Nov 2026 00:00:00 +0000</pubDate><guid>https://10d532f8.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></channel></rss>