Skip to main content

Simulating social for the heck of it...is silly.


In a recent article:

"At $16,000 each, the Beam isn't cheap. But Suitable Technologies says it was designed with features that make "pilots" and "locals" feel the remote worker is physically in the room: powerful speakers, highly sensitive microphones and robust wireless connectivity. The company began shipping Beams last month, mostly to tech companies with widely dispersed engineering teams, officials said. "Being there in person is really complicated—commuting there, flying there, all the different ways people have to get there. Beam allows you to be there without all that hassle," said CEO Scott Hassan, beaming in from his office at Willow Garage in nearby Menlo Park."

-- My wager, and the reason I invented Action Oriented Workflow is that systems like this are simply continuing the inefficiency of the old paradigm of stateful work processes.

This is silly, $16,000 per unit to try and simulate a social element that for many workers is not required continuously. So the payment is made for a continuous system that is used in a discontinuous fashion. It's incredible waste.

Instead, much greater value I posit can be derived per worker by providing user opt in social tools, the video chat, the audio calls, the chat and mail interaction...and then letting the work related actions route around the workers where ever they happen to be...this is what Action Oriented Workflow makes possible. People opt in, do work, the system merits them objectively and sends work to them where ever they happen to be when they opt in. No one is pressured to be any where or do anything they didn't explicitly "raise their hand" to do.

I am betting that most companies will find far more value in implementing such a system because the focus is taken off of making social interaction easy for humans who may not want it (big problem) and puts the focus on making the work actions as hyper mobile and social (across the organization) as possible.

The analysis of tele present work forces was something I started devoting serious mind time too, nearly 7 years ago as I was in the midst of implementing the code for the Action Oriented Workflow. The future I saw then and have now made possible by building...involves minimal interactions in office environments which will increasingly be restricted to the agents in business that make critical deals for the entire organization. Pointed social interaction coupled with high value deriving agents will end up being much more efficient and useful than making social the goal and spending money to achieve it just for the sake of it without  any knowledge as to why that would be most beneficial in a quantified manner.

Links:

http://sent2null.blogspot.com/2008/03/increasingly-telepresent-workforce.html

http://sent2null.blogspot.com/2011/09/action-oriented-workflow-maximize-your.html

http://sent2null.blogspot.com/2009/04/agilentity-architecture-action-oriented.html

Comments

Popular posts from this blog

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…

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…