Metropolis and Gotham: Two Approaches to Enterprise Site Development
In the last five years, UF Health's web services team has launched two enterprise-wide web projects supporting six colleges, six hospitals, and 15,000 staff and students. Our Metropolis was an external web presence supporting over 600 websites, built in the light of day as a positive affirmation of our future as an organization. Our Gotham was a new intranet, built on social networking and web best practices, constructed internally and away from the light, but nonetheless as important. This talk will focus on the strategies used in building both and the lessons learned in the process: Building momentum for the project and guiding consensus versus leveraging political capital and goodwill Creating your Justice League - a team of unique and overlapping skill sets that can support the infrastructure Overcoming the rogues gallery of barriers that threaten to stall or derail the project, or worse, destroy team morale Managing client expectations
Recommandé
Recommandé
Contenu connexe
En vedette
En vedette (14)
Plus de Jeffrey Stevens
Plus de Jeffrey Stevens (20)
Dernier
Dernier (20)
Notes de l'éditeur
- Me and some background about my time at UF.
- a. UF Health i. Health Science Center description ii. Academic components iii. Hospital components iv. Campus within a campus v. Extended ecosystem of UF – Up and Down the Hill
- i. 6 colleges ii. hospitals and clinics iii. many centers, institutes and related sites iv. Unified web presence
- [twitter]A HBR survey showed 27% of employees want colleagues who are ‘forward-thinking’; leaders, 72% http://bit.ly/1ErV6w0[/twitter]
- [twitter]How have you successfully empowered a committee to be champions of change?[/twitter]
- [twitter]The key to a committee that works is picking skills over titles.[/twitter]
- 1. Do you have a professor who does innovative work in presenting his data on his lab site, that conforms to best practices? Include them! Empower them to be a part of the process.
- [twitter]Meet the UF Health Web Services team here: http://webservices.ufhealth.org/the-team/[/twitter]
- [twitter]Choose committee sizes and focuses on what works for your institution. Avoid committee bloat to keep on track. [/twitter]
- i. Committees were then altered to become working groups, which included the 20% of the committee that were most involved in develop, evaluate, and refining the work of web services
- Cross-functional teams benefit from support by a single high-level executive champion. Projects that had strong governance support — either by a higher-level cross-functional or by a single high-level executive champion — had a 76% success rate, according to our research. Those with moderate governance support had a 19% success rate. [twitter]Projects that had strong governance support have a 76% success rate, versus 19% with moderate governance support. http://bit.ly/1Hb1nT0[/twitter]
- [twitter]Our website was an invaluable tool for letting people know about the features and rollout. http://webservices.ufhealth.org/ [/twitter]
- [twitter]Nielsen media shows that 92% of people trust recommendations of friends and family the most. http://bit.ly/1fyoMzu[/twitter]
- [twitter]Here are tips for turning around team morale during challenging projects http://tek.io/1Q12DKt [/twitter]
- i. External presence needs updating and refinement
- i. New homepage for computers across the system – no exceptions In retrospect, I should have resurrected our web services blog to do longer form articles on the transition process and why it was necessary - the changes was big enough to document in all channels.
- Georgy - Decentralized approach to content strategy.
- [twitter]It’s our job as web professionals to guide our institutions into doing better today, tomorrow, ad infinitum.[/twitter]
- [twitter]Thank you all for coming to my talk. I’ll be happy to answer any followup questions on Twitter at @kuratowa[/twitter]