Last modified 3 years ago
User Story: The IM practitioner finds an article on data governance by searching through Google. The user has never been to the MIKE2.0 site before.
UX Goals
- For the user to read the article
- For the user to be able to understand the comprehensive approach in this area within the MIKE2.0 framework
- For the user to be able to understand how they can apply the approach in their own organization
- For the user to engage in the MIKE2.0 community by:
- Registering for the site
- Registering to receive notifications from the MIKE2.0 site (articles changes, blog posts, network updates)
- Updating their skills profile and building a social network
- Encouraging others to join
Required Capabilities
- The user lands on the data governance article via search. From the navigation extension they can very quickly understand:
- Where this article fits in the overall approach
- Where there are other articles like this article
- Who contributed to the article
- How they can apply this approach
- How others have applied this approach
- Who they can reach out to for help
- The user wants to ask a question on the article. They click on the conversation extension. This extension provides a single mechanism from which the user can:
- Decide where, who and how they should ask questions (forums, social profile walls, talk page)
- Design consideration: how to do this best without confusing the user. It should be seamless.
- The user wants to change the article. They click on the help extension in the edit page to understand:
- How to change an article
- The impacts of changing an article
- The user is encouraged to register for the site and populate their social profile. Once populated, the content suggest extension? recommends articles they may be interested in.
- As part of the registration process, the user is encouraged to register for notifications and to invite others to the MIKE2.0 site.
