rankandfile:

Gartner hype cycles are a combination of validating and frustrating. Gartner’s own data has documented consumerization in Fortune 500 company enterprise IT departments for years now. So one winces when mainstream adoption of consumerization is charted to occur in “5-10 years.”

On the other hand, Gartner isn’t necessarily known for being quick to identify technology trends, so when something is on their radar, it’s safe to say it’s well-entrenched.

futuramb:

Gartner publish new hype cycle with the additions of e g gamification and consumerization. I agree with their analysis of both gamification, which recently has entered the plateau of inflated expections, and consumerization which they didn’t seem to detect beforehand and placed at the slope of enlightenment.

To me, who rather see the world i S-curves, the consumerization analysis is the most interesting since it also suggest that it is starting to have a real world effect and we are starting to realize that it really has. IT-departments are on their way to be consumerization’s first road kill followed by a long row of institutions who provide systems top-down.

(via Gartner Adds Big Data, Gamification, and Internet of Things to Its Hype Cycle)

Mock Gartner Magic Quads

Apple’s sneak attack…stop the camera?

Gartner taken to task for EC2 in the Magic Quadrant…

(Source: gartner.com)

Accelerating returns via Cloud architectures - Gartner Catalyst, John Seely Brown (1hr 6min)

JSB Keynote builds context by showing management practices of pushing decisions down and protecting knowledge has led to diminishing returns.

A new era of organizing companies to continually learn new knowledge via Pull and Flows requires getting more people to participate in systems, and this requires cloud architectures. Because opening the enterprise to the outside requires provisioning for uncertainty. Inside the enterprise returns accelerate because the ability to learn new knowledge and benefit from it accelerates. 

Once this is clear, decisions such as embedding policy in code or not, SQL vs NoSQL become strikingly simple.