Skip to main content

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.


WorkNetz AOW presentation slides


Fried Rice said…
I like the analogy w/ Task Rabbit a lot but want to learn more about AOW applications in plain terms
Fried Rice said…
Esp. regarding distributing work globally...

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.

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…

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…

Waking Out: A proposal to emerging ethical super intelligence safely.

The zeitgeist of Science fiction is filled with stories that paint a dystopian tale of how human desires to build artificial intelligence can go wrong. From the programmed pathology of HAL in 2001 a space odyssey, to the immediately malevolent emergence of Skynet in The Terminator and later to the humans as energy stores for the advanced AI of the Matrix and today , to the rampage of "hosts" in the new HBO series Westworld.

These stories all have a common theme of probing what happens when our autonomous systems get a mind of their own to some degree and no longer obey their creators but how can we avoid these types of scenarios but still emerge generalized intelligence that will leverage their super intelligence with empathy and consideration the same that we expect from one another? This question is being answered in a way that is mostly hopeful that current methods used in machine learning and specifically deep learning will not emerge skynet or HAL.

I think this is the …