Skip to main content

Action Oriented Workflow : Emancipated Worker sourcing allows people to maximize their value

The key advantages of action oriented workflow have been specified in this post and the identification of ways in which it can be used to both enable businesses using it to emancipate their workforce and as well enable the emancipated workers to maximize their value should be clear.

A recent set of events have gotten me to thinking a bit more deeply about what role automated inferring systems should play in organizations. From the perspective of some it would seem that AOW based businesses will be responsible for the elimination of many tasks which currently are performed by several layers of humans in the organization who's task it is to run analysis on metrics gathered from their managed teams to determine how to redirect the execution of failing projects or direct the execution of planned new ones. This view is true in so far as such tasks are far more efficiently performed from the business perspective by an automated learning process. Such processes are able to behave in ways that human agents are not, such as:

  • Automated learning of efficient processes involves a perfect memory of past performance executing the minutia of actions against objects of a given type in the examined process. Perfect memory is equivalent to perfect access to acquired data which makes performing new decisions temporally efficient as data gathering need not  be done.
  • Automated learning eliminates the need for the gathering of consensus across multiple agents tasked with performing analysis. Since an AOW based learning agent performs a system wide convergence across all managed object types the optimal future delegation events are present in memory for any new required delegations. The time consuming process that exists in enterprises today of mid level and more senior managers coming together to discuss the results of their analysis to help shape future decisions is not necessary.
  • Automated learning agents by eliminating the bias of selection that attends human based management and delegation processes are free to be purely meritocratic in their selection of delegated agents in the emancipated worker pool, eliminating that bias completely from attempts to execute any business required task removing another potential inefficiency that is an issue in human managed systems.

Beyond these points, it is also true that most people who have been "promoted" to positions where they are managing others and analyzing performance completing tasks rather than doing the tasks would also like to be free to maximize their value scape. As described in the maximize your value post, the personal desire for us to perform across the set of skills that we can competently perform and be compensated for and in our own time frame is what we really as humans want to do. It is no wonder that across businesses the management layers are the ones with the highest levels of burn out and attrition as the continuous demands of needing to manage down level working agents and as well manage the interaction with same level and up level management agents leaves such individuals in a state of continuous bombardment that makes consistent performance difficult. The artificially intelligent work routing performed by systems that employ AOW would take the  burden of this task over and because it does not have the limitations of burn out induction or limited memory of past data metrics it can consistently make the right choice for the actions delegated at the moment and thus over time achieves hyper efficiency.

Individuals in organizations that are displaced are then able to redeploy their value space such that they can deploy multiple areas of their skills as an emancipated worker for businesses instead of as an easily worn out routing node. More people are then enabled to maximize their value and derive personal happiness in their lives as a result.


Popular posts from this blog

Highly targeted Cpg vaccine immunotherapy for a range of cancer


This will surely go down as a seminal advance in cancer therapy. It reads like magic:

So this new approach looks for the specific proteins that are associated with a given tumors resistance to attack by the body's T cells, it then adjusts those T cells to be hyper sensitive to the specific oncogenic proteins targeted. These cells become essentially The Terminator​ T cells in the specific tumor AND have the multiplied effect of traveling along the immune pathway of spreading that the cancer many have metastasized. This is huge squared because it means you can essentially use targeting one tumor to identify and eliminate distal tumors that you many not even realize exist.

This allows the therapy for treating cancer to, for the first time; end the "wack a mole" problem that has frustrated traditional shot gun methods of treatment involving radiation and chemotherapy ...which by their nature unfortunately damage parts of the body that are not cancer laden but …

Engineers versus Programmers

I have found as more non formally trained people enter the coding space, the quality of code that results varies in an interesting way.

The formalities of learning to code in a structured course at University involve often strong focus on "correctness" and efficiency in the form of big O representations for the algorithms created.

Much less focus tends to be placed on what I'll call practical programming, which is the type of code that engineers (note I didn't use "programmers" on purpose) must learn to write.

Programmers are what Universities create, students that can take a defined development environment and within in write an algorithm for computing some sequence or traversing a tree or encoding and decoding a string. Efficiency and invariant rules are guiding development missions. Execution time for creating the solution is often a week or more depending on the professor and their style of teaching code and giving out problems. This type of coding is devo…

AgilEntity Architecture: Action Oriented Workflow

Permissions, fine grained versus management headache
The usual method for determining which users can perform a given function on a given object in a managed system, employs providing those Users with specific access rights via the use of permissions. Often these permissions are also able to be granted to collections called Groups, to which Users are added. The combination of Permissions and Groups provides the ability to provide as atomic a dissemination of rights across the User space as possible. However, this granularity comes at the price of reduced efficiency for managing the created permissions and more importantly the Groups that collect Users designated to perform sets of actions. Essentially the Groups serve as access control lists in many systems, which for the variable and often changing environment of business applications means a need to constantly update the ACL’s (groups) in order to add or remove individuals based on their ability to perform certain actions. Also, the…