WHY UX SHOULD OWN RETENTION
UX should own retention because churn often starts with a broken customer experience. By improving onboarding, support, renewals, and upgrades, UX teams can protect revenue and prove their strategic value.
Full-text search across article titles and summaries. Refine with sector, year, content type, and reading-time filters.
UX should own retention because churn often starts with a broken customer experience. By improving onboarding, support, renewals, and upgrades, UX teams can protect revenue and prove their strategic value.
Teams are hard to define because the org chart rarely matches how work actually gets done. The real challenge is naming the messy dependencies, incentives, architecture, and history that everyone sees but few teams feel safe enough to discuss.
PMs are less powerless than they think. By challenging stale assumptions, gathering evidence, finding ways to reach customers, and framing ideas around business priorities, they can influence roadmaps, leaders, and cross-functional decisions.
Defect backlogs are retention risks, not just engineering chores.
IBM is treating AI agents like digital employees that need lifecycle management, credentials, oversight, and retirement plans.
Sponsored
Everyone's building an agent framework. OpenProse [4] has one: it's called English.
AI will not replace product managers wholesale. The best PMs will use it to improve decisions, alignment, and product impact.
Non-technical PMs need to become builders, not backlog managers. AI tools now let PMs prototype, ship low-risk work, and orchestrate agents while preserving judgment, taste, and product quality.
PostHog keeps product marketing fast, practical, and story-driven. Great launches need clarity, strong writing, smart channels, internal alignment, and real customer stories.
Slowing growth is not always a sales problem. In the AI era, product velocity and competitiveness may be the real growth levers.
Sponsored
Veriff's 2026 Deepfakes Report [9] reveals that the average person's ability to detect a deepfake is just 7% ABOVE THE THRESHOLD OF RANDOM GUESSING. Don't leave your platform's trust and safety to chance. Download the full research report here [9] to stay ahead of identity fraud.
User interviews help teams understand what users need, why they behave the way they do, and where products can improve. This guide shows how to run them well, from recruiting participants to analyzing insights.
PMs should use AI agents to automate routine workflows, not replace judgment. The best PMs will become agent orchestrators who protect their taste, focus, and strategic thinking.
AI is moving deeper into product workflows through Notion Workers, agentic Android features, and vibe-coded tools. At the same time, companies are cutting weak AI features and rethinking how to use AI without adding bloat.
AI frustration is a signal, not a reason to settle. The last 10% of craft is where better tools, stronger judgment, and real differentiation emerge.
Skip abstract strategy debates that only sound smart.
Great products need clear positioning.
AI is making it possible for senior individual contributors to drive major business impact without managing a team. The best “High-Impact ICs” use AI to build, test, and ship work end to end, making management a choice rather than the only path to influence.
Product management became diluted by overhiring, bureaucracy, and distance from customers. A better way is to have a small team of senior, hands-on PMs who own problems, stay close to users, ship quickly, validate early, and use AI to amplify real product judgment.
In AI, product-market fit can become a trap when companies over-optimize around what worked last quarter while customer expectations keep changing. Winning teams will stay lean, close to customers, and willing to replace their own product before the market moves past them.
AI initiatives quickly turn normal product work into transformation work by exposing messy workflows, unclear ownership, and weak governance. The best PMs keep momentum by starting with narrow, low-risk pilots, learning quickly, and adding structure only once the workflow proves repeatable.
PM work is shifting from one-off AI chats to persistent agent systems that can access files, use tools, learn from feedback, and run across devices. The best PMs will build self-improving workflows in Claude Cowork, Claude Code, and Dispatch, using AI to orchestrate work instead of repeatedly prompting from scratch.
AI coding assistants improve individual developer speed, but they do not automatically improve team delivery. The next frontier is lifecycle orchestration across the full software development process, helping the entire team work faster, cheaper, and more effectively.
SEO should operate like a product function, with the authority to coordinate engineering, content, and long-term roadmap work. AEO belongs with the brand because AI visibility depends less on technical optimization and more on reputation, authority, narrative, and what the broader internet says about the company.
Inference costs are becoming a major threat to AI product margins, and traditional SaaS metrics do not isolate the problem quickly enough. The Inference Efficiency Ratio helps teams measure AI revenue against token spend, spot inefficient usage, and protect margins through better pricing, routing, caching, and launch gates.
OpenAI's Symphony points to a future where product teams manage agents through task queues instead of manually prompting models.
The real test for foundation labs is whether they can become durable, cash-generating businesses rather than capital-hungry revolutionary bets.
Sponsored
Happening this Wednesday [4]: join Kyle Poyar and Scott Woody for a lively discussion on how to translate agentic outcomes into revenue opportunities.
Product transformations fail when teams chase OKRs, discovery, strategy, or AI before fixing delivery. If teams cannot ship quickly and reliably, everything else becomes slower, weaker, and harder to trust.
AI makes it easy to build too much, too fast. Product teams need clearer outcomes, direct customer validation and the discipline to stop work that does not move toward a Minimum Productive Outcome.
AI makes prototyping fast, but speed is no longer the designer's advantage. The real edge is intent: understanding the problem clearly before using AI to build.
Application performance is a product requirement. Product and engineering must define what “fast enough” means for key user journeys, then balance performance work against the need to keep the system changeable.
Sponsored
Many ID verification providers are "black boxes" built on third-party wrappers, leading to hidden latencies and brittle integrations. LEARN WHY A VERTICALLY-INTEGRATED STACK [9] IS ESSENTIAL to eliminate vendor-on-vendor lag, ensure architectural integrity, and truly own your user's trust by verifying the tech behind your verifier. Read the
Agent harnesses are hidden AI technical debt. As models improve, today's prompts, workflows, and tool wrappers will become obsolete, so teams should keep harnesses thin, invest in durable skills and evals, and build systems they can replace easily.
Computers can now talk to us and do real skilled work. Software, teams, and organizations must adapt to a world where agents are no longer just tools, but active participants in how systems get built and used.
AI agent orchestration can become “doom building,” draining attention while feeling productive. Most agent work should be supervised through clear scopes and review blocks, while staying deeply involved only in the creative work that needs human judgment.
Organizations need enough consistency to stay aligned, but not so much that teams lose flexibility. AI can help translate across different ways of working, as long as it does not replace the human sensemaking that creates real alignment.
Sponsored
Executives are investing heavily in AI, but many product teams still struggle to execute. New research shows where delivery breaks down and
AI coding agents are shrinking months of roadmap work into days.
Old work hides in backlogs, roadmaps, and defect trackers, increasing WIP and slowing delivery.
Sponsored
Monetizing AI is tricky. Monetizing agents? Somehow, even trickier. In this Metronome webinar [4], SaaS pricing expert Kyle Poyar and CEO Scott Woody will explain:
These metrics reveal whether customers are building a habit or quietly preparing to churn.
Product work in Europe can be slowed by process, consensus, and risk avoidance. The PMs who stand out are the ones who simplify, make evidence-based decisions, and create progress where others wait for permission.
AI lock-in is an architecture problem, not just a vendor problem. The best teams will move fast while preserving portability across models, data, evaluation, and deployment.
AI coding tools are only as effective as the organization around them. Strong engineering foundations turn AI into leverage, while weak systems turn it into more chaos.