It's hands down the best approach to roadmapping out there.
The tl;dr:
Commit to Outcomes (future states of the world your product can create that don't exist today, and have meaning for your customers) without committing to solving for those Outcomes in any particular way.
So something like "It's easy for customers to get their data out of the product to feed into other applications" is an Outcome, and the Outputs can be all sorts of things: APIs, Direct Integrations to Other Apps, Excel exports, or just a dumb form for them to request the data and you have a SQL script you run to do it because it just doesn't happen enough to warrant the investment.
Go read this book: https://www.amazon.com/Product-Roadmaps-Relaunched-Direction...
It's hands down the best approach to roadmapping out there.
The tl;dr:
Commit to Outcomes (future states of the world your product can create that don't exist today, and have meaning for your customers) without committing to solving for those Outcomes in any particular way.
So something like "It's easy for customers to get their data out of the product to feed into other applications" is an Outcome, and the Outputs can be all sorts of things: APIs, Direct Integrations to Other Apps, Excel exports, or just a dumb form for them to request the data and you have a SQL script you run to do it because it just doesn't happen enough to warrant the investment.