Ishikawa Fishbone Diagram

// CAUSES • EVIDENCE • STATUS • EXPORT

A whiteboard for working out causes. It does not find the root cause, and online boards are stored on a hobby server. The diagram shows what your team typed and the status you gave each cause. In online mode, everything on a board is sent over HTTPS, stored, and visible to everyone on the board and to the server operator. Online boards are not open yet; solo mode never contacts a server. Open for the full scope limits.

What this tool does not decide

It draws and counts. It does not test, rank, weigh or determine a root cause.

  • "Verified" and "ruled out" are your team's claims, recorded as typed. Nothing on the page checks them against data.
  • A cause on the diagram is a hypothesis until your own data supports it, and a tidy diagram is not evidence.
  • The practice checks look at wording and structure only. A diagram with no notes under "Check these" can still be wrong.

Not a regulated or official record

Do not use a project or a board as the record of a corrective and preventive action (21 CFR 820 or ISO 13485), an ISO 9001 nonconformity, an 8D report, a workplace injury or incident investigation, a patient safety event review, or any record a regulator, auditor, insurer or court may ask for.

  • There is no validated audit trail, no electronic signature and no Part 11 control.
  • History keeps only the last 500 entries, and it can be lost.
  • Export what you need and file it in a system that is fit for that purpose.

Causes about people

Write causes about conditions, not individuals. A diagram names whoever you type, everyone who sees it can read that, and an exported or kept copy may be disclosed later. Avoid names, performance judgments and disciplinary matters entirely.

What happens to the data

  • Solo mode stores nothing on any server. Projects stay in this browser's storage, and clearing site data deletes them. Export a project file to keep a copy.
  • Online boards are planned and not built. When they open, a board's contents, the name the site owner gave each member and the time of each edit will be stored on Cloudflare under the operator's account, deleted one year after the last edit (up to three years if a champion extends it), or sooner when a champion deletes the board. The site owner's list will hold each member's email address, name and the hash of their access phrase. How long platform backups are kept has not been confirmed and will be stated here before boards open.
  • Online, nothing will be end-to-end encrypted, and the operator will be able to read what is stored.

The full description is on the privacy page, and it governs where this summary is shorter.

Access, roles and locks are not confidentiality

  • Online, only people the site owner listed will sign in, and only members a champion added will open a board. But every member can read everything on it.
  • A champion can limit downloads, which removes the buttons but cannot stop a screenshot or a member saving the page from their browser. A copy is outside anyone's control once downloaded.
  • The access phrase is a throwaway made for this tool and is not a password: never reuse it elsewhere, and never type one of your own passwords in its place. A shared access phrase makes the history name the wrong person.
  • A lock stops edits on an online board. In a project file it is only a label anyone can remove, which is all it is in solo mode.

Never put this in

  • Personal information about anyone. Health information. HR, legal, disciplinary or safeguarding matters.
  • Trade secrets or information under a nondisclosure agreement. Export-controlled technical data (ITAR, EAR).
  • Credentials, details of an unpatched security vulnerability, or customer data.

Snapshot links carry the whole diagram inside the link. Anyone who gets the link can read it, it cannot be revoked, and it is a fixed snapshot that does not follow later changes. Treat a sent link as public.

Other people edit too

On an online board, any member will be able to change or delete anything that is not locked, including your entries. A merged project file takes whichever side you chose for each difference. Check an exported copy before you rely on it.

No availability or durability guarantee

Online mode will run on a personal account as a hobby project. It can be slow, unavailable, read-only or discontinued, access can be withdrawn, and boards can be lost without notice. Browser storage can be cleared at any time. Keep a copy of anything that matters.

Fill in the parts and the problem is written from them.

State the problem as it is seen, not a solution: "Short shots on cavity 3", not "Need a new nozzle".

Solo in this browser, no server contacted

These stay in this browser and do not change exports of other people's copies.

These travel with the project, so every export of it looks the same.

Double-click a cause on the diagram to edit it, or drag it onto another bone. On a phone, edit in the outline.

Outline

Enter adds a line, Tab indents, Ctrl+Enter asks "why?". Escape leaves the outline.

