BoardSnap is an iOS app that reads a fishbone (Ishikawa) diagram whiteboard — problem statement, category bones, and cause spines — and produces a structured cause analysis organized by category.
The fishbone diagram — also called the Ishikawa or cause-and-effect diagram — organizes potential causes into standard categories: People, Process, Equipment, Materials, Environment, Management (or the 6Ms: Man, Method, Machine, Material, Measurement, Mother Nature). The visual structure forces systematic thinking. Instead of brainstorming causes randomly, you fill each bone of the fish with causes specific to that category.
Fishbone diagrams are standard in manufacturing quality management, healthcare process improvement, and operations problem-solving. They're most useful when the problem is well-defined and the team needs to ensure they've considered all possible cause categories, not just the obvious ones.
The diagram's branching structure — main bones, sub-bones, and detail spines — is dense and hard to transcribe accurately. The categories and their associated causes need to be preserved as a structured set, not flattened into a bullet list. A flat list of causes loses the organizational logic that makes the fishbone useful.
Horizontal spine pointing right. At the right end, draw the fish head — write the problem effect inside it. This is the problem you're diagnosing. Draw four to six diagonal bones extending from the spine — these are the cause categories. Standard 6M categories: Man (People), Method (Process), Machine (Equipment), Material, Measurement, Mother Nature (Environment). Write the category name at the tip of each bone.
For each category bone, brainstorm specific causes. Write each cause as a sub-spine extending from the main bone at a 45-degree angle. Use sticky notes on the bones if you have them — easier to add and reposition. One cause per sub-spine. Be specific: 'No training documentation' not 'training issues.'
For each cause sub-spine, add tertiary spines for the underlying reasons. 'No training documentation' → 'Documentation owner left company.' 'Equipment calibration off' → 'Calibration done monthly, not weekly as spec requires.' The tertiary spines are where the root causes live.
After all bones are filled, vote on the causes most likely to be contributing to the problem. Each person gets five dots total — place them on the causes they believe are most significant. Circle the top vote-getters.
The circled causes become your investigation priorities. Write a box in the corner: 'Investigate first:' followed by the top three to five causes. These become the immediate corrective actions or data collection tasks.
Open BoardSnap. The fishbone has a horizontal spine, category bones with labels, cause sub-spines, and circled priority causes. BoardSnap AI reads the bone-and-spine structure, assigns causes to their categories, and identifies the circled priority items.
A structured cause analysis organized by category: each category (People, Process, Machine, etc.) is a section with its associated causes listed as bullets and sub-causes indented under them. The priority causes (circled) appear in a 'Priority Investigation' section at the top. The output is a structured quality report — paste it into a CAPA (corrective and preventive action) document or an improvement project brief.
A quality team drew a fishbone with six bones for a recurring product defect. Machine category had four causes; Method had three; Materials had two. The vote concentrated on two causes in the Machine and Method categories. BoardSnap produced the full categorized analysis. The quality manager used it as the basis for a CAPA report submitted to the QMS.
The engineering team adapted the fishbone for a software context: People / Process / Technology / External / Data / Environment. Five incidents in three months with a common thread. The fishbone session revealed that two Technology causes and one Process cause were appearing in every incident. BoardSnap structured the categories and the vote results. The team prioritized three improvements in the next sprint.
A clinic ran a fishbone session with doctors, nurses, and admin staff. Six category bones. The Measurement bone was nearly empty — the clinic had almost no data on where time was being spent. That absence was itself a finding. BoardSnap's output included a note that the Measurement bone was underpopulated — an observation that wouldn't have been visible in a simple brainstorm.
Yes. The 6Ms are defaults — if your context needs different categories (People / Process / Technology / External for software teams, for example), write those names on the bones. BoardSnap reads whatever labels are on the board, not a fixed list of categories.
BoardSnap AI reads the branching structure — which sub-spines connect to which main bones — based on physical proximity and directionality, not just angle. Text written at the ends of spines is attributed to the nearest main bone. Writing cause labels at the spine tip (not along the spine line) gives the best results.
Yes, but dense bones need clear spacing between sub-spines. If causes overlap on the board, readability drops. For very dense bones, write the cause labels at the end of each sub-spine, not along the line.
Snap the board, ship the action items in ten seconds.