Skip to main content

Big Business: Where Innovation goes to starve.





A recent medium post contained the following quote:

"I promise you, my reaction to the project’s cancelation wasn’t “Too bad, let me find my next longshot!” It was more like grief that a year of my life had been wasted, guilt that I’d wasted the efforts of my team, fear of reputation damage, and determination to work on something next time that would actually matter.

As individuals, we have no portfolio strategy — so those 10% odds are no longer palatable. When we fail, most rational people respond by trying to avoid dumb ideas and pick smart bets with clear impact the next time. People who happen to have a hit in their first few tries are even more vulnerable to the belief that they have to succeed every time (and take it harder when subsequent failures inevitably occur.) And that’s it — the dead-end for innovation.

I’ve met a few people who don’t seem to have this reaction (serial entrepreneurs every one of them) and I can’t tell you what makes them react differently or how to learn to be that way. But I do know there aren’t enough of them out there to hire your team exclusively from their ranks."

--- Another factor that ties into this feeling of personal failure and the desire to avoid risk and failure of that sort ever again in the enterprise or in the start up is the social expression of the risk and failure that *each* individual expresses into the organization.

This projection is deadly to an environment where innovation can foster *especially* when people who still imagine success in risky bets are hired. This then means that not only does the past failing impact the individuals in the organization it leaves a sticky social residue that retards innovation on the part of any one new that comes in with genuinely good ideas as they face all manner of systemic push back for their grand ambitions...after all every one there is licking some wound...they've all battened down the hatches and are not going to let any one sink their ship....again.

This is a major reason why I felt a dozen years ago that the social glue (our org chart levels of control) that we use to orchestrate the building of products and services is a huge drain on the very process by these forces that retard against doing anything that sticks the individuals neck out or a teams neck out, or a divisions neck out ...or by multiplication of effect the companies neck out.

I reasoned that there should be a way to minimize the impact of risk averse agents in the organization to let innovative ideas bubble up by merit despite their risk and be subject to experimentation that can have them take root. However real businesses that don't use this system I imagined (what would eventually be the Action Oriented Workflow paradigm) are still stuck with risk averse employees and environments that choke out the innovative new hires.

So what happens?



People with innovative ideas can go to work for large companies, they get the ah ha moment...they share it with the status quo in the organization ...who all look at the dreamer like they are crazy because of their past failures trying disruptive things and the fear of the social ramifications the organization could bring down if they fail again. The dreamer either keeps trying to rage against the machine and gets excommunicated, admonished or fired and the status quo continues on it's safe route (and thus the company becomes vulnerable to disruptive startups doing exactly what the innovative employee was suggesting).

Meanwhile the employee becomes increasingly despondent...and leaves the company for greener (read: more innovation friendly) pastures OR to go start their own company doing what they imagined.

It's not that large companies don't know how to do innovation, large companies forget how on purpose and actively starve....by their social hierarchies of control, any new efforts to be innovative!

This latter story has strong resonance with me as it closely matches what I did after I was laid off from TheStreet.com. I'd suggested a radical approach to designing the CMS that would make it impervious to the amazing amounts of instability we were seeing at the time. I had already proven the concept by redesigning the entire ad management application using a subset of the approach I was suggesting and it was working perfectly..I brought my idea as a proposal to the CTO and was told that there was no desire to monetize the platform at that time.

Fine, I figured at that moment that I'd build the framework I imagined myself...it wasn't until a year later that I got started, the week that I couldn't go to work after the 9/11 attack on Monday September 17, 2001. I started working on an important collection class in the AgilEntity framework....and by doing so began my discovery and exploration of the action landscape and creating the technological base for a future emancipated workforce.


Article originally posted at LinkedIn

Comments

Popular posts from this blog

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