While there’s nothing wrong with being strategic, thinking on too large of a scale is a common pitfall of overly ambitious automation projects. Taking on too much strategic work too early runs a high risk that the organization doesn’t see any business value for a long time. As a result, developers will most likely get completely stuck in shaping a complex platform without understanding its use case.

Instead, try to break down larger strategic initiatives into component parts, starting with the most urgent or important projects first. Here’s one way to approach it:

• Start with Pilot Project: The goal of this project is to define and validate both architecture and stack. Very often, this pilot project is set up as a proof-of-concept (PoC). However, it is important to go-live with that pilot to really learn about all aspects of the workflow solution throughout the full software development life cycle (SDLC).
• Accelerate to a Lighthouse Project: Soon after running a successful pilot, you should tackle a lighthouse project. This project should have a broader, but still realistic scope which can be better leveraged to show off architecture, tooling, and value of workflow automation to other people and teams within your organization.
• Progress to Broad-Scale Transformation: Leverage the lessons learned from the lighthouse project, empowering the people on that project team to run a Center of Excellence (CoE) to break down silos across teams and drive organization-wide change.  Read On: