Breadboard (UI Flow Diagram)
Drawing out every state of a flow is too time-consuming, so we’ll use words for everything instead of pictures. That's Breadboarding. A lightweight notation for user flows.
Breadboarding is like state diagram. It allows us to play out an idea and judge if the sequence of actions serves the use case we’re trying to solve. Once we get to a place where we play through the use case and the flow seems like a fit, we’ve got the elements we need to move on to start defining the project more clearly.
There are times when text alone isn't enough, and you need to sketch out an idea. A drag and drop interface of some sort comes to mind. They can be complicated enough that breadboarding alone wouldn't be sufficient.
For that, use the Fat Marker Sketching technique. Both techniques are quick and cheap enough to do often. That said, they are ideal for supporting conversations in the earliest stages of an idea for a solution. Visually externalizing representations of our mental models is imperative to continuously maintain a shared understanding of the work.
This template was created by Matt Lane.
Get started with this template right now.
SIPOC Template
Works best for:
Agile Methodology, Strategic Planning, Mapping
A SIPOC diagram maps a process at a high level by identifying the potential gaps between suppliers and input specifications and between customers and output specifications. SIPOC identifies feedback and feed-forward loops between customers, suppliers, and the processes and jump-starts the team to think in terms of cause and effect.
UML Communication Diagram Template
Works best for:
Software Development, Mapping, Diagrams
Most modern programs consist of many moving parts working to a precise set of instructions. With a communication diagram, you can visualize exactly how those parts work together, giving you a clearer understanding of your program as a whole. What’s more, the diagram leaves spaces for expanding the network of relationships as your product grows and evolves. A communication diagram is a vital tool in any software designer’s arsenal.
Fishbone Diagram Template
Works best for:
Operations, Diagrams, Workflows
What is the best way to solve any problem your team faces? Go straight to the root. That means identifying the root causes of the problem, and fishbone diagrams are designed to help you do it best. Also known as the Ishikawa Diagram (named after Japanese quality control expert Kaoru Ishikawa), fishbone diagrams allow teams to visualize all possible causes of a problem, to explore and understand how they fit together holistically. Teams can also use fishbone diagrams as a starting point for thinking about what the root cause of a future problem might be.
UML Sequence Diagram Template
Works best for:
Software Development, Mapping, Diagrams
Analyze and showcase how external entities interact with your system using a sequence diagram. Get a bird’s-eye view of your work processes, business functions, and customer interactions using this diagram. Also, identify any potential problems early and solve them before implementation.
5-Circle Venn Diagram Template
Works best for:
Diagramming, Mapping, Brainstorming
Discover how Miro's 5 Circle Venn Diagram Template can simplify complex decision-making processes. Learn how to create, customize, and share your diagrams for effective visual collaboration. Transform brainstorming sessions with real time, remote teamwork.