Learn by goal
QwenWorkStart from the outcome you need
Feature-first learning wastes a week. Outcome-first learning gets one thing done today and teaches the pattern along the way.
Pick your outcome
| I need to… | Go here | The check that matters |
|---|---|---|
| Send a report tomorrow morning | Documents | Read only the numbers and names |
| Find out why two exports disagree | Spreadsheets | Sort the source column once and compare |
| Present a recommendation to management | Slides | Say the ask in one sentence first |
| Get a page online without a developer | /features/documents.html | Open it on a phone before sharing |
| Stop doing the same task every Monday | Automation | Run it manually ten times first |
The pattern behind all five
Material in, structure approved, output reviewed. Every shortcut above is that loop with a different file type at the end. People who get poor results almost always skip the middle step — they ask for the whole thing at once, then try to fix a finished document by re-prompting, which is much harder than fixing an outline.
A 30-minute plan for today
- Pick the one deliverable you owe someone this week.
- Paste the raw material you already have — not a description of it.
- Approve or fix the outline before any prose is written.
- Let it draft, then read only the facts: numbers, dates, names, owners.
- Send it. The first one is the hardest; the pattern transfers.
If the output is generic, the input was generic. 「Write about our product」 produces marketing filler from any model. The fix is always more specific material, never a longer instruction.
Want the mechanism rather than the recipe? Academy module 01 explains why this loop works.