PERF RMANCE 04 - The Performance Portal - Ernst & Young
PERF RMANCE 04 - The Performance Portal - Ernst & Young
PERF RMANCE 04 - The Performance Portal - Ernst & Young
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Connection as competitive<br />
advantage<br />
Figure 1. Communities follow a life cycle with definite phases of value<br />
Building<br />
Sustaining<br />
Closing/transferring<br />
Plan<br />
• Identify sponsor and engage<br />
stakeholders/core team<br />
• Identify business requirements<br />
and timescales<br />
• Identify success measures<br />
• Create community charter<br />
Develop<br />
• Identify community processes<br />
• Identify community business and<br />
functional requirements<br />
• Build IT systems and processes<br />
(conference calls, dbase, etc.)<br />
• Define rewards and recognition<br />
Implement<br />
• Launch community<br />
• Train/equip community members<br />
• Capture and implement initial<br />
lessons learned from rollout<br />
Feedback<br />
• Meet with sponsor and<br />
stakeholders regularly<br />
• Survey/poll participants on<br />
progress and direction<br />
• Monitor usage of technology<br />
systems<br />
• Review and report against<br />
success measures<br />
Evolve<br />
• Refine/evolve business purpose<br />
• Enhance IT systems and<br />
processes<br />
• Review rewards and recognition<br />
in context of participation/results<br />
• Standardize approach<br />
Ongoing<br />
• “Wash, rinse and repeat” the<br />
cycle of lessons learned and<br />
course corrections<br />
Reinvigorate (option 1)<br />
• Identify new sponsor and<br />
members<br />
• Change processes and<br />
procedures<br />
• Discuss state of community with<br />
participants (as they “own” it)<br />
Transfer (option 2)<br />
• Change scope<br />
• Identify other networks to link<br />
to, transfer or partner<br />
Close (option 3)<br />
• Understand why closing is<br />
necessary<br />
• Have an honest discussion with<br />
sponsor, core team and<br />
membership<br />
• Explain alternatives<br />
• Close and transfer knowledge to<br />
permanent repository<br />
41