Standup notes without the standup

Not every standup is a Zoom meeting with a shared Jira board. Some teams — especially colocated teams that value speed — run standups at a physical board. Today / In Progress / Done columns. Sticky notes or markers. Ten minutes, everyone's moving.

The downside: the board doesn't email itself to the people who were on it. The async record of what happened in the standup either requires a note-taker or a photo-to-Slack workflow.

Here's how BoardSnap fits into the physical standup board workflow.

### The standard physical standup setup

Typical board layout:

• Yesterday or Done: what moved to completion
• Today or In Progress: what's actively being worked on
• Blocked or Help needed: items that need attention

Optionally: one lane per team member (vertical format) or one lane per project (horizontal format). Sticky notes are common; marker directly on the board also works.

The board gets updated at the start of the standup, the team discusses it briefly, and then the standup ends. Total time: 5–15 minutes.

### How to snap it

At the end of the standup, before anyone erases or removes stickies:

1. Open BoardSnap, select (or create) the Project for this team
2. Snap the board — VisionKit detects the board boundary, you confirm, done
3. BoardSnap reads the layout: Done column items → automatically marked as done in the action list, In Progress column → in-progress, Today items → open

The output is a clean standup summary: what completed, what's in flight, what needs attention. Formatted for sharing to Slack.

### Where it's imperfect

Sticky notes create specific OCR challenges. Small text, inconsistent handwriting, sticky notes that overlap or aren't fully flat — these are harder conditions than a well-marked whiteboard.

If your standup board uses sticky notes: photograph straight on, as close as you can get while keeping the whole board in frame. The resolution on an iPhone camera is high enough to read clearly-written sticky notes at arms length, but not cramped or tiny writing at board distance.

For boards where text is very small or very dense: consider using BoardSnap's chat to ask specific questions about the board — "what are the blocked items?" — rather than relying on the automatic action item extraction to catch everything.

### The async standup use case

Some teams run async standups: each person writes their update on the board before the standup time, the team reviews without a meeting, someone snaps it at the end of the async window.

This is an underrated workflow. The physical board makes the async updates more visible than a Slack thread (you can see all updates at once, spatially), and a BoardSnap snap at the end creates the async record without a synchronous meeting.

If your standup has started creeping up in duration: try async-first with a physical board for two weeks. Snap it at 10am, share the BoardSnap summary to Slack, no meeting required. Sync only when the board shows blocked items that need discussion.

### What the snap doesn't replace

The conversation that happens about the board. When someone says "I'm blocked on X — here's the situation," that context isn't on the board. The snap captures the status; it doesn't capture the discussion.

For teams that want that context in the record: add a brief note to the relevant action item in BoardSnap after the snap, or use the BoardSnap AI chat to annotate — "add context to the 'API integration blocked' item: waiting on credentials from the vendor."

The board is the structure. The conversation is the substance. Both belong in the record.