<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Tanuja Hegde on Medium]]></title>
        <description><![CDATA[Stories by Tanuja Hegde on Medium]]></description>
        <link>https://medium.com/@hegde.tanu0306?source=rss-094de53999e2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*-tQruEXDyQrCLCJ1IHe6tQ.jpeg</url>
            <title>Stories by Tanuja Hegde on Medium</title>
            <link>https://medium.com/@hegde.tanu0306?source=rss-094de53999e2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 03:12:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hegde.tanu0306/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Engagement ≠ Value — My learnings from Meta Settlement as a Product Manager]]></title>
            <link>https://medium.com/@hegde.tanu0306/engagement-value-my-learnings-from-meta-settlement-as-a-product-manager-5bb1f580b320?source=rss-094de53999e2------2</link>
            <guid isPermaLink="false">https://medium.com/p/5bb1f580b320</guid>
            <category><![CDATA[ethics-and-engageemnt]]></category>
            <category><![CDATA[values]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[value-proposition]]></category>
            <category><![CDATA[customer-centricity]]></category>
            <dc:creator><![CDATA[Tanuja Hegde]]></dc:creator>
            <pubDate>Sun, 11 Oct 2026 15:33:45 GMT</pubDate>
            <atom:updated>2026-10-11T15:33:45.841Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wMttzb0tyYMxw3FPvn4_Eg.png" /></figure><p>Meta’s landmark $18 billion settlement with state attorneys general marked a major turning point for the tech industry. The lawsuit alleged that Meta intentionally built addictive product features — like infinite scroll and algorithmic feeds — that harmed young users’ mental health while failing to protect their privacy.</p><p>Beyond the financial penalty, Meta agreed to major structural changes: default daily screen time limits, nighttime feed blocks, and muted push notifications during school hours. <em>(Full news article linked in reference)</em></p><p>As a Product Manager, this news raised an immediate question for me: Where did the gap open between product value proposition and the metrics we track?</p><p>When we celebrate surging DAUs, higher session frequencies, and notification open rates, are we measuring genuine user value — or just engagement? Here are my key learnings on why Engagement ≠Value and how we can build more customer-centric products.</p><p><strong>1. Value Proposition</strong></p><p><strong>The fundamental question to ask is, “what value are we promising to create for the customer”</strong></p><p>Meta’s mission is to <strong>“give people the power to build community and bring the world closer together.”</strong><br> For Facebook, that value can include connecting with friends and family, finding communities, expressing yourself and building businesses.<br> Instagram has evolved around similar themes — connection, creativity, self-expression, discovery, entertainment and community. These are compelling value propositions. People reconnect with friends. Creators find audiences. Small businesses reach customers. People discover communities around interests they care about.<br> Artists showcase their work. Users find entertainment, information and inspiration.</p><p>So, the question isn’t:<br> “Does Instagram or Facebook create customer value?”<br> Clearly, they do.<br> The more interesting question is:<br> <strong>“Is the value delivered to the customer always proportional to the engagement generated by the product?”<br> </strong><br> And that distinction matters.</p><p><strong>2. Engagement is not the same as value</strong></p><p>Imagine as a Product Manager looking at a dashboard:<br><strong> </strong><em>• Daily active users are increasing.<br> • Session frequency is increasing.<br> • Average time spent is increasing.<br> • Retention is increasing.<br> • Notifications are being opened.<br> • Users are consuming more content.</em><br> The dashboard looks fantastic. But what does it actually tell us? It tells us that people are using the product. It doesn’t necessarily tell us that people are getting more value from the product.</p><p>A teenager spending three hours scrolling through Instagram may represent extremely high engagement. But it doesn’t automatically mean three hours of customer value.<br> Perhaps the teenager came to:<br> <strong>Connect with friends →<br> </strong>and ended up:<br> <strong>Scrolling → Comparing → Consuming recommendations → Reopening the app → Scrolling again.<br> </strong>The product has successfully generated engagement. But did it successfully solve the customer’s problem?<br> That’s the distinction I think Product Managers need to pay attention to. Customer activity is an observable behaviors. Customer value is an outcome. And the two can diverge.</p><p><strong>3. The metric we choose shapes the product we build</strong></p><p>Suppose a team is given this objective: “Increase average daily time spent by 20%.”<br> The team will naturally look for ways to achieve it.</p><p><em>Better recommendations.<br> More personalized feeds<br> Autoplay.<br> Infinite scrolling.<br> Notifications.<br> More content.<br> More frequent re-engagement.</em><br> <br> All these methods, they are not bad, but they can create a product that becomes extremely good at capturing attention. Now, if change the objective, imagine the team is instead asked:<br> “Increase meaningful social connections while maintaining healthy usage.” The product decisions might be very different.<br> <br> We might optimize for:<br> <br><em> • meaningful conversations<br> • content relevance<br> • user satisfaction<br> • quality of interactions<br> • user control<br> • healthy session patterns</em></p><p>The lesson is simple:<br> What we measure influences what we optimize. And what we optimize eventually influences what we build.</p><p><strong>4. What does the customer actually hire the product to do?</strong></p><p>This is where the <strong>Jobs-to-be-Done</strong> perspective becomes useful.<br> A teenager may “hire” Instagram to:<br><em> • stay connected with friends<br> • understand what’s happening in their social circle<br> • express themselves<br> • discover content<br> • find communities<br> • be entertained</em><br> <br> They aren’t necessarily hiring Instagram to: <strong>“Keep me on platform for as long as possible.” </strong>That may be the outcome of the product’s optimization — not the customer’s original job. This raises an uncomfortable Product Management question:<br> <strong>“Have we optimized the product around the customer’s job, or around a metric that benefits the business?”</strong><br> The answer doesn’t have to be one or the other. A healthy product needs both.</p><p><strong>5. Customer value and business value are not the same thing</strong></p><p>Meta operates a particularly interesting business model because there is a relationship between user engagement and advertising value. Users receive services without directly paying for them. Advertisers pay to reach those audiences. So, there is a legitimate value exchange:<br> Users give their time, attention and data. Meta provides connection, communication, discovery and entertainment. Advertisers pay to reach relevant audiences. That model can work extremely well. The Product Management challenge arises when the optimization for one side of the value equation starts creating problems for another.<br> <br> For example:<br> More attention can create more advertising opportunities.<br> But:<br> More attention isn’t automatically more customer value. This doesn’t mean that maximizing engagement is inherently wrong. It means engagement is a proxy.</p><p><strong>6. The role of customer empathy</strong></p><p>This brings me back to something we often hear in Product Management:<br> “We need to be customer centric.” But what does customer-centric actually mean?<br> It can’t simply mean conducting user research, creating personas and putting customer quotes into a presentation. True customer empathy should influence product decisions. When you are empathetic to customers, it should help you to build the relationship, not break the one you already have.</p><p>Consider a teenager using a social media platform.<br> The PM needs to understand more than:<br> <br> <em>Age: 13–17<br> Likes: Music, sports, influencers</em><br> <br> The team also needs to understand the context:<br> <br><em> • social pressure<br> • peer validation<br> • comparison<br> • sensitivity to social feedback<br> • difficulty recognizing when engagement has become excessive</em></p><p>That context should influence product design. And this leads to an important distinction: Empathy is not just understanding the customer. Empathy is allowing that understanding to change what we build.</p><p><strong>7. The bigger Product Management lesson</strong></p><p>I don’t think the lesson from the Meta situation is: “Engagement is bad.”<br> Nor is it:<br> “Companies shouldn’t optimize engagement.”<br><em> Engagement matters.<br> Retention matters.<br> Business outcomes matter.<br> Revenue matters.</em></p><p>But the bigger lesson may be:<br> <strong>Engagement should be treated as a means of delivering customer value — not automatically as a substitute for customer value.</strong></p><p>A product can be highly engaging and highly valuable. But it can also be highly engaging while creating unintended consequences.<br> <br> The Product Manager’s responsibility is to understand the difference.</p><p><strong>8</strong>.<strong> Questions I would carry forward as a Product Manager</strong></p><p>1. <strong>The Outcome</strong>: What real-world customer value are we creating? Are we just triggering a behavior ? What is the Jobs-to-be-done?</p><p>2. <strong>The Proxy</strong>: Are our metrics good proxies for that outcome? If the answer is no, we may be optimizing the wrong thing.</p><p>3. <strong>The incentive</strong>: What behaviors are our metrics incentivizing?</p><p>4. <strong>The Scale</strong>: What happens if we succeed beyond our expectations?<br> Because sometimes the unintended consequences of success can become the biggest product problem.</p><p><strong>Conclusion:</strong><br> <br> <strong>What Does True Customer-Centricity Mean?</strong></p><p>For me, this is the core lesson of the Meta settlement.</p><p>Customer-centricity isn’t a high NPS score, an escalating retention curve, or an impressive engagement metric. It isn’t about how long we can keep someone’s eyes on a screen.</p><p>True customer-centricity means continuously asking one uncomfortable question:</p><p><strong>“Are we still delivering the value we promised, or are we just capturing attention?”</strong></p><p>As products scale and integrate into daily life, the line between engagement and value can easily blur. Our responsibility as Product Managers is to ensure we don’t lose sight of the difference.</p><p>We shouldn’t just build products people want to use — we must build products that enrich their lives when they do.</p><p><strong>Engagement tells us that people are using our product. Value tells us why they should.</strong></p><p><strong><em>News Reference:</em></strong></p><p><a href="https://edition.cnn.com/2026/08/26/tech/meta-states-settle-trial-children">Meta settles landmark state child harm claims for $18 billion and promises changes to its platforms | CNN Business</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5bb1f580b320" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>