Free fishbone (Ishikawa) diagram maker

How it works, step by step

Before entering information, decide which decision or discussion the project should support. Choose a title that identifies the objective and use consistent vocabulary across activities. For team work, agree on criteria before assigning scores or responsibilities. Verifiable descriptions are more useful than broad labels such as improve everything or resolve issues. Record questions in notes so that assumptions are not presented as conclusions.

Use Example to explore fictional data. The editor saves the current project and creates another after confirmation, preserving previous records. New starts an empty document; Duplicate keeps the data in an independent copy. You can return to any project using the saved projects selector. An example is a starting point for understanding fields, not a universal recommendation for your organization.

Begin with simple fields and open advanced mode when you need details. Add an item, observe the result, and check that the classification matches what you intended to represent. Field changes are applied when confirmed or when leaving the field. On boards, drag cards or use the movement selector; in tables and diagrams, the button bearing an item's name opens its editor. Review warnings before sharing and keep a copy of the original project when comparing alternatives.

1. Describe the observed problem and choose a category template.
2. Add causes and sub-causes to each category and note your evidence.
3. Flag investigation priorities and export PNG, SVG or PDF.

Method, interpretation and limitations

Define an observable problem and organize causes by category. The 6M template includes method, people, machine, material, measurement and environment. Choose services, education, four categories or customize. Causes and subcauses form a hierarchy without cycles. Causes are hypotheses: the diagram does not prove causality. Record evidence and highlight investigation priorities.

The completed example lets you explore the method with fictional data. Before applying it to a real decision, replace names, values and notes with information checked in your context. Record what remains unknown as well. A short problem statement and an explicit review criterion are often more useful than dozens of entries without a clear question.

Use simple mode to begin and open advanced mode when you need details, filters or imports. Duplicating a project creates an independent copy for exploring alternatives without losing original assumptions. Undo and redo apply to the open project; export a backup before deleting projects or clearing browser data. Local saving is not collaboration and other people do not receive your changes.

Check the preview after major changes. For printing, choose A4 or Letter and the orientation suited to your content. Your browser can save as PDF; entered names and text remain as written while only the document structure follows the selected language. Visual files help presentations, while JSON restores the complete project. Document limitations alongside results to prevent misleading interpretations.

Example

The table in this guide uses the same source as the Example button. Compare its records with the editor to understand how input becomes a classification, table or diagram. IDs are internal references used in relationships; they do not indicate priority or quantity. Examples are fictional and should be adapted to your context, the people involved and the information you actually know.

After completing the document, ask someone who did not edit it to explain what they understand. This reading helps identify missing activities, ambiguous descriptions and conclusions that depend on unrecorded information. Check each item's details rather than judging only the visualization's appearance. Where numbers are involved, review units, comparison periods, scoring criteria and currencies before interpreting totals or positions.

Choose a format suited to your purpose. JSON preserves the complete project for further editing. CSV and Excel, where available, make records usable in spreadsheets. SVG and PNG appear in tools with visual exports; these files do not restore editable fields. For PDF, select Print / PDF and check paper, orientation and pages in your browser's dialog. Report structure follows the page language, while names and entered content remain in their original language. Exporting does not add a signature, certification or formal approval.

Saving, export and privacy

Automatic saving keeps up to 50 projects per tool in this browser, with up to 200 items in each project. Data is local: clearing site data, using another profile or changing devices can prevent access. Export a JSON backup of every important project and keep your own copies. Undo and redo help during the current editing session but do not replace permanent version history or external backups.

Entered content is not sent to the tool's server. Someone using the same browser profile or holding your exported files may still access it. Avoid unnecessary personal information on shared computers. The editor does not offer simultaneous collaboration, synchronization between devices or recovery through a Quima account. When transferring items to another tool, the copy is independent and does not receive future changes from the original.

If storage is blocked or its quota is exceeded, the interface shows an error. Preserve your work as JSON before closing the page. When importing, review the preview and accepted, rejected and ignored record counts. Importing creates a new project; never assume an imported file is correct without reviewing its context and the criteria used to produce it.

Import UTF-8 CSV or XLSX with the exported headers in the current language. Dates use YYYY-MM-DD. JSON preserves all fields. Files up to 5 MB and 200 items; formulas are rejected. Review before creating a new project.

Copying creates an independent project. Name, owner, date, tags and notes are preserved when compatible. GUT uses the problem as an action. Nothing is removed or synchronized after copying. In PESTLE → SWOT, factors become opportunities or threats in a reviewable draft. The saved SWOT remains unchanged until you explicitly save.