Use AI Well in Your Own Work
Last Updated:
A 8-10 weeks development journey
AI tools are now part of your job, and what you get from them depends on how you use them. This learning path builds that skill in the order you will need it. Learn what you may put into a tool, then write requests that produce a usable first draft. Check every output before it goes into your work, then apply the same habits to the documents and presentations you produce.
Your Development Roadmap
Protect Data When You Use AI
What you paste into an AI tool may be stored, reviewed, or used to train a model. Classify the information before you share it, and use only the tools your organization has approved. Replace names and account numbers with placeholders when the real ones are not needed.
- Classify information before you share it with a tool
- Use only the AI tools your organization has approved
- Replace names and account numbers with placeholders before you paste
Get Useful Results From AI Tools
A usable first draft starts with the request. Write the objective, the audience, the format, and the constraints into every one. Treat the first response as a draft, and ask for specific changes instead of starting over.
- Write the objective, audience, format, and constraints into every request
- Ask for specific changes instead of starting over
- Build AI into the recurring tasks where it takes less time
Check AI Output Before You Use It
AI output reads as confident whether or not it is correct. Treat every claim as unverified until you check it against its source, and check harder when more depends on the result. State your own reasoning even when you agree with the tool.
- Check every statistic, citation, and claim against its source
- Ask whether you verified the answer or it just sounds right
- Test any output about people for bias and report what you find
Write and Present With AI
Documents and presentations are where the first three milestones get used most. Ask for outline options before prose, and give the tool a sample of your own writing to match. Edit every draft for facts, filler, and voice before anyone reads it.
- Ask for outline options before prose and choose the structure yourself
- Give the tool a sample of your own writing to match
- Decide for each content type whether AI drafts it or you do
The Journey
Data protection comes first because it decides what you may put into a tool. Requests come second because a clear request produces the draft the rest of the path works on. Checking comes third because a draft is usable only once its claims are verified. Writing and presenting come last because they use all three on the work you produce most often.
Frequently Asked Questions
I already use AI tools every day. Where do I start?
Start with milestone one and check two habits: you classify information before you share it, and you use only approved tools. If both hold, move to milestone two. Daily use builds speed, and the later milestones add the request, checking, and editing habits.
How is this different from a course on prompting?
A prompting course covers milestone two. This path adds what you may share, how you check the result, and how you edit what you produce. Admire tracks those habits through what you do with real work, not what you completed.
What changes when I finish?
You share only what your organization allows, and your requests produce drafts you can use. Every claim you pass on has been checked, and the documents and presentations you produce read as yours.
My manager wants the whole team to use AI. Is this the right path?
This path is for each person's own use of AI. A manager who wants to coordinate how the team uses AI and coach people through the change should take Become an AI-Ready Leader alongside it.
Related Paths
Become an AI-Ready Leader
Build your own AI fluency, then coordinate how your team uses AI, then coach people through the change.
Master Personal Productivity with AI
Build a reliable productivity system, then add AI to it. AI speeds up whatever system you already run, so the system comes first.