1 vcommons analysis / recommendations vcommons analysis / recommendations july 1, 2010 vcommons...

1

vCommons Analysis / Recommendations vCommons Analysis / Recommendations July 1, 2010

vCommons

Analysis / RecommendationsTalking Points

Johnny Negretti

Chief Architect – Enterprise 2.0

July 1, 2010

2


Legend

ISSUE (RED) – “High level” of problem areas or needs improvement

SOLUTION (BLUE) – I’ll be taking on this

RECOMMENDATION FOR OTHERS (GREEN) – Recommendation for someone else.

3


Production / Technical Resources

1. Little enthusiasm – Get them excited about the potential of this project (July 2010)

2. Not users of product – require staff to use product (August 2010)

3. No collaboration on Fridays (everyone is gone) – Have Fridays be earned / privilege

4. No code review – Start code review (July 2010)

5. LIMITED DOCUMENTATION – Start documenting, even in source code (July 2010)

6. Isolated work – Work as a “team” (August 2010)

7. Poor source code quality – Hands on development 1-on-1 mentoring (July 2010)

8. No “user experience” QA – Hire a QA Analyst, User Experience (w/ tech QA experience)

9. Too much complaining (even myself) – Then fix it!

10.Major disconnect with NJ team – TBD

11.Limited collaboration (unless fixing a bug) – Team brainstorming, conference room meetings

12.Limited visibility into RELEASE process / schedule – Be more strict on release process

4


Project Management (workflow)

1. Two “Project Managers” – Two areas of discipline

2. Jockeying for “seniority” – Based on experience1. Michael is better on production, customer interaction

2. Don is better on strategy, process

3. Unclear direction – TBD

4. Limited documentation on long-term vision – Make one!

5. Limited “technical” knowledge / Drupal capabilities – Me

6. Bugzilla is NOT a project management tool – Use Bugzilla ONLY for “bugs”

7. Reporting and updates are too much a manual – automate (via CVS, bugzilla, other PM tools)

8. CONCON – PROPRO

9. CONCON – PROPRO

10.CONCON – PROPRO

5


“User Adoption” / Marketing / Branding

1. Too much of out of the box look & feel – Simplify! More info in next weeks UIX Review meeting (Tuesday)

1. No top talent “web designer” (not graphic designer)

2. User Adoption should not be a “responsibility” – It should be a measurable KPI (via vMetrics)

3. Too confusing to “post” – Simplify the forms

4. Too many videos / instructions – 1 single point, “Help” page (section)

5. Too many user profiles – One singular profile (excluding vTeam), (August 2010), email branding

6. Too many customizable widgets – Singular and simple front page, with fresh/real-time data (long-term)

7. What do I post?? – Not clear on what an average employee is supposed to post

8. No incentive!! – Rewards Program (gradual, status, point)1. Little reason to post – Get HR to push more “I am Verizon” campaigns

9. Confusion on the “collaboration” mission statement – Get one!

10.“Hank” – Behind the scenes (vCommons development), no one person spokesman*

11.Limited measurable “viral” components – Replace email (Boston events example)

6


Products (high level) - 1

vDigg Not really used

Move off of and move link sharing via vTweet

vTweet Good usage (in the beginning)

Get rid of a lot of the misc features

Promote to be used instead of email (vSearch)

vMetrics Limited reporting

Too much backend data gathering / syncing

Needs to be priority application (ROI calculations)

Executive Dashboard (see plan)

Front-end metrics gathering

7



vForum Integrate more with vTweek (and vWiki)

Keywords (tag cloud)

vTube Better organization / layout

Streams (within)

vPreso Replacement for SharePoint PPT docs?

Used for conference room meeting (like this one) under the “PRIVATE” section (who in IT sees private?)

8



vWiki Can be the biggest player

vBlog Can be the biggest contribution to user adoption

Content would be work related, but not “official” (Boston events)

vSearch Main usage across all sites, and simplified results (and advanced)

9


Long-term Roadmap

vCommons as the singular starting point for all employees home page (main intranet)

Increased user adoption, no just spikes, ensure visitors are repeat visitors

Simplified design (increased usability)

vCommons branding is well known throughout the company

Prove substantial ROI (vMetrics and other Enterprise reporting tools)

Reduced team for vCommons “operations” and maintenance

Stop complaining (among the group), accept the limitations of big business, and get inspired to push change and innovation (through proper Verizon channels).

10


Conclusion

I’m staying!

1 vcommons analysis / recommendations vcommons analysis / recommendations july 1, 2010 vcommons...

Documents