Statuses are your team's claims, not the tool's findings. Online boards will be stored on a hobby server and visible to everyone on them. The diagram draws and counts what was typed; it does not test, rank or determine a root cause. Used at your own risk. See the full disclaimer at the top of the page.

    How to use

    1. What a fishbone is for

    A fishbone, or Ishikawa, diagram lays out the possible causes of one specific problem, sorted into groups, before anyone fixes anything. The problem sits in the head on the right; each bone is a category; each line on a bone is a cause, and each level below it is one more "why?". It is not a root cause verdict, a list of solutions, or a list of people to blame.

    2. Your first diagram in five minutes

    1. Write the problem in Problem (the head), above the diagram.
    2. Open Setup, pick a Template and press Add its categories, or add your own with Add category under the outline.
    3. In the Outline, type a cause under a category. Enter adds the next line, Tab indents it, and Ctrl+Enter adds a "why?" under it.
    4. Mark what you have checked with the status menu on each line, and write the evidence in the panel that opens below the outline. Outline in the toolbar hides or shows it.
    5. Use Export for an SVG, a PNG or a print, and the Project menu to save a project file.

    3. Writing a good problem statement

    Say what is wrong, where, when, and how much, as it is seen. Good: "Molded housings have short shots on cavity 3 since October, 4% of parts." Not good: "Need a better mold" (a solution) or "Quality problems" (too vague to test). The Problem statement helper has a field for each part. A question also works, as the Alberta Medical Association's guide uses: "What causes appointments to start late?"

    4. Running a session

    Before: invite the people who do the work, pick who runs it (the champion), and write the problem.

    During: list ideas first; the Brainstorm, not yet sorted example shows them waiting in the Unsorted bin. Sort them onto bones without discussion, then look at the sparse bones; the Late pizza deliveries example leaves one empty on purpose. Under each cause, ask "why?" until the answer is specific enough to test a change and measure its effect (IHI's stopping rule); the Nightly backup example goes five deep. Watch for fixes worded as causes and for "human error" with nothing under it; the Patient wait example shows both the flag and the chain you get by asking why. Unsorted also works as a parking lot for issues to come back to.

    After: give causes owners, gather data, mark each verified or ruled out with its evidence (the Short shots example), and export. For a process, the Invoices paid late example uses the steps as bones.

    Silent brainstorms and votes are planned for online boards.

    5. Marking causes

    • Not examined (thin line, no mark): nobody has looked yet.
    • Suspected (dashed line, question mark): worth testing.
    • Verified (thick line, bold text, check mark): your data shows it contributes.
    • Ruled out (gray line, struck-through text, cross): your data shows it does not.

    Write down what was checked, when and with what result, such as "Flow test 2026-10-14: nozzle 3 at 62% of the others". A verified cause still needs a test after the fix: the problem should go away.

    6. Working with others without going online

    In the Project menu, Export project file, send it, and have the other person import it, edit, and send it back. Then use Merge a file into this one: anything only in their copy is added, and for each item you both changed you pick a side. Two files with nothing in common are offered as a new project instead. A lock in a file is only a label; the merge lists any that were removed.

    Share as link packs a snapshot into the link for a quick look. Anyone who gets it can read the whole diagram, it cannot be taken back, and it never updates.

    7. Online boards (coming)

    Not built yet. The plan: the site owner keeps a list of email addresses, and each person on it gets a generated access phrase of seven words. It is not a password: never reuse it anywhere, and never type one of your own passwords in its place. A champion creates a board, adds members by exact email, and everyone on it edits at the same time. Boards are deleted one year after the last edit unless a champion extends them.

    8. For champions (coming)

    On an online board a champion will lock items, branches and the whole board, freeze it for a review, accept or decline status proposals, and hand the role over. In solo mode you can already set item and branch locks from the panel below the outline; they travel in the project file as labels.

    9. Keyboard shortcuts

    In the outline (use Cmd for Ctrl on a Mac):

    KeyDoes
    EnterNew line below, at the same level
    Tab, Shift+TabIndent, outdent
    Ctrl+EnterNew "why?" under this line
    Ctrl+Shift+Up, Ctrl+Shift+DownMove among siblings
    Ctrl+Shift+1, 2, 3, 0Suspected, verified, ruled out, clear
    Up, DownPrevious or next line
    Backspace on an empty lineDelete the line
    EscapeLeave the outline
    Ctrl+Z; Ctrl+Shift+Z or Ctrl+YUndo; redo

    On the diagram: arrow keys move between causes in outline order (Left goes to the parent, Right to the first child), and Enter edits the selected cause in the outline.

    10. Formats

    Outline text: an unindented line is a category; each indent is one more "why". effect: text (or a first line # text) is the head, preset: 6M picks a template, and kind: process the kind. End a cause with [verified, @Owner]; the tags are [suspected] or [?], [verified] or [v], [ruled out] or [x]. A line starting > under a cause is evidence, and // starts a comment. A backslash keeps the next character as plain text. Bullets are stripped when you paste, and anything the reader had to guess is listed with its line.

    Mermaid: the ishikawa-beta syntax from Mermaid 11.12.3, which is still beta. Statuses and owners are written after each cause in brackets. CSV: one row per cause. Project file: everything, including history and locks.

    11. Where your data goes

    In solo mode, nowhere: projects are kept in this browser, and no request is made to any server for them. Exports and links are made in the browser. See the privacy page.

    Share as link

    • Anyone who has this link can read the whole diagram. There is no password and no way to take it back. Links get forwarded, pasted into chats, and saved in email and browser history, so treat it as public once sent.
    • This is a snapshot of the diagram as it is now. It will not update when you change your project, and changes made by whoever opens it do not come back to you.

    The link carries the diagram, statuses, owners and evidence. It does not carry the history or deleted items. Some chat and email tools shorten or break long links, so open it once before sending it.

    Edit as text

      Merge a file

        Are you sure?

        Attributions and licenses

        Space Grotesk

        The page font, vendored as a Latin subset so a PNG export can carry it.

        License: SIL Open Font License 1.1. Read the license. Source: github.com/floriankarsten/space-grotesk

        Category lists

        Each template names the source its list was copied from, in the help under the Template menu.

        Privacy