# Whiteboard Layout Copy Pack

This free, editable Markdown pack accompanies the AFFiNE guide “10 Whiteboard Layout Ideas for Work.” Copy a layout into a document, recreate its zones on a physical board, or use the headings as frames on a digital canvas.

All filled examples are fictional teaching examples. Replace the names, dates, targets, and decisions with your own information. No account, formulas, macros, or automation are required.

## How to use the pack

1. Choose the question your board must answer.
2. Copy only that layout; do not combine every field into one board.
3. Put the purpose, owner, and next review time in the header.
4. Add one filled card to show teammates how to use each zone.
5. At the scheduled review, archive finished work and remove stale items.

---

## 1. Personal weekly plan

### Blank layout

**Weekly outcome:** [One result that would make the week successful]<br>
**Week of:** [YYYY-MM-DD]<br>
**Owner:** [Name]<br>
**Friday reset:** [Time]

| Monday | Tuesday | Wednesday | Thursday | Friday |
| --- | --- | --- | --- | --- |
| [One next action] | [One next action] | [One next action] | [One next action] | [One next action] |

**Must do (maximum 3):** [ ] [ ] [ ]<br>
**Waiting for:** [Person / item / expected date]<br>
**Notes or next week:** [Capture, do not schedule yet]

### Filled fictional example

**Weekly outcome:** Approve the onboarding email by Friday<br>
**Week of:** 2026-10-05<br>
**Owner:** Maya<br>
**Friday reset:** Friday 16:30

| Monday | Tuesday | Wednesday | Thursday | Friday |
| --- | --- | --- | --- | --- |
| Review 12 support tickets | Draft email | Collect legal feedback | Revise copy | Record approval |

**Must do:** draft email; receive legal feedback; record approval<br>
**Waiting for:** Omar — legal feedback — Wednesday 15:00<br>
**Notes or next week:** translate approved copy

---

## 2. Team Kanban with WIP limits

### Blank layout

**Service or team:** [Name]<br>
**Board owner:** [Name]<br>
**Review:** [Cadence]<br>
**Done means:** [Observable completion rule]

| Ready | Doing — WIP [limit] | Review — WIP [limit] | Blocked | Done this week |
| --- | --- | --- | --- | --- |
| [ID / task / owner / due] | [ID / task / owner / start] | [ID / output / reviewer] | [ID / blocker / next action] | [ID / evidence] |

**Pull rule:** Start a Ready card only when Doing is below its WIP limit.<br>
**Blocked rule:** Add the blocker, next action, and owner on the same card.

### Filled fictional example

**Service or team:** Checkout launch<br>
**Board owner:** Ana<br>
**Review:** Weekdays at 10:00<br>
**Done means:** Acceptance check passes and evidence is linked

| Ready | Doing — WIP 3 | Review — WIP 2 | Blocked | Done this week |
| --- | --- | --- | --- | --- |
| K-19 / Help copy / Mei / Oct 8 | K-17 / Checkout copy / Ana / Oct 5 | K-16 / Form validation / Leo | K-18 / Tax text / waiting for Finance / Ana to follow up Oct 6 | K-14 / Mobile layout / screenshot linked |

---

## 3. Project milestone roadmap

### Blank layout

**Goal:** [Delivered outcome]<br>
**Target finish:** [YYYY-MM-DD]<br>
**Project owner:** [Name]<br>
**Health:** [On track / At risk / Off track]

| Workstream | Milestone | Target date | Owner | Depends on | Acceptance evidence |
| --- | --- | --- | --- | --- | --- |
| [Stream] | [Decision or deliverable] | [Date] | [Name] | [Milestone] | [Link or condition] |

**Next decision:** [Question / decision maker / due date]<br>
**Change log:** [Date / approved change / approver / impact]

### Filled fictional example

**Goal:** Launch a working webinar registration page<br>
**Target finish:** 2026-10-20<br>
**Project owner:** Maya<br>
**Health:** At risk — prototype approval due Oct 7

| Workstream | Milestone | Target date | Owner | Depends on | Acceptance evidence |
| --- | --- | --- | --- | --- | --- |
| Discovery | Brief approved | Sep 30 | Maya | None | Signed brief |
| Design | Prototype approved | Oct 7 | Nia | Brief approved | Approval comment |
| Build | QA passed | Oct 16 | Leo | Prototype approved | Test checklist |
| Launch | Page live | Oct 20 | Sam | QA passed | Live check linked |

