by Debbie Wilson | July 1, 2019 | Comments Off on “Goodbye Business Analysts, Hello Cloud Analysts” by Paul Schenck
Up until the last 5-10 years, on-premise ERP solutions dominated the IT landscape. A key role in supporting those systems was the Business Analyst. Since that time though, cloud has emerged as the new platform where most ERP functionality will be delivered. With that a new role is also coming that will replace the Business Analyst, the Cloud Analyst.
Before I discuss the Cloud Analyst, it is worth looking into why the Business Analyst title fit the last generation of ERP support. “Business” came first in the title and everywhere else. A part of the naming is that ERP changes originated in the Business. Internal end users would make their request to an Analyst, thus placing the Business Analyst in the role of order taker.
The old Business Analyst would:
- Perform requirements gathering as a follow up to a business request.
- Categorize changes as customizations (deliver new or modified functionality) or a break fix (correct previously functionality that no longer works) or a project (large size).
- Consolidate changes into a request backlog and work with Line of Business leaders (LoBs) to establish a priority list.
- Work with developers on hand-off of requirements, perhaps even doing configuration or light development themselves.
- Do testing such as unit/dev, functional and coordinating UAT.
- Coordinate with a release manager and help with communications to impacted users until the change went live, thus ending the change cycle.
This cycle and Business Analyst role places IT in a reactive position. IT becomes the organization of ‘no’ since not all change requests can be made, or at least made as quickly as the business wants them. This role and model caused IT to be seen as a cost center instead of a leader and value driver. The cloud along with the Cloud Analyst role can position IT as an innovation leader.
Moving to the cloud, the old title of Business Analyst no longer fits because most new functionality now starts in the cloud with best practices developed by the vendor. It does not start in the business. “Cloud” is where everything starts, including the job title. All major ERP vendors now spend the vast majority of their R&D dollars on their cloud solutions. The title of Cloud Analyst is now most accurate.
The new Cloud Analyst will:
- Spend much more time researching upcoming changes from the vendor in new cloud releases.
- Understand how that new functionality can be applied to the current business processes at their organization.
- Focus more on the wider technology ecosystem, such as integrations, data and analytics, and related cloud releases.
- Help with the testing which will become much more frequent as cloud vendors release updates rapidly.
- Proactively recommend activation of new features and best practices to the business users, thereby cementing the position of IT as an innovator and leader.
The Cloud Analyst role will be vital in allowing CIOs to shift the organization mindset so that spending in IT is seen more as an investment which can drive exponential productivity gains. There is a term for this in the military, it is a “force multiplier”. When assets and technology are deployed in conjunction with soldiers, it multiplies the effectiveness of that fighting unit. An example would be that 100 soldiers on foot have a force level of 100, since that is the base level. When the same 100 soldiers fight equipped with some jets, they have the force level equal to 500 soldiers on foot, making the force multiplier of the jets x5. With the right ERP system, employees should be multiplying their productivity. Just as jets allow soldiers to literally take to the clouds, the IT department should use the cloud to exponentially enhance productivity. On the front lines will be the Cloud Analyst.
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.