[secondary artif@cts]

Dion Hinchcliffe Exploring E2.0 Methodologies #e2conf-26 live-blog

dion hinchcliffe - exploring early enterprise2.0 methodologies

#e2conf-26 hashtag

topics for today

1. innovator’s dilemma - how do we disrupt ourselves before our competition does?
2. how to handle innovation that happens faster than the organization can absorb?
3. types of enterprise2.0

SLATES methodology

became FLATNESSES

slides available after for your study

community management “most essential” to success and health

cost of project

tools 15%

integration, customization 25%

community management 25%

it support 15%

project/ change mgmt 20%

your mileage will vary

SAP talks about hidden cost of community mgmt

at first 90% us, 10% them

agile processes

rapid course corrections

essentially the spirit of e2.0

make discoveries all the time that change requirements

business doesn’t like this type of planning

1 way of implementing e2.0, the Hinchcliffe way

identify - biz opp, risks, priorities, budget

prepare - strategy, comm plan, setting expectations (most important), policy of when to use tools, how to use tools, build skills/training, measurement plan, infrastructure

assess - understand competencies, understand stakeholder concerns, understand initiatives

pilot - create social computing env, build critical mass, capture lessons learned (agile), build

roll-out - expand audience and reach

manage - community mgmt, guide-direct-moderate (don’t control),

there is a social computing help desk (easy way to explain it - to keep it healthy and show it’s value)

this job is never finished, this is the long term commitment, this is what you’ll be doing as long as you exist

ECM - biggest related industry to draw best practices from

AIM is best example of this

Emergent Architecture is big thing from this year

focus on creating adaptive processes - growth->refinement->disruption->renewnal as change comes into the organization

also informs the community management process

deloitte’s ecm process

ross dawson’s enterprise2.0 impl framework

social media delivery process http://gauravonomics.com

more focus on data mining, tools, linear process, consumer

Roundabouts model 0.3 - like it b/c it’s more mature as a dashboard to tell you what to do

the app gap model

blueprint mazyar hedayat - good for validation but too light on community

conclusions

still at low level of maturity

existing frameworks usually miss key e2.0 elements today

adaption best parts you think you need is often best strategy

improvements are coming but ‘unified process’ for e2.0 not there

slides available in conference portal and by email info@hinchcliffeandco.com

McAfee Keynote E2conf-9 Live-blog

andrew mcafee keynote

E2conf-9 hashtag

victory - the good

1. adoption in the face of the recession
2. mckinsey study shows benefits to org’s that adopt enterprise2.0 - 3rd of it’s kind study, input from champions (skew possible). but given these benefit numbers ”i can’t understand why companies aren’t stampeding towards these tools”
3. 20adoption council
4. bizarre popularity of sharepoint - i don’t mean sp sucks, but b/c of the increasing demand for solutions like this
5. US intelligence community - they declare ”we know when we don’t share information, people die.”

snatching defeat - the bad

1. declaring war on the enterprise

calling “the Enterprise” obsolete isn’t a great adoption (or marketing) strategy
marxists’ apartment a microcosm of why marxism doesn’t work

2. allow walled gardens to flourish

do not create more silos with each group that wants some of that
one of the deep reasons that the web works, is that there is one web

3. accentuate the negative

i used to a big fan of this
Ross Mayfield said in conversation “when i look at the program - all i see is focus on downsides and risks”
this caused me to rethink the way we’re presenting these topics
risks are manageable - intelligence community has shown this

4. replace email

checking email is a bad disruption to personal interaction and collaboration
C suite likes the one stop shop approach of email

5. fall in love with features

we don’t need more features, we need features that work better
ask yourself, what is the simpliest thing that could work?

6. overuse the word “social”

it’s good that we’re not trying to automate people out of work
never come across a pragmatic line manager that likes the word “social” to describe his business
best thing is that it’s neutral and accurate
worst thing is that it’s a waste of time
i’m not running a social club, i’m running a business
social describes a picture of smelly hippies and free love to some