Using Strategic Contrast to Expose Status Quo Risk

The buyer says the current scripts work fine. You list platform features, and the answer is still no change. Listing benefits rarely moves a team that has learned to live with its tools, because the pain of the old way feels familiar and the pain of switching feels new.

Put the two paths next to each other

Draw one workflow twice on the same board. On the left, show the manual path as it runs today. On the right, show the same steps under orchestration. The comparison does the persuading, so you can keep your commentary short.

Point to a silent failure

Choose one concrete place where the manual path drops information without anyone noticing, such as a script that exits cleanly after a partial error. Ask the team how they would find out. A quiet failure is the clearest form of status quo risk, because nobody sees it until a customer does.

Stay factual and respect the work

1. Credit the original: the scripts solved a real problem when they were written.
2. Use their data: draw the flow from the discovery notes, not a generic example.
3. Name the exposure: state what could be lost, delayed or repeated, and how often.

Ask what the failure would cost

Hand the question to the practitioner: what happens downstream if this step fails on a Friday night? When the buyer states the cost, you no longer have to claim it. This keeps the status quo risk in their words.

Decision and check

Decision: for each deal with a legacy process, prepare one before-and-after drawing built from the customer’s own steps and mark the single riskiest gap. Check: ask the team to explain the gap to a colleague. If they can describe what fails, how it is detected and what it costs, the contrast landed. If they defend the scripts, return to discovery for more evidence.

The free SE Ignite curriculum covers contrast and risk framing like this as part of the 80% of the SE role that holds steady across products.