You have the AI mandate now.
Maybe the founder asked what the company is doing with AI. Maybe a vendor demo made your current workflow look painfully manual. Maybe your team has tried ChatGPT, Copilot, and a few automations, and now everyone has a different idea about what should happen next.
The pressure is real. So is the risk of spending money on a tool that creates another disconnected system, another unclear process, or another pilot nobody owns.
The first AI decision is not which tool to buy. It’s whether you can name the problem well enough to solve it.
The expensive failure happens before anyone compares models. A tool gets bought before the organization has decided what work should change, what information the system can use, who’s accountable for the result, and how anyone will know the workflow got better.
Start With the Decision
A useful AI initiative starts with a business decision or workflow that’s slow, inconsistent, repetitive, or poorly supported today.
Ask:
- What decision or task is difficult right now?
- Who does it, and who feels the consequence when it goes wrong?
- What information does the work depend on?
- What would a meaningful improvement look like?
- What failure would be unacceptable?
That moves the conversation from “Where can we use AI?” to “Where would assisted judgment improve the work?”
The Tool Is Only One Possible Move
Once the problem is clear, choose the intervention rather than the brand name.
| Move | Choose it when | Example |
|---|---|---|
| Improve the process | The work is unclear or inconsistent before technology enters it | Standardize an intake, approval, handoff, or exception process |
| Repair the data | The workflow depends on incomplete, conflicting, or inaccessible information | Resolve source-of-truth conflicts, clean identifiers, document definitions |
| Automate with rules | The task follows stable conditions and predictable actions | Route an approved request, move records between systems, schedule a notification |
| Use AI assistance | The work benefits from categorization, summarization, retrieval, drafting, or bounded judgment support | Search an approved knowledge base, classify records, generate a reviewed first draft |
| Keep it human-led | The task depends on empathy, intuition, human connection, or hands-on assessment | Sensitive service interactions, complex real-world assessment, final consequential judgment |
Sometimes the answer is a better intake form, a documented procedure, cleaner reporting definitions, or data repair before anything intelligent can help. That’s the right order of operations, even when it lands smaller than the answer you were promised.
The best answer improves the work while staying proportionate to the risk, maintainable by the team, and defensible to the people responsible for the outcome. That’s often less technical than the option currently on the table.
Don’t Buy Yet If
Pause the purchase conversation when the missing work is diagnostic rather than technical. A new model, platform, agent, or subscription can’t decide what the workflow is for, reconcile competing definitions, establish permission to use data, assign ownership, or create the evidence proving an output improved the work.
So pause if any of these are true:
- Nobody can name the workflow, owner, and outcome the tool is meant to improve.
- The information the system needs lives in several places and nobody knows which version is current.
- The team can’t describe what a bad answer would look like.
- A vendor promises autonomous outcomes without showing how people will review, correct, or stop the system.
- The plan ends at the demo and doesn’t include training, access, maintenance, cost, or accountability.
Every one of these points to the same next investment: discovery and design, rather than another tool.
If a vendor can’t explain how the system will be evaluated, maintained, corrected, and retired when conditions change, the proposal is incomplete however impressive the demo was.
Readiness Is a Property of One Workflow
AI readiness isn’t a score, a certification, or something an organization either has or lacks.
It’s specific to the use case. A team may be ready to summarize approved internal material or search a well-maintained knowledge base while being nowhere near ready for a workflow that handles sensitive customer information, writes to operational systems, or produces customer-facing recommendations.
The useful question is narrower. What has to be true for this particular workflow to improve the work without creating a problem you can’t explain, test, or manage?
Readiness belongs to the broader system: the workflow, the data and context, the controls, the people, and the organization’s ability to learn from use.
| Readiness condition | A credible answer looks like | An unclear answer suggests |
|---|---|---|
| Problem | A specific task or decision is slow, repetitive, inconsistent, or poorly supported | The team is shopping for a capability rather than solving a defined problem |
| Outcome | The team can name what should improve and how it will be observed | The pilot becomes a demo with no viable success condition |
| Context and data | Sources, definitions, permissions, and limitations are understood | The system produces plausible output from incomplete or unsuitable information |
| Workflow | Inputs, handoffs, exceptions, downstream actions, and human roles are visible | Automation adds a disconnected process rather than improving the existing one |
| Ownership | A named person owns the decision, maintenance, monitoring, and escalation | The workflow becomes an orphaned pilot or a responsibility nobody can exercise |
| Evidence and controls | The system can be tested with realistic examples, boundaries, and pause conditions | The team is relying on a demo or a confident output rather than proof |
Six separate questions, with different owners and different fixes. Keep them separate long enough to make the next decision clear.
NIST’s AI Risk Management Framework and its Generative AI Profile offer a useful lifecycle: govern the work, map context and risks, measure performance and impacts, manage the system over time. The framework is voluntary, and AI RMF 1.0 is currently being revised under the White House AI Action Plan, so treat it as a durable discipline rather than a fixed checklist. The discipline is useful even for a small company with no compliance function.
You don’t need a large data team to answer these questions. You do need someone responsible for answering them.
Human Review Needs a Job
“Human in the loop” means something only when the person in the loop can affect the result.
Meaningful oversight requires four things: subject-matter expertise to recognize a weak, misleading, or harmful output; enough access and context to add what the system doesn’t know; authority to override, reject, or change the output; and a documented escalation path when the issue can’t be resolved inside the workflow.
For low-risk work, that may mean initial review, structured feedback, sampling, quality thresholds, or monitoring for defined failure conditions. For a higher-impact use case, the reviewer may need formal decision rights, evidence matched to the consequence, and authority to pause the system.
A person who can’t challenge the output isn’t providing meaningful oversight. They’re being asked to approve a system they don’t control.
Some Work Shouldn’t Be Handed to AI
AI shouldn’t be the final decision-maker when the result materially affects a person’s life, livelihood, safety, rights, health, legal standing, financial standing, employment, or access to essential services. It may support research, preparation, analysis, or a qualified person’s judgment. It doesn’t replace the accountability of the person responsible.
It’s also a poor substitute for work depending on empathy, intuition, human connection, or hands-on assessment of a real situation.
Whether AI can produce an answer was never the question. The question is whether your organization should rely on that answer, in this context, with these people, under these conditions.
A Demo Is Not an Evaluation
A vendor demo shows what a tool can do under prepared conditions. It doesn’t show what the workflow will do with your definitions, exceptions, data quality, permissions, users, change history, and operating constraints.
Before relying on an AI-enabled workflow, define the context it may use, the sources it should prefer, the output it’s allowed to produce, the boundaries it must respect, realistic test cases, known failure conditions, the evidence required for a recommendation, and the conditions requiring human review or a pause.
The aim is an evaluation process that reveals whether the system improves the work, where it fails, and whether your team can catch and correct those failures before they become routine. Perfect prediction was never on offer.
Adoption Is Part of the Evidence
Accuracy, reliability, security, and cost matter. So do adoption, trust, accessibility, and whether the people doing the work experience a real improvement.
A system people route around hasn’t created much value. A system people use enthusiastically but can’t challenge or safely correct isn’t a success either.
Look at three levels. At the task level, did the work become faster, clearer, or less repetitive? At the workflow level, did the end-to-end process improve once review, exceptions, handoffs, maintenance, and rework are counted? At the outcome level, did the change improve a customer experience, a team capability, a decision, or a risk profile?
A small, bounded workflow that earns trust and teaches a company how to operate AI well can be worth more than a technically impressive proof of concept ending in a slide deck.
The Next Useful Move
If your internal AI efforts have stalled and you can’t quite name why, don’t respond by buying another tool.
Start with one workflow. Map what happens now, who does it, what information it depends on, where the exceptions are, what failure would look like, who owns the decision, and what evidence would show the work improved.
Then choose the next move: automate, improve the data, redesign the process, use bounded AI assistance, or leave the task human-led.
That diagnosis is valuable before the spend.
AI earns its place in the workflow when people can understand it, challenge it, and keep it running.
When the Stall Has No Name
If several AI efforts have stalled and nobody can say why, the first useful work is naming what’s blocking them, with the evidence attached.
An AI Foundation Diagnostic does that for up to three related use cases and ends with a named primary blocker and a sequenced 90-day plan. Three weeks, fixed scope and fee.
