<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Feature Creep on blog.pierrehenry.be</title><link>https://blog.pierrehenry.be/tags/feature-creep/</link><description>Recent content in Feature Creep on blog.pierrehenry.be</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright © 2026, Pierre-Henry Soria.</copyright><lastBuildDate>Tue, 30 Dec 2025 10:31:38 +0000</lastBuildDate><atom:link href="https://blog.pierrehenry.be/tags/feature-creep/index.xml" rel="self" type="application/rss+xml"/><item><title>Ship Perfect Products or Lose Users to Feature Overload</title><link>https://blog.pierrehenry.be/blog/ship-perfect-products-or-lose-users-to-feature-overload/</link><pubDate>Tue, 30 Dec 2025 10:31:38 +0000</pubDate><guid>https://blog.pierrehenry.be/blog/ship-perfect-products-or-lose-users-to-feature-overload/</guid><description>Let’s talk about a trap I see a lot of dev teams fall into: building out every possible feature just to check boxes, instead of actually solving the problems users care about. I’ve been there. You&amp;hellip;</description></item></channel></rss>