The Step Method allow you to identify the driver behind each workflow step in Puzzle, whether it’s run manually by a person, automated, or powered by an AI agent. This feature gives you quick, visual clarity into how each step is executed, helping teams understand at a glance who—or what—is responsible for moving work forward as organizations embrace the future of operations.
Benefits of Using Step Method
Clarity: Instantly identify the execution method behind each step, whether it’s manual, automated, or AI-driven, allowing teams to understand the workflow
Alignment: Ensure your workflows reflect modern operations by clearly showing the balance of human, automated, and AI-powered steps.
Efficiency: Quickly spot areas where tasks are automated or driven by AI, streamlining operations and supporting future-ready processes.
Methodology
Within the Puzzle product, there are various approaches to map processes — some users map where each step represents very granular increments of the process (i.e a GET pull from a system).
Whereas other users use steps to represent a collection of actions (i.e generating a proposal), whereby a collection of actions are taken to complete the step.
There are pros and cons to each mapping approach. For example, if you're using the diagram for system change management, the granular maps come in handy to understand where data is being passed across systems.
But, if you're using the diagram to present the overarching process to non-technical stakeholders, the high-level overview may be better suited because the back-end technical steps often don't concern the front-line team.
This context is relevant to the Step Method and the Step Type indicators because the options within each feature imply how certain processes are mapped.