Why the summary isn't the product

I used to describe BoardSnap as an app that generates whiteboard summaries. It does that. But that description is wrong about what the product is.

Here's what I observed: in my beta testing sessions, when a summary appeared on screen, users would skim it in 15–20 seconds and then immediately scroll to the action items. The action items got tapped, edited, and shared. The summary was background context.

I ran an informal test: I removed the summary from the display and just showed action items in one beta variant. Engagement metrics barely moved. Then I removed the action items and just showed the summary. Usage dropped significantly — fewer return visits, less engagement per session.

The product is the action items. The summary is evidence that the AI understood the board.

### Why this matters for design

If the summary were the product, you'd design around making summaries longer, richer, more detailed. You'd optimize for the quality of the prose. You'd put the summary first.

If the action items are the product, you design around the list. You make it scannable. You make the state changes fast and satisfying. You put the action items first and above the fold. You optimize for the time from snap to actionable list.

After the week-one data, we inverted the UI hierarchy. Action items now appear above the summary. The summary is collapsible. This was the right call — the data showed it, and post-change engagement with action items increased.

### Why the summary still matters

The summary isn't useless — it's essential context for the action items to make sense. When you share a board with someone who wasn't in the meeting, the summary gives them enough background to understand why the action items exist. Without the summary, the action items are just a list of tasks without a story.

The summary is also the signal that the AI understood the board. If the summary is incoherent or wrong, users don't trust the action items — even if the action items themselves are correct. The summary is the confidence signal.

So: the summary is necessary, but it's not the thing users are paying for. The action items are the value. The summary is the proof of work.

### Implications for what we optimize

This distinction shapes our priorities:

• Action item quality > summary quality when we have to choose where to spend prompt engineering effort.
• Action item UI gets more design attention than summary formatting.
• Activation is measured by first action item interaction, not by "viewed the summary."
• Churn analysis looks at whether users are maintaining action item state (open → in-progress → done), not at whether they're reading summaries.

The product is the loop: snap the board, get the action items, work them to done. Everything else — the summary, the chat, the brand voice — is in service of that loop.