---
title: "Design Sprint Sketch: Brainshelf Camera-Capture Validation"
description: "Brainshelf Tuesday artifact: 12 lightning demos across team (Apple Wallet, Instagram, Pinterest, Google Photos, Linear, Robinhood, Notion, Goodreads, Letterboxd, Things 3), swarm assignment, 4 independent solution sketches showing distinct design philosophies, recruiting tracker absorbs Discord-2 cancellation via buffer activation."
artifact: design-sprint-sketch
version: "1.0"
repo_version: "2.15.0"
skill_version: "0.1.0"
created: 2026-05-16
status: sample
thread: brainshelf
context: "Brainshelf pre-seed B2C SaaS for personal book collection management; Design Sprint week of 2026-06-01 testing Foundation Sprint assumption A1 (sub-3-sec camera-first capture switchability)"
---

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->

## Scenario

Tuesday 2026-06-02. Monday closed with Jamie selecting the capture-plus-confirmation moment as the target. The team invokes `tool-design-sprint-sketch` to structure today's lightning demos + four-step independent solution sketch protocol. Each team member produces one sketch independently; the skill orchestrates but does not author.

## Lightning Demo Board

Each team member presented 3 demos (3 min each) during the 09:15-10:45 lightning session. Facilitator (Riley) extracted reusable patterns. Total demos: 12. Total patterns: 12.

| Presenter | Demo source | Reusable pattern (one line) |
|---|---|---|
| Jamie | Apple Wallet (add pass flow) | Single-tap commit with system-handled confirmation animation |
| Jamie | Instagram (capture and post) | Camera-first surface with one-frame preview before commit |
| Jamie | Bear (note app) | Tag-on-save with auto-suggested tags from recent context |
| Alex | Day One (journal) | Library view with chronological + manual collection switching |
| Alex | Pinterest (pin save) | Save-from-anywhere with visual confirmation card overlay |
| Alex | Google Photos (face grouping) | Trust through "we found this; correct us" framing |
| Sam | Linear (issue creation) | Quick-add field with smart parsing of free-text input |
| Sam | Robinhood (buy confirmation) | High-stakes confirmation with explicit cancel window before commit |
| Sam | Notion (database row) | Editable-in-place after capture; correction is friction-free |
| Riley | Goodreads (book add) | The status quo we are competing against; over-friction at capture |
| Riley | Letterboxd (film log) | Capture-as-rating; rating becomes the capture confirmation |
| Riley | Things 3 (task quick-entry) | Capture flow that escapes to background instantly; no modal trap |

