<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Systems-Thinking on Roethof.Net</title><link>https://roethof.net/tags/systems-thinking/</link><description>Recent content in Systems-Thinking on Roethof.Net</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>ronny@roethof.net (Ronny Roethof)</managingEditor><webMaster>ronny@roethof.net (Ronny Roethof)</webMaster><copyright>© 2026 Ronny Roethof</copyright><lastBuildDate>Sat, 13 Jun 2026 06:29:24 +0200</lastBuildDate><atom:link href="https://roethof.net/tags/systems-thinking/index.xml" rel="self" type="application/rss+xml"/><item><title>The RTO Charade: A Systemic Engineering Failure</title><link>https://roethof.net/posts/2026/06/the-rto-charade-a-systemic-engineering-failure/</link><pubDate>Fri, 12 Jun 2026 00:00:00 +0200</pubDate><author>ronny@roethof.net (Ronny Roethof)</author><guid>https://roethof.net/posts/2026/06/the-rto-charade-a-systemic-engineering-failure/</guid><description>Return-to-office mandates are a systemic failure. Treating human infrastructure with the same flawed logic as bad server maintenance is why IT is burning out.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://roethof.net/posts/2026/06/the-rto-charade-a-systemic-engineering-failure/cover.png"/></item></channel></rss>