Technology decisions
Score the product and the delivery plan separately.
Separate product fit from delivery confidence when comparing technology suppliers, so a strong demo cannot hide an unproven implementation plan.
A polished product demonstration can answer the wrong question. Imagine a hypothetical shortlist where both platforms handle the everyday workflow. One supplier gives the stronger demonstration, but its proposal is vague about data migration, integrations, business decisions and the work expected from the customer. Product fit and confidence in delivery are related, but they are not the same judgement.
Keep two scorecards
Use one scorecard for the product and another for the delivery plan. Product criteria should cover the business outcomes, important rules, user journeys, reporting, administration and relevant exceptions. Delivery criteria should examine how the supplier proposes to move from today’s position to an accepted working service.
Avoid combining the two too early. A single overall score can allow excellent presentation or a long feature list to compensate for a delivery weakness that will determine whether the change succeeds.
Test product fit with the same real scenarios
Give each supplier the same representative scenarios and ask them to show the result rather than only describe capability. Include one ordinary case, one consequential exception and one change an administrator may need to make later. Record any configuration, custom work or third-party component needed to complete the scenario.
Separate what was demonstrated, what was stated and what remains to be confirmed. This keeps a confident answer from becoming evidence that the product has already met the requirement.
Ask for delivery evidence, not delivery adjectives
Words such as proven, collaborative and low risk are starting points for questions. Ask who owns the plan, which customer roles are required, what decisions are needed and how dependencies will be tracked. Examine the approach to data rehearsal, integration testing, user acceptance, operational readiness and recovery when a milestone does not pass.
Request examples of the actual working artefacts the engagement will use: a plan structure, decision log, migration reconciliation, acceptance record or readiness checklist. These need not reveal another client’s information. They should make the proposed method observable.
Set separate thresholds before choosing
Agree the minimum acceptable position for product fit and delivery confidence before final scoring. Treat an unproven critical requirement or an implausible implementation dependency as a decision to resolve, not a small deduction hidden inside an average.
Then consider price, terms and strategic fit with both scorecards visible. Record the important uncertainty and the evidence needed before contract, design or mobilisation. Rethink’s technology second opinion can provide an experienced challenge to both the product choice and the plan for making it work.