Dan Keldsen's Library tagged silo →  View Popular, Search in Google

Nice post tying lean thinking and doing root cause analysis on information overload. Agree that's it's not that there's too much information - there always has been, since well before anyone currently living. It's the amount of information that you're actually expected to consume, understand and react to that's gotten out of control.

Nice quote re: Peter Drucker:
"In an earlier post, I talked about how Peter Drucker viewed an excess of meetings as a sign of a dysfunctional organization. He wrote that:

'Too many meetings always bespeak poor structure of jobs and the wrong organizational components. . . if people in an organization find themselves in meetings a quarter of their time or more — there is time-wasting malorganization.

Too many meetings signify that work that should be in one job or in one component is spread over several jobs or several components. They signify that responsibility is diffused and information is not addressed to the people that need it.'

I wonder if you could say the same thing about too much email. Yes, when you’re collaborating with teams located in different offices around the world email is a incredibly useful communication tool. But lord knows that there are plenty of people, teams, and companies that don’t have that convenient excuse.

The root causes behind our biblical email plague are myriad — and almost certainly don’t involve something we can’t fix, like a vengeful god. Asking questions that reveal the root causes can help you take appropriate countermeasures. It’s a better approach than blaming email on “filter failure,” or meekly accepting the worsening status quo."

lean_thinking information_overload lean_management A3s filter_failure clay_shirky nathan_zeldes dan_markovitz silo disintegration fragmentation peter_drucker

Presentation given on Wednesday, June 16, 2010 at 8am ET at the Enterprise 2.0 Conference. 5th presentation I've given at this event over last 2.5 years. Timing is right - convergence, integration, standards - people are finally looking at E2.0 as PART of their overall business architecture, and not just a stand-alone capabilities.

Track: Tackling Enterprise 2.0 Business Challenges

It is now 4 years into the Enterprise 2.0 movement, 7 years into Enterprise Wikis, and 20 years since the birth of HTML and the web.
Organizations have never had as much potential flexibility for collaboration, content, search and process tools to be used with their employees, partners, suppliers and customers - but even though core beliefs at the heart of Enterprise 2.0 are in the power of transparency and loosely coupled services, most organizations have blown themselves to bits through extremely DIS-integrated E2.0 (and prior era) solutions.

If you're headed down the path of a microblogging platform from one vendor, a wiki from another, a mashup platform from yet another, a community site from another, and a search engine from yet another - save yourself the time, money and resources BEFORE you commit a single cent, and set yourself up for faster, better and cheaper STRATEGIC flexibility. Or be ready to watch your competition/market fly by while you're busy playing Enterprise 2.0 Twister with a dozen, non-integrated, siloed solutions, and the fiefdoms that come with them.

If you've fallen into this trap already - how do you get out? and without breaking the bank, or getting fired?

Let's talk best AND worst practices - and how to balance the pragmatic and simple, with the need for a strategy that converge and unify your Enterprise 2.0 investments before it's too late.

informationarchitecture information_architected dan_keldsen enterprise2.0 e20 e2.0 silo flexibility federated search portals taxonomy business_process_management enterprise_portals integration convergence