Every session I run with a client or a team ends the same way. Someone takes a photo of the whiteboard. That photo sits in a group chat or a Slack channel doing nothing until someone (usually me) manually translates it into a document. Redrawing diagrams. Retyping lists. Reorganising sticky notes into something readable. Two weeks ago I uploaded a whiteboard photo to Claude and asked it to turn it into a structured document. Not describe what was on it. Turn it into an actual usable output: headings, bullet points, action items, decisions listed separately from ideas. It worked well enough that I sent the output directly to the client without touching it. I’ve been manually transcribing whiteboards for two years. The prompt that works: I’m uploading a photo of a whiteboard from a working session. Organise what you can see into a structured document: - Main topics or themes as H2 headings - Points under each topic as bullet points - Any action items in a separate section at the end with the format: [action] / [owner if visible] / [deadline if visible] - Any questions or unresolved items in a separate section - Any decisions that were clearly made in a separate section Where handwriting is unclear, write [unclear] rather than guessing. I’d rather know what you couldn’t read than get a plausible-sounding wrong word. Where the spatial arrangement on the whiteboard seems meaningful (things grouped together, arrows connecting items), try to preserve that structure in how you organise the output. Output as a clean document ready to share. The “write [unclear] rather than guessing” instruction is the critical one. Without it Claude will confidently fill in unclear handwriting with plausible words. With it you get honest gaps you can fill yourself. Works beyond whiteboards. Three other versions I use: Meeting notes on paper. Photograph handwritten notes from a notebook or notepad, ask Claude to extract them into typed structured notes with action items separated. Faster than typing them up yourself and more consistent about catching action items you’d otherwise miss. Sticky note sessions. Photo of a wall covered in sticky notes from a brainstorm. Ask Claude to group them by theme, identify the main clusters, and suggest a hierarchy. Turns a visual mess into a structured analysis. Handwritten forms or tables. Photo of a handwritten form, data sheet, or table. Ask Claude to extract the data into a structured digital format. Works well for field notes, inspection forms, manual data entry sheets. Things worth knowing: Photo quality matters significantly. Good lighting, no glare, camera directly facing the whiteboard rather than at an angle. A bad photo produces bad output regardless of how good the prompt is. Take 30 seconds to get a clean shot. Complex diagrams with arrows and boxes don’t always translate perfectly into linear document structure. For diagrammatic content, ask Claude to “describe the diagram and its relationships” rather than “turn it into a document.” Different output format, more accurate representation. Multiple photos work. If the whiteboard was too large for one shot, upload multiple photos and tell Claude “these photos are different sections of the same whiteboard, treat them as one session.” The shift, if it’s useful: photos of physical working sessions have always been a dead end in most workflows. They get taken, shared, and forgotten. Treating them as inputs rather than archives changes what you can do with the work you’ve already done. I put together the full document workflow toolkit - PDF extraction, file creation, whiteboard transcription, spreadsheet cleanup, and the 10 tools I cancelled after building this system. Full doc with the cancelled tools and replacement here if interested. If you only test one version of this this week, try the whiteboard prompt on the most recent meeting photo sitting unused in your camera roll. That photo is probably already there. submitted by /u/Professional-Rest138
Originally posted by u/Professional-Rest138 on r/ArtificialInteligence