Create a clean, shareable company org chart in under an hour using ProcessOn’s web editor. This guide shows two fast paths—starting from free templates or building from scratch—plus collaboration, export, verification, and troubleshooting tips.
- Difficulty: Beginner-friendly
- Time: 20–60 minutes (depending on team size)
- You’ll need: A free ProcessOn account, your roster (names, titles, reporting lines), optional role photos/icons
Why this works: ProcessOn supports organizational charts in both its mind map and flowchart editors, with structure switching, themes, real-time co-editing, and multiple export formats confirmed in ProcessOn’s own tutorials and product pages, such as the official overview of organizational chart methods in mind maps and flowcharts by ProcessOn in the article “What is an organization chart? Concepts, types, tutorials.”
Step 1: Set up and find a free template (fastest path)
Sign in and open the template library.
- Go to the official “ProcessOn Template Library.”
- Search for “organizational chart” or browse the Org Chart category. Templates tagged as “ProcessOn Free” are free to clone and edit.
Pick a starting point.
- Choose a layout that resembles your company’s structure (flat startup, functional departments, or matrix). If you’re unsure, a simple hierarchical template is easiest to adapt.
Clone the template to your workspace.
- Open the template and select the option to clone/duplicate. You’re now in the editor with an editable copy.
Replace placeholder content.
- Double-click a node to edit name and title.
- Use the on-canvas add controls to insert sibling roles (same level) or child roles (direct reports). From experience, it’s safer to add children via a node’s built-in controls so connectors attach automatically.
Adjust the layout.
- Drag to reorder nodes. If branches look cramped, apply a different theme or spacing preset. ProcessOn’s org chart structure and style options are discussed in the ProcessOn tutorial “How to draw the organizational chart.”
Checkpoint: Can you scroll from the top node (e.g., CEO) to each department head without a connector crossing through other nodes? If not, try a different theme or regroup roles by department.
Step 2: Build from scratch (two options)
You can build an org chart without templates in either the mind map editor (quick structure control) or the flowchart editor (maximum layout flexibility).
Option A: Mind map editor with organizational chart structure
ProcessOn confirms you can switch a mind map to an org chart structure using the right-side “Structure” control; see ProcessOn’s overview in “What is an organization chart? Concepts, types, tutorials.”
Create a new mind map.
- In ProcessOn, choose New → Mind Map. Name your file.
Switch to the organizational chart structure.
- In the editor’s right toolbar, find Structure and choose an organizational chart layout. This enables auto-branching and a top-down view.
Enter the top role.
- Click the central/top node and enter your highest-level role (e.g., CEO). Keep labels short: “VP, Marketing” reads cleaner than long descriptions.
Add direct reports.
- Use the node’s add controls to insert child nodes for each direct report. Use sibling nodes for peers at the same level.
Build out departments.
- Continue adding children for each manager. For large teams, sketch the top three levels first, then fill in deeper layers.
Style for readability.
- Apply a theme and adjust fonts, colors, and line styles. ProcessOn’s tutorial on org chart creation explains inserting icons and images into nodes, which helps roles stand out; see the ProcessOn guide “How to draw the organizational chart.”
Group by function (optional).
- Color-code department branches (e.g., blue for Engineering, green for Sales) to improve scanning. This is especially helpful for functional structures; ProcessOn describes functional org patterns in “What is a functional organizational structure.”
Why choose this option: You get quick auto-layout and easy branch growth—ideal for conventional hierarchies and fast edits.
Option B: Flowchart editor for full control (great for matrix)
The flowchart editor gives manual placement and connector control—useful for matrix structures where people report to both functional and project managers. ProcessOn’s flowchart tutorial outlines the basics of placement and export in the article “How to make a flow chart.”
Create a new flowchart.
- Choose New → Flowchart. Name your file.
Place role shapes.
- Drag rectangle shapes for roles onto the canvas. Enter the role title and name.
Connect reporting lines.
- Use connectors to link each report to their manager. For a matrix, use distinct line styles or colors (e.g., solid for functional, dashed for project) and include a small legend.
Align and distribute.
- Select a row or column of roles and use alignment tools for neat spacing. Group related department areas visually.
Style and finalize.
- Apply consistent fonts, colors, and borders. Keep contrast high so titles remain legible when printed.
Why choose this option: Maximum flexibility—great for matrix or nonstandard orgs that don’t fit an auto-structured layout.
Step 3: Make it readable and leadership-ready
Follow these practical styling moves:
- Keep labels short and consistent: “Role, Name” or “Name — Role.”
- Use color to signal departments, not to decorate every node.
- Reserve photos or icons for top roles or department heads so the chart doesn’t get heavy.
- Check spacing: Nodes should have enough breathing room so connectors don’t cross.
- Prefer a top-down layout with high-level roles aligned horizontally for quick scanning.
Tip: ProcessOn supports inserting icons or pictures into nodes and switching styles/themes, highlighted in its org chart tutorials; see the ProcessOn article “How to draw the organizational chart.”
Step 4: Collaborate and control access
ProcessOn supports real-time co-editing and permission control—inviting colleagues to view or edit your org chart. The ProcessOn getting-started guide states that files support multiple people editing simultaneously with permissions you can set; see “ProcessOn Getting Started Guide.”
Open the Share/Collaborate dialog.
- In the editor, click Share (label may vary). Choose to invite by link or by account/email.
Set permissions.
- Select View or Edit access. When inviting managers to review, View is often sufficient; grant Edit to the HR/ops owner only.
Test the link.
- Copy the share link and open it in a private/incognito window to confirm the exact access others will see.
Use comments/notes for change requests.
- Ask reviewers to comment inline with corrections. This avoids version sprawl.
Note: For an additional description of exporting or sharing after editing, ProcessOn’s tutorial on creating mind maps also mentions generating an online sharing link; see “Mind map creator: how to make a mind map.”
Step 5: Export for slides, print, or wiki
ProcessOn documents multiple export options. The Mind Maps product page notes image format exports like PNG/JPG/SVG (and commonly PDF via tutorials); see “ProcessOn Mind Maps.” Flowchart tutorials also mention exporting to PDF/PNG; see “How to make a flow chart.”
Open Export/Export As.
- In the editor, choose Export/Export As.
Choose the right format.
- Screen use (Slack, Confluence, Notion): PNG or SVG.
- Slides (PowerPoint, Google Slides): PNG/SVG. For crisp scaling, prefer SVG if your destination supports it.
- Print or PDF handouts: PDF for best text clarity and pagination.
Check quality before sharing.
- For images, confirm pixel dimensions are large enough for your use (zoom to 100% to check crispness). For print, use PDF and preview page breaks.
Caution: Some third-party sources mention additional export targets (e.g., DOC/PPT/CSV). Availability can vary by diagram type and plan—verify in your account before relying on them. A neutral overview mentioning such options is the OMR product page “ProcessOn – product review.”
Which structure should you choose?
- Functional hierarchy (most common): Group people by department, then show teams within each function. ProcessOn explains functional orgs and provides examples in “What is a functional organizational structure.”
- Flat startup: Use a shallow hierarchy template and keep labels concise. Highlight leads rather than adding too many levels.
- Matrix organization: Consider the flowchart editor for manual layout. Use distinct connector styles for functional vs. project reporting.
From experience, if you’re uncertain, start with a simple hierarchical template, then adapt as your company’s structure becomes clearer.
Verification checklist (run this before you share)
- Every role has exactly one manager (unless your design intentionally shows matrix dual-reporting).
- Manager spans are realistic (e.g., avoid 10+ direct reports unless necessary) and fit on one screen width.
- Department color-coding is consistent and explained (legend or clear labeling).
- At 100% zoom, names and titles are legible without squinting.
- Share link opens with the expected permissions in an incognito window.
- Export looks crisp: PNG/SVG for screens; PDF for print.
Troubleshooting: quick fixes that save time
Nodes overlap or look cramped
- Mind map org structure: Try another theme, increase spacing in the right panel, or temporarily collapse deep branches while editing.
- Flowchart: Use align/distribute on selected nodes; widen the canvas and regroup departments.
Connectors look wrong or detach
- Mind map: Add child nodes from the parent’s controls so lines auto-attach; avoid free-floating lines.
- Flowchart: Reconnect using shape anchor points; use straight connectors when possible to reduce crossings.
Text overflows nodes
- Increase node width or reduce font size slightly; shorten titles (e.g., “Sr. Product Manager” instead of a multi-phrase description). Wrap on two lines where needed.
Export looks blurry
- Use PDF for print. For images, export at higher resolution or use SVG for infinite scaling (when supported). Avoid upscaling in third-party apps.
People can’t access the chart
- Re-open Share and confirm View vs. Edit permissions; regenerate the link if needed. Always test in a private window.
Privacy and change safety
- Avoid publishing personal data (photos, personal emails, phone numbers) in public links.
- If you must share broadly, prefer view-only links and remove sensitive fields.
- For reorgs or hiring changes, duplicate the file before making major edits so you can roll back if needed.
Quick-start recap
- Fastest: Clone a free template from the “ProcessOn Template Library,” replace content, and apply a clean theme.
- Flexible: Build in the mind map editor and switch to the org chart structure for auto-layout; see ProcessOn’s overview “What is an organization chart? Concepts, types, tutorials.”
- Custom: Use the flowchart editor for matrix or unusual layouts; see “How to make a flow chart.”
- Share and export: Test permissions (Getting Started guide) and export PNG/SVG/PDF per “ProcessOn Mind Maps.”
With these steps, you’ll have a clear, on-brand org chart you can maintain as your team grows—without paying for specialized software.