Why "just use ChatGPT" is the worst AI advice you can give your team.
A short rant about tool-dropping — and the simple framework I use with clients to actually pick the right AI stack without wasting a quarter on trial-and-error.
Every week a well-meaning leader tells their team "just use ChatGPT." Two weeks later, nothing has changed. Nobody shipped faster. Some people feel guilty for not using it enough. A few tried it for one task, got a meh result, and quietly gave up.
Here's the thing: "just use it" isn't advice. It's a wish.
Why tool-dropping fails
Dropping a tool on a team without context is like giving someone a gym membership and being surprised they don't get stronger. Tools don't change behavior. Specific, practiced workflows change behavior.
Nobody ever got faster at their job because a URL was emailed to them.
The 3-question framework
Before I drop any tool on a client's team, I run through three questions. They take five minutes and save entire quarters.
1. What's the specific pain?
Not "we should use AI more." Specifically: Marketing spends 6 hours a week repurposing one blog into five social posts. PMs lose Monday mornings to sprint summaries. Customer support rewrites the same 12 email templates.
If you can't name the pain in one sentence, no tool will help.
2. Who's the champion?
For every workflow you pick, you need one human who is genuinely curious about it. Not mandated. Not guilt-tripped. Curious. They run the first 10 reps, find the sharp edges, and write the 1-page playbook for the rest of the team.
3. What does "worked" look like?
Name the metric before you start. Hours saved? Output shipped? Number of drafts per week? Without this, "we used AI" becomes a vibe instead of a result.
A quick worked example
A client's comms team was drowning in internal updates. Instead of "try Notion AI," we:
- Named the pain: Weekly all-hands recap took one person 4 hours.
- Picked a champion: The one person who'd been begging to try AI tooling.
- Defined success: 4 hours → under 1 hour, with the same quality bar.
Within three weeks: 45 minutes per recap. Six weeks later the workflow was documented and a second team was copying it.
Nobody used a fancy tool. They used ChatGPT. But the difference between "just use ChatGPT" and this workflow for this person for this job is everything.
The takeaway
If you're a leader: stop recommending tools. Start funding workflows. Pay for the reps, the playbook, the 30-day follow-up. That's what actually moves the needle.
If you're an IC: don't wait for the mandate. Pick one painful task this week. Try one prompt. Keep a note of what worked. That's your stack forming.
If this hit a nerve → book a workshop and we'll run this framework on your team's real work in a single session.