<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Delegation on Pierre-Henry Soria – CTO Insights, Software Architecture &amp; Product Leadership</title><link>https://blog.pierrehenry.be/tags/delegation/</link><description>Recent content in Delegation on Pierre-Henry Soria – CTO Insights, Software Architecture &amp; Product Leadership</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright © 2026, Pierre-Henry Soria.</copyright><lastBuildDate>Sat, 26 Aug 2017 10:10:00 +0200</lastBuildDate><atom:link href="https://blog.pierrehenry.be/tags/delegation/index.xml" rel="self" type="application/rss+xml"/><item><title>Why I Document a Process Before I Automate It</title><link>https://blog.pierrehenry.be/blog/why-i-document-a-process-before-i-automate-it/</link><pubDate>Sat, 26 Aug 2017 10:10:00 +0200</pubDate><guid>https://blog.pierrehenry.be/blog/why-i-document-a-process-before-i-automate-it/</guid><description>Automating work that is poorly understood repeats its mistakes faster. A tested procedure reveals the decisions, exceptions, and controls first.</description></item></channel></rss>