Soft Skills Are Your Superpower
Everything from the talk, on one page. Driftless is at the bottom — on purpose.
AI is great at transparency. It can't do adaptation.
It surfaces what's in the data faster than you ever could. The adapting still happens in a conversation between people. That conversation is your job.
False productivity is real.
If AI takes reporting off your plate and you fill the time with more reporting, you've automated yourself into irrelevance.
A good Scrum Master's output is a conversation that moves the team closer to working product.
If it doesn't, it was just a meeting.
You can build your own tools now.
If you can describe what a good coach would notice, you can build something that notices it.
The Human Play prompt
Works in ChatGPT, Copilot, Claude — anything. Paste your sprint data, meeting notes, or retro output above it.
Here is my sprint data. Tell me what a good Scrum Master would notice. Then tell me: who do I need to talk to, what is the first sentence I should say, and which part of the Scrum Guide backs me up.
That's most of what Driftless does. If you've tried AI and got garbage, it's usually because you asked for a summary. Ask for the human play instead — tell it to end with a person and a sentence.
The three-question test
For any AI output — including the ones you build.
Did it get me to a person?
Do I know what to say?
Does the conversation move the product?
Two out of three, keep it. Fewer, it's a nicer dashboard.
The card question
Index cards, three minutes, nobody reads anyone else's. Top line: the admin thing you'd hand to AI. Then the only real question:
What would you do with that hour?
Be specific. Not "coaching." A name. A conversation. If it's hard to write, that's the trap catching you before it happens — which is the best time to catch it.
The Sprint Journal habit
One line per sprint per team. Human signal only. No tool required.
Pat had a hard week. Jamie's scope additions are back. First standup where everyone named the goal unprompted.
Then close the loop. Next sprint, before you write the new line, read the old one and ask: did what I did about that actually work? That's it. The Scrum Guide asks you to identify the most helpful change and address it — and then nobody checks. We instrumented velocity, which isn't in the Guide. We never instrumented the improvement, which is.
In three months you'll have a memory no dashboard has — and a record of what you changed.
Build one thing
The first half of your card is the spec. Give this to an AI, then show the result to one peer.
I'm a Scrum Master. Here's a repetitive thing I do every sprint: [the admin task from your card]. Here's what a good coach would notice while doing it: [two or three things]. Here's who I'd talk to about what I noticed: [who]. Build me a small tool that does the first part, notices the second, and ends every output by telling me who to talk to and what to say first.
Describe what a good coach would notice. That's the whole prompt. It's not a secret.
Or use the one I built.
Driftless reads your Jira or Rally board and hands you The Human Play — the one move only you can make, with the words to say and the Scrum Guide line behind it.
Comes with 20 free runs. No card, no keys.
Install Driftless
From the Chrome Web Store.
Open a board
Any Jira Cloud or Rally board, then click the Driftless icon in your toolbar.
Sign in with your email
We send a 6-digit code. Your 20 runs are waiting.
One run is one tool click or one follow-up question. When you want more, buy runs: 50 for $9, never expire. Either way — hold it to the three-question test.
Driftless for Jira
The same coach, inside Jira — installed by your Jira admin for the whole site, no extension needed. Inside Jira, Driftless can read what happened to every issue and when, which is what makes the closed loop possible.
Everything on this page as one PDF, sized for a phone.