Visual canvas
Arrange the thinking spatially instead of burying it in a paragraph.
AMS · Connected business workflows
Diagrams — See the thinking. Share the direction.
Map processes and relationships on a visual canvas before they become complicated work.
Who this helps
Teams agreeing how work should move before assigning responsibilities or configuring rules.
The situation
People disagree about when creative work is ready to become launch assets because the review step is implicit.
Fictional example: a process map connects Creative brief, Visual direction, Review and Launch assets. This website example makes no live changes.
Follow the example, step by step
Name the starting point
- What you do
- Place the creative brief at the beginning of the process.
- What changes
- The diagram has a clear starting node.
- Why it helps
- Everyone can agree on what must exist before work begins.
Show the work that follows
- What you do
- Connect the brief to Visual direction.
- What changes
- A connector explains the order of the first two stages.
- Why it helps
- The relationship between input and creative work is visible.
Make review a decision
- What you do
- Place Review between Visual direction and Launch assets.
- What changes
- The decision-shaped node separates preparing work from proceeding with it.
- Why it helps
- The team can discuss what the reviewer needs to decide.
Walk through the whole process
- What you do
- Review the connected path with the people responsible for the work.
- What changes
- The complete map shows the route from the brief to launch assets.
- Why it helps
- You can resolve missing steps before translating the agreement into tasks or rules.
What your team gains
The team has a visible process to discuss, including the decision between preparing work and releasing it.
Make those relationships visible, so the team can discuss the same picture.
Inside Diagrams
Nodes & connections
Show sequence and relationships between parts of a workflow.
Process mapping
Explain a delivery flow, a decision path or a campaign plan.
Reusable context
Keep the diagram accessible as the work develops.
Access controls
Manage who can open and work with a diagram.
Share links
Use the available sharing controls for the intended audience.
Questions and requirements
Will this diagram move tasks through the process?
No. A diagram explains a process. Executable behavior must be configured separately in Automations or performed by the team.
Can other people review the map?
AMS supports diagram collaboration and sharing under the applicable access settings. Diagrams require an eligible paid plan.
Requirements and limits
Diagrams require a paid plan. Drawing a workflow does not itself create an executable automation.
Understand the next tool here
Read how each connection helps before choosing whether to open another page. Moving between tools does not itself configure an automatic handoff.
Projects & tasks — read how it fits
Use the agreed process when your team creates tasks and decides how to track progress.
Give every task an owner, a deadline and the context to move forward.
Fictional example: Nour moves the Autumn launch creative brief from In progress to Review.
Before you use it
Available views and actions depend on your access. Time tracking and automations require an eligible paid plan.
Optional: explore the full Projects & tasks story ↗Automations — read how it fits
Implement a suitable repeated step as a separately configured executable rule.
Turn repeatable decisions into workflows your team can inspect, test and control.
Fictional example: a high-priority task entering In review is assigned to Layla by a configured workflow.
Before you use it
Automations require a paid plan. Triggers and actions are filtered by permissions, scope, connected account capabilities and configuration.
This page simulates a task-status rule locally; it does not execute a server workflow or send notifications.
Optional: explore the full Automations story ↗