How I Use AI
Short version: my work is human-first. I use AI as an assistant, not a replacement. Here is what that means in practice.
The tools
Mostly Gemini and Claude for words, and Canva AI for images. For videos, Claude helps with the visuals, and it picks different tools depending on the model.
Models change often. I use whichever current model of each tool fits the job, and I name the specific one when it matters. This list might change. When it does, I'll note it on this page.
Where this applies
Everything I publish: the articles on this site, my weekly Focus. #deliver articles on LinkedIn, my emails (see below), the podcast, the Commonwealth Agency Agile Conference (CAAC) pages, and my whole YouTube channel (@mvizdos), not only the videos mentioned below.
What I use them for
- Brainstorming. Angles, titles, structure, the question I hadn't asked yet.
- Drafting and editing. It depends on the piece. Some are mine start to finish. Some start as my notes or ideas that AI helps shape. Some start as an AI draft that I then rewrite heavily, in my voice, with my examples.
- Transcribing and organizing. Turning audio into text and formatting my rough notes.
- Images. I often use Canva AI to create the background image for a new article. Canva AI is also how I make the drawing at the top of each Thursday LinkedIn post. You can search them all on the Focus. #deliver page.
- Research and summaries. Reading, summarizing and pointing me toward sources I then look at myself.
- The CAAC pages. The session summaries and takeaways on the CAAC pages are drafted with AI from the Virginia State Police's public recordings, working from the recordings' automatic captions. I curate and review them. I don't publish transcripts, and those pages are not the official conference site.
- This website. Claude helps me write and maintain the site's code and tooling.
- The podcast. Implementing Scrum: Unscripted is human created, with AI-generated voices, mostly from NotebookLM (now Gemini Notebook). They are not clones of real people. It started as a test of how far I could guide that tool using only my own vetted sources, and every AI-generated episode says so. I'm not planning new episodes made this way. The existing ones stay up.
- The emails. My Saturday morning Implementing Scrum email, and the check-in email every other Wednesday, are drafted and brainstormed with a vault of ideas that I keep updating. I send them with Kit, and that link is an affiliate link (more below). Focus. #deliver is a different thing: a weekly article on LinkedIn, with a summary of each one on this site.
- The AI and Scrum videos. See the series below for who does what.
What stays human
- The experience. Stories, client examples and lessons come from my own work as a Scrum trainer and practitioner. I don't ask AI to invent them, and I don't publish invented ones.
- No made-up people or quotes. No AI personas, no fabricated testimonials, no quotes attributed to people who didn't say them.
- No voice cloning. I don't clone anyone's voice. The podcast voices are generated, not copied from a person.
- No AI-made images passed off as real. I don't present AI-generated images as photographs of real people or events.
- The decision to publish. My name is on this site and I approve what goes on it.
Labels
If a piece is mostly AI-written with little change from me, I'll say so in a note at the top.
A few articles already carry one, and I'll add more when it applies.
Private and client information
When the material is confidential or about a client, I use private or local AI models. When I use a public tool, I turn off training on my data and limit what the tool can access.
How I check the work
I review what I publish, but I'll be honest: I don't always read every line of every piece the same way. AI can get facts wrong, and so can I. If you spot something wrong, I want to know.
For the video scripts, I use a fact-checking skill in Claude to check claims against sources. I built that skill myself, and it keeps changing as I learn more. I also check names, numbers and quotes myself. That is a check, not a guarantee.
Found a mistake?
Please tell me which page and what's wrong. I'll fix it and, where it matters, note the correction on the page.
The AI and Scrum video series
AI and Scrum is a series of whiteboard videos on what AI changes, and doesn't, for Scrum teams. It has three parts so far. I may add more.
Each part has a page on this site: The 1999 Trap, Code Got Cheap. Accountability Didn't. and Why AI Is Breaking Your Definition of Done.
Here is who does what:
- The script. The ideas and words are mine. Claude and Gemini Notebook help me brainstorm and write it.
- The voice. It is my own voice. I record it myself.
- The visuals. The whiteboard track is made with AI. I give Claude my recording, and it matches the visuals to the script beat by beat. I tune the result. Claude uses different tools depending on the model.
- The captions. I supply the English captions file. The other languages are created automatically by YouTube.
So: my words and my voice, with AI help making the pictures. I try to improve the process with each part.
Links that may benefit me
Two links on this page are affiliate or referral links: Kit, above, and the one for Claude below. If you use them, I may benefit. A few links to books on other pages are affiliate links too. The full list is on my Affiliate Disclosure page.
I have three Claude guest passes to share, while they last. Here is my referral link.
Use this as a model, not a place to hide
I'd like you to use this page as a model for how you might disclose your own AI use. Using AI is fine. Hiding it is the problem.
I'm not a lawyer, and this is not legal advice. These are ideas to spark your own thinking. Rules vary by country, platform, employer and client, so check the ones that apply to you.
Ideas you could borrow:
- Name the tools, and say what each one did.
- Say what stays human, and what you check before you publish.
- Say where the statement applies: which sites, channels and formats.
- Treat each format on its own. A video is not an article.
- Be honest about the limits of your review.
- Put a date on it and keep a short list of what changed.
- Link to it from the work itself, not only from a footer.
- Give readers an easy way to tell you about a mistake.
If you have something specific and actionable that would make this page better, please send it to me.
What changed on this page
- November 16, 2026. Added my whole YouTube channel to where this applies. Added the AI and Scrum series and who does what in it. Added Canva AI for the Thursday LinkedIn drawings, and the Saturday and Wednesday emails (sent with Kit, affiliate link). Added how I check video scripts. Added the "use this as a model" section. Dropped "and others" from the image tools and said the list may change. Added the affiliate and referral link note, and a link to the new Affiliate Disclosure page. Replaced the old case-studies section. Added this list.
- October 20, 2026. Added the CAAC pages.
- October 5, 2026. First published.
I update this page with Claude Code, the same way I help maintain this site. I give it the facts about my practice, it drafts the change, I review it and decide what goes live. I'd encourage you to keep your own statement current the same way.