1 min lesson
Discover before proposing a rollout
Understand the current workflow, people, cost and approval bar before choosing a test.
Step 1 of 2
Cursor does not publish a discovery exercise for this role. Discovery still matters because the SA must find workflow friction, lead technical working sessions, design adoption plans and support recovery when use slows.
Stay with the current environment before proposing Cursor. Use a recent development task, measure what happened and learn who can approve or block a change. Play back your reading before you recommend anything. Ask the customer to correct the problem, affected users, starting measure and decision owner. Use the corrected account when you choose a test. If code review delay is the problem, trace one recent change. Learn whether unclear ownership, repeated edits, a missing check or an approval queue caused the wait. Each cause needs a different test.
Learn more
Full explanation
Map the discovery sequence
Interactive diagram. Step through it with the Next and Previous controls below, or Tab to a region to read its detail.
Confirm the problem, approval path and measure before choosing the rollout step.
For Cursor, separate product interest from an adoption plan. Existing individual use may show demand, but a broader rollout still needs workflow fit, approval evidence, enablement and a clear owner.
- Question
- How do engineers use AI tools today?
- Decision it informs
- Which groups and workflows already have demand, and where unapproved use creates risk.
- Question
- Where does development work slow down?
- Decision it informs
- Which task should enter a bounded evaluation and which starting measure matters.
- Question
- What must a source code tool prove?
- Decision it informs
- Which data flow, access, retention, deletion and audit evidence the reviewer needs.
- Question
- What would broader adoption require?
- Decision it informs
- Which champions, platform work, enablement and decision owners are missing.
| Question | Decision it informs |
|---|---|
| How do engineers use AI tools today? | Which groups and workflows already have demand, and where unapproved use creates risk. |
| Where does development work slow down? | Which task should enter a bounded evaluation and which starting measure matters. |
| What must a source code tool prove? | Which data flow, access, retention, deletion and audit evidence the reviewer needs. |
| What would broader adoption require? | Which champions, platform work, enablement and decision owners are missing. |
Each question should change the rollout decision. Remove questions that do not.
Learn more
Optional practice
Test a security concern
QA customer raises a source code security concern early in discovery. What should you do first?