Skip to main content

Workforce Emancipation: An awakening in the Zeitgeist

It's been bitter sweet watching the conversation on jobs finally start shifting to where I'd been saying it was going to go since I wrote about the telepresent workforce in 2006.

At the time I'd already invented Action Oriented Workflow in an "explicit" form, that required a workflow modeling processing to define the various stages of work and the individuals that would be delegated to them. I knew that a more efficient way would be possible if I could have the system learn from past routing activities and so set a plan in my development to build an "implicit" routing algorithm at some point.

I didn't get to do that until 2011, after a year of working at McGraw Hill and being *miserable* at what I was seeing in the office. The terrible waste of humanity...

Every day I was tasked to get up at 6 am and prepare myself to be at work for 9, so that I could sit at a computer and supposedly be "productive" for 8 continuous hours.

The absurdity of this expectation needs to be fully realized to understand why I've been evangelizing AOW and what it does for all of US.

If we could be emancipated from location and time in our knowledge work then we'd be free to multiply our skill across multiple assignments FOR multiple employees. This was the vision as expressed in that original post...which is notable as it did not mention AOW at all.

At the time I felt it was important to keep shut with my idea, that others might "steal" it and build systems to do the same things but it turns out that it has been even more difficult for technologists to even understand the value proposition until NOW...

until that recession in 2008 smacked the fuck out of people into realizing that there had to be a better way for humans to utilize their EXISTING *value landscape*, that humans had better figure out a way to work simultaneously for companies and clients in London , Moscow, Kiev and New York.

When I finally decided to come out with the AOW idea I realized I'd better do it in as public a way as possible and so I started a blog and began blogging about technology and other things of interest and in my areas of research. The AOW  white paper which had been proprietary and in house at Apriority LLC was turned into a post and put online for all to see.

The fear of stealing the idea was replaced by my confidence that the world was so behind the ideas that it would take years for people to even recognize the value of it (or admit to the viability of letting people work from wherever on their own time schedule..which even today I see silly counter arguments to...) it's extra ironic that the post went online in 2009, at the height of the economic implosion that the world was going through at the time.

The great adjustment was in progress and would finally get other minds to start thinking about work as I'd been thinking about it already for nearly 10 years....and had built (not was building) HAD BUILT a solution.

Here we are 2014, the zeitgeist is alive with this and that about the meaning of work...and I am shaping a startup around the AOW technology and the ADA (action delta assessment) extension of that technology I completed in 2011.

Today, "marketplace" services like amazon's mechanical turk, taskrabbit, elance, freelancer and others all are jumping on the bandwagon of trying to enable companies to find free make outsourcing easier...but that is not what emancipates the *workforce*.

A workforce already has a corporate home, AOW is for both outsourcing (to build marketplaces for outsourcing is trivial on the platform) and ..what I call INSOURCING, liberating existing workers to derive their best work on their time schedule ...not just reaching out to a pool of hungry nodes looking to do atomic units of your work. Insourcing also allows companies to retain the integrity and privacy of business processes while enabling those companies to continuously harness their global workforce. However, insourcing is where ADA was most critical, the holistic discovery of work patterns and then automatic routing of work to available agents was a key requirement and that was achieved in the second half of 2011 when ADA, the implicit workflow and work routing algorithm API was implemented in AOW.

In my last post on the blog I described the importance of retaining ideas until they were ready to be implemented and drive adoption.

If you can't execute it...don't talk about it unless you want others to try to execute it, well AOW and ADA are executed and I am excited to show how they are going to enable human workforces to be emancipated one vertical at a time now that the world finally sees the importance of such ideas.

Took you guys long enough. ;)

I look forward to presenting the first vertical disruption which leverages AOW and ADA to solve a very present work related problem to all human beings via the first service to be presented by WorkNetz.

Are you ready to be emancipated from work??



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 …