Follow Us on Google
By Chinonso Arubayi
Every product fails for the same reason. Someone in a meeting room decided what to build before anyone asked what hurt. Product management exists to stop that pattern.
The role is not about roadmaps, backlogs or sprint rituals. It is about pain: finding it, naming it and removing it before the customer has to ask twice. A product manager who forgets this becomes a project coordinator with a fancier title.
The numbers now back this up. According to Productboard’s 2025 survey of 379 product professionals, every team surveyed uses AI tools, with 96% reporting consistent use and time savings of around four hours per task. Forrester reports that 84% of product managers embedded generative AI into at least some of their products in 2025, up from 58% in 2024.
Pragmatic Institute found that 64% of product teams have integrated AI into their products, while McKinsey’s global survey of nearly 2,000 respondents across 105 countries found that almost nine in ten organisations now use AI regularly. None of this changes the core task. AI removes friction from research and documentation. It does not decide which pain matters most. That judgement still belongs to a human.
Pain First, Features Second
A feature list is a guess until it meets a problem. The strongest product managers treat customer complaints, support tickets and abandoned carts as evidence, not noise. They read between the lines of a one-star review and ask why a user gave up rather than what button they clicked last. This habit separates teams that ship things people use from teams that ship things people tolerate.
What Makes a Great Product Manager
Other News
Curiosity that doesn’t switch off: Great product managers ask “why” until the answer stops changing, then ask it once more.
Comfort with ambiguity: Markets shift, data contradicts itself, and stakeholders disagree. The best product managers make calls without waiting for certainty that never arrives.
Ruthless prioritisation: Saying no to good ideas is harder than saying yes, but a roadmap with everything on it has nothing on it.
Communication that travels: Engineers, designers, executives and customers all need a different version of the same story, told without losing the truth in translation.
Ownership of outcomes, not output: Shipping a feature is not success. A customer’s problem disappearing is success.
Where AI Fits Into the Picture
AI has changed the mechanics of the job everywhere, not just in Silicon Valley. Teams in Lagos, London and Lahore now draft specifications, summarise interview transcripts and spot patterns in support tickets within minutes rather than days.
Productboard’s research found that 98% of respondents have changed or plan to change team structures because of AI, and Forrester notes that 73% of product managers now use AI tools weekly for research synthesis and prioritisation. This frees time, but it also raises the bar. When the busywork disappears, what remains is judgment, taste and the discipline to stay close to the customer’s pain rather than the model’s confidence.
The danger is mistaking output for insight. A summary of a thousand support tickets is still a summary. It tells you what was said, not why it mattered or what to do next. That interpretation is, and will remain, a human responsibility.
The Constant Beneath the Change
Tools will keep changing. The instinct to chase the customer’s pain rather than the loudest voice in the room will not. Product managers who hold onto that instinct, while using every tool available to act on it faster, are the ones building things people actually need. Everyone else is just shipping.
