Collaboration Sessions: How to Lead Multidisciplinary Teams, Generate Buy-In, and Create Unified Design Views in Compressed Timeframes

I have participated in, led, and suffered major website redesign efforts. Whether at process-heavy consultancies, notable product companies, or design studios, all teams experience the same points of pain: late feedback, lack of common design vision, and complaints that individuals or teams didn’t have enough input.

Verhage, Sasha. Boxes and Arrows (2005). Articles>Collaboration>Usability>User Centered Design

Customer Partnering: Data Gathering for Complex Online Documentation  

Technical communicators today must document complex applications used in complex environments. Information about users and use models is important under these conditions, especially if documentation will be presented online. Customer partnering, a method of information gathering that supplements surveys, contextual inquiries, usability testing, and interviews, provides a way of involving the users of complex applications in the design of information delivery systems. We used this method to help a client gather important information about user and use models and design a new information library for complex server computer systems.

Hackos, JoAnn T., Molly Hammar and Arthur Elser. ComTech Services (1997). Articles>Documentation>User Centered Design>Collaboration

Ensuring A Successful CMS Implementation

The single most important factor in a successful CMS implementation lies with you and your people. Your staff members are the principal users of the system, and the SMEs in your organization are the secondary users. It is their adoption of the new processes and governance structures that makes or breaks a CMS implementation. According to some, process and cultural change accounts for 90%, while technology contributes only 10% to the success of a CMS.

Hamer, Emma C. Rockley Bulletin (2007). Articles>Content Management>User Centered Design>Collaboration

Listening to the Customer's Voice

Perhaps the greatest challenge facing the software developer is sharing the vision of the final product with the customer. All stakeholders in a project-developers, end users, software managers, customer managers-must achieve a common understanding of what the product will be and do, or someone will be surprised when it is delivered. Surprises in software are almost never good news. Therefore, we need ways to accurately capture, interpret, and represent the voice of the customer when specifying the requirements for a software product.

Wiegers, Karl E. Process Impact. Articles>User Centered Design>Collaboration

Task Analysis, User-Centered Design, and Group Decision Making  

Task analysis information is gathered from present and future customers within a clearly specified domain. Participants in the session are carefully selected to be representative of the target market. Information is gathered in a way to reduce the potential for bias. Participants provide information in their own words, group data in ways meaningful to them, prioritize tasks according to their business needs, and provide extensive detail on their most important tasks. By session end, there is group consensus defining the most important user tasks. And, through use of our meeting software, we have captured all the information for ready analysis.

Rauch, Thyra L., Candace Soderston and Rick LaRose. STC Proceedings (1996). Articles>User Centered Design>Collaboration

The Impact of Agile on User-Centered Design    

Discusses the impact of an agile software development process on usability testing. Reports opinions about usability testing within a company before and after a change to agile. Presents strategies to incorporate usability testing into agile product development.

Dayton, David and Carol S. Barnum. Technical Communication Online (2009). Articles>User Centered Design>Collaboration>Agile