How many months has it been since Copilot was introduced to your company?
And has your work changed at all? You've read the feature introduction articles. You thought it looked convenient. You even saved a collection of prompts. Yet the next day, you open Word as usual and start writing from the first line, just like always.
This isn't a matter of ability. It's a matter of order. By the time you finish reading this article, you will be able to:
- Draw the line on how much to delegate to Copilot when given a new task.
- Stop starting from a blank page for boss reports, meeting summaries, and document structures.
- Identify at a glance which parts of a Copilot response need human verification.
- Judge when not to use it.
The fourth point is the most important. You don't need to read everything. Just Chapter 1 will help you decide on one task to try today.
■ A Day in the Life of Someone Who Can't Use Copilot
In the morning, a long email arrives. They read it all from the beginning. They spend 10 minutes looking for the parts relevant to them. In the afternoon, they are asked for a document. They open PowerPoint. They get stuck on the title of the first slide for 15 minutes.
In the evening, the meeting ends. They write a report from scratch while looking at their notes. By the time they finish, their memory of the decisions made has faded. Copilot was in the corner of the screen all day, never once clicked.
I have also experienced opening the input field, not knowing what to write, and closing it.
■ The Definition of 'Mastery' is Probably Misaligned
What do you think it means to master Copilot? Knowing all the functions? No. The goal for 30 days from now isn't to be someone who can explain every feature.
It's to be someone who, when handed a new job, can judge for themselves how much of it can be left to Copilot. Even if you know 100 functions, nothing changes if you can't use them for work. Even if you only know one function, if you can integrate it into your weekly reports, meetings, and emails, your work will change.
Let's break one more misconception: the idea that you can't do it because your environment has fewer Copilot features. The available range changes depending on the account, contract, and license, so your screen might not be the same as someone else's. Still, if you have one chat field open, you can execute almost all of these 30 days.
■ These 30 Days Are Not About Studying Copilot
You might have thought you'd be studying hard for 30 days. It's the opposite. What you'll do in these 30 days is an inventory of your work. Stop looking at feature lists. The first thing to look at is your own work. Start from there.
■ Here is the Content in Advance
Total of 8 chapters. From Day 0 to Day 30. For each day, I've placed one prompt that you can copy and paste as is. 30 prompts in total. From Day 1 to Day 7, we remove the resistance to asking Copilot.
From Day 8 to Day 14, we delegate real tasks one by one: emails, reports, meetings, and planning. From Day 15 to Day 21, we acquire the skill to fix subtle responses. From Day 22 to Day 26, we connect Word, Excel, PowerPoint, Outlook, and Teams.
From Day 27 to Day 30, we complete your own personal manual. And Chapter 7 is the chapter on judging when not to use it. Don't put everything in. Don't believe everything. This chapter isn't in prompt collections. This is where your true skill lies.
■ Why Provide This for Free?
I believe this content could be paid. However, there are two reasons I made it free. First: some people feel satisfied just by buying prompts. This article has zero value unless you read it and take action.
So, I want you to read it with a reason to try it tomorrow, not a reason for having paid. Second: Copilot depends on company contracts. Not everyone who reads this will have the same screen or features.
I decided not to put a price on something where I can't promise the same results to everyone. You can save it and read it later. But before you close it, please copy the prompt for Day 1.
■ It Only Takes One Session a Day
30 days might sound heavy. But all you do is once a day. Copy one prompt, put in your work information, and look at the response. That's it for the day. You don't have to start after reading everything.
The Day 1 prompt can be copied today while this article is open. You don't even have to read in order. If it's a week with many meetings, open Day 11 and 12. If reports are taking time, Day 10. If you're stuck on document creation, Day 24.
Open the day closest to your work this week. Now, let's start with Day 0. The first thing to check is not the features, but your usage environment.
1. You Don't Have to Remember Everything. First, Decide on the 'Usable Environment' and 'Tasks to Delegate'
Perfection is Not Knowing Everything
First, let's set the goal. Mastering Copilot. Hearing that, you might think, "Don't I have to remember all the functions?"
However, the goal for 30 days from now is not to be able to explain all features. It's to be able to judge "how much of this task can I leave to Copilot?" when given a new job.
For example, suppose your boss asks you to create a proposal. Before, you might have opened PowerPoint and started from the first slide.
But 30 days from now, it will be different.
First, you divide the work.
- Confirm the purpose. Gather necessary information. Organize the points.
- Come up with ideas. Create a structure. Write the first draft.
- Check for weaknesses. Verify numbers and facts. Get approval from the boss.
Once divided like this, you don't have to handle everything alone. Organizing points, brainstorming, structuring, drafting, and identifying weaknesses—Copilot can help with these.
On the other hand, whether to actually execute, whether the numbers are correct, how to convey it to the other party, and whether the company can take responsibility—these are human judgments.
In other words, mastering Copilot is not about delegating everything. Conversely, it's not about delegating nothing out of fear of mistakes.
It's about separating tasks Copilot is good at from tasks humans should hold.
This is the skill you will acquire over these 30 days. Knowing 100 functions changes nothing if you can't use them for work. Knowing just one function and integrating it into weekly reports, meetings, and emails changes everything.
Become a person who can use it, rather than just a person who is knowledgeable. To do that, stop looking at feature lists. The first thing to look at is your work.
First, Check Your Usage Environment, Not Features
Even if it's introduced under the name Copilot, not everyone will have the same screen or features. The range of use changes based on the account, contract, license, and company management settings.
So, don't stop because your screen is different or a button is missing. On Day 0, check the following:
- Are you signed in with a work Microsoft account?
- Can you open the Copilot chat screen?
- Can you input text and receive responses?
- Can you reference or attach files?
- Are there Copilot features available in Word, Excel, PowerPoint, Outlook, or Teams?
- Has the company issued guidelines on AI usage?
- If you don't know, who should you check with?
The important thing here is not to make everything usable, but to know what is usable in your current environment.
For example, if you can't find Copilot in PowerPoint, you can still practice document creation. Give Copilot the audience, purpose, conclusion, and required number of pages in the chat, and have it create a structure. Then, input that into PowerPoint yourself.
Inputting Information vs. Being Allowed to Input Information
When you open the Copilot input field, you might want to paste work documents immediately. However, the first thing to learn is not how to input, but how to judge what is okay to input. Companies have rules.
Even if it's technically possible, it might be prohibited by internal regulations. Therefore, in initial practice, do not use information like:
- Customer names or contact info
- Employee personal info
- Unreleased sales data
- Original contract text
- Recruitment or evaluation info
- Confidential plans or unreleased product info
- Passwords or authentication info
Don't input based on "it's probably fine." If you don't know, check. Until you can confirm, use other information.
At first, using text you wrote yourself is enough. Change company names to "Company A," names to "Person in Charge," and specific numbers to dummy data. Use public information. This is enough for practicing shortening, paraphrasing, summarizing, and brainstorming.
Choose Your First Task Based on 4 Criteria
After checking the environment and rules, choose the first task for Copilot. Don't pick a critical plan or difficult analysis yet. Choose based on:
- Frequency: Is it a daily, weekly, or monthly recurring task?
- Burden: Not just time. Small stalls like not knowing the first sentence of an email or how to summarize a report are burdens.
- Verifiability: Can you judge if the response is correct?
- Safety: Is the impact small if it's wrong, and is the input information safe?
Shortening your own text, finding deadlines in long notices, or summarizing a report into 200 words are perfect. Don't try to change the whole job at once. Change one recurring step.
Create a Copilot Work Note
Create a place to record your 30 days (Word, Excel, or a note app). Call it Copilot Work Note. Record four items:
- Task
- Instruction (Prompt)
- Result
- Improvement
Don't just record successes. Record if the answer was too long, if it hallucinated a deadline, or if it misunderstood a number. You need to know where to fix it to make it usable.
Day 0 Completion Conditions
Check your current state for these 5 items (Cannot do / Can do a little / Can do alone):
- Know what to ask Copilot
- Can explain the task including purpose and conditions
- Can fix subtle responses
- Know where to check the response
- Can judge when not to use Copilot
Day 0 tasks: Checked environment, checked company rules, prepared one safe practice data set, decided on one task to try, and created the Work Note. Once done, you're ready.
2. The First 7 Days: Removing Resistance to Asking Copilot
The goal for the first week is not to get perfect answers, but to get used to the flow: Ask -> See response -> Find differences from intent -> Change conditions -> See again.
Day 1: Questioning and Specifying Responses
Don't try to complete something today. Just ask a question. But don't just say "Tell me about X." Tell it what you want to know, why, your knowledge level, and what you'll use it for.
Today's Prompt
===== Prompt Start =====
Please explain the following theme so I can use it at work.
[Theme I want to know]
[e.g., How to make internal regular meetings more efficient]
[Purpose of the question]
[e.g., I want to shorten meeting times and clarify decisions starting next month]
[Current situation]
[e.g., 8 participants. 60 minutes weekly. Most time is spent on individual reports]
[My knowledge level]
[e.g., No professional experience in meeting improvement]
[Content to include]
- Basics to understand first
- Methods to try immediately
- Common failure points
- Specific examples
- Things to check before execution
[Conditions]
- Explain technical terms if used
- Don't just give generalities
- Don't fill in unknown circumstances arbitrarily
- Don't state unverified facts as certain
- If more info is needed, ask up to 3 follow-up questions
[Output Format]
- Conclusion
- Basic concept
- 3 actions to try tomorrow
- Common failure points
- What to check next
===== Prompt End =====
Day 2: Shortening Text Without Changing Meaning
Just saying "shorten it" might delete important info. Decide what to keep, what not to change, and the character count.
Today's Prompt
===== Prompt Start =====
Please shorten the following text without changing its meaning.
[Purpose of the text]
[e.g., Reporting progress to a boss via chat]
[Reader]
[e.g., Direct supervisor who knows the project outline]
[Original Text]
[Paste text]
[Information to keep]
- Conclusion, Date, Numerical values, Person in charge, Things for the recipient to check
[Things not to change]
- Facts, meaning of numbers, distinction between decided/undecided, proper nouns, request content
[Priority for cutting]
- Repetitions, 2. Background not affecting the conclusion, 3. Excessively polite expressions, 4. Abstract prefaces
[Conditions]
- Within [200] characters
- Conclusion clear in the first sentence
- Don't add info not in the original
- Mark unjudgeable parts as [Check Required]
[Output Format]
- Shortened text
- Content deleted or integrated
- Parts for human verification
===== Prompt End =====
Day 3: Telling It Who the Reader Is
"Make it easy to understand" isn't enough. Is it for a newcomer? A manager? A customer? The required explanation changes.
Today's Prompt
===== Prompt Start =====
Please rewrite the following text so the specified reader can easily understand it.
[Purpose] [e.g., Explaining new internal application rules]
[Reader] [e.g., General employees who don't know the system]
[What the reader already knows] [ ]
[What the reader doesn't know] [ ]
[Action to take after reading] [ ]
[Original Text] [Paste text]
[Conditions]
- Show "Who, By when, What to do" first
- Change technical terms to general words
- Don't add facts not in the original
- Don't change dates, numbers, or names
[Output Format]
- Rewritten text, 2. Points changed for the reader, 3. Insufficient explanations, 4. Check items
===== Prompt End =====
Day 4: Deciding What to Know Before Reading Long Texts
Don't make Copilot a "replacement for reading." Make it a guide to decide where to read.
Today's Prompt
===== Prompt Start =====
Please organize the following document so I can check the necessary parts.
[Purpose of reading] [ ]
[My position] [ ]
[Things I specifically want to know]
- What changed, when, for whom, my actions, deadline, notes, contact
[Document] [Paste text]
[Rules]
- Don't guess unwritten content
- Separate decisions, proposals, and unconfirmed items
- Mark items for important judgment as "Check original"
[Output Format]
- 3-line summary, 2. Changes relevant to me, 3. My actions, 4. Deadline, 5. Notes, 6. Parts to check in original, 7. Unjudgeable items, 8. Follow-up questions
===== Prompt End =====
Day 5: Generating Ideas in Different Directions
"Give me 10" results in similar ideas. Separate the directions.
Today's Prompt
===== Prompt Start =====
Please provide ideas for the following issue that do not overlap in direction.
[Issue] [ ]
[Current Situation] [ ]
[Ideal State] [ ]
[Unchangeable Conditions] [ ]
[Directions for Ideas]
- Try today, 2. No cost, 3. Reduce work, 4. Change storage, 5. Change communication, 6. Change management behavior, 7. Reuse existing tools, 8. Check root cause first
[Output Format]
For each: Name, Action, Aim, Preparation, Burden, Potential issues, First step
===== Prompt End =====
Day 6: Creating Comparison Materials Instead of Letting Copilot Decide
Today's Prompt
===== Prompt Start =====
Please compare the following options so I can make a judgment.
[Purpose] [ ]
[Issue] [ ]
[Options] A, B, C
[Criteria] Effect, Speed, Cost, Staff burden, User burden, Sustainability, Impact of failure, Measurability
[Rules] Don't guess missing info; mark as "Insufficient material." Don't pick one recommendation.
[Output Format] 1. Comparison table, 2. Suitable conditions for each, 3. Unsuitable conditions, 4. Missing info, 5. Small test method, 6. Human judgment points
===== Prompt End =====
Day 7: Turning Useful Instructions into Work Cards
Today's Prompt
===== Prompt Start =====
Please organize the following practice record into a "Copilot Work Card" for next time.
[Task Name] [ ]
[Scenario] [ ]
[Prompt Used] [Paste prompt]
[What worked] [ ]
[What was subtle] [ ]
[Changes for next time] [ ]
[Output Format] 1. Card name, 2. Scenario, 3. Info to prepare, 4. Reusable prompt, 5. Parts to swap, 6. Copilot's part, 7. Human's part, 8. Check items, 9. Improvements, 10. Status (Verifying/Reusable/Needs Review)
===== Prompt End =====
3. From Day 8, Delegate Real Tasks One by One
From here, use real work as teaching material. But don't dump everything. Delegate the draft, organization, candidates, points, and weaknesses.
Day 8: Don't Write Emails from the First Character
Today's Prompt
===== Prompt Start =====
Create a first draft of an email to a client based on these conditions.
[Purpose] [e.g., Consult on postponing next week's meeting by a week]
[Recipient] [ ]
[Background] [ ]
[Must convey] Our convenience, request for change, apology, candidate dates, prioritizing their intent
[Candidate Dates] [ ]
[Conditions] Polite but not excessively humble, don't make long excuses, within 300 characters, don't invent reasons/dates/names.
[Output Format] 1. Subject, 2. Body, 3. Pre-send check items
===== Prompt End =====
Day 9: Changing the Same Email into 3 Communication Styles
Today's Prompt
===== Prompt Start =====
Create 3 patterns of this email based on the relationship with the recipient.
[Purpose] [ ]
[Recipient] [ ]
[Must convey] [ ]
[Facts] [Paste facts]
[3 Patterns] 1. Prioritize politeness, 2. Prioritize softness, 3. Concise for busy people
===== Prompt End =====
Day 10: Putting the Conclusion Before the Background in Boss Reports
Today's Prompt
===== Prompt Start =====
Organize this info into a report so my boss can grasp the situation quickly.
[Purpose] [ ]
[What boss knows] [ ]
[Info to convey] [Paste background, status, actions]
[Consultation/Confirmation] [ ]
[Rules] Conclusion first, separate facts from judgment, separate decided from undecided.
[Output Format] 1. 200-character report, 2. Oral supplements, 3. Questions for boss, 4. Facts to check before reporting
===== Prompt End =====
Day 11: Prioritizing Decisions Over Discussion in Meetings
Today's Prompt
===== Prompt Start =====
Organize the points and questions before the meeting based on this info.
[Purpose] [ ]
[Participants] [ ]
[Time] [ ]
[Known info] [Paste background/docs]
[Decisions wanted] [ ]
[Output Format] 1. Decisions to make, 2. Pre-meeting checks, 3. Questions for participants, 4. Contentious points, 5. Missing info, 6. Proposed agenda, 7. Records to keep
===== Prompt End =====
Day 12: Turning Meeting Notes into Next Actions
Today's Prompt
===== Prompt Start =====
Organize these meeting notes into a form usable for practical work.
[Purpose] [ ]
[Notes] [Paste]
[Rules] Don't guess, separate decisions from proposals, mark unknown owners/deadlines as "Unset," separate facts/hypotheses/unconfirmed info.
[Output Format] 1. Decisions, 2. Undecided, 3. Tasks, 4. Owner, 5. Deadline, 6. Facts to check, 7. Next meeting decisions, 8. 150-char boss report, 9. Follow-up email, 10. Missing info
===== Prompt End =====
Day 13: Starting Planning with a Draft, Not a Finished Product
Today's Prompt
===== Prompt Start =====
Create a draft proposal for internal consideration based on these conditions.
[Theme] [ ]
[Problem] [ ]
[Target] [ ]
[Current Status] [Paste]
[Ideal State] [ ]
[Constraints] [ ]
[Success Metric] [ ]
[Output Format] 1. Issue summary, 2. Purpose, 3. 3 different directions, 4. Implementation for each, 5. Preparation, 6. Burden/Risk, 7. Small test, 8. Success indicators, 9. Decisions needed, 10. Questions
===== Prompt End =====
Day 14: Making Copilot the Critic
Today's Prompt
===== Prompt Start =====
Review this proposal from the perspective of different stakeholders.
[Proposal] [Paste]
[Perspectives] 1. Approving manager, 2. Executing staff, 3. Admin department, 4. Actual users
[Criteria] Problem fit, evidence, burden, cost/time/owner clarity, success judgment, fact vs hypothesis.
[Output Format] For each: 1. First thing to check, 2. Concerns, 3. Lack of evidence, 4. Info to add, 5. Answers to prepare, 6. Fix priority
===== Prompt End =====
4. Don't Finish in One Go. Improve Quality While Looking at Responses
Day 15: Categorizing Causes of Subtle Responses
Causes are usually: Insufficient info, request too large, vague conditions, or weak reference info.
Today's Prompt
===== Prompt Start =====
Compare my instruction and Copilot's response to diagnose why it's hard to use.
[Purpose] [ ]
[Instruction] [Paste]
[Response] [Paste]
[Issues] [ ]
[Output Format] 1. Main cause, 2. Diagnosis by cause, 3. Missing info, 4. Steps to split, 5. Vague conditions, 6. Reference info to add, 7. Fix proposal, 8. Human judgment part
===== Prompt End =====
Day 16: Changing Information Order When Changing the Reader
Today's Prompt
===== Prompt Start =====
Reconstruct the original info for 3 different readers.
[Original Info] [Paste]
[Purpose] [ ]
[Reader 1-3] Position, what they know, what they want to know, action to take.
[Conditions] Change order and amount of explanation, not just endings. Don't change facts/dates/numbers.
===== Prompt End =====
Day 17: Deciding Output Format Based on Usage Scenario
Today's Prompt
===== Prompt Start =====
Convert the original info into formats usable in different practical scenarios.
[Original Info] [Paste]
[Formats] 1. 200-char boss report, 2. Team share, 3. Task list, 4. Next meeting agenda
[Rules] Don't add info, mark unknown owners/deadlines as "Unset," separate decisions/proposals and facts/hypotheses.
===== Prompt End =====
Day 18: Comparing Multiple Options with the Same Criteria
Today's Prompt
===== Prompt Start =====
Compare multiple options using common evaluation criteria and priorities.
[Judgment] [ ]
[Options] A, B, C
[Criteria & Weight 1-5] Effect, Speed, Cost, Staff burden, User burden, Sustainability, Impact of failure, Measurability
[Output Format] 1. Comparison table, 2. Missing info, 3. Conditions where each is strong/weak, 4. Result if priorities change, 5. Pre-judgment questions
===== Prompt End =====
Day 19: Increasing Preparation Based on Opposing Views
Today's Prompt
===== Prompt Start =====
Review this proposal from a cautious or opposing standpoint.
[Proposal] [Paste]
[Perspectives] Manager, Staff, User, Data Admin
[Criteria] Necessity, existing methods, cost/man-hour underestimation, burden shift, measurement validity, reversibility.
[Output Format] 1. Opposing views, 2. Reasons, 3. Info to check, 4. Explanations to add, 5. Fixable parts, 6. Answers to prepare
===== Prompt End =====
Day 20: Separating Omissions and Ambiguities
Today's Prompt
===== Prompt Start =====
Check if this document is in a state where the reader can judge or execute.
[Purpose] [ ]
[Reader] [ ]
[Document] [Paste]
[Criteria] Purpose, target, background, content, owner, deadline, cost, approval, completion condition, judgment criteria, exceptions, troubleshooting, next action.
[Output Format] 1. Completely missing info, 2. Vague info, 3. Misleading parts, 4. Stalling points, 5. Lack of evidence, 6. Questions, 7. Fix priority
===== Prompt End =====
Day 21: Separating Natural Sentences from Correct Information
Today's Prompt
===== Prompt Start =====
Extract parts from this text that humans must fact-check.
[Purpose] [ ]
[Text] [Paste]
[Reference Info] [ ]
[Targets] Numbers, ratios, calculations, dates, deadlines, names, systems, products, quotes, sources, causal assertions, predictions, additions not in original.
[Output Format] 1. Target expression, 2. Category (Fact/Calc/Hypothesis/Opinion/Proposal/Unconfirmed), 3. Info to use for check, 4. Method, 5. Impact if wrong, 6. Priority, 7. Human judgment part
===== Prompt End =====
5. Don't Learn Apps Separately. Connect Text, Numbers, Documents, and Meetings
Word, Excel, PPT, Outlook, Teams. Work isn't divided by apps. One project passes through multiple places. So, prioritize "advancing work" over "learning apps."
Day 22: In Word, Decide "What to Keep" Before Writing
Today's Prompt
===== Prompt Start =====
Analyze this document to improve it for the specified reader's practical use.
[Type/Purpose/Reader/Goal] [ ]
[Document] [Paste]
[Must keep] [ ]
[Output Format] 1. Main points, 2. Info to keep, 3. Redundancies to integrate, 4. Insufficient explanation, 5. Stalling points, 6. Recommended new structure, 7. Human check items
===== Prompt End =====
Day 23: In Excel, Ask for Facts Before Asking for Causes
Today's Prompt
===== Prompt Start =====
Analyze this Excel data as a pre-report checker.
[Purpose/Data/Range/Period/Criteria/Values] [ ]
[First checks] Blanks, inconsistencies, units, exclusions, conditions.
[Rules] Separate facts from hypotheses, don't assert causes, specify ratio bases, show ranges used.
[Output Format] 1. Data issues, 2. Large changes, 3. Verifiable facts, 4. Hypotheses, 5. Additional data, 6. Boss report points, 7. Human re-check parts
===== Prompt End =====
Day 24: In PowerPoint, Win Before You Create
Today's Prompt
===== Prompt Start =====
Design a 5-slide PPT structure based on these conditions.
[Purpose/Reader/Decision wanted/Conclusion/Background/Evidence] [ ]
[Constraints] 5 slides, 1st slide shows conclusion/reason/judgment, one claim per slide, no invented numbers.
[Output for each slide] 1. Number, 2. Role, 3. Title, 4. Points, 5. Evidence, 6. Visuals, 7. Oral supplement, 8. Q&A. Plus: Weaknesses, lack of evidence, info to cut, points of opposition.
===== Prompt End =====
Day 25: In Outlook, Find Undecided Items Before Writing a Reply
Today's Prompt
===== Prompt Start =====
Organize this email thread as a pre-reply checker.
[Purpose/Thread] [Paste]
[Rules] Separate old/new conditions, don't confuse who said what, separate decisions/proposals, keep unanswered questions, don't guess dates/amounts/attachments.
[Output Format] 1. Current conclusion, 2. Latest conditions, 3. Changes, 4. My actions, 5. Their actions, 6. Unanswered questions, 7. Deadline, 8. Attachment check, 9. Parts to check in original, 10. Reply draft
===== Prompt End =====
Day 26: In Teams, Don't End Meetings as Just "Records of Talk"
Today's Prompt
===== Prompt Start =====
Convert this meeting info into practical work deliverables.
[Purpose/Participants/Info] [Paste]
[Rules] Separate decisions/proposals/opinions, don't guess, mark unknown owners/deadlines as "Unset," separate facts/hypotheses, don't force consensus on disagreements.
[Output Format] 1. Conclusion, 2. Decisions, 3. Undecided, 4. Tasks/Owner/Deadline/Condition, 5. Facts to check, 6. 200-char boss report, 7. Participant share, 8. Next meeting decisions, 9. Docs to prepare, 10. Parts to check in original.
===== Prompt End =====
6. From Day 27, Advance One Job from Start to Finish Together
Day 27: Decomposing Large Jobs into Small Steps
Today's Prompt
===== Prompt Start =====
Decompose this job into small executable steps from start to finish.
[Job/Purpose/Deliverable/Current method/Info/People] [ ]
[Rules] Don't use big terms like "make document," separate collection/organization/judgment/creation/check/approval, clarify fact-check steps, don't assign final judgment to AI.
[For each step] 1. Name, 2. Action, 3. Input info, 4. Completion condition, 5. Copilot support, 6. Human part, 7. Expert check, 8. Impact if wrong, 9. Handover. Plus: Waste, redundancies, first Copilot trial steps.
===== Prompt End =====
Day 28: Finding 5 Weekly Recurring Jobs
Today's Prompt
===== Prompt Start =====
Evaluate my tasks to select 5 jobs to establish Copilot usage.
[Job type/Tasks] [List]
[Criteria 1-5] Frequency, Burden, Verifiability, Safety.
[Output Format] 1. Evaluation table, 2. Top 5 candidates, 3. Steps to delegate for each, 4. Human check steps, 5. Safety prep, 6. Order to try.
===== Prompt End =====
Day 29: Deciding Steps to Delegate, Not the Whole Job
Today's Prompt
===== Prompt Start =====
Separate steps for this job into Copilot, Human, and Supervisor/Expert.
[Job/Steps] [From Day 27]
[Criteria] Impact if wrong, input safety, verifiability.
[Categories] A: Delegate to Copilot, B: Copilot support + Human judgment, C: Human only, D: Supervisor/Expert check.
[Output Format] 1. Step name, 2. Category A-D, 3. Reason, 4. Info for Copilot, 5. Expected output, 6. Human check, 7. Safety check, 8. Impact if wrong, 9. Completion condition.
===== Prompt End =====
Day 30: Completing Your Personal Copilot Manual
Today's Prompt
===== Prompt Start =====
Create my personal "Copilot Manual" from these 30 days of records.
[Records] [Paste Work Note]
[Criteria for inclusion] Actually used, recurring, verifiable, safe conditions known, reusable value.
[Output Format] 1. List of frequently used jobs, 2. 5-10 priority Work Cards, 3. Finalized Work Cards, 4. Jobs needing more verification, 5. Jobs decided NOT to use Copilot for, 6. Re-check items for next month.
===== Prompt End =====
7. Don't Put Everything In, Don't Believe Everything. Judgment is Skill
As you use it for 30 days, you'll feel you can use it for more. That's when you need the brakes. Check three things before use:
- Is the impact large if wrong?
- Is it okay to input this info?
- Can I verify the correctness myself?
Generation vs. Delegation
Important contracts, recruitment, legal judgment, critical numbers—these are not for delegation just because Copilot can answer. Use it for organizing materials, questions, checks, and drafts. Final judgment is human.
Company Info Follows Company Rules
"Product has protection" is different from "Company allows input." Check for customer, HR, unreleased, contract, or financial info. If you don't know, don't put it in.
Doubt Beautiful Sentences
Watch out for natural-looking text. Check numbers, dates, names, sources, and causal assertions. Separate Fact and Hypothesis.
Check in Order of Impact
Check what hurts most if wrong first. Boss report: numbers, deadlines, causes. Email: names, dates, amounts. PPT: evidence, quotes, conclusions.
8. Don't End at 30 Days. Keep Updating Your Model
Copilot will change. Don't try to learn every new feature. Just ask: "Does this change the work I do every week?" If not, ignore it. If yes, test it small.
Monthly Inventory
Once a month, review your Work Cards: Did I use it? Was it reusable? What do I always fix? Are check items enough? What can I delete?
Share Success and Failure
If you have a model that works, share it with your team. Share failures too—like hallucinated deadlines—and turn them into team check rules.
The Next 30 Days: Deepen One Job
Pick one job (Sales, Management, Admin) and map Copilot to its Before, During, and After stages.
The Goal: AI Study Feeling Disappears
Eventually, you use it because you have an email to write or a meeting to organize. It becomes a choice, like Excel. Mastering it means being able to say, "I'll use Copilot for this step, but I'll judge this part myself."
That is the state of mastery we aimed for in these 30 days.
