1 min lesson
Recommend, don't just describe
Use "The bridge between them is your running map of capability to customer situation" to say what you would do next.
Step 1 of 3
Recommend, don't just describe
Describing a feature is what a website does. Recommending one is what a trusted advisor does. The bridge between them is your running map of capability to customer situation.
Learn more
Advanced table
The right-hand column is the whole job. The left is just being literate
- Recently relevant capability
- A new agent capability
- Describe (weak)
- “The agent can now do larger multi-file tasks.”
- Recommend (strong)
- “Your platform team's migration backlog is exactly this - let's pilot it there next sprint.”
- Recently relevant capability
- A new admin / analytics control
- Describe (weak)
- “There's a new usage dashboard.”
- Recommend (strong)
- “This gives your VP the seat-activation view she asked for in the last EBR - I'll set it up.”
- Recently relevant capability
- A new model option
- Describe (weak)
- “There's a new model available.”
- Recommend (strong)
- “For your cost-sensitive teams this changes the price/quality tradeoff - here's how I'd configure it.”
| Recently relevant capability | Describe (weak) | Recommend (strong) |
|---|---|---|
| A new agent capability | “The agent can now do larger multi-file tasks.” | “Your platform team's migration backlog is exactly this - let's pilot it there next sprint.” |
| A new admin / analytics control | “There's a new usage dashboard.” | “This gives your VP the seat-activation view she asked for in the last EBR - I'll set it up.” |
| A new model option | “There's a new model available.” | “For your cost-sensitive teams this changes the price/quality tradeoff - here's how I'd configure it.” |
The right-hand column is the whole job. The left is just being literate.
Name-dropping a feature you've only read about and getting a detail wrong is worse than admitting you haven't used it yet. A skeptical engineer will probe one level deeper and the gap shows. If you haven't used something hands-on, say so and say what you'd test first - that's honest and still demonstrates the learning instinct.
“I use Cursor every week on a side project and I read the changelog the way I'd read release notes for any product I support. When something ships, my first question is which of my accounts now have a use case for it. The product moving this fast is a feature for this role - every release is a reason to re-engage a customer.”
QWhy is treating each new Cursor release as an expansion trigger a stronger ADM habit than waiting for the renewal date?