Difference between revisions of "Apache OpenOffice User Experience"

From Apache OpenOffice Wiki
Jump to: navigation, search
(Adding new content to AOO UX page)
m (Adding new content to AOO UX page)
Line 82: Line 82:
  
 
*[[OpenOffice.org User Experience|OpenOffice.org User Experience Homepage (Work Product Archive)]] - OO.org UX archival content
 
*[[OpenOffice.org User Experience|OpenOffice.org User Experience Homepage (Work Product Archive)]] - OO.org UX archival content
*[[AOO UX Categories|Wiki Categories]] - Links to wiki categories that include user experience design-oriented content
+
*[[AOO UX Categories|UX View of Wiki Categories]] - Links to wiki categories that include user experience design-oriented content
 
<br /><br />
 
<br /><br />
  
 
[[Category:UX]]
 
[[Category:UX]]

Revision as of 08:11, 29 June 2012

Introduction

Our Mission

Our mission is to ensure that the design of the Apache OpenOffice user experience resonates with our users, and allows them to realize their goals and accomplish their tasks, in a way that compliments their context of use, in their world. We want to design and deliver great software that helps people capture their thoughts and share their ideas! We want to make Apache OpenOffice the best open source office suite in terms of usability, productivity and enjoyment.

About User Experience

AOO user experience (UX) efforts seeks to provide guidance to the product management, and development community to ensure that AOO offers the best user experience possible.

Our duties include gathering user input, distilling insight into opportunities, designing solutions to realize opportunities, advocating usability within the broader design and development process, and helping turn ideas into reality. Our work products include user research, user roles/personas, usage scenarios, wireframes, design explorations, design evaluations, and user testing.

How to Get Involved?

User experience (UX) is an umbrella term that encompasses information architecture, usability engineering, user interface design, interaction design, and visual design, as components of the holistic user experience. Apache OpenOffice user experience is currently looking for creative, passionate people to join the effort. You don’t have to be a C++ guru (or even know what that means) to get involved. You just have to love software. Join our user experience community and contribute to the conversation. Your research, writing, story telling, sketching, and design skills will be greatly appreciated.


User Experience Program

Strategy

  • UX Research Strategy - How might UX gather data to characterize the current state of the product experience and identify opportunities for improvement?

Planning

Tasks

Reporting


User Experience Research

To help make informed design and development decisions, the OpenOffice community needs to understand who uses OpenOffice, what they use it for, and what is important to them. Beyond roles and goals, we need to understand user attitudes and behaviour, uncover latent and emerging needs, and understand drivers and barriers of change. User data is captured by asking questions, listening and observing people using our software. Activities include interviews, surveys and direct observation. The outcome of user research is enhanced insight into the user, their context of use and criteria for success. The output of user research are a collection of work products that tells the user's story, and criteria for success.

Research

  • UX Research Surveys - We need data! This activity seeks to design and deploy user research surveys which characterize the state of our product experience and identify opportunities for improvement.
    • Ux task icon.png ACTIVE UX ACTIVITY - Volunteers are needed to help design and deliver the user research surveys.
  • Harvesting Social Sentiment - Our social assets (mailing lists, forums, and social media) present a great opportunity to gather user insight and feedback - very low cost, high value. This activity seeks to harvest user research data from our social assets as input to future research and design activities.

Work Products

  • Who the? What the? - Who uses Apache OpenOffice? What do they want to do? This activity seeks to understand the AOO users, and identify what is important to them.
  • Top Tasks - What are the key tasks that our users perform in OpenOffice? This activity seeks to inventory and categorize key OpenOffice tasks.
  • Storytellers Wanted - How does OpenOffice help our users accomplish their tasks, and achieve your goals - now and in the future? This activity seeks to capture stories that share how people use OpenOffice in their daily lives.


User Experience Design

Design is choice. How might we make the best design choices that deliver the best user experience and realize our criteria for success as identified from our user research.

Analysis

Explorations

  • AOO 4.0 Logo Design Exploration [1] - How might we refresh the OpenOffice identity? No wrong answers, please share your designs and join the conversation.
  • AOO 4.0 UI Style Exploration - How might we refresh the AOO common UI to be more compelling? No wrong answers here, just a collection of thoughts, ideas and criteria for success.
  • AOO 4.0 Social Design Exploration - How might we integrate social tools that support social interaction and behaviour? No wrong answers here, just a collection of thoughts, ideas and criteria for success.

UX Design Backlog


Evaluation

To ensure that our current offering, proposed enhancements, or new capabilities realize our stated criteria for success, as identified in our user research work product, we can perform user experience evaluations.

Design Evaluations

  • Design Evaluations - Collection of design evaluations with feedback, guidance and recommended opportunities for improvement.

User Evaluation

  • UX Research Surveys - We need data! This activity seeks to design and deploy user research surveys which characterize the state of our product experience and identify opportunities for improvement.


OpenOffice.org UX Archives

The Apache OpenOffice User Experience community appreciates the efforts of the previous UX communities that have resulted in the great product we have today. We are fortunate to have inherited a library of great UX research, UI design and user evaluation work products. As part of the transition from Oracle to Apache, some UX content, and supporting links, are invalid or out-of-date. Other content is extremely valuable and will be integrated into the Apache OpenOffice UX effort moving forward. To ensure that the previous material is still accessible, we have archived the former UX wiki home page.



Personal tools