title: “Learning to Work with AI” description: “Learning section: progressing with Cowork, building prompting skills, measuring progress” tags: [learning, progression, prompting, skills] —
Learning to Work with AI
| 🌐 Languages: English | Français |
The difference between someone who uses Cowork for 5 minutes a day and someone who saves 3 hours of work per week isn’t the tool. It’s how they use it.
This section is for those who want to progress, not just “use” it.
Contents
| File | Topic | For whom |
|---|---|---|
| learning-with-ai.md | Understanding how to learn with Cowork, identifying your profile, 30-day plan | Any profile, just starting out |
| building-prompting-skills.md | CTOC progression: from “copy-paste” to “writing your own prompts” | After 2-3 weeks of use |
| measuring-progress.md | Concrete measurement of gains, keeping motivation, adjusting | After 1 month of use |
Where to Start?
I’m just starting out: read learning-with-ai.md. It gives you the mental framework and a structured plan.
I’ve been using Cowork for a few weeks but I’m stalling: go directly to building-prompting-skills.md. The problem is likely that you’re copying prompts without adapting them.
I want to know if I’ve progressed: measuring-progress.md gives a simple template for tracking time saved.
What “Progressing” Means Concretely
In week 1, you copy prompts from this guide and just change the file paths.
In week 3, you adapt prompts to your context without looking at the guide.
In month 2, you write your own CTOC prompts from a blank page, for tasks that this guide hasn’t covered.
In month 3+, you train your team and document the prompts that work for your business.
That’s progression. Not “I learned to code” — “I learned to delegate intelligently.”
Further Reading
- Methodologies — CTOC, iterative refinement, batch processing
- WP-01: Effective Prompts — 20 before/after examples
- WP-11: ROI and Deployment — how to measure concretely