Your Team Saved Time with AI.
What Did Your Organization Gain?
1058 words/4.5-minute read
Speaking at Project Management Business Analysis World in Vancouver, I gave AI a job that sounded simple enough. “Help a business analyst decide which conference sessions to attend and what to ask the speakers.” The analyst wanted to get better at writing requirements and help other BAs do the same. With that context, AI suggested a schedule, explained its choices, and gave us enough questions to take up the speaker’s entire lunch hour.
Then we added one detail. You have thirty seconds with this person in the hallway. Which one question would you ask?
That’s a different assignment. It’s also the one the analyst actually needed help with.
Leaders face a version of this every time someone says, “Look how much time I saved with AI.” I believe them. I also want to know what happened next. Did a customer get an answer sooner? Did a developer get a requirement they could build from on the first pass? Did we finish the release without paying for Saturday overtime?
Your team can tell you where AI helped. As a leader, you can connect that work to an outcome the organization values. Here’s where I’d start.
1. Give the team a business problem they can recognize
“Use AI to improve productivity” leaves a lot of room for interpretation. A BA might produce requirements faster while the developers who receive them spend longer figuring out what they mean. Both teams can be working hard, and the project can still be standing still.
Try a more specific assignment. “Our developers keep sending stories back because they can’t tell what counts as done. On the next ten stories, let’s see whether the BA can use AI to prepare better questions before meeting with the business owner.”
Now the BA knows where to experiment. The developer knows what feedback to give. And the leader has something worth measuring. Look at ten comparable stories from the last release. How many came back for clarification? How much time did the BA, developer, and business owner spend resolving them? Use that as your starting point. Include the time people spend checking the AI-assisted work when you compare results.
That last part matters. If the BA saves twenty minutes and the developer spends thirty more, you want to hear from both of them.
2. Make room for the judgment that turns a draft into a decision
In my project management session, we used an oil and gas scenario. A PM taking on an enterprise AI project asked for possible stakeholders and questions to ask them. AI suggested a safety role. If the PM inherited a charter that omitted safety, what should they do with that suggestion?
I’d take one question to the sponsor. “Do we need someone from safety involved in this project?”
The sponsor might say yes and identify the person who needs to weigh in before scope approval. They might say the existing review covers it. Either answer is useful. The PM has checked an assumption while there’s still time to act on it.
Leaders can encourage that behavior by asking, in a project review, “What did the tool suggest, who checked it, and what decision changed?” Give the PM credit for getting the right person into the conversation. If that early involvement later prevents a repeat review, document what actually happened. Until then, describe it accurately as a risk the team addressed.
3. Pay for the time it takes to make good work reusable
In the BA session, I suggested starting a prompt library in a shared Word or Google document. A BA who finds a useful way to prepare for a stakeholder interview can save the prompt where colleagues already work. That’s easy. The leadership decision is whether that BA gets time to help a second person use it successfully.
Give two analysts half an hour together. Ask the first to bring a prompt that worked and the second to bring a real upcoming interview. Have the second analyst try it. Where did they need more context? Which questions did they discard? What did they learn from the stakeholder that they would otherwise have missed? Save the revised prompt alongside a short note about when it’s useful and what needs checking.
That half hour makes the original analyst’s contribution visible. It also gives you better evidence for expanding the practice. A second person has used it on a different piece of work, and you know what it took for them to succeed.
4. Follow the saved time all the way to the budget
Say a team saves enough time preparing and reviewing requirements to free up forty hours a month. What you fill that time with shows weather you’re moving forward with AI or simply spinning your wheels with another technology that you’re not getting the true value. Basically, do you see the time as space to do all those other things you never got time to finish (i.e., more busy work)? Or do you see it as added capability. I.e., what can we do now that we never had the time before.
Suppose the team uses those hours to clear a backlog. Report what the organization gained. How many additional requests did the team complete? How much sooner did customers get an answer? That’s a result worth taking to leadership. Keep it in those terms until you can trace it to a financial outcome.
What to ask at your next leadership meeting
Pick one workflow where people are already experimenting. Invite the person doing the work and the person receiving it. Ask them three questions.
- Where does this work slow down or come back for another pass?
- If AI gives us time back, what specifically will we do with it?
- In thirty days, what evidence would convince us to keep funding this?
Then put the follow-up on the calendar and give someone responsibility for bringing the evidence. Your BA or PM can show how the work changed. The person downstream can tell you whether it helped. The budget owner can verify what reached the bottom line.
View our article sharing and reuse policy here
