Automation – The Key Benefit

Software provides the speed, the accuracy, the repeatability, the security – they all exist because of automation. These in turn provide the “real-world” benefits or “bottom-line justifications” to a business. But these benefits are just an effect of the primary benefit of software – automation. Software automates tasks, processes, behaviours in a business. This automation is justified if and only if it brings in increased productivity to the business.

Lot of software projects fail today, and the reason for them is improper or insufficient automation. A business invested heavily in a ERP software to find out that it lacked the flexibility of workflow management that was required. The business had to change its own workflows so that they could be handled by the software. This in turn caused decrease in the productivity, finally hitting hard on the revenue. The root cause of this lies in the incomplete information, flexibility in the workflow management was not considered when the investment was done.

Let us look at definition of automation: “automatically controlled operation of an apparatus, process, or system by mechanical or electronic devices that take the place of human organs of observation, effort, and decision“, Merriam-Webster Online Dictionary. This definition implies that successful automation depends on:

  • complete information about the process or system to be automated.
  • the appropriateness of the process – a good automation of a bad process will still result in undesired output.
  • implementation of the automation.

The first two points focus on the information or requirements gathering activity, if not done right, it will result in an unsuccessful automation. Before the automation starts, the appropriateness or correctness of the processes involved should also be assessed. Businesses should realise that investing in software is an automation initiative, for which a second look at the processes might be required.

In the real world, some supplementary information should be considered

  • perceived ROI
  • business constraints like budget, existing skill set, maintainability
  • future roadmap

This information can factor not only into technical decisions, but management decisions like whether the automation initiative should be phased out. All these factors can help in deciding path for the implementation. With the tremendous number of options available in technologies, these factors can help in making a better selection.

Last but not the least, the software itself does not provide the benefits, its usage does. It is of paramount importance to make sure that the business uses the software in the right manner. Training is as much a factor in the success as is the implementation. A good help documentation and training can really make the automation successful.

Technorati tags: , , ,

Copyright Abhijit Nadgouda.

3 Responses to “Automation – The Key Benefit”

  1. Abhijit Nadgouda @ iface » Blog Archive » Theory Of Constraints And Software Concerns Says:

    […] TOC tells that an organization can benefit if its constraints are targeted and resolved. If a software has to be beneficial, it has to follow the same way. The key benefit of software is automation – automation of processes. TOC, through its focus on constraints, which are part of processes in an organization, typically leading to BPR. Use of TOC in Business or System Modeling can lead to right automation of these optimized processes which will provide maximum benefit to the organization. […]

  2. Abhijit Nadgouda @ iface » Blog Archive » Requirements Are Important Says:

    […] Most of the times businesses decide that they want to start using a software because they think that it will solve their problems. However, the problems are only the symptoms. It is important to gather more information so that the diagnosis can be successful and the right cure can be proposed. Especially in today’s age, softwares are not just adopted by businesses, softwares become integral to execution of the business processes. However, the software can provide the perceived Return On Investment (ROI) only if the automation attacks not the problems, but the root causes of these problems. To be able to do that it is imperative to gather more information – which is the requirements gathering. […]

  3. Abhijit Nadgouda @ iface » Software Development Is Like Running A Restaurant Says:

    […] Having said all this, running a restaurant is still a metaphor. The biggest difference is that the software development is about automation that is expected to serve for a longer time. This is what makes it complex, it is expected to serve for a time in which the customer’s needs and requirements keep changing. […]

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: