AOW: Shooting for the Moon instead of the Mountain

A recent Medium article exposes some of the drawbacks inherent in the business model of the TaskRabbit service.

TaskRabbit is very much in the space that my Action Oriented Workflow mines for all possible work interactions but only for the subset of physical labor of a temporary and nature. They are a subset of the much larger space that AOW enables harnessing with both physical and knowledge work (this being the much bigger piece of the pie that WorkNetz will primarily focus on)...that said, one of the key features of the AOW technology is the ability for delegated agents to REJECT work they do not wish to do OR to even simply never get work in their cue at all if they are not electing to receive it.

I saw this as a critical requirement of the system for two reasons:

1) If you give them the ability to reject they retain that sense of ownership, they are indeed their own boss and work on their own schedule as most people want and with Taskrabbits pivot are not denied.

2) Allowing people to reject work allows that work to move with alacrity to those who are available and want to do it, if you've got a global pool of options then this becomes MORE certain the larger your organization and or the larger your pool of possible contractors are.

:I explain why this is critical in my posts on Action Oriented Workflow but the sound bite can be had by flipping through this presentation deck I prepared last year to describe how AOW enable systems will work.

WorkNetz AOW presentation slides

With the implementation of the autonomous work routing of the ADA (Action Delta Assessment) algorithm the determination of who gets a delegated action is done purely by the historical algorithm and those preferred nodes are virtual managers by virtue of the fact that their past performance has made them stars to the system and they still have the ability to re-delegate (reject work) that they get in their queue.

This virtual or dynamic management is the only type of management that should exist I posit, a real time assessment of ability to redelegate work trumps the manual distribution of labor that is done when people are in charge of teams of workers which is rife with opportunity for cronyism to skew results away from what would be ideal for the business. I elaborate on this in the AOW white paper.

When TaskRabbit was announced, I recognized it immediately as a play that was tacking toward what I'd already built with AgilEntity in the form of the AOW paradigm which generalizes the solution for any vertical physical labor or knowledge work. I considered describing WorkNetz the company I am working on now to present solutions built on the AOW paradigm as: "taskrabbit for everything" at some point...given this shift in their approach, which makes sense given that in any given geographical region, there is a low density of people who can mobilize, are skilled and willing to perform a specific physical task it is clear why as a target TaskRabbit was aiming too low, they built a rocket that only allowed them to reach for the mountain instead of the moon.

Solving the problem for one type of labor (physical) made sense as there would be no need to tackle the much harder problem of generalizing to all types of work actions irrespective of their nature as physical labor associated or knowledge work associated would be a much more difficult task one that I took on and completed when I completed the implementation of the Action Oriented Workflow technology in AgilEntity in 2005.

I chose to generalize the solution for any type of interaction and let the business decide how it is going to provide incentives to the agents it already has...what I defined as "in sourcing". This is critical as it prevents the attrition problem that is described in the article where once a person is set up with a tasker through the service why would they use the service a second time if they can get the direct contact information for that same tasker from the initial interaction? By enabling any existing business to turn all it's employees into an emancipated workforce of contingent laborers who are employees one can harness that existing workforce optimally to make action execution fluid and 24/7 possible and maintain this advantage even as the company grows from 10 to 10,000 "employees" distributed all over the globe.

Links:

https://medium.com/matter/hunting-task-wabbits-c60679bad0f6

WorkNetz AOW presentation slides

the attributes of web 3.0...

As the US economy continues to suffer the doldrums of stagnant investment in many industries, belt tightening budgets in many of the largest cities and continuous rounds of lay offs at some of the oldest of corporations, it is little comfort to those suffering through economic problems that what is happening now, has happened before. True, the severity of the downturn might have been different but the common factors of people and businesses being forced to do more with less is the theme of the times. Like environmental shocks to an ecosystem, stresses to the economic system lead to people hunkering down to last the storm, but it is instructive to realize that during the storm, all that idle time in the shelter affords people the ability to solve previous or existing problems. Likewise, economic downturns enable enterprising individuals and corporations the ability to make bold decisions with regard to marketing , sales or product focus that can lead to incredible gains as the economic

How many cofactors for inducing expression of every cell type?

Another revolution in iPSC technology announced: "Also known as iPS cells, these cells can become virtually any cell type in the human body -- just like embryonic stem cells. Then last year, Gladstone Senior Investigator Sheng Ding, PhD, announced that he had used a combination of small molecules and genetic factors to transform skin cells directly into neural stem cells. Today, Dr. Huang takes a new tack by using one genetic factor -- Sox2 -- to directly reprogram one cell type into another without reverting to the pluripotent state." -- So the method invented by Yamanaka is now refined to rely only 1 cofactor and b) directly generate the target cell type from the source cell type (skin to neuron) without the stem like intermediate stage. It also mentions that oncogenic triggering was eliminated in their testing. Now comparative methods can be used to discover other types...the question is..is Sox2 critical for all types? It may be that skin to neuron relies on Sox2

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 cert

sent2null space

Search This Blog