10
Information Management ICANN 53: Buenos Aires | June 2015

Information Management ICANN 53: Buenos Aires | June 2015

Embed Size (px)

Citation preview

Page 1: Information Management ICANN 53: Buenos Aires | June 2015

Information ManagementICANN 53: Buenos Aires | June 2015

Page 2: Information Management ICANN 53: Buenos Aires | June 2015

| 2

Information Management UpdateProjects:

Membership Management + WebDocument CollaborationWorking Group ManagementCommunity Wiki

Additional Updates

Page 3: Information Management ICANN 53: Buenos Aires | June 2015

| 3

Information Management Update

1. The Information Science (librarian) role was approved in May and we're actively seeking an appropriate person. I expect to have someone hired by end of July.

2. Next steps to improve content access on ICANN.org

1. Light redesign to the home page to help people more easily find the content they need.

2. Redesigning the Resources section, where most of the content on ICANN.org resides.

3. New UX Designer on staff.

Page 4: Information Management ICANN 53: Buenos Aires | June 2015

| 4

What We've Done

1. We interviewed knowledgeable members or leaders from four groups: ALAC, IPC, ISPCP, and NCSG

2. We investigated a number of potential options and working with Rafik Dammak completed a deeper investigation of the preferred service provider.( MembersClick)

3. We identified budget ($68,000 for year 1 + $22,500 recurring -- for 7 licenses)

Next Steps

4. Run a beta test with the NCSG and other groups [1QFY16]

5. Deploy a production solution to the community [2QFY16]

Project: Membership Mgmt + Web

Page 5: Information Management ICANN 53: Buenos Aires | June 2015

| 5

What We've Done

1. Captured hypothesis and requirements and presented to the SSAC working group for Document Collaboration.

2. Researched 50 potential off-the-shelf tool sets that accomplish co-authoring and editing.

3. Conducted a pilot with SSAC working group to test out functionality for feasibility and fit.

Next Steps

4. Wrap up the pilot program and documenting insights and lessons learned.

5. Present findings to the community and begin a dialog from a community wide perspective.

Project: Document Collaboration

Page 6: Information Management ICANN 53: Buenos Aires | June 2015

| 6

What We've Done

1. Researched potential tool sets in workspace management.

2. Ran pilot with DMPM to test out some of Kavi’s workspace management features.

3. Captured initial lessons learned and other valuable insights from the pilot .

Next Steps

4. Continue working the pilot program through July.

5. Continue the dialog with the community as to ways to improve how they work within working groups.

6. Open up Kavi to be experimented with by other organizations; At-Large has shown interest.

Project: Working Group Management

Page 7: Information Management ICANN 53: Buenos Aires | June 2015

| 7

What We've Done

1. We've assigned a Product Manager (Steve Allison) to work with interested community members to improve the wiki

2. Completed an internal assesment of the wiki (posted on the Community Wiki)

Next Steps

3. Vet our findings with the community.

4. Start an open dialog with the community and uncover any other gaps in our understanding of what could or should be done.

5. Prioritize those requirements and work with internal project teams to illustrate a future vision (e.g. Upgrades, Custom Features/Widgets, Site Maps, Governance Models, Training, etc.)

Project: Community Wiki

Page 8: Information Management ICANN 53: Buenos Aires | June 2015

| 8

Additional Updates

1. Currently beta testing mobile meeting app.

2. The Digital Services page on the Community wiki https://community.icann.org/display/digitalservices/Digital+Services

Page 9: Information Management ICANN 53: Buenos Aires | June 2015

Appendix

Page 10: Information Management ICANN 53: Buenos Aires | June 2015

| 10

What We've Done

1. In Singapore community leaders, general members, and board members expressed dissatisfaction with the lack of content describing how ICANN is structured and how it works.

2. We also needed a means of directing people to the SO, AC, and stakeholder group websites.

3. Using data gathered from 1:1 interviews in Singapore we created a series of wireframes and initial working pages.

Next Steps

4. Review the wireframes and alpha pages with community members for input.

5. Review the content describing the groups.

6. A/B test the page to see if a) readers better understand ICANN and b) does it drive traffic to the groups’ websites.

Project: Community Page Redesign