Work with Claude to transform dense process documentation into flowing visual diagrams that show how your system actually works. Through conversation, you'll map out decision points, alternative paths, and volume distributions—turning dense documents into clear visualizations your team can use in real-time.
I'm uploading our enterprise software implementation playbook—42 pages of customer onboarding procedures that nobody can navigate in real-time. We have a few different paths based on data quality, integration capability, resources, and deployment readiness.
Can you help me visualize this so we can see the whole system in one view and understand how customer volume distributes across the different paths.
Create a Sankey flow diagram with organic curved paths. Make it screenshot-worthy with professional, bold typography and a natural color palette. Enable interactive zoom and pan with smooth Bezier curves. Apply Tufte-level information design.
Provide your process document so Claude can identify the structure, decision points, and flow logic that make up your procedure to map it out visually.
Upload a file of your procedure document. Click the (+) button in the chat bar to browse through your files, or alternatively, drag and drop files into the chat box area.
Enable Extended Thinking for Claude to think through more complex processes and produce higher quality outputs.
Claude analyzes your process documentation and transforms it into an interactive Sankey flow diagram that visualizes implementation pathways and volume distribution across paths. Each implementation phase becomes a clickable card that reveals the detailed documentation behind it.
Done! I've created a flowchart of your customer onboarding process. Let me show you what I've mapped out.
Here's what the visualization shows:
The Flow Structure
I've used flowing bands where the width shows you volume—so you can immediately see that most customers (62%) take the primary path, while smaller percentages take the alternatives:
Interactive Phase Cards
Click any phase card to see detailed documentation including:
Next steps: Review the flow with your team and let me know if any decision points need adjustment or if there are edge cases I should add.
Using connectors like Mermaid Chart, Claude converts artifact diagrams to editable formats, generates shareable links, and provides portable code for cross-platform embedding and team collaboration
Can you convert this artifact flowchart to Mermaid.js format using the Mermaid Chart connector? I'd like an editable playground link to share with my team and the raw Mermaid code so we can embed it in our docs or export to other platforms.
Claude can expand on specific parts of the diagram while keeping other sections at their current level of detail, providing deeper understanding where you need it.
The implementation phase has a lot more steps than shown. Can you expand that section to include: technical discovery call, sandbox setup, data mapping session, initial configuration, testing phase, and training? Keep the other sections at their current level of detail.
Claude can reorganize flow direction and apply color coding systems to separate different owners or stages in your diagram.
Can you reorganize this to flow left-to-right instead of top-to-bottom? Also use colors to distinguish different team owners—sales in blue, customer success in green, implementation in orange.
Your process document doesn't need perfect formatting. Claude identifies decision points, parallel workflows, and conditional logic from narrative descriptions, bullet lists, scattered emails, or step-by-step instructions. Upload what exists and Claude can map the underlying process structure. You can continue to work with Claude to revise and refine the process as needed.
Set up a dedicated Project for process mapping. Then, upload your process documents and flowchart standards to Project Knowledge. When procedures change, start a new conversation in that Project and describe the updates—Claude maintains context on existing diagrams and your conventions, so it updates specific sections while preserving consistency. This transforms flowcharts from static snapshots into living documentation that evolves with your organization, rather than starting from scratch each time something changes.
