Holistic, Collaborative Experience Design and Development Process

Holistic, Collaborative Experience Design and Development Process Process Proposal Documentation | Version 1.0 | lou suSi | January 14, 2014 NOTE Always Start with the Big, Beautiful, Blue Sky Story and Design Ideas Then Use the Most Relevant Research You Can Conduct or Get to Iteratively Inform the Design Along the Way PROJECT PLAN PROJECT START ITERATIVE PROJECT DESIGN, DEVELOPMENT AND DELIVERY PROCESS TEST PROCESS ANALYSIS AND SUCCESS MEASURES Project Kick Off Meeting Planning Meeting Outcome Project Collaboration Success Report Iterative Project Planning Meeting Planning Meeting Outcome Sandbox Session Sandbox Outcome Iteration Outcome Pre-Release Project Inception Lessons Learned Session Design Nodes Testing Continue Investigation and Research and Document Appropriately for Both the Current and Future Applicable Projects Keep Improving Personas, Stories, Contexts and Other UX Documentation • Refine Visual Design Treatment Identify and Document Design Patterns Develop Working Prototype Code and Continue to Improve Per Iterative Sprint Test Test Test (UAT and Usability) WS Assign Core Team Establish and Communicate Assign Project Lead Establish and Assess Initial Decide on Initial User Types Dev CS Lead Lead Lead for Consideration • Understand User Needs and Project Goals • Articulate and Document Dev WS Scope and Timeline Communicate Business Goals Business Plus CS Content Other Motivations on to the Next Project Lead Success Measurements Set the High Level Timeline Assess the Projected Scope and Document Assumptions,, Dependancies and Risks and Success Metrics Initial Planning and Coordination Begins for Next Design Sandbox Stories Establish Up-Front Device Design Order Risk Business Steps in the Process Create a First-Stab List of Situational Contexts and Environments to Design To Rescription The sandbox session leverages a group of inter- disciplinary talent to best-guess approximate who our estimated primary and secondary users are using as much currently-available research as possible toinform our discussions and decisions. Description Although we continually conduct as much usability as possible throughout the entire design and development part of the process," - this is that special kind of intense 'all handş on deck' timespans of pre-release testing that aims to fix as many open bugs and issues as humanly possible before the actual product release. Checkpoint If all of the planning meeting outcomes are successfully established and documented, move on to the Project Description • The kick off introduces the project to *the newly assigned Core Project Team onły. Description Ideas for official projects can actually come from anywhere in the organization but normally funnel through, get approval and then come back through the Business. Anyone should feel properly empowered to express and communicate new projects that help the company innovate, improve and optimize the overall customer experience and corporate brand. Description The planning session should be a smallish meeting of about 2 to 4 people tops, each person representing each of the initial departments coming together to collaborate on the project work. Checkpoint If all of the kick off outcomes are successfully established and documented, move on to the Project Design, Development and Delivery. Checkpoint Any outcome for a sandbox session is sufficient to move forward. The results should feel totally unrefined, just the beginning dregs of the process to iteratively improve as we move the project forward. Description Checkpoint Keep the project in Iterative Design either until the Innovation Team reaches the established timeline Description After collecting self-assessments and other project-related feedback from the Innovation Team the Lead conducts a Lessons Learned Session to discuss the challenges, failures and successes for the team as experienced over the full duration of the entire interdisciplinary collaborative process. Description At this point the Project Lead should meet with the appropriate management to review an Project Collaboration Success Report that captures all of the information discussed in the Lessons Learned Session as well as any other critical insight coming directly from the Lead regarding areas for team dynamic improvement, collaboration styles and all the highlight particulars that properly celebrate each player for their success and contributions while pointing out areas for team performance improvement and any 'nice-to-haves' that would make collaboration smoother for the organization moving forward. This is where the typical sprint-based iterative Agile Design and Development nests within the holistic ověrall collaborative project process. or until the project feels complete and ready to release. Kickoff. At this point the project is now officially 'owned' by the Core Project Team with an upward mentorship support relationship back up to the original Project Planning Team throughout the entire duration of the project. Each time boxed sprint in this case not only involves the development and designerly aspects of the process but also works to increasingly optimize the stories, personas, contêxts and other research information to build toward a more and more realistic and valuable experience for our. target customers. If any of the meeting outcomes in planning are not clearly established, If any of the meeting outcomes in the kick off are not clearly communicated and assessed during the meeting session circle back and set up another Project Kick Off Meeting until we feel comfortable enough to move on with sufficient confidence. Remember to always, always, always: The session shouldrfeel very loose, open, fun and free. All of the brainstorming andɖdiscussion should be captured using analog visual thinking and face-to-face interaction. Take photo captures of the resulting raw artifacts to officially document ina more digital and clean format. Only move 'back' if there are not enough people involved in the sandbox to make a sufficient mess of raw material to work from – this is normally just due to the Once the project is ready to release - conduct intense UAT and Usability Testing, Bug Fix, Refine and Release. documented and communicated during the meeting session circle back and set up another Project Planning Meeting until we set up sufficient clarity around the project. Checkpoint Delay the release or push as deemed appropriate by the results of the pre- release testing. Praise those team members that went over and beyond to push the project to its ultimately successful final state Discuss everything we learned as a team to leave as important legacy information for all of our future projects Talk about how we can improve the process moving forward – in this particular context, discussion of improvement is for processes, not people need to reschedule the session. DESCRIPTION+ CHECKPOINTS PEOPLE + OUTCOMES STEP