Where should our organization use AI?
Start from the work, not the tool. Look for tasks that are slow, repetitive, inconsistent, or dependent on one person — then decide which of those AI can genuinely help with and which it should stay out of.
AI Advisory
Decide where AI belongs.
I help organizations evaluate where AI can create practical value, how it should be governed, how people should use it, and how adoption should be measured.
Let’s Talk AI
Bring the problem, not a software shortlist.
The distinction
Adding AI and governing AI are not the same thing.
AI tools can be easy to adopt. Building the policies, oversight, training, expectations, and measurement around them is the harder part.
The goal is not to add AI everywhere. It is to decide where it belongs.
What this can cover
Responsible adoption starts with the organization.
Understand where the organization is today before selecting tools.
Create structure around how AI is selected, approved, and used.
Evaluate AI against the actual business problem—not simply because the technology exists.
People need the information, authority, time, and ability to challenge the system.
Give employees clear expectations for useful, responsible AI use.
Measure AI adoption against business outcomes.
What this can look like
A law firm wants to add AI.
Leadership sees opportunities in drafting, research support, intake, summarization, and routine administrative work.
Then the questions begin.
The software decision is only one part of responsible adoption.
A practical start
Start with discovery. Build toward structure.
- 01Understand
- 02Map
- 03Prioritize
- 04Implement
- 05Measure
Understand → Map → Prioritize → Implement → Measure
Academic foundation
Research informs the work.
My University of Denver master’s work informs how I approach AI literacy, ethics, governance, responsible adoption, human oversight, risk, resilience, and organizational change.
Frameworks and principles that inform the work.
Research + Applied Thinking
The AI Continuity Project
A continuing exploration of responsible AI, governance, human oversight, and organizational resilience.
My University of Denver master’s work explored a practical question: What happens when AI becomes part of the systems organizations depend on? The research examined governance, risk, explainability, human oversight, resilience, failure detection, continuity, and organizational responsibility.
“What happens when the technology an organization depends on continues operating — but can no longer be trusted?”
The article trail remains available when you want the depth.
Connected risk
AI also creates new risk.
As AI becomes part of the systems organizations depend on, cybersecurity, data handling, vendor risk, and continuity become increasingly connected.
AI questions
What leaders ask about AI.
Do we need an AI policy?
If employees are already using AI tools, you already have AI in the organization and need a policy. A short, readable policy covering approved tools, data that must never be pasted in, review expectations, and who to ask beats a long unread document.
What is responsible AI governance?
Knowing where AI is used, who owns each use, what data it touches, how output is reviewed, what happens when it is wrong, and how the organization would notice. It is accountability, not paperwork.
How do we evaluate AI vendors?
Ask what data the vendor stores and trains on, where it is processed, how access is controlled, what happens on termination, what the vendor claims versus contractually commits to, and how the feature behaves when it fails.
How should employees be trained to use AI safely?
With their real work, not generic demos. Show approved tools, the data boundary, how to verify output, and where judgment must stay human — then keep the conversation open as tools change.
How do we measure whether AI adoption is actually helping?
Define the before state first: time spent, error rate, turnaround, backlog, or consistency. Without a baseline, adoption gets judged on enthusiasm rather than results.
A practical first step
Let’s Talk AI.
Bring the business problem first. The technology comes second.