Quest 3 of 15
Choosing & Piloting AI Tools
Evaluate and pilot workplace AI tools: compare copilots, automation platforms, and vertical SaaS; run a 90-day bounded pilot with time-saved metrics and kill criteria; build a simple business case for your manager or finance team. You will avoid buying tools before defining the workflow they must improve. For example, a three-scenario comparison can show cost and adoption risk for an internal knowledge copilot versus a manual wiki update process.
Start here
Before your company buys another copilot licence, define the workflow it must improve. This module shows how to compare tools, run a 90-day pilot, and build a simple case for your manager or finance team.
Big idea
Tool selection starts with the job: triage tickets, draft reports, search policies, sync CRM fields. Pilots prove time saved and adoption — kill criteria stop bad buys early.
Learn one idea at a time
Read, explore, then mark each idea when you can explain it.
Idea 1 of 7
Shortlist tools by workflow fit, not brand recognition. The categories genuinely differ: an embedded copilot (Microsoft 365 Copilot, Gemini in Workspace) works inside documents and email your staff already use, which lowers training cost but ties you to that suite. A standalone assistant (ChatGPT Enterprise, Claude for Work) is more flexible for general drafting and analysis but lives outside your systems. Automation platforms (Zapier, Power Automate) excel at moving data between apps on triggers, with AI as an optional step. Vertical SaaS — say, document intelligence for invoices — does one job deeply. Write down the workflow first, then ask which category naturally serves it; a mismatched category fails no matter how good the vendor demo looked.
Live interactive diagrams
Tap nodes, stages, or cards to explore — these diagrams match this module’s ideas.
Tool chase vs workflow-first
- Buy the trendiest model first
- Name the business decision and owner
- Promise enterprise ROI from a demo
- Pilot against a baseline metric
Tap Left or Right for each example, then "Why?" for the AI explanation.
Choose a deep dive
Open the topics you want to explore. The detail stays folded until you need it.
Deep dive 1ROI needs a credible counterfactual
ROI compares an investment with what would have happened otherwise. If an AI assistant saves staff time, confirm that the saved time can actually be redeployed to valuable work rather than simply moved elsewhere. Benefits can also include avoided losses or improved service, but each needs an evidence-based estimate.
Deep dive 2Treat uncertainty as management information
Adoption, accuracy, and data availability rarely match the first forecast. Show a conservative, expected, and optimistic case so finance and sponsors can see what drives the result. This is more useful than hiding uncertainty behind a large headline number.
Deep dive 3Worked example: a business case in five numbers
A team proposes an invoice-processing assistant. Baseline: two staff spend a combined 30 hours weekly keying invoices, with a 4% error rate that costs rework and late-payment penalties. Proposal: document AI extracts fields, staff verify instead of type. Estimated effect: 60% time reduction (18 hours weekly) and errors halved — figures taken from the pilot, not the vendor brochure. Costs: licence, four weeks of integration effort, and ongoing checking time. Payback lands around month seven in the expected case, month eleven in the conservative case. The one-page version of this — baseline, effect, cost, payback, assumptions — is more persuasive to finance than any slide about innovation.
Deep dive 4Count the benefits that are hard to count
Some real benefits resist neat numbers: staff no longer dreading a tedious task, faster responses improving customer goodwill, fewer compliance near-misses. Do not convert these into invented currency figures — finance teams see through that instantly. Instead, report them as tracked indicators alongside the financial case: staff satisfaction on the affected task, response-time distribution, near-miss counts. A business case that says 'here is the cash effect, and here are three monitored qualitative effects' earns more trust than one that claims morale is worth exactly $23,000.
Deep dive 5Compare tools fairly
Per-seat cost, integrations, pilot metrics, kill criteria — not demo sparkle alone.
One-minute challenge
Connect this lesson to real life
Name one situation where this idea could help, and one thing a person should still check.
Explore a real-world example
Use the arrows to connect the idea to a visible situation.
Photo example
Example: 90-day pilot
Two teams, baseline time-on-task, agreed stop rules.
Key terms
Tap a term to flip and read the definition.
Optional further learningFree textbooks and trusted online resources
These sources informed the course structure. Use them to revisit a concept or study it in more depth.
Ready check
Tick each idea only when you could explain it without looking back.
Ready for practice? Use sliders and ROI exercises after reading — practise stating ranges, not false precision.
Extra context (audience, logistics, curriculum notes)
Built for: For managers and project leads who must recommend tools, run pilots, and show evidence before company-wide rollout.
Formats: Workshop: cost–benefit and pilot planning (live or virtual) · Self-paced templates (spreadsheet + narrative outline) · Optional manager coaching slot for cohort premium tiers
Week 3 — tool selection, pilots, and value framing (report §1).
Next up
Ready for the next part?
When you've finished the reading, inline exercises, and knowledge check for this part, check the box to continue.