Quickstart
QwenWorkOne real document in five minutes
Skip the feature tour. Do one task end to end, with material you already have, and judge the product on that.
The task we will use
Take a real meeting transcript you have — anything over a page. The goal is a two-page summary with decisions, owners and dates pulled out, in a format you could send without apologising for it.
The prompt pattern
Two sentences, one paste. The pattern is: what this is, who reads it, then the raw material. Not what you want written.
This is a 40-minute product review transcript. The reader is a technical lead who was not in the room.
Turn it into a two-page note with the decisions, the action items with owners, and the disagreements left open.
[paste the full transcript]The difference between this and 「summarise this meeting」 is not politeness. It is that the model now knows the audience and the required sections, and it stops guessing at both.
What to check before you accept it
- Owners and dates. These are the two fields it invents most often when the transcript is ambiguous.
- Decisions versus discussion. It tends to promote a strong opinion to a decision.
- Anything numeric. If the transcript says 「around 30%」 and the output says 「30%」, that is a change of meaning.
Then make it a habit
- Save the prompt
The pattern works for any meeting. Keep it as a note; retyping it is why people drift back to one-line prompts.
- Do it three times on real material
Three real documents teach you more than thirty feature demos.
- Only then look at automation
Once the manual run is stable, wrapping it in a trigger is a five-minute job. Before that, it is a way to produce broken documents faster.