Operations · Guides
Review a runbook for missing failure paths
A runbook is incomplete when it describes only the happy path.
From the cub house
Guides — Page 3
Practical briefs, worked examples and review checklists. Use these workflows with the tools you have connected.
-
Presentations · Guides
Outline a pitch deck without inventing traction
An early pitch often lacks verified metrics. A practical OfficeCubs workflow with a review checklist.
Spreadsheets · Guides
Write a precise brief for a pivot-style summary
A grouped summary needs a measure, grouping dimensions and aggregation rule.
Writing · Guides
Write error messages that help users recover
An error message should explain what happened and the next available action.
Documents · Guides
Summarize changes between two policy drafts
A comparison should show what changed without deciding legal or organizational meaning on its own.
Operations · Guides
Analyze process delays without inventing causes
Timestamped records can show where work waits, but they do not establish why.
Documents · Guides
Draft a project status memo from evidence
A useful status memo identifies what changed and what decision is needed.
Workflows · Guides
Define proof of completion for file-producing tasks
A completion message is weaker evidence than an artifact that opens and passes checks.
Documents · Guides
Draft a proposal with explicit scope boundaries
A proposal can become misleading when assumptions are presented as included work.
Product and code · Guides
Build a QA checklist for a specific change
A change-focused checklist should cover the behavior affected and plausible regressions.
Presentations · Guides
Build a quarterly review deck from a workbook
A review deck needs consistent periods and definitions across every chart.
Product and code · Guides
Audit a README against the project it describes
A README should help a new reader run the current project.
Spreadsheets · Guides
Reconcile two exports using stable keys
A row-by-row visual comparison breaks when sorting changes.
Product and code · Guides
Build a release checklist tied to evidence
A release checklist should identify the exact artifact, required checks and the person or process authorizing release.
Writing · Guides
Turn change records into readable release notes
Release notes should explain user-visible changes while retaining important compatibility information.
Workflows · Guides
Turn a successful task into a reusable working guide
A reusable guide should capture what made the task repeatable, including required inputs and known failure conditions.
Operations · Guides
Design an intake form from recurring requests
An intake form should ask for information needed to route and complete work.
Research · Guides
Write a research brief that produces usable evidence
A bounded research question is easier to answer than a request to learn everything about a market.
Research · Guides
Package research so another person can continue it
A useful handoff preserves the question, evidence trail and unresolved work.
Research · Guides
Turn unanswered questions into a research backlog
A research backlog should explain why a question matters and what evidence would resolve it.