If Business Process Re-engineering (BPR) is new to you, here is a quick summary. Michael Hammer and James Champy were proponents of BPR in the mid 1990s. It was a way to having an incisive look at your current process; identify value and non value adding activities (vis a vis process objectives) and rethink your process for magnified gains - we are talking of 500 % + improvements. Often would not only the process change, but also surrounding entities and capabilities. Organizational change, standardization and IT as a cornerstone were big topics then. Sounds familiar now? If you are into AI implementations, you would start seeing the equivalence. Businesses compete more fiercely driven by advantages of process change, where boundaries are in turn pushed by technological advances. And the impact is felt all over. Like any other change, this can be managed reasonably to everybody’s advantage. Two key words that were important then, and are so now - the two eternal Es - Expectations and Execution. Expectations from and for the exercise, people, processes, management, external entities and other impacted stakeholders need to be not only set, but actively managed. Execution if done to meet expectations and continually learn and reset expectations accordingly, can pay rich dividends. AI is about learning from past data. Why not learn from past experiences like BPR for implementing AI! And that should take you one step closer towards implementing practical AI. #abhayPracticalAI #artificialintelligence #AI
top of page
Search
Recent Posts
See AllWe have discussed a few aspects of defining a prediction end point. Here is one more. Always work with your business users to understand...
160
While defining the prediction rule end point, I have often seen the spec designed such that the data science behind it becomes logic...
180
The end result of a requirement gathering exercise for AI is often the end point definition for the desired prediction rule. Defining the...
100
bottom of page
Comments