MasterOS
Learning path for applying AI at work
WHY5 min

Choose one piece of work to improve

What you'll learn

Start with a recurring task, the person who depends on its result, and the problem you want to solve.

On this page

  1. Start with the work, not the tool
  2. Check what your organization has already decided
  3. Think about a recent attempt

Start with the work, not the tool

Imagine that every Friday you prepare a project update using a task board, customer emails, and meeting notes. AI may help assemble a first draft, but the useful question is not whether it can write one. It is whether the person who relies on that update gets a more complete, dependable result with less total effort.

But a fluent draft is not automatically a dependable report. If it says a customer has approved something when the team is still waiting for a reply, or turns a target date into a firm commitment, you still need to find the error, correct it, and own the final message.

If a draft turns a pending reply into an approval or a target date into a commitment, someone still has to find and correct the mistake. A quicker first draft may leave the work no better if the same gathering and checking remain.

This program starts with one practical question: which part of your work is worth improving, and how would you recognize a real improvement? Choose a small, recurring task with a result someone uses. You are choosing a place to learn, not promising that AI is the answer.

AI Trial Card

A one-page record for a small AI experiment. It states the task, the person accountable, the information AI may use, what must be checked, and the result that would make the experiment worth continuing. It prevents a promising chat from disappearing as an anecdote.

Use it when: you want to test AI on real work without turning a vague idea into an uncontrolled change.

Choose a taskresult user + problemRun a bounded testapproved inputsReview evidencequality + riskDecide next stepcontinue, improve, stop
The same Trial Card follows the learner through the program: choose a task, test a bounded step, check the result, then continue, improve, or stop.

Check what your organization has already decided

If your organization has guidance for using AI, check it before using company work or data. It may name approved tools, permitted information, decisions that stay with people, and someone to contact. If no guidance has been shared, treat that as an unanswered question: do not infer permission from an example in this program.

If you are bringing company work, check these points

  • The business outcome or team problem the organization wants to improve.
  • The approved tool, account, and route for getting support.
  • What data may be used, what must be redacted, and who answers uncertain cases.
  • Which decisions or actions always need a responsible person to approve.
  • Where to submit a useful idea, a recurring problem, or evidence from a trial.

Think about a recent attempt

What did you ask AI to help with? Perhaps you summarized a report, drafted a customer reply, prepared a meeting document, or explored ideas for a proposal.

What genuinely helped? What did you still have to check or redo? This is not a test of whether you are already good at AI. It is how you find a useful starting point for the rest of the program.

Recurring task / recipient:
Current problem / baseline or not yet measured:
Step AI may support:
Owner / permitted and prohibited information:
Required review / exception owner:
Continue condition / stop condition:
Practice: about 10 min

Start an AI Trial Card. If you have not used AI yet, choose a recurring task such as preparing a weekly report or drafting customer replies.

  1. 1Name one recurring task.
  2. 2Write who uses the result and what they need from it.
  3. 3Note one problem you can observe today: delay, repeated work, missing information, or avoidable corrections.

A fast result that cannot be trusted yet

AI produces a project update in minutes, but the user cannot tell which claims come from source material and which were inferred. They end up reviewing it as closely as a new draft. A faster first draft creates little value if it does not reduce checking time or improve the final result.

Starting with a task that is too broad

"Improve customer support" is an ambition, not a task to begin with. "Draft replies to order-status questions" has a clearer boundary, is easier to check, and gives the team something specific to learn from.

For now, record just these three things

  • The recurring task you chose.
  • The person who uses or depends on its result.
  • The problem you want to understand better.
    1. Why is a fast first draft not enough to show that AI has improved a task?
    2. Which task of yours is small and clear enough to bring into the next lessons?
Next lessonDecide what a worthwhile improvement would look like