My team ran story-based interviews with eight PMs, so I tested each one against what fills a PM’s day.
| Market type (Blank) | Ocean | What it had to believe about PMs | |
|---|---|---|---|
| Jira | Existing | Red | PMs will work wherever engineering works |
| Linear | Resegmented | Red, but it made its own lane | Speed and good defaults beat configuration |
| Productboard | New | Mostly blue, now red | Deciding what to build is the job, and PMs will buy their own tool |
Jira. Clever: it launched in 2002 as a cheap bug tracker for developers, and PMs followed the engineers. Flawed: owning the data doesn’t make it clear. One PM spent two hours finding who owned a Jira ticket.
Linear. Clever: Blue Ocean’s eliminate-and-raise move inside a red ocean, cutting configuration and raising speed, and it’s working ($1.25B valuation in 2025). Flawed: the slowness PMs described came from interruptions. One said a two-minute interruption costs twenty minutes.
Productboard. Clever: it tied customer feedback straight to the roadmap. Flawed: it bet on the job PMs want, while status chasing eats their actual days. LeMay says PMs carry responsibility without authority, budget included. Blank warns new markets take years to educate, and Jira Product Discovery moved in (2023) before that finished. Productboard cut over 30% of staff in April 2026.
“Sometimes I feel less like a product manager and more like the company’s memory.” (PM interviewee)
What I’d do instead: all three sell PMs a better place to work. But in our interviews, the pain lived in the gaps between them, what one PM called the “connective tissue.” Our TAM puts PM-specific tools at only $1-2B, and PMs’ homemade fixes ran on Docs, Slack and Obsidian. I wouldn’t build another standalone app. I’d resegment with a layer over Jira or Linear that handles status and context, paid from the AI budget.
