Slides
QwenWorkSlides with an argument inside
Most slide generators make twelve pretty pages that say nothing. This one writes the argument first, which is why the result survives a review meeting.
The order of operations matters
Ask for 「a Q3 review deck」 and you get a generic template filled with generic claims. Ask for 「a deck arguing that we should delay the launch by three weeks, audience is the exec team, we have cost data and two competitor dates」 and you get an argument. The difference is entirely in how much context you supply.
What comes back
| Element | Generated | Needs your edit |
|---|---|---|
| Structure | Yes — chapters with a through-line | Cut one chapter, usually |
| Slide titles | Usually assertive sentences, not labels | Check they are claims you can defend |
| Body text | Three to five bullets per slide | Trim to two on most slides |
| Speaker notes | Yes, one paragraph per slide | Read once; they reveal weak slides |
| Charts | Placeholder with described data | Replace with the real chart |
Where it goes wrong
- Density. It fills slides because empty space looks unfinished to a model. Cutting half the text usually doubles the deck's effectiveness.
- Chart placeholders. It describes what a chart should show; it does not query your data. The description is useful, the placeholder is not.
- Confident numbers. Same rule as documents — any figure not in your input is invented.
A 20-minute deck workflow
- Write the ask in one sentence
What decision should the audience make? If you cannot state it, the deck cannot either.
- Give the evidence, not the topic
Attach the numbers, the dates, the quotes. Topic-only prompts produce topic-only slides.
- Approve the chapter list
Four chapters is usually right. Six means you are avoiding a decision about what matters.
- Edit for density, then rehearse from the notes
The speaker notes are the fastest way to find the slide that does not belong.