Now that you have a clear understanding of what you’re doing, you can start to think about how and where you are going to do it. You need to identify where each step of your process will take place: will you build everything in Coda or will your users do some tasks in other tools?
You will also need to identify the level of interaction with other tools in each step. There are 3 levels of interaction:
Separate: The step is fully performed on the other tool.
Example: A design team creates a mock up in Figma
Integrated: The actions are performed in Coda, but the data is stored in another tool.
Example: An engineer updates his Jira issues in Coda, which then syncs back to Jira.
Coda only: The step is fully stored and performed in Coda.
Example: A product manager updates a status on a project tracker in Coda.
Why identify other tools?
By gaining a clear understanding of where each step is performed within a workflow, it becomes easier to identify potential integration opportunities. When data points are utilized or modified in both Coda and another platform, it indicates a chance to leverage Packs to help maintain alignment between the platforms and minimize any potential challenges or discrepancies in data.
Objectives
Identify what tool will be used to power each process step
Decide which parts of the workflow will take place in Coda
