Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Cpwf On-line consolidation and next steps

903 views

Published on

A summary of the asssessment of CPWF systems carried out by Markus Stass. Also provides next steps and ways forward.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Cpwf On-line consolidation and next steps

  1. 1. CPwf Online Consolidation<br />Findings and recommendations<br />
  2. 2. Overview | Goals<br />Create high level consolidation strategy<br />Review content to improve usability & information architecture<br />Minimize publishing workflow & efforts<br />Generate high level functional specifications & technical architecture<br />
  3. 3. Overview | Process<br />Review CPWFs online information offering<br />Conduct simple heuristic usability review <br />Identify consolidation potential<br />Review CPWF’s branding approach<br />
  4. 4. Overview | Findings | General<br />Fragmented information spread over many platforms<br />Comprehensive search and other navigation aids are missing<br />Current branding approaches do not support, rather damage CPWFs brand<br />Inconsistent data presentation throughout all platforms<br />General user-friendliness and UX design offer room for improvement<br />Passive audience, no added value <br />These issues show the need for a DETAILED online communication strategy<br />
  5. 5. Findings | Waterandfood.org<br />Search offers limited functionality, search result display is sub-standard<br />No sitemap!<br />No legal disclaimer, invalid copyright information, no privacy policy<br />Not accessible (WAI, BitV, etc)<br />Dead and misleading links<br />Media is not properly presented (i.e. Movie with the title “change” and no other info)<br />Text heavy pages without optical clues, bullet points and are not web friendly (i.e. Basin info)<br />The current website is not on par with today’s Internet communication standards<br />
  6. 6. Findings | Social Networks<br />Uses Twitter<br />Does not use Facebook, Wikipedia (limited, BFP entry exists)<br />Non-Twitter audience is excluded from feeds<br />Some feeds and website news overlap (could be combined)<br />No consistent use of social networking tools, lack of social networking strategy <br />
  7. 7. Findings | Online Media Storage (Social) <br />Uses YouTube, SlideShare and Flickr<br />Poor data quality (Audio, video, photos are often of low quality)<br />Poor meta data quality, makes it difficult to use and generate value out of the media<br />Most media is presented as standalone rather than embedded in to article, topics, tags, etc.<br />Great potential not yet utilized<br />
  8. 8. Findings | Online Media Storage (CG Space ) <br />CG Space as authoritative CPWF product storage<br />Good compliance, uses standards and open source<br />Part of the CG System and many other CG institutes using it. <br />Seems to be constantly evolving and outside support. <br />No access through waterandfood.org site tools<br />CG Space offers online document storage, standardization and outputs RSS/ATOM that could be implemented within waterandfood.org<br />
  9. 9. Findings | Google<br />Maintains several Google sites<br />Extranet content (For selected audiences)<br />Inconsistent branding and design<br />Collaboration enabled<br />Excluded from main website (Good!)<br />Google sites offers collaboration & interaction functionality, seems to be a good choice for an Extranet (Best to hide pages until log in)<br />
  10. 10. Findings | Project; Basin; Research sites<br />Limited branding<br />Language (Spanish/English)<br />Inconsistent<br />Technical issues<br />Can export data (RSS/ATOM)<br />Need branding, platform & content strategy<br />
  11. 11. Current state<br />CG Space<br />Google <br />Sites<br />waterandfood.org<br />? ??<br />PBWorks<br />Wordpress<br />Google Groups<br />Wikispaces<br />Slideshare<br />YouTube<br />Main Flickr<br />BFP Flickr<br />Twitter<br />Condesan.org<br />Smallreservoirs.org<br />Mpowernetwork.org<br />Bfpandes.org<br />
  12. 12. Recommendations| Strategy<br />Define detailed online strategy (Use cases; Personas; Task definitions; etc.)<br />Define branding strategy (Branding tiers; style guide, color palette; etc.)<br />Create tonality guidelines<br />Introduce publishing workflow<br />Introduce success metrics<br />
  13. 13. Recommendations| Releases<br />Define release cycle<br />Release 1: Consolidate meta data, improve search ability and implement portal structure into waterandfood.org<br />Release 2: Synthesize information; build information networks; engage audience; add value<br />
  14. 14. Future state | Release 1<br />Slideshare<br />YouTube<br />Main Flickr<br />BFP Flickr<br />Twitter<br />CG Space<br />outcomes<br /><br />Protected Intranet/Extranet<br />Index & embed<br />Provide multimedia storage; drive additional traffic<br />Pure bliss<br />waterandfood.org<br />Google <br />Sites<br />PBWorks<br />Wordpress<br />Google Groups<br />Wikispaces<br />Pull & feed<br />Satisfy user needs; add value; increase relevance;<br />outcomes<br />Condesan.org<br />Smallreservoirs.org<br />Mpowernetwork.org<br />Bfpandes.org<br />Only for members; playground; collaboration; think tank; rant bunker <br />Provide up to date info; drive traffic; <br />
  15. 15. Details Release 1<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />Strategy<br />
  16. 16. Details Release 1<br />Quality Management! If your data is …. and you show it, you harm the organization and the brand (Rule: “Website users do not come back”)<br />Consolidate social media, but first define a social media strategy!<br />
  17. 17. Details Release 1<br />Useful meta data, XML, RSS and ATOM are our friends (If they are faulty and incomplete, they are our enemy!)<br />Authoritative, non-redundant information sources will make it easy for us<br />Pull that meta data and feeds, buffer it in data storage, make it searchable, present it in a directory structure and other relevant chunks (Tag clouds)<br />
  18. 18. Details Release 1<br />Define online release cycles, so your co-workers, management, and other stakeholders can adapt to it with requirements<br />Offer an easy to apply requirements gathering process<br />Use those cycles for QM!!!<br />Review and adjust your Online Strategy within those cycles<br />
  19. 19. Details Release 1 | Details<br />Drupal<br />You already use it, so you know the backend<br />Open source with excellent documentation and built on Internet standards<br />Fully customizable, module structure<br />Portal enabled out of the box<br />No need to change hosting company or upgrade data plans (yet)<br />Migration<br />Take over the visual design (after eliminating usability flaws)<br />Implement new information architecture<br />Manually migrate existing content<br />

×