Skip to main content

Action Oriented Workflow, workforce emancipation, maximized value landscapes lead to the future we must have.

A recent article indicated in a chart some serious issues facing the American economy specifically but the global economy in general. It focuses on the short term maximization that is the inherent pull for corporations and how that mantra leads businesses to take a relentless approach to cost cutting which includes cutting costs in terms of the salary and other compensation given to employees.

 In a response to a thread started to discuss this article I posted the following that described again from some new angles why Action Oriented Workflow technology allows people to maximize their inherent value and work across their value landscapes. I felt it was worth transcribing into a formal blog post so here it is: What AOW does is it allows performance evaluation to be properly modulated by social cues only so much as needed to complete initiatives begun.

Ideally merit and performance evaluation are linked 1 to 1 and the couple are linked to one simple concept "action", humans take actions....machines take actions but up until my solution no system was designed to granulate action of any type across business processes. When you do that you now bring to life a new landscape of data that you can then make all kind of powerful predictive measures against. Predictive measures that remove the need for people to manage people and instead allow ones action history to be a guide to how new actions are routed to you. Facebook has seen the light...they have a system that also granulates action in terms of verbs that can be defined on their system for the building of semantic relationships between user behaviors on their platform...it is an idea that is a subset of what AOW does.

 https://developers.facebook.com/docs/opengraph/creating-action-types/

 Where Facebook stops by defining actions in a free semantic way important to linking behaviors...AOW goes on to automatically mine those actions and the linking can include semantics (as Facebook) or it can include physical behavior.

 A perfect example, in the real world a bar is a beautiful demonstration of a dynamic action landscape. If you go into a bar all manner of activity is being performed on the part of the establishment. Bar Tenders are ordering, preparing and taking money for drinks. Waiters are moving to tables to take drink and food orders in the back of the house various staff are preparing food items. Actions are popping off across the business creating data history that is connected to physical objects and people performing them across a temporal scale.

I see these patterns as signals on multiple graphs that plot the relative performance of the actions by the agents across time...these data can be used to find interesting information out about the business....like who is your best bar tender to call if you need a worker on a wednesday at 9 pm?? who is your best chef? how many drinks does Jane make on average in an hour compared to Peter when customer density is the same? All of this information can inform making the business more efficient...AOW allows a business (like a bar) to surface those actions and then monetize them.

The startup I am working on now is presenting a different business from bars but I have my eye on bars and restaurants as a business RIPE to be disrupted. In fact...if you truly "get it" you'll realize ALL existing businesses.....physical or virtual are subject to the advantages of AOW modelling and efficiency creation. Now do this across all the areas in which you can perform "action" across your competence sets and you now can earn compensation in parallel ( for all business roles that don't require physical presence) instead of in the serial fashion we have been lulled into believing was the only model.

 The machines should be the only things doing the judging of our competence...people fuck that task up every time. So now what is the result of an AOW ubiquitous future? You get people working on their own schedules...across all the things they do well...being able to opt into work and then have that work magically COME TO THEM based on their past performance...and then when they are satisfied opt out and go to the beach...and the next time they come back the system remembers they are awesome and again drowns them with work. Multiple employers...multiple roles...multiples lines of compensation...derived on THEIR schedule...without nepotistic or biased selection in the picture.

 Anything we can do to stop ad hoc automation (the regime we are in now and that Amazon is employing) from turning people into low paid robots must be in place and that is what AOW is all about...by allowing us to maximize our inherent value by working across our value landscapes we increase our ability to derive compensation even as automation is deployed to eliminate entire classes of jobs. It's been the hardest task I've ever done to evangelize this new way of looking at workflows...looking back on the work of my heroes in engineering and science to do the same with the Universe they invented I understand the reasons...the first thing people do is try to find holes in an idea...but AOW is not a dream...it's a working platform that simply needs to be put in the cloud...again I am glad to have finally gotten the serious attention of those that can make that happen now that the need for it is a daily stress to people slowly being cut out of jobs by automation deployed *the old* way. Kind of ironic isn't it?...that the answer to the automation "problem" is MORE automation but deployed in a more efficient manner to benefit the agents as well as the workflows they work in.

Comments

Popular posts from this blog

On the idea of "world wide mush" resulting from "open" development models

A recent article posted in the Wall Street Journal posits that the collectivization of various types of goods or services created by the internet is long term a damaging trend for human societies.

http://online.wsj.com/article/SB10001424052748703481004574646402192953052.html

I think that the author misses truths that have been in place that show that collectivization is not a process that started with the internet but has been with us since we started inventing things.

It seems that Mr. Lanier is not properly defining the contexts under which different problems can benefit or suffer from collectivization. He speaks in general terms of the loss of the potential for creators to extract profit from their work but misses that this is and was true of human civilization since we first picked up a rock to use as a crude hammer. New things make old things obsolete and people MUST adapt to what is displaced (be it a former human performance of that task or use of an older product) so as to main…

Highly targeted Cpg vaccine immunotherapy for a range of cancer

Significance?


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…