<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Product on sofiakodar.github.io</title><link>https://sofiakodar.github.io/tags/product/</link><description>Recent content in Product on sofiakodar.github.io</description><generator>Hugo -- 0.161.1</generator><language>en</language><lastBuildDate>Thu, 30 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://sofiakodar.github.io/tags/product/index.xml" rel="self" type="application/rss+xml"/><item><title>Speed vs stability: the divide between product and engineering</title><link>https://sofiakodar.github.io/posts/senseofurgency/</link><pubDate>Thu, 30 Apr 2026 00:00:00 +0000</pubDate><guid>https://sofiakodar.github.io/posts/senseofurgency/</guid><description>&lt;h2 id="the-urgency-gap"&gt;The urgency gap&lt;/h2&gt;
&lt;p&gt;Over the last few months, I’ve sat across from product leaders and engineers in different companies and they all told me the same story: a frustration from product managers and the leadship team about lack of urgency in dev teams and whether they truly care about the company’s success.&lt;/p&gt;
&lt;p&gt;Product leaders and managers are super eager to deliver new features and to fulfill commitments to customers, but feel that the development teams are slow and don’t care if a feature gets pushed. &lt;em&gt;“Why don’t the engineers feel a sense of urgency? They don’t care if a feature gets delayed for weeks!” “It feels like they don’t care about the success of the company!”&lt;/em&gt;.&lt;/p&gt;</description></item></channel></rss>