Season's Savings | ₹5/mo for 3 months

₹199/month after first 3 months. Renews automatically. Terms apply.
Leveraging AI Micro Series Part 2: Stop Using AI to Save Time. Use It to Build Capacity. cover art

Leveraging AI Micro Series Part 2: Stop Using AI to Save Time. Use It to Build Capacity.

Leveraging AI Micro Series Part 2: Stop Using AI to Save Time. Use It to Build Capacity.

Listen for free

View show details
About this listen

Every leader has been told to document their processes. Almost nobody has done it — not because they didn't believe it mattered, but because writing it all down took longer than just doing the work themselves. That math has changed.

In part two of her AI micro series, Brooke picks up where part one left off: AI is the smartest new hire you've ever had, and when its work comes back generic, the problem is usually that nobody onboarded it. This episode gets practical about closing that gap. She lays out the difference between handing AI tasks one at a time and teaching it how things work at your organization — and why the second one is what actually builds capacity.

Along the way she makes a case for the messy voice memo over the polished manual, and for letting AI interview you about the things you've known so long you've forgotten to say them out loud.

What You'll Learn
  1. The two ways to use a brilliant new hire — and why only one of them scales. Handing over tasks one at a time gives you time back on each task. Teaching how the work gets done means the organization stops routing everything through you.
  2. How to turn a spoken explanation into usable documentation. Talk one recurring process through out loud the way you'd explain it to someone on their first day, then hand the recording to AI and ask it to produce a step-by-step process.
  3. The follow-up question that surfaces what you forgot to say. Asking AI to interview you about what a new person would need to know pulls out the know-how you've held so long you no longer notice you're holding it.
Key Takeaways
  • Saving time and building capacity are not the same thing. Brooke Richie-Babbage defines capacity as the organization's ability to do more without routing every decision and task back through the executive director. Faster task completion doesn't produce that. Written-down process does.
  • When AI output comes back generic, the problem is onboarding, not the tool. AI has no context on your organization until someone gives it context. The gap it exposes is a documentation gap that already existed.
  • The barrier to documenting processes was never belief — it was time. Leaders have always known it mattered. Writing a manual took longer than doing the work. AI removes the writing, which means the leader only has to talk.
  • Documentation built for AI is documentation built for people. Once how the work gets done exists in writing, a staff member can run it, a contractor can run it, and the next hire can run it. The AI use case is the forcing function, not the point.
  • "Only I can do this" is usually "only I know how — for now." The process quietly eating your week is almost always the one you've assumed is non-transferable. Most of the time what's non-transferable is the knowledge, not the work.

Want to work together?

Apply for the Next Level Nonprofit Mastermind, a high-touch coaching and training accelerator for established organizations with $1M+ budgets that are ready to design for impact sustained at scale.

Budget under $1M? Join Elevate and get proven step-by-step playbooks + coaching support to build each of the core elements of your nonprofit's operating system - strategic clarity, a fundraising engine, a high-performance team, and an active and engaged board!

Connect with me!

  • LinkedIn
  • Instagram
  • YouTube
adbl_web_anon_alc_button_suppression_t1
No reviews yet