Technology can be discussed later

•  Let’s procure the license of an RPA tool. That’s what all our competitors are doing.
•  I attended a Podcast of this amazing tool that can automate stuff across departments.
•  We haven’t used the license we procured last year. The management won’t approve our next budget. Let’s do something about it.
•  My previous organization used this tool to do automate. We should do the same.
•  That conference I attend of XYZ vendor showed some use cases that resonated well with our requirements.

We have all heard these or similar statements and sentiments. Many of us have agreed to them because they came from influencers in the organization. Or because some consultant or salesperson says so.

• Let’s put this in a perceptive of non-IT automation.
• I am a farmer, and I want to plough and seed my fields.
• I want to wash my clothes and dry them too.
• I want to fly from New York to Frankfurt.
• My office is calling everyone back, and I need to commute to office daily now.
• My friend is setting up a factory to manufacture garments – shirts, pants, denims etc.

Let’s purchase this single machine for all the above use cases. This machine will do it all. It will farm, it will wash, it will fly, it will drive on roads, and it will sew the garments too! How amazing is that?

Do you think I am crazy reading this? Wasting time on this page! Huh – Isn’t that your current thought?

I agree, I am getting overboard. Let’s come back to IT now.

How can a single platform be the savior in the name of automation do-it-all then? We all love RPA! It is amazing. And many of us equate RPA to automation. That’s a blunder.

There are just too many tasks that happen in IT and they need to be segregated into groups of similar ones.

The groups club the tasks. The groups then give a clearer picture of what needs to managed and how.

Based on the type, the tool can be decided. But that comes latter, after the analysis is done properly.

That’s why we say – Technology discussion needs to wait.