2 min lesson

What to extract from the answers

Match each case in "What to extract from the answers" to the signal and response that fit it.

What to extract from the answers

Pain to quantify

Payments PR-to-merge cycle time, onboarding ramp for new hires and the review backlog the principals complain about.

Pick one you can baseline and re-measure in a pilot.

Risks to surface

Data-retention exposure, shadow self-serve seats outside SSOSingle Sign-On. One company login (usually via SAML or OIDC) instead of a separate password per tool. Press Enter for the full definition. and the credibility scar from the Copilot rollout.

Name them before the platform team does.

Success criteria to lock

One headline metric the VP Eng named, plus the principals' merge conditions.

Written down and agreed, so the pilot can pass or fail honestly.

Learn more

Full explanation

The discovery summary you send back

Within a day, you send a short confirmation note. It proves you listened and converts spoken answers into a shared, correctable record. If you got something wrong, this is where they fix it for free.

Discovery summary: send within 24h

Subject: Northwind x Cursor: what I heard, please correct

The decision: by end of Q2, a go/no-go on standardizing AI-native
development, evidenced by a scoped pilot rather than a seat purchase.

The pain we'll baseline: payments PR-to-merge cycle time (currently
~3.5 days median, per the squad) and new-hire ramp-to-first-merge.

Hard gates (platform): zero-data-retention required, SSO/SAML
mandatory, SCIM deprovisioning + admin audit before any expansion.

The skeptics' bar: principals will merge AI-authored code only if it
passes existing review + tests with no drop in defect rate.

Success = cycle time down, no governance regression, two principals
shift from skeptic to neutral-or-better.

Open unknowns: confirmed champion, budget ceiling, security-review
lead time. Proposing we close these next session.

Watch out

The failure mode of this section is pitching disguised as questions. "Don't you think faster reviews would help?" is a pitch. "Where does a change wait longest between idea and prod?" is discovery. If your notes are full of Cursor features instead of their facts, you ran a demo with a question mark on the end.

QA Northwind principal engineer says "AI writes bad code. Copilot proved it." You are mid-discovery. What is the strongest move?

What to extract from the answers

Step 1 of 3