Workflows rarely exist in a vacuum. The output of one role frequently serves as the input for another, creating a chain of dependencies that define how an organization functions. When a content strategist finalizes a brief, a designer must receive and interpret it. Traditionally, these handoffs occur in the dark, with each party understanding only their side of the transaction.
By cross-referencing a coworker's flow node, you illuminate these shared boundaries. The Lab allows you to see exactly how a colleague has mapped a shared process step, offering a window into their methods and experiments. This practice of communal creation ensures that workflows built by one individual become a resource for the entire team, transforming isolated tasks into a cohesive, interconnected system.
Assignment
Identify a process step in your current workflow that directly connects to a colleague's work. Find their corresponding flow node in the Lab and create a cross-reference from your node to theirs. Write a brief note on what you learned from observing their approach to the shared step.
Learning Objectives
- Identify shared process steps across different roles within your team.
- Cross-reference a coworker's flow node to integrate their work into your own process.
- Apply the principle of communal creation to build more robust, interconnected workflows.
Communal Creation
The idea that workflows built by one team member become available to others as a reference. This transforms isolated tasks into a shared, evolving repository of organizational knowledge.
Cross-Referencing Nodes
Linking your process steps to those of a coworker when workflows overlap. For example, connecting a content strategist's 'write brief' node to a designer's 'receive brief' node.