How to use this booklet

Work at your own pace. There are no wrong answers.

Where to begin. The strongest place to start is a task your team already does often—and that takes longer than it should. You don’t need a full strategy before you start. You need a concrete task, a tool (or a willingness to try one), and someone who will run the experiment. It works best when completed by someone who does or oversees the process day to day—they know where it really hurts.

This guide walks you through five parts: Scope your domain, Break down your journey, Find pain and value, Identify AI opportunities, and Next steps. Each part has space to write your answers and, if you get stuck, short prompts to nudge your thinking. For each opportunity you identify, you’ll also work through four check questions later in the booklet. If you can’t answer all four clearly, that opportunity isn’t ready to move forward yet.

You can complete it for one process or workflow. If you have several, pick the one that matters most or that you know best. Honesty beats perfection: describe how the process really runs, not how it should.

1
Scope
2
Break down
3
Pain & value
4
AI opportunity
5
Next steps

At the end you’ll find a First 30 days checklist to turn your notes into action. You can return to this booklet whenever you add a new workflow or want to compare opportunities.

Part 1

Scope your domain.

Choose one process or workflow to focus on. Naming it and defining its start and end keeps everything else bounded. Who is responsible for it? What kicks it off, and what is the final output?

Name the process

Give it a clear name (e.g. “Customer onboarding,” “Invoice processing,” “Proposal development from RFP to submission”).

My process name
What triggers this process? (What event or input starts it?)
If you’re stuck

Ask yourself: What is the very first thing that has to happen before anyone does any work? Is it an email, a form, a date, a request from another team?

What is the end output? (What is the tangible thing produced when the process is done?)
Who owns this process? (Name or role of the person most responsible for it running well)
Why does this process matter to your business? (One or two sentences)
Part 2

Break down your journey.

This is the hardest part—and the most important. List every major step in order. For each step, note what happens, who does it, what goes in and out, and roughly how long it takes. Describe the real process, not the ideal one. Include the messy, manual, or duplicated steps. Someone outside your team should be able to follow the sequence.

Tip: If a step is vague (“we process it”), break it into smaller steps. “We open the email, we read the attachment, we type the key fields into the system, we send a confirmation” is better than one big “we process it.”

List each step in order in the table below. Add rows on paper if you need more.
# What happens Who does it Inputs / outputs Rough time or frequency Where could AI help? (optional)
1
2
3
4
5
6
7
8+
If you’re stuck

Walk through one recent example from start to finish. What was the trigger? What did the first person do? Then the next? Where did things wait or get handed off? Write down what actually happened, step by step.

  • Where does work sit in someone’s inbox or queue?
  • Where do people copy information from one system to another?
  • Where does one person’s knowledge become a bottleneck?
  • How is work assigned or routed to the right person or team today?
  • Which steps are rules-based and predictable? Which require judgment?
Who are all the people involved in this process? (Include anyone who touches it—your team, other teams, external parties)
What data or documents does this process use? (Forms, PDFs, emails, spreadsheets, system data—where do they come from and in what format?)
Roughly how often does this process run? (Per day, week, or month?) And how long does one full run take from trigger to output?
Current tools
Part 3

Find pain and value.

Where does it hurt? Where do mistakes happen, delays build, or people get frustrated? Be specific. Then ask: if we improved this, what would it be worth? You don’t need exact numbers—a back-of-the-napkin estimate is enough (e.g. “20% less time,” “fewer errors in step 3,” “2 weeks faster to delivery”).

The ONE step that is most painful, slow, or error-prone
What tasks feel repetitive, tedious, or like they shouldn’t have to be done by a person?
If you’re stuck

Ask: When something goes wrong, where does it usually go wrong? When customers or colleagues complain about this process, what do they complain about? Where do backlogs or queues build up?

  • When does your process involve reading a document and extracting specific information? (That’s often prime territory for AI.)
  • What decisions does your team make repeatedly that follow a similar pattern each time?
Where do mistakes most often happen—and what is the cost when they do? (Time to fix, rework, lost trust, etc.)
Rough value of improving: if we made this process better, what would that be worth? (Time saved, errors reduced, faster delivery—even a rough guess)
Part 4

Identify the AI opportunity.

The steps that hurt most or feel most repetitive (from Part 3) are often the best candidates. Which of those could be assisted by AI? Think about the type of help: reading and extracting information from documents, summarising text, routing work to the right place, answering repeat questions, or spotting patterns. You don’t need to know the technology—just the kind of task.

Common patterns: Document intake and classification · Extracting data from forms or PDFs · Summarising long documents · Routing or triaging work · Answering repeated questions from a knowledge base · Spotting anomalies or risks. Which of these (or something else) might fit your process?

Look back at your step list and the “Where could AI help?” column if you filled it in.

Which step(s) could AI assist? Describe what the AI would do in plain language.
Who would benefit—the person doing the work, the team, the customer, or the business? How would you measure success? (e.g. time saved, errors reduced, faster cycle time)
What data would we need for this to work? Do we have it? Is it in a usable form?
If you’re stuck

Look back at your step list. For each step, ask: Could a tool read documents here? Could it suggest an answer or a next action? Could it do the first draft so a person only reviews? Could it route work to the right person automatically?

  • If you could eliminate one manual step completely—which would it be and why?
  • Which steps could theoretically run without a human, and which couldn’t?
  • Where do your best people spend the most time—and could AI free them to do more of that?
  • What data does your process generate that you’ve never had time to analyse?
Do we have historical data for this process—and is it clean enough for an AI to learn from?
If this AI got it wrong 5% of the time—what would happen? Is that acceptable for this use case?

What makes a quick win: Bounded scope, data you already have, one clear owner, and a result you can measure in weeks.

Is this a good quick-win candidate? Why or why not? (e.g. We have the data; scope is bounded; one person could pilot it. Or: data is scattered; we’d need 6 months to prepare.)
Part 5

Next steps and prioritisation.

Before you move an opportunity forward, run it through the four questions below. If you can’t answer each one in a specific way, the opportunity isn’t ready yet—refine it and try again. If you have more than one opportunity, run these four questions for each—use extra paper or copy this section so each opportunity has its own answers.

If you can’t answer these clearly, or you don’t have data or an owner, pause and refine the opportunity (or pick another) before piloting.

  • No data (or data not in a usable form)
  • No clear owner for the pilot
  • Can’t define what success looks like in measurable terms

Essential questions

1. What does success look like?

Define the measurable evidence of success—not the high-level goal, but the signals you could actually track. If you can’t name them, the opportunity isn’t defined well enough yet. Example: instead of “improve customer response quality,” use: fewer follow-up contacts, a specific satisfaction score, or time to first draft down from 2 hours to 15 minutes.

My signals for this opportunity

2. What understanding does the AI need?

What documents, data, policies, or examples does the AI need to produce something useful? Context is what turns generic output into something you can use. Without it, results are weak; with the right context, they become actionable. Think: templates, sample outputs, audience and tone, relevant precedents, product or service documentation.

Context we would provide

3. What is the AI allowed to do—and who reviews?

Spell out what the AI can do and who must review the output before it is used or published. This should be an explicit list, not a vague sense of what seems okay. Example: the AI drafts; a named staff member reviews and approves before anything is sent. Or: the AI summarises internal documents only—no external use.

Permitted actions and review

4. Do not allow the AI to…

Define the hard limits: sensitive data, legally protected information, decisions that must stay with a human. These are non-negotiable boundaries. Examples: never put customer personal data into unapproved tools; never publish AI output without human review; never use AI to make final decisions on matters with legal or regulatory impact.

Hard limits for this opportunity

Turn your thinking into action. What is the smallest experiment to test this idea? Who would own it? What would success look like in 6 months—in one sentence, and measurable?

Smallest experiment to validate this idea
Who would own this? (Name or role)
Success in 6 months—one line, measurable
If you have more than one opportunity, rank them. Score each 1–5 (5 = high) and add the total. Focus first on those with the highest total—or on the one that is fastest to try.
Opportunity Impact
1–5
Feasibility
1–5
Data ready?
1–5
Speed to value
1–5
Total

Scores 20+ = consider starting a pilot soon. 15–19 = plan for the next quarter. Below 15 = revisit when data or capacity is ready.

Practice

How AI work actually happens.

Using AI well is a loop, not a one-off. Useful output comes from iteration—refining your request and context—not from a single perfect prompt.

Plan your result

Clarify the outcome you want. Write down the steps of your current process and what a good output looks like. The clearer your intent, the better the result.

Gather materials

Gather the right documents, policies, examples, and instructions. The context you give is what separates useful output from generic filler. Ask: what would I hand to a skilled new hire to get this done?

Review outputs

Review the output for accuracy, tone, and completeness. Always verify facts and specific claims. AI can be confidently wrong—human review is the safeguard, not an afterthought.

Iterate / Improve

Adjust your prompt, add context, or give an example of what you want. Each round teaches you how to direct the tool better. Keep the prompts and context that work.

Reference

Governance.

Before you scale any AI use, get two things clear.

  • Define what the AI can and cannot do. Be explicit about scope, boundaries, and where human judgment is required.
  • Define who is involved and who signs off. Be clear on who must review, approve, or be consulted—and who is accountable for the output.
Roles

Who does what.

AI adoption needs three distinct functions. They don’t have to be three different people—in smaller teams one person may cover more than one. But the functions need to exist. Identify who owns each before you finish.

Leaders: set direction and gain executive-level approvals. End Users: have the detail necessary to properly determine what an improvement actually is. Champions: are highly motivated AI champions who want to learn all they can, evangelise AI, and constantly look for ways to improve the effort.

The essential questions, the plan–gather–review–iterate loop, and these three roles are the structure. Tools, timelines, and specific use cases fill in once you know which opportunities are worth pursuing and who is responsible for each.

Your first 30 days

Turn this booklet into action.

Use this checklist to take your first steps. Tick or write the date when you complete each. You don’t have to do them in order—pick what makes sense for you.

Notes / date
Notes / date
Notes / date
Notes / date
Notes / date
Notes / date

You’ve started. This booklet is a guide, not a one-time test. Revisit it when you add another workflow, when you run your first pilot, or when you want to compare and prioritize more opportunities. For a facilitated half-day workshop with your team and a prioritized list with named owners, get in touch with Optimaiz.

Contact Optimaiz.ca · We are here to help.