Which of the following is a question you should ask yourself before approaching a workflow?

• A. What are the reporting requirements?
• B. What is your use case?
• C. What is the instance?
• D. How many instances are we dealing with?

Answer: (B)

Before approaching a workflow, zero in on the use case—the specific problem you’re solving and the outcome you want to achieve. Clarifying the use case guides every design decision: what to automate, what data to collect, which triggers should start the flow, and what success looks like. This keeps the workflow focused on delivering real value, rather than building something generic or overly complex. For example, if the goal is to route new inquiries to the right team with defined response times, you’ll map out who handles each step, which fields are required, and how escalations should work, so the automation directly supports actual tasks. Other considerations like reporting needs or how many instances you’ll run become important later and help validate success or scale, but they shouldn’t drive the initial design.