Prioritize use cases

After you finish the interviews, list the use cases, and capture metrics, the next step is to rank the use cases by priority. For the top ten use cases, include a mix of easy use cases that are quick wins and more complex, high-value use cases that might take longer to automate and orchestrate.

To determine the use case priority, consider the following points:

  • Business impact — how much you can save or how much sooner the business can produce revenue or productive work
  • Deadlines for when a critical business event is planned or will occur, such as onboarding a new acquisition or customer
  • When a strategic initiative is scheduled to roll out, during which the workflows can ensure success
Recommendation

If you are just starting with BMC Atrium Orchestrator and do not have critical or strategic events driving adoption of orchestration immediately, begin with a lower-priority use case that has minimum impact on the business. This way you can accomplish the first workflow rollout without critical business impact from errors. Additionally, you gain insight into success factors for your organization that can be applied to the successful adoption of orchestration of more important processes in subsequent projects.

Where to go from here

Develop-formal-designs

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*