Solution Path vs Product Shortlist
Compare a complete solution path with a product shortlist, including when each is useful, what each omits and how to sequence them.
A solution path describes the full combination of process, people, technology, services and governance needed for an outcome. A product shortlist compares candidate products inside one part of that path.
Compare the decision, not just the artefact
The two tools answer different questions and are usually sequential rather than competing.
- 01
Question answered
A solution path asks what complete change could deliver the outcome. A shortlist asks which available product best fits a defined role.
- 02
Scope
Paths include operating change, dependencies and delivery. Shortlists normally focus on comparable suppliers or products.
- 03
Best timing
Use paths before committing to a category; use a shortlist after the required role and acceptance conditions are confirmed.
- 04
Failure mode
A shortlist can optimise the wrong category. A broad path can remain too abstract to procure or deliver.
Example: reducing invoice exceptions
One path combines supplier data cleanup, approval redesign and targeted automation; another outsources exception handling with reporting controls. Only after choosing a path does a product shortlist become meaningful. A product-led start would have hidden the operating-model choice.
What this method cannot guarantee
- A path is a hypothesis until dependencies, costs and evidence are tested.
- A shortlist is not vendor due diligence or contract evaluation.
- The method supports judgement; it does not transfer accountability from the people approving the decision.