Taking a user-centric, story-based approach to MIKE2.0 highlights some of the issues we have had in growing the community. This goal of this section is to drive initial changes through better identification of user requirements.

MIKE2.0 Personas

Shown below are some typical MIKE2.0 user types – referred to as personas. “Top down” users are those that want to understand the big picture or a number of articles, “bottom up” are more interested in just a few articles.

The Project Manager

- Needs Comes to MIKE2.0 looking for help in managing an engagement. They are looking for help in creating a project plan, how much a project will cost, how much technology will cost, risk points, lessons learned.
- Collaboration Style: May contribute back to the approach but need to find an area where they are comfortable adding value. The most likely way is in adding specific questions.
- Orientation: Typically Top Down

The Proposal Writer

- Needs: Come to MIKE2.0 looking for case studies, proposal templates, plans, text to copy against proposal questions, solution techniques and estimating techniques.
- Collaboration Style: Very unlikely to contribute back to the approach. They may want to ask questions, but they are typically under pressure for quick results.
- Orientation: Typically Top Down

The “Hands On” IM Practitioner

- Needs: Come to MIKE2.0 for community networking, design templates, answers to focused questions they may have, technology-specific assets, innovative approaches to solving IM issues and answers to specific, focused questions.
- Collaboration Style: Good candidates to contribute back to the approach. They will still find it easier to read than write. They should be encouraged to contribute to specific articles, post questions to forums and add their favorite bookmarks.
- Orientation: Typically Bottom Up

The Novice IM Practitioner

- Needs: This may be a junior person or a senior person who is junior to information management. They come to MIKE2.0 to understand IM terminology (definitions), steps in a project, how it is different than other areas of technology, case studies, business benefits and relationships to vendor technology.
- Collaboration Style: May contribute but will be hesitant due to their inexperience. They will still find it easier to ask questions and to add bookmarks when contributing.
- Orientation: Top Down and Bottom Up

The Solution Architect

- Needs: Comes to MIKE2.0 for community networking, design templates, answers to focused questions they may have, technology-specific assets, innovative approaches to solving IM issues and solution approaches.
- Collaboration Style: They are good candidates to contribute back to the approach. They will still find it easier to read than write. They should be encouraged to contribute to specific articles, post questions to forums and add their favorite bookmarks.
- Orientation: Top Down and Bottom Up

The Academic

- Needs: Interested in information management from a theoretical perspective. They come to MIKE2.0 for community networking, information management concepts, innovative ideas and ways to reach a community with their own perspective.
- Collaboration Style: Good candidates to contribute back to the approach. They will still find it easier to read than write. They should be encouraged to contribute to specific articles, post questions to forums and add their favorite bookmarks.
- Orientation: Typically Top Down

The Advertiser

- Needs: They come to MIKE2.0 to look for opportunities to highlight themselves, their company or their product. They may do this in a way that is perfectly fine with the goals of the community. They will be primarily interested in social networking, product articles and bookmarks to their companies.
- Collaboration Style: They are the best and worst contributors at the same time. By nature they will be writing on the site. We need to encourage their contributions while at the same time making it follows site guidelines.
- Orientation: Typically Bottom Up

Illustrative User Stories

Below are some of key ways the above personas engage with MIKE2.0. User stories are defined in the content of how they should ideally engage with MIKE2.0 and what collaboration capabilities should be provided to encourage this behavior.

- Discovering MIKE2.0 User Story
- Help Build the Integrated Content Repository User Story
- Proposal Support User Story
- Highlight the Individual User Story
- Reward the Individual User Story
- Social Network Integration UserStory
- Highlight Team Contributions User Story
- Membership User Story
- Dynamic Front Page User Story