Is product discovery the last part of software development that AI hasn't touched yet?

Reddit r/artificial / 4/5/2026

💬 OpinionSignals & Early TrendsIdeas & Deep Analysis

Key Points

  • The post argues that AI has largely improved the “how to build” side of software development, while product discovery—the “what should we build” decision—has seen less meaningful AI-driven improvement.
  • It contrasts available AI support for engineers (e.g., Cursor) and designers (e.g., AI-assisted Figma plugins) with how PMs still manually review large volumes of support tickets, juggle tools like Amplitude and Notion, and write PRDs by hand.
  • The author questions why AI hasn’t meaningfully transformed the discovery process and invites discussion on where teams spend the most time during discovery.
  • The core prompt is a community inquiry asking whether any tools or approaches have actually helped teams improve discovery outcomes with AI.

Since Last Tuesday night I have been thinking of this problem and it really has hit me hard.

Engineers have Cursor. Designers have AI-assisted Figma plugins. But PMs are still manually reading through 50 support tickets, switching between Amplitude and Notion, and writing PRDs by hand.

I've been thinking about why AI hasn't meaningfully improved the discovery side of product development — the "what should we build" question — even as it's dramatically accelerated the "how do we build it" side.

Curious what this community thinks. Where does your team actually spend the most time in the discovery process? And has anything actually helped?

submitted by /u/Sat0shi619
[link] [comments]

Is product discovery the last part of software development that AI hasn't touched yet? | AI Navigate