Microsoft created Project Muse to interview and engage 2,000+ users
about their likes and dislikes of their mobile experiences. These
volunteers helped crowd-source the design of Kin 1, Kin 2 and Kin
Studio – the "productized" results of the user research.
There were 3 big user pain points found in the Project Muse work. They were users' needs for a mobile experience focused on:
- social connections
- multi-screen digital life
While Kin 1 and Kin 2 may have suffered from poor execution at the "whole product" level, Kin Studio received significant recognition for breaking new ground by improving the social experience, integrating mobile + cloud and redefining the mobile user interface.
I believe there's value in distilling Project Muse and Kin Studio down to a few design lessons and guiding principles for consumer and enterprise mobile + cloud social software.
Guiding Principles of Real-Time Mobile Social Cloud Design:
- Enable users to easily create, publish and share the "story-line" of their real life activities
- A user's story-line (pictures, video, texts, call logs) created on any device should be available from the cloud on any web browser
- Story-lines are activity-streams mapped and prioritized in time, by tags, by strength of ties and/or media
- Personalize and prioritize the real-time push of feeds
- Simplify the ability to share and aggregate news and social feeds
- Strong Ties before Weak Ties or Temporary Ties
- Archive Mobile Sensor Data to the Cloud
- Extend through 3rd Party Applications & Developers
- Enable & manage user identity (e.g. Contacts, CallerID) as a cloud service
- Engage end users early and often through user research and design iteration
What would you add?