**Patterns most likely to influence sketches** (Riley's read; not voted): single-tap commit with animation (Jamie/Apple Wallet); trust through "we found this; correct us" framing (Alex/Google Photos); editable-in-place after capture (Sam/Notion); capture escapes to background instantly (Riley/Things 3).

## Sketch Assignment Plan

**Approach:** Swarm. All four team members sketch the same target moment. Rationale: first Design Sprint for this team; default for v0.1 sprints; divide would broaden coverage but reduce comparability.

**Target for sketching:** "Capture moment plus immediate post-capture confirmation surface" (map Steps 2 + 3 transition; includes a 2-step recall flow from the confirmation surface).

**Time allocations:** Notes 20 min (11:00-11:20); Ideas 20 min (11:30-11:50); Crazy 8s 8 min (13:30-13:38); Solution Sketch 90 min (13:40-15:10). Team committed to the full 90-min Solution Sketch window for thoroughness.

**Constraint:** Silent independent work. No looking at others' Figma frames. No talking. Riley times each step and gives 5-min and 1-min warnings.

## Four-Step Sketches

All four sketches produced in Figma frames sized 1170 x 2532 (iPhone Pro vertical). Each sketcher used a single artboard with a 3-panel storyboard structure. Sketches collected at 15:10 PT, attribution stripped, named "Sketch A / B / C / D" in random order for Wednesday's heat-map.

### Sketch B (Jamie's; attribution visible Tuesday to team for completion verification, stripped Wednesday morning for blind heat-map)

**Solution Sketch description:** Panel 1 shows the camera surface with a book held in frame; the cover is recognized with a subtle pulsing outline; bottom shows "Twig and Cover Books" detected with a thumbnail-sized cover preview. Panel 2 shows the post-capture confirmation: a card slides up from the bottom with the book cover, title, author, and 4 chips for "Read / Want to read / Reading / Reference"; a 5-second visible undo countdown sits in the top-right. Panel 3 shows the immediate recall surface: the same book now appears at the top of a "Recently captured" row in the user's library, with a "where you saw it" tag (geolocation; bookstore name detected) and a "books like this you have" mini-row.

**Distinctive elements:** Drew on Sam's Robinhood pattern (explicit cancel window before commit; 5-second undo countdown). The "where you saw it" geolocation pattern is novel; no demo had it.

### Sketch D (Alex's; attribution stripped Wednesday morning)

**Solution Sketch description:** Panel 1 shows a full-bleed camera viewfinder with a thin AR-style frame around the book; recognition is indicated only by haptic-equivalent visual (a soft glow at the edges); no on-screen text during capture. Panel 2 shows the confirmation as a Polaroid-style card that animates into a stack of recent captures; the card itself shows cover + title + a "Tap to correct" small text at bottom; correction tap opens an inline editable field with auto-suggestions. Panel 3 shows the library view as a visual-first wall of book covers with a search bar at top; search opens to a "found in your library: 3 books that mention X" panel.

**Distinctive elements:** Drew on Alex's own Google Photos "we found this; correct us" pattern (correction is friction-free in-place). The Polaroid-stack metaphor is novel. Panel 1 trusts haptic feedback over visual text; tests whether minimalism feels confident or anxious.

### Sketch C (Sam's; attribution stripped Wednesday morning)

**Solution Sketch description:** Panel 1 shows the camera surface with explicit two-step capture: tap to capture, tap again to commit (vs. auto-commit on recognition). Panel 2 shows the confirmation as a full-screen modal with the book cover plus 6 explicit metadata fields the user can edit (title, author, edition, format, status, optional note); a prominent "Save" button bottom-right; no auto-tagging. Panel 3 shows the library as a tabular list with sortable columns (title, author, captured-on, status).

**Distinctive elements:** Engineer's preference for explicit user control over magic. Drew on Linear's quick-add pattern but inverted (Linear is fast; Sam's sketch is intentional and thorough). Tests whether the target customer wants confidence-via-control or confidence-via-system-intelligence.

### Sketch A (Riley's; attribution stripped Wednesday morning)

**Solution Sketch description:** Panel 1 shows the camera with the book in frame; recognition surfaces a single best-match cover at the top of the screen with "Is this right? Yes / No"; tapping Yes commits. Panel 2 shows the confirmation as a journal-entry-style card: book cover left, freeform text input right ("Why did you grab this?"); the text field is optional but prominent. Panel 3 shows the library view organized by "captured contexts" (chips at top: "Last weekend at Powell's" / "From Devon's recommendation" / "Following the Octavia Butler trail"); tapping a chip filters the library.

**Distinctive elements:** Customer-expert's reading on what readers actually care about: the story of why they grabbed the book, not just the metadata. Drew on Things 3's escape-to-background pattern (the freeform text is optional; capture completes without it). The "captured contexts" library organization is novel; no demo had context-as-primary-organization.

## Recruiting Tracker Update (Tuesday Check-in, 12:35 PT)

| Slot | Customer name (or ID) | Status | Notes |
|---|---|---|---|
| Fri 09:00 | UI-Panel-A (US, age 38, M) | Confirmed | Reschedule risk Low; reminder sent |
| Fri 10:30 | Discord-1 (UK, age 31, F) | Confirmed | High enthusiasm; pre-screen score 9/10 |
| Fri 12:00 | Discord-2 (US, age 45, F) | Cancelled (work conflict; 12:20 PT email) | Buffer activation needed |
| Fri 14:00 | Discord-3 (Canada, age 29, M) | Confirmed | |
| Fri 15:30 | UI-Panel-B (Australia, age 52, F) | Confirmed | Time-zone challenge: 09:30 their local; confirmed comfortable |
| Fri 17:00 (buffer) | Discord-4 (US, age 36, M) | Activated 14:50 PT in response to 12:00 cancellation | Moved to 12:00 slot; buffer slot now empty |

**Cancellations to date:** 1. **Buffer slot activation needed:** Triggered; Discord-4 moved to 12:00; buffer slot now empty (next cancellation triggers escalation). **Risk level for Friday:** Low. Buffer used; team aware that one more cancellation triggers cohort-shrinks-to-4 protocol.

## Decider Checkpoint

**Decider sign-off required before Wednesday begins.**

- [x] Jamie confirms all 4 team members produced a Solution Sketch (no skipping; no group sketches; Riley enforced silence during the 90-min Solution Sketch window).
- [x] Jamie confirms sketch attribution has been stripped before sketches are added to Wednesday's heat-map board (sketches renamed A / B / C / D in random order; sketcher names removed from Figma frame metadata).
- [x] Jamie acknowledges that Wednesday's heat-map is blind (votes on sketches, not on sketchers); team has agreed not to discuss attribution until after the supervote.
- [x] Jamie commits to attending Wednesday morning 09:00-12:30 PT for heat-map plus critique plus supervote.
- [x] Jamie confirms recruiting tracker status: 1 cancellation absorbed by buffer activation; risk Low for Friday; one more cancellation triggers cohort-shrinks-to-4 protocol.

**Signed:** Jamie (founder, PM), 2026-06-02 16:50 PT.

**Tuesday closed. Sketches uploaded as Sketch A/B/C/D to shared Figma board for Wednesday's heat-map.**
