Process Automation / Business Rule Optimization is a nearly untouched field for large, existing software driven companies.
For goal N, where N is an amalgam of small processes, what can we do to isolate, automate, and optimize the process?
Everyone is hyper focused on generic ML solutions, but there's it has been a hell of a lot easier to hand-code solutions to problems in existing mid-to-large scale businesses that are looking to alleviate a process pain point. If you have the brains to determine some basic ROI ballparks, you can make back engineering hours fast if you can either increase the output of your business, or decrease the required people to accomplish that output.
There's some fields that touch upon this, like Dev-Ops, but this is a more strict definition of 'operations', in that I'm referring to the non-technical people.
The impact of this practice is amplified by two major factors;
1. Quantity of work
3. Difficulty of work
If you have high quantity of N, small optimizations are compounded across all the work centers.
If you have highly difficult work, reducing the time it takes to 'handle' or 'create' output can be reduced.
This idea ties in to a fantastic book, 'The Goal' by Eliyahu M. Goldratt.
Being in 'hot tech' is cool, but mastering old concepts is valuable to businesses rigid to change. As the number of established companies that leverage tech for a majority of their work grows, the need for brains that are capable of process improvement with a scalpel, rather than a chainsaw.
For goal N, where N is an amalgam of small processes, what can we do to isolate, automate, and optimize the process?
Everyone is hyper focused on generic ML solutions, but there's it has been a hell of a lot easier to hand-code solutions to problems in existing mid-to-large scale businesses that are looking to alleviate a process pain point. If you have the brains to determine some basic ROI ballparks, you can make back engineering hours fast if you can either increase the output of your business, or decrease the required people to accomplish that output.
There's some fields that touch upon this, like Dev-Ops, but this is a more strict definition of 'operations', in that I'm referring to the non-technical people.
The impact of this practice is amplified by two major factors; 1. Quantity of work 3. Difficulty of work
If you have high quantity of N, small optimizations are compounded across all the work centers. If you have highly difficult work, reducing the time it takes to 'handle' or 'create' output can be reduced.
This idea ties in to a fantastic book, 'The Goal' by Eliyahu M. Goldratt.
Being in 'hot tech' is cool, but mastering old concepts is valuable to businesses rigid to change. As the number of established companies that leverage tech for a majority of their work grows, the need for brains that are capable of process improvement with a scalpel, rather than a chainsaw.