You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Flowcharts are one of the most versatile diagram types. Companies use flow charts to document complex business processes in Confluence or Jira. Software engineers use them to envision data flow. Hipsters post them online to amuse each other with their snarky witticisms 👓🐈
Regardless of your needs, a flowchart maker (we will be using Gliffy for Confluence!) will facilitate the process of creating flowcharts in Confluence or Jira.
Following are the six most commonly seen types of flow charts, each explained and illustrated with a template — click any image to launch in Gliffy (or find in templates on our Confluence or Jira app) and get started creating a flowchart of your own.
One of the more common uses of the flowchart is to map out a process. These process charts can be troubleshooting guides to problems, templates for efficient action, or step-by-step walkthroughs for any series of events or decisions.
One process flowchart template example would be a phone tree. See how each option in the process leads to its own chain of possible actions and decisions?
If not, press 0 to speak to a customer service representative. We’re here to help.
Swimlane diagrams show how interdependent procedures unfold in parallel, presenting a collection of distinct but linked process flowchart examples. Swimlane diagrams mimic a lap pool, dividing each action/decision thread into its own distinct lane — one for each operator or group of operators.
In a swimlane diagram, each lane contains flowchart elements arranged in sequence. Arrows connect these elements, and arrows cross lanes as responsibility transfers back and forth between operators. In this way, multiple processes come together to form a whole and a single process gets split into assigned tasks that teams can easily track.
As you guessed, workflow diagrams are a flavor of flowchart that businesses use to direct workflow. They visually lay out the steps of a task so that complex processes become easy to follow, one step at a time.
Workflow diagrams can include traditional flowchart symbols and/or icons. They can also include annotations of specifics, such as how long an action should take or what resources are required.
Impact maps are a specialized sort of flowchart template that illustrate the connections between specific deliverables and business goals. They accomplish this task by utilizing a four-column format, as seen in the example template below.
Each impact map starts with a goal. Each goal leads to one or more ‘actors’ — actors being people or groups of people with the ability to influence the outcome of the goal. For example, if your goal were to sell movie tickets, possible actors would include theater staff, studio marketing departments, cinemagoers, and actual Hollywood actors.
A third column lists ‘impacts’. Impacts describe how actors’ behavior might change in order to help or hinder the achievement of the goal. So for the goal ‘sell movie tickets’ and given the actor ‘cinemagoers’, possible impacts could be ‘see films more frequently’ and ‘subscribe to loyalty program’.
Finally, an impact map lists the deliverables that you propose in order to create the impacts that will guide the actors to support your goal. For the impact ‘subscribe to loyalty program’ for example, a deliverable might be ‘free popcorn special offer’.
When you create an impact map, you’re clearly showing how your deliverables connect to an overarching goal via a chain of dependencies.
Context diagrams and other data flow diagrams show — in flow chart form — how data moves through an information system. They are by nature system design and analysis tools, but they can be used to illustrate a wide range of processes.
Unlike other flowcharts, context diagrams and data flow diagrams don’t indicate the sequence of the depicted events. Instead, they only represent the exchange of data and the directionality of that exchange.
There are rules to making a flowchart. These include agreed upon definitions for the symbols and pro diagramming tips and various flowchart styles and formats.
But there are no flowchart police.
If you want to use the basic language of the flow chart to communicate without adhering to any of the above-listed standards — as we have in the example below — that’s perfectly fine.
One of the beauties of the flow chart template is its flexibility. At Gliffy, we’re here to help, not to inhibit.
Click any image above to launch it as a template in Gliffy and you’ll be well on your way to creating your own flowchart 🤘
❤️ The Gliffy Diagram Team
Product @ Gliffy
3 accepted answers