Jira entered an existing market. Issue tracking and project management already existed, and Jira competed by becoming an extremely flexible system for organizing work. Today that flexibility lets teams customize workflows and use Jira as a shared source of truth. This is a red-ocean strategy: Jira had to win in an established category. Its bet was that teams would value configurability and scale enough to accept the complexity that comes with them.
Linear resegmented that market. It did not invent issue tracking; it made it faster, simpler, and more opinionated for modern software teams. Linear still describes issues as its core unit of work and positions itself around fast-moving product teams. I would still call this a red ocean, but with a much sharper wedge. Linear’s bet was that a meaningful segment was frustrated enough with heavyweight tools to switch for speed and a better experience. To me, this is the cleverest strategy because it changes the experience without asking users to adopt an entirely new behavior.
Productboard entered a new market by arguing that PMs needed their own system for understanding customer needs, prioritizing features, and managing roadmaps, rather than stretching delivery tools like Jira to do that work. That makes its original bet closer to a blue ocean. Productboard had to believe the pain was strong enough for PMs to add another system to their workflow.
In this week’s reading, Teresa Torres makes the key validation point: product teams need to understand customers’ actual goals, context, and unmet needs, not simply ask whether they would use a solution. For all three companies, the real test was whether PMs’ existing behavior supported the bet.
Sources:
https://www.atlassian.com/software/jira/guides/getting-started/basics
https://linear.app/startups
https://www.productboard.com/product-management-software/
https://www.producttalk.org/story-based-customer-interviews/
