Confluence Retirement

In an effort to consolidate USGS hosted Wikis, myUSGS’ Confluence service is scheduled for retirement on January 27th, 2023. The official USGS Wiki and collaboration space is now SharePoint. Please migrate existing spaces and content to the SharePoint platform and remove it from Confluence at your earliest convenience. If you need any additional information or have any concerns about this change, please contact myusgs@usgs.gov. Thank you for your prompt attention to this matter.
Skip to end of metadata
Go to start of metadata

Resource: Sharing ownership of UX

Discussion Topic(s) Addressed: Fostering user-centered approach within a project team/throughout the project lifecycle 

Resource Summary:

  • The resource provides recommendations for team-based usability efforts.
  • In particular, the resource explains that although it is important for project teams to have dedicated usability roles, the ownership and responsibilities of usability should be shared.
  • Additionally, the resource headlines the concept that “creating truly great products requires an entire product team to place the needs of users foremost when making product decisions—or even better, a user-centered corporate culture”.

Other Key Features of the Resource:

  • The resource’s reading time is about 12minutes.
  • The resource discusses what and how three key role types should be working together to foster user-centered culture.
  • Although the resource uses role names that might be more common in a corporate setting or commercial industry, the concepts from the resource are still applicable to other team types with roles that have different titles but with similar responsibilities.

  


Citation for the Resource:
Gabriel-Petit, Pabini. (2007, May 28). Sharing ownership of UX. Retrieved from https://www.uxmatters.com/mt/archives/2007/05/sharing-ownership-of-ux.php



Additional/Related Resources:  

The following resources provide two examples of how usability can be implemented with different team environment/project lifecycles.

  • The first resource discusses an experience of establishing usability culture within an academic library.
  • The second resource highlights how Agile and usability processes can complement each other more successfully.


  1. Godfrey, K. (2015). Creating a Culture of Usability. Weave: Journal of Library User Experience, 1(3). https://doi.org/10.3998/weave.12535642.0001.301
    1. Key Takeaways:
      1. Buy-in is important because one must believe in the changes in order for them to succeed. However, join-in can be even more powerful because it promotes participation in the change and ownership over the outcomes.
      2. By incorporating usability into all aspects beyond web services, usability also becomes a recognized skill and value within the organization.
      3. By creating goals that work towards realigning priorities, rather than implementing drastic culture shifts, it is possible to introduce new values, such as usability, and slowly adopt a new culture.
  2. Laubheimer, Page. (2018, March 9). Attributes of effective Agile UX. Retrieved from https://www.nngroup.com/videos/effective-agile-ux/
    1. Key Takeaways:
      1. Usability can be integrated with existing Agile processes.
      2. However, blending Agile and usability together might require some adjustment in team culture and mindset.
      3. The four attributes discussed in this resource outline the key characteristics of a team that will allow Agile and usability to work well together.



This resource review is created as a response to the “Usability -- before, during, or after design?” topic posted to the forum.