DECEMBER 2020CIOAPPLICATIONS.COM9and every stage of the design should be tested and improved rapidly. This is the cheapest and quickest way to discover usability issues and get user reactions early on. If a problematic design gets into engineer development cycle, the costs of changing the designs would be much higher. And sometimes, it takes years to fix, or it never gets fixed at all and affects subsequent experience in the long run.Designers, product managers and researchers should plan the research together to identify research goals, methodologies, and divide the roles of facilitation, note taking and reporting for faster turnaround. Product managers, designers, engineers, and business stakeholders should all observe user research sessions and debrief together to share different perspectives and learning. Recruit users early, employee testing and virtual testing groups are all good ways of getting users. Prototype: for concept testing, paper prototype or click through screens are fine. For complex, innovative products and mid stage designs, high-fidelity and high quality prototypes are critical. Because testing context, refined user flows, detailed interactions & animations can't be replicated by low-fidelity prototypes, a low quality prototype will affect research accuracy and lead to product failures. This is why we need UX engineers to build working prototypes - engineers in development teams will almost never have the time to build cutting edge working prototypes for radical concept testing, or for redesigns that might be thrown away. At Facebook, we have invested in building our own working prototyping tools, this is incredibly helpful for designers to build working prototypes with shortened turnaround time.Once designs are done and almost front end ready, designers need to sit next to engineers to do desk check, or diff review. This is to ensure design details and interactive intentions are replicated pixel perfect, what we designed is what users will see. Prior to product launch, all teams get together to do bug bashing to ensure all major issues are discovered and fixed. It is also critical to break down large releases or features into tangible milestones, so you can carefully monitor performance step by step, and able to fix unforeseen problems quickly. It is costly to bundle too many changes at once, because it will take longer and be harder to know what goes wrong when things are jumbled together. Post product launch, working teams and business stakeholders should monitor performance data together on a weekly basis for iterative improvements.Communication & Collaborations60-70% work of a high performing design team is communication and collaboration so stakeholders are on the same page, understand what we are trying to achieve and how success will be measured. The worst thing that could happen to a design team is to have product managers or business stakeholders give endless subjective feedback and end up with a design that's done by too many cooks but the designer and taking too long. To overcome such a situation, and to incorporate different perspectives from different stakeholders early on, a world class design team would operate in an inclusive and systematic fashion, to create shared visions, collect different perspectives, understand user needs and business opportunities, and to come up with minimum valuable product solutions that are tangible, scalable and desirable. Thought works, an agile design and development company, has made this framework into a fine art and breaks organizational siloes effortlessly. Every project is kicked off with a 1 to 2 week inception workshop facilitated by experienced consultants. During which time, working team and key business stakeholders are gathered together to go through a well curated agenda. A concrete list of deliverables are pre-identified to enable speedy deliveries right after the workshops. This inception workshop is flexible and usually consists of 1. Current product states sharing, to get everyone on the same page and have the same information. 2. Competitor analysis, to illustrate the industry landscape and opportunity space.3. Shared business vision, to align everyone's understanding of who our customers are, what products or services we want to offer, and what results we can achieve. This is usually broken down into short, mid and long term to be more realistic and scalable.4. User persona creation, to get everyone see things from user's perspectives instead of from individual department's perspective.5. Current and to-be user journey, to see how users complete their tasks in today's world, and how that journey might be improved in tomorrow's world.6. Technical approach, what technologies we should use to build the product.7. Features and stories, to break down features from user's perspective and prioritize.8. Estimations, to understand the scope and how long it will take to build these features.9. Release plan, based on the short, mid and long term vision and the estimations, to form a tangible release plan.10. Communication plan, how frequent, in what format, with whom we should communicate what.11. Roles & responsibilities, who should be doing what, do we have the right talents and skill sets? Do we need to hire or share resources?12. Risks, dependencies, issues and assumptions mapping and contingency plans. With such a collaborative framework, designers become facilitators to guide stakeholders to generate solutions that are holistic, inclusive and user centric. Combined with high quality craftsmanship, rigorous design process, diversified skill sets, a world class design team is in the making. Xiaodan Wang
< Page 8 | Page 10 >