Presentations
Hierarchy tree slides
A tree slide shows that one thing sits above several others, or that one question splits into a small number of answers. Ten layouts carry both readings: three are organisational charts, and seven are decision or taxonomy trees with a root, branches and details.
Org charts: three levels, and the caps
Three of the ten are organisational: a root with two to five direct reports, a wide chart with exactly six reports in one row, and a four column hex layout for departments. The renderer draws three levels: the root, up to six items, and up to four children under each of those. The org chart layout also pins its diagram kind, so it cannot be switched to another diagram. A larger organisation needs either several slides or the text only team directory in the profile role.
Decision trees: forks with consequences
Four layouts are built for a decision rather than a hierarchy: a binary fork with two branches and six details, a yes or no flow with two verdict cards and four consequence chips, a three path splay with a trade off chip per branch, and a root with three branches and six details. What makes these better than a bullet list is that each branch carries its consequence, which is the part people argue about.
Taxonomies: root, branches, leaves
Three layouts describe a structure rather than a choice: a classic root with three branches and six leaves paired two per branch, a horizontal root with branches and detail chips, and a radial hub with six flanking branches. The pairings are fixed by the layout, so six leaves means exactly two per branch. Writing to that constraint is usually clarifying, because a taxonomy with uneven branches is often two ideas wearing one diagram.
Tree against flowchart
A tree splits downward and never rejoins. A flowchart can loop, merge and branch on conditions, and the process role carries one with four node shapes, an automatic layout button, drag to connect and a cap of 20 nodes, or 12 on the decision flowchart layout. If your diagram needs an arrow that goes back up, it is a flowchart. If every path ends where it started going, it is a tree.
How the AI picks this slide
Tree is chosen when the brief describes a structure of people or a branching decision. The fill writes the node labels within the template's budgets and will not invent names, so an org chart from a brief with no names comes back with roles rather than people. Because the org chart's diagram kind is pinned, swapping to a different diagram means swapping the layout.
How it works, in three steps
Step 1
Decide: hierarchy or decision
Three layouts draw an organisation, four draw a choice with consequences and three draw a taxonomy.
Step 2
Add the slide from the library
From Library on the slide rail with the Role filter set to tree. Ten layouts come back, plus one that lists tree as a secondary role.
Step 3
Write the consequence, not just the branch
On a decision layout each branch has a chip for the trade off or the next step. That chip is the slide's whole value.
Step 4
Check the depth before you commit
Three levels is the maximum: root, six reports, four children each. Anything deeper needs a second slide.
The full walkthrough with screenshots is in the guide Add charts, maps and diagrams to slides.
Limits worth knowing
- The org chart renders three levels only: a root, up to six items and up to four children under each.
- The org chart layout pins its diagram kind, so it cannot be switched to another diagram type.
- Branch and leaf counts are fixed by the layout, including the two leaves per branch pairing.
- A tree cannot merge or loop; a process that rejoins needs the flowchart in the process role.
See it on a finished piece
Questions people ask
How many tree layouts are there?
Ten carry tree as their primary role, and one more lists it as a secondary role. Three are organisational charts and seven are decision or taxonomy trees.
How deep can an org chart go?
Three levels: the root, up to six first level reports and up to four children under each of them. For a bigger structure, split it across slides or use the text only team directory layout in the profile role.
Can I drag nodes around?
On the flowchart, yes: nodes drag, ports connect and an automatic layout button tidies it. The tree and org chart layouts draw from their data rather than from positions you set.
What is the difference between a tree and a flowchart?
A tree splits and never rejoins. A flowchart has real edges and can loop or merge, with four node shapes and a cap of 20 nodes, 12 on the decision flowchart layout.
Can I put headshots on the org chart?
Not on the org chart layouts, which are text nodes. The profile role has ten layouts built for headshots, including a team row and a founders and advisors grid.
Will a tree survive a PowerPoint export?
In the editable export the diagram artwork stays a picture, but its labels are emitted as native text boxes, so the names can still be edited in PowerPoint.
Make your own presentation
The button opens the generator with this use case already described. Change the wording to match yours, generate, then edit anything you like.
Create a presentation with OneCraftRelated pages
Add a logo to slides
One control puts your brand mark on the deck. It lives in the same panel as the transition and footer settings, applies at deck level, and offers exactly the decisions worth making: what to show, how big, and on how many slides.
Q&A slides
The slide that says Questions? in the middle of an empty screen is doing one job badly. There are six layouts here, and the useful ones do a second job: they give the room something to ask about, or they leave your contact details on screen while people are still looking.
Diagram slides
A diagram here is a list of labelled items and a decision about how to arrange them. Twelve arrangements are available and they all read the same list, so a funnel becomes a pyramid without you retyping anything.
More finished work of this kind is on the presentation examples hub.
Written and checked by the OneCraft team. Last checked .