**Next decision:** Keep Oct 20 or reduce scope — Sam — Oct 7<br>
**Change log:** None yet

---

## 4. Meeting decisions and actions

### Blank layout

**Purpose:** [Decision or outcome]<br>
**Date / facilitator:** [Date] / [Name]<br>
**Attendees:** [Names]<br>
**Agenda:** [Timeboxed topics]

| Evidence and questions | Decisions | Actions |
| --- | --- | --- |
| [Fact, link, or open question] | [Decision / date / decision maker] | [Action / owner / due / done when] |

**Parking lot:** [Relevant but out-of-scope topics]<br>
**Record location:** [Where the final decisions and actions will live]

### Filled fictional example

**Purpose:** Choose the beta launch date<br>
**Date / facilitator:** 2026-10-06 / Priya<br>
**Attendees:** Priya, Leo, Sam<br>
**Agenda:** readiness 10 min; risks 10 min; decision 5 min

| Evidence and questions | Decisions | Actions |
| --- | --- | --- |
| Signup validation passes on desktop; mobile retest open | Beta launches Oct 21 if mobile check passes by Oct 9 | Priya / validate signup / Oct 9 / evidence linked |

**Parking lot:** pricing page rewrite<br>
**Record location:** Launch brief — Decisions section

---

## 5. Start / Stop / Continue retrospective

### Blank layout

**Period reviewed:** [Dates or project phase]<br>
**Objective:** [What the team wants to improve]<br>
**Facilitator:** [Name]

| Start | Stop | Continue |
| --- | --- | --- |
| [Evidence-backed suggestion] | [Behavior or process to change] | [Practice worth keeping] |

**Votes:** [How the team selects one improvement]<br>
**One experiment:** [Change / owner / start date / success signal]<br>
**Review date:** [When the team will inspect the result]

### Filled fictional example

**Period reviewed:** Support sprint, Sep 21–Oct 2<br>
**Objective:** Reduce avoidable handoffs<br>
**Facilitator:** Ravi

| Start | Stop | Continue |
| --- | --- | --- |
| Template the five most common replies | Reassign tickets without a note | 10:00 triage |

**Votes:** 4 votes for response templates<br>
**One experiment:** Ravi publishes five templates by Oct 8; track reuse for one week<br>
**Review date:** 2026-10-16

---

## 6. Study map and review queue

### Blank layout

**Learning objective:** [What you should explain or do without notes]<br>
**Session date:** [YYYY-MM-DD]<br>
**Source:** [Course, chapter, lecture, or URL]

| Cue or question | Concept map / explanation | Worked example |
| --- | --- | --- |
| [Prompt] | [Terms and relationships] | [Apply the idea] |

**Confusion list:** [What remains unclear]<br>
**Review queue:** tomorrow [ ] / three days [ ] / seven days [ ]<br>
**Next retrieval prompt:** [Question to answer from memory]

### Filled fictional example

**Learning objective:** Explain the water cycle without notes<br>
**Session date:** 2026-10-05<br>
**Source:** Earth science lesson 4

| Cue or question | Concept map / explanation | Worked example |
| --- | --- | --- |
| Why do clouds form? | Evaporation → condensation → precipitation → collection | Puddle warms, vapor rises, cloud forms, rain returns water |

**Confusion list:** How temperature changes condensation rate<br>
**Review queue:** tomorrow Oct 6 / three days Oct 8 / seven days Oct 12<br>
**Next retrieval prompt:** Draw the four-stage cycle and explain each arrow

---

## 7. Priority matrix with parking lot

### Blank layout

**Decision window:** [Today / this week]<br>
**Owner:** [Name]<br>
**Top three outcomes:** [1] [2] [3]

| Do now: urgent + important | Schedule: important, not urgent |
| --- | --- |
| [Next action] | [Next action + calendar time] |
| Delegate: urgent, lower leverage | Drop: neither |
| [Action + owner + due] | [Explicitly removed item] |

**Parking lot:** [Ideas to review later, not hidden commitments]

### Filled fictional example

**Decision window:** Tuesday<br>
**Owner:** Jordan<br>
**Top three outcomes:** fix signup; approve FAQ; send partner brief

| Do now: urgent + important | Schedule: important, not urgent |
| --- | --- |
| Reproduce registration bug | Draft FAQ copy Thursday 14:00 |
| Delegate: urgent, lower leverage | Drop: neither |
| Partner badge artwork — Nia — Wednesday | Unused dark-theme mockup |

**Parking lot:** November webinar idea

---

## 8. Root-cause investigation board

### Blank layout

**Problem statement:** [Observed condition / population / time window]<br>
**Investigation owner:** [Name]<br>
**Decision deadline:** [Date]

| Evidence | Hypothesis | Test | Finding | Action |
| --- | --- | --- | --- | --- |
| [Measured observation] | [Possible mechanism] | [How to disconfirm it] | [Result] | [Next step / owner / due] |

**What is not yet known:** [Uncertainty]<br>
**Stop condition:** [What evidence closes or redirects the investigation]

### Filled fictional example

**Problem statement:** 18% of fictional mobile signup attempts stopped at address validation, Sep 1–7<br>
**Investigation owner:** Leo<br>
**Decision deadline:** 2026-10-09

| Evidence | Hypothesis | Test | Finding | Action |
| --- | --- | --- | --- | --- |
| Drop occurs after invalid ZIP entry | Error message sits below the fold | Test five viewport widths | Reproduced at 320 px only | Move validation above CTA / Leo / Oct 8 |

**What is not yet known:** Whether the fix affects completion on other widths<br>
**Stop condition:** Retest passes on all five viewports

---

## 9. Content pipeline

### Blank layout

**Audience and channel:** [Who / where]<br>
**Pipeline owner:** [Name]<br>
**Publishing cadence:** [Schedule]<br>
**Review policy:** [What must be checked]

| Backlog | Brief — WIP [limit] | Draft — WIP [limit] | Review — WIP [limit] | Scheduled / published |
| --- | --- | --- | --- | --- |
| [Topic / audience signal] | [Query / angle / evidence / CTA] | [Owner / due] | [Reviewer / open issue] | [Date / URL / learning] |

### Filled fictional example

**Audience and channel:** Small-team operations / help center<br>
**Pipeline owner:** Mei<br>
**Publishing cadence:** One article each Thursday<br>
**Review policy:** Source, screenshot, link, and product-claim check

| Backlog | Brief — WIP 2 | Draft — WIP 2 | Review — WIP 1 | Scheduled / published |
| --- | --- | --- | --- | --- |
| Meeting handoff checklist | Reset a stale Kanban board / operators / support logs / copy checklist | Weekly planning FAQ / Mei / Oct 8 | Onboarding glossary / Ana / verify screenshot | Task ownership guide / Oct 1 / add decision example next update |

---

## 10. Goal-to-metric scoreboard

### Blank layout

**Goal and deadline:** [Outcome / date]<br>
**Outcome metric:** [Lagging measure and baseline]<br>
**Leading indicator:** [Behavior or condition that can change sooner]<br>
**Owner:** [Name]

| Week | Hypothesis / bet | Planned change | Actual | Learning | Next decision |
| --- | --- | --- | --- | --- | --- |
| [Date] | [If…then…because…] | [Experiment] | [Number + unit] | [What the result means] | [Continue / change / stop] |

### Filled fictional example

**Goal and deadline:** Improve fictional webinar registration completion from 62% to 70% by Oct 31<br>
**Outcome metric:** Completed registrations / started registrations<br>
**Leading indicator:** Mobile validation error rate<br>
**Owner:** Priya

| Week | Hypothesis / bet | Planned change | Actual | Learning | Next decision |
| --- | --- | --- | --- | --- | --- |
| Oct 5 | Fewer optional fields will reduce mobile errors | Remove company-size field | 66% completion | Direction improved; sample is still small | Run one more week before deciding |

---

## Maintenance rule to copy onto any board

**Owner:** [One named person]<br>
**Next review:** [Date and time]<br>
**Archive rule:** [Where completed cards and decisions go]<br>
**Stale-item rule:** [After how many days an item must be updated, archived, or removed]<br>
**Color legend:** [Color → meaning; keep the list short]
