All categories/Office and documents
Office and documents
Meetings, reports, proposals, process. Structure matters, not word count.
52 entries here · one process per category, checkpoints written per job
- Meeting notes: decisions, actions and disagreement kept apartThe transcript is one wall of text and nobody can tell who does what.
- Weekly report: from log to decision materialMost weekly reports read 'did A, B, C this week' and leave the reader with nothing to act on.
- Deck outline: one decision per slideBefore any layout, decide what each slide asks the audience to do.
- Spreadsheet formulas: structure first, formula secondYou want the sheet to compute itself but cannot describe where the columns are, so any formula is a guess.
- Minutes: two hours of audio into one pageA two-hour meeting just ended. I have a rough transcript and need one page to post in the group.
- Agenda: cut the meeting in halfI am calling a 60-minute meeting with five people. The last ones of this kind ran two hours and decided nothing.
- Decision log: still readable in three monthsThe team re-litigates the same decision because nobody remembers why it was made.
- Chasing action items without being annoyingHalf of last week's action items have not moved. I need a follow-up message that does not feel like pressure.
- Retro: causes, not culpritsThe project slipped two weeks and the retro is turning into mutual justification. I need a process that reaches conclusions.
- One-on-one: a useful 30 minutesThe weekly one-on-one keeps turning into a status report. I want it to solve something.
- Standup: making 15 minutes workStandup keeps running to 40 minutes with everyone reading status aloud.
- Requirements review: from opinion to criteriaRequirements review turns into design arguing with engineering, and nothing is decided.
- Client meeting: complaint into requirementThe client complained for half an hour. I need what they actually need, not to be swept along by the emotion.
- Cross-team ask: from favour to scheduleAnother team needs to do something for us and keeps saying they are busy. Nothing moves.
- Kickoff: settle who decides firstA new project with five parties. Past projects like this died on 'I thought they were doing it'.
- Acceptance: pass or fail, not 'close enough'At acceptance the client said 'roughly fine' while known issues remain. I need criteria someone can sign.
- Crisis meeting: agree the line before speakingAn outage happened and support, marketing and engineering are all speaking externally. We need a 20-minute alignment.
- Quarterly review: numbers, not narrativeThe quarterly review goes upward. I have plenty of data but no causal story.
- Brainstorming: diverge, then convergeI am hosting an eight-person ideation session. Last time the loudest person decided.
- Meeting invite: say what you need from themInvites get no response, and people who come do not know why they are there.
- Audio cleanup: two hours into 20 minutes of readingThe transcript is a mess of repetition and tangents. Turn it into something readable.
- Decision memo: three options for the bossI need approval. Asking 'can we' usually gets a no, so I need something easy to decide on.
- OKR: objectives that can be checkedThe team's OKRs read like 'improve user experience'. Rewrite them so they can be checked.
- Promotion case: what problem you solvedA promotion defence is coming. I have done a lot but cannot show weight.
- Risk register: from caveats to trackable rowsRisks live in people's heads until something blows up.
- Handover doc: nobody has to ask youI am leaving this role. Handover must be complete so nobody has to ask me.
- Runbook: written for a person under pressureA runbook gets followed at 3 a.m. by a stressed person. It cannot be ambiguous.
- Training material: productive in three daysNew hires get documents thrown at them and still ask basics two weeks later.
- Doc structure: make it skimmableNobody finishes the 30-page proposal. Restructure it so it can be skimmed.
- Weekly report: three minutes, clear asksThe weekly report goes to my manager and peers. It used to be a list of completed items nobody read.
- Monthly report: trends instead of listsThe monthly report goes to management. They care about trend and inflection, not my task count.
- Project update: no follow-up questions neededMy boss asks where we are every week. I need an update that answers before he asks.
- Data weekly: anomalies first, normal skippedBusiness data arrives constantly. Most of it is normal; only a few points matter.
- Quarterly deck script: one sentence per slideA 15-slide quarterly deck with 20 minutes to present. The risk is reading the slides aloud.
- Incident report: no 'great attention'An incident needs a post-mortem read by both engineers and non-engineers.
- Option comparison: two choices, one tableA choice between two technical options needs a fair comparison for the decision maker.
- Bad news upward: impact, then optionsThe project will slip and the boss has to be told. Saying it plainly invites an interrogation.
- Asking for headcount: show the arithmeticThe team is overloaded and I need to ask for another head. Budget is tight.
- Post-mortem to rules: lessons that change behaviourThe project is done and the retro says 'improve communication'. The same thing happens next time.
- Minutes templates: one shape per meeting typeOur team runs five or six kinds of meeting on one template, and it fits none of them.
- Async update across time zonesThe team spans three time zones. Sync meetings are expensive, so updates must work asynchronously.
- Charts in reports: one message per chartThe report has charts with eight lines, and the reader cannot tell what to conclude.
- Annual plan: goals into quarterly deliverablesThe annual plan is due. Past versions were directions, impossible to check in December.
- Issue tracker: owners, not orphansIssues scatter across chat groups and nothing gets followed. The table has to actually move things.
- Budget note: spend as investmentThe budget is being cut. I need a note that ties spend to output.
- Client review: quarterly progress they can seeA quarterly client review must show value without looking like self-praise.
- Retro minutes: conclusions and owners apartThe retro produced conclusions but no owners, so improvements never land.
- One-pager for people who will not read emailImportant information goes unread in email. I need a one-pager that survives a chat group.
- Role charter: state what the role does not doRole boundaries are blurry and blame bounces. The team needs charters.
- Process doc: verbal process into executable stepsMany processes live only in senior heads. New hires ask around; errors are a matter of luck.
- Weekly to your manager: judgement, not logMy weekly report keeps getting sent back for detail. The real gap is judgement.
- When the meeting failed: explain upwardTwo hours and no conclusion. The boss needs an explanation and a next step.
Try another category
- Writing and copy47
- Data and analysis50
- Code and debugging50
- Learning and exams47
- Life and decisions53
- Agents and automation48
- Image and video45
- Job hunting30
- Workplace communication39
- Marketing and growth36
- E-commerce36
- Teaching and training36
- Research35
- Translation and localisation28
- Legal and contracts35
- Finance and operations35
- Product and design39
- Health35
- Customer support48
- Hiring and people ops48
- Social and content ops47
- Engineering and manufacturing48
- Security and operations48