Skip to content
MyDSHMy DSH Field Notes
中文
Independently maintained; not affiliated with DeepSeek. No association with mydsh.dev or other MyDSH sites.

All categories/Office and documents

Level Starter · Report Status Outcomes

Weekly report: from log to decision material

Most weekly reports read 'did A, B, C this week' and leave the reader with nothing to act on.

Prompt

Turn this week's log into a report.

What I did this week (brain dump):
{{log}}
My role: {{role}}
Who reads it: {{reader}}
The real blocker this week: {{blocker}}

Four paragraphs, under {{words}} words total:
1. One-line conclusion: what moved, how far from the goal.
2. Three results: outcomes not activities ('cut X from 3 days to 1', not 'improved X').
3. One blocker: what or who it is stuck on, what support is needed, two options for the reader to pick.
4. Two things next week, each with a definition of done.

Do not write: process detail, hours worked, stacked adjectives.

What to state before it starts

Leave these unsaid and the model fills them with an assumption. Most 'wrong answers' start here.

  • {{log}}: the messier the better; tidying is its job
  • {{reader}}: manager / founder / other teams
  • {{blocker}}: the highest-value line, do not skip it
  • {{words}}: e.g. 250

Go through each of these

Where this kind of work most often goes wrong. Already in the prompt, so you do not have to remember it.

  • Offering two options turns the report into a decision the reader can make in one line.
  • Watch the outcome rule — models default to listing activities.