hebel. today · 10 November 202623 / 74

Career · Product Management Evolution

Glean shifts product metrics from feature volume to organizational intelligence

Emrecan Dogan, Chief Product Officer at Glean, manages a product organization where the correlation between shipping volume and value creation has weakened in the AI era. Instead of tracking feature output, Glean uses its…

Emrecan Dogan, Chief Product Officer at Glean, manages a product organization where the correlation between shipping volume and value creation has weakened in the AI era (SC Moatti from Products That Count). Instead of tracking feature output, Glean uses its own AI platform to monitor organizational intelligence in real time, replacing manual status reporting and preparing for one-on-ones through automated progress tracking (SC Moatti from Products That Count). This approach treats the product organization as a laboratory for systems thinking, where fixing a bottleneck moves the constraint elsewhere rather than eliminating it.

Glean maintains enterprise predictability alongside frontier-speed shipping by decentralizing decision-making, where team members take autonomy rather than waiting for it to be granted. This shift mirrors broader trends in AI-native product management, where the primary constraint moves from engineering capacity to the quality of human judgment and the design of work processes (Ops Forward). As Paula Goldman notes, effective AI adoption requires moving from individual output metrics to managing how work happens between people, with teams acting as a unified organism rather than a collection of efficient individuals (Untangled with Charley Johnson Your…).

IKEA successfully retrained 8,500 workers after a chatbot replaced their previous roles, resulting in the company’s fastest growth in remote sales (Hands-on Agile by Stefan Wolpers AI…). Peec AI updated descriptions on 15 of 60 YouTube videos, which led to a 359% increase in daily AI retrievals compared to 17% for unchanged content (TLDR Marketing).

Try today · 30 min

Audit your current product constraints to distinguish between capability, governance, and work design gaps.

Identify one stalled project and ask 'why' twice to find the root cause.

You need

  • Project list
  • Constraint worksheet

Steps

  1. List three current product constraints.
  2. Ask 'what is causing this' for each constraint.
  3. Ask 'why' again for the answer to identify the true root cause.
  4. Tag each constraint as a capability, governance, or work design gap.
  5. Rank the three constraints by potential 90-day impact.
  6. Write a one-sentence justification for the highest-ranked constraint.

One email instead of your newsletter pile.

Forward the newsletters you already get (a Gmail filter does it) and tell Hebel your goals. Every morning it reads them with 20,000 others and sends one short email, with one small thing to do today. Fewer emails, not more. Free during beta.

Start my paper →
LinkedIn X

Sources

  1. SC Moatti, Products That Count on hebel. → ✎ Written by a personEmrecan Dogan explains why feature shipping volume is a weak proxy for value in AI-native product organizations.

  2. Ops Forward on hebel. →Zheng argues that AI shifts the product management constraint from execution capacity to decision-making and problem definition.

  3. Hands-on Agile by Stefan Wolpers AI… on hebel. →This newsletter tracks industry news, including IKEA's successful retraining of 8,500 workers after chatbot implementation.

  4. Untangled with Charley Johnson Your… on hebel. →Paula Goldman discusses why AI adoption metrics must focus on team dynamics and group patterns instead of individual output.

  5. TLDR Marketing on hebel. →A Peec AI experiment demonstrates how structured YouTube descriptions drive a 359% increase in AI search retrievals.

More in Career

Protecting the creative core from digital drift

Niche communities beat general networking

When managers stop providing answers

Build reputation through quiet reliability or aggressive digital curation

T-shaped expertise versus problem-focused repositioning

Product Management Evolution yesterday

Product teams shift from token-heavy experiments to evidence-based workflows

Sign in to Hebel first

Likes, your collection and done Hebel need an account. We email you a six digit code; no password.