whole team of developers and I’m the only UX designer. They’re building features faster than I can design them. I can’t keep up!” Feeding the beast “Yes, we technically delivered all the features this sprint, but looking at the big picture, the design’s an incoherent mess!” Sprint Tunnel-Vision “Our PO’s under pressure to deliver the next release and signing off on features despite crap-ass usability. Help!” Half-Baked UX “Our developers are a fine-tuned Agile machine, but our design dept. can’t figure out how to fit in what we do, so we’re basically still just continuing to create big-ass spec docs and handing them to the devs.” AGILEFALL Saturday, December 1, 12
and continuous collaboration. - Communication through direct collaboration. - Reach the finish line early and often to win the game. Saturday, December 1, 12
and continuous collaboration. - Communication through direct collaboration. - Reach the finish line early and often to win the game. UX Biz Dev GD PM BA Saturday, December 1, 12
Not designed for collaboration. - Slow debugging of issues, differences in understanding. Our top goal is to…but what’s most important is that we…tho what we really must do is to… Saturday, December 1, 12
Not designed for collaboration. - Slow debugging of issues, differences in understanding. What about…? But I thought… Whaa…? Our top goal is to…but what’s most important is that we…tho what we really must do is to… Saturday, December 1, 12
- Design Studio - Dotvoting - Ideation Clearinghouse - Paired Interviews - Product Box - Provisional Personas - Speed Boat - Story Mapping and many more... A UX Rugby Toolkit... Saturday, December 1, 12
Open, Lean Documents - Org. Structure - Biz Dev - Sales - Marketing - Facilities - Human Resources - IT Department ...and beyond. Saturday, December 1, 12
Traditional UX Design, Usability What are we making? Agile UX How do we make it? Collaboration, Delivery Lean UX Are we making the right thing? Measuring,validating product/market fit. Startup Saturday, December 1, 12
- At-a-glance view of the project. - Big visible open document, created through active team involvement. Source: David Hussman Saturday, December 1, 12
Tablet App for a Children’s Charity Providing education and shelter for abandoned and orphaned children around the world. (a real charity I’ve worked with) Saturday, December 1, 12
presents project goals. 2.Team crowd-sources shared understanding. 3.Start creating your collaborative charter project document. 4.Iterate with Biz Sponsor. 5.Distill down to top goals. 6.Next: Continue populating, updating the charter with additional activities... Source: David Hussman Saturday, December 1, 12
just received funding from an anonymous donor to update our digital presence. Our current website is very outdated. We think we can better reach our target demographic through mobile media and social networking, so we’d like to create a tablet app. We think that will be an effective way to increase overall donation revenue, with all the social networking and what-not out there. We know we have a good cause and we want to make sure visitors agree and we’d like them to be confident their donation is going toward the actual cause. And yet, what really matters are the donations. We’ve also been struggling on the upsell front. This is slightly less important. Well, actually, it’s really a top priority come to think of it, since it will lead to higher overall revenue. Though what really is important is to attract users to the site. And just as important is that they make a donation and that it is easy to make a donation. Usability is a must. Also, the payment part must be easy. Should be completely seamless. And we want lots of social networking and Facebook and Twitter in there too.” Saturday, December 1, 12
to make a donation. 2. Persuade visitors to donate a little more than intended. 3. Instill confidence donation is going toward cause. 4. Motivate visitors to tell others to donate. Saturday, December 1, 12
people from one team to the next team. 2. Conduct 5-minute interviews. 3. Collect as many cards as possible. 4. Chunk and prioritize cards. 5. Create a Persona as a team. Saturday, December 1, 12
I want to search for parts visually, so I can be sure I’m ordering the right part. Many Simultaneous Functions (A Boundary Object) Saturday, December 1, 12
I want to search for parts visually, so I can be sure I’m ordering the right part. Many Simultaneous Functions (A Boundary Object) PMs Testers Developers Users UEDs ? POs Saturday, December 1, 12
Supporters (Now) Words/Content needed to support a current conversation or collaboration. Placeholders (Future) Words/Content needed to trigger details in a future conversation or collaboration. As an auto sales rep, I want to search for parts visually, so I can be sure I’m ordering the right part. Saturday, December 1, 12
goals, Personas as a foundation. 2. Create cards from research, cardstorming. 3. Chunk, prioritize cards. 4. Create storymap backbone. 5. Populate map. 6. Iterate, as needed. Saturday, December 1, 12
3m timebox. - Write down as many scenarios or feature ideas you can think of. - One per sticky. - After the timebox, start chunking cards. - Transition to self-organized storymapping as a team. Saturday, December 1, 12
Stories Feature Stories Story Glue More Accurate Estimates Better Story Coverage Written by users, business Independent Negotiable Valuable Estimable Small Testable Saturday, December 1, 12
Stories Feature Stories Story Glue More Accurate Estimates Better Story Coverage Written by users, business Independent Negotiable Valuable Estimable Small Testable Saturday, December 1, 12
- Everyone sketches. - No rules. - If conducting with general stakeholders, clarify that this is research, not design. - If conducting with the internal team, the UI concepts can be the basis for the actual design. Saturday, December 1, 12
2-minute round-robin, then open critique. - Take careful notes, attach to the respective sketches. - Look for and work to resolve vision differences. - (Optional) Dot-vote to uncover trending solutions. Critique Saturday, December 1, 12
opinions. - How many dots? About half of qty items to vote on, rounded up. - Use markers or stickie dots. - Everyone votes at once. - Voters can distribute dots any way they want. Saturday, December 1, 12
1.Revisit the storymap backbone and feature set. Still accurate? 2. Work with “devs” to generate card from UI. 3. Attach/Map feature cards to “dev-cards” (optional) Saturday, December 1, 12
1.Revisit the storymap backbone and feature set. Still accurate? 2. Work with “devs” to generate card from UI. 3. Attach/Map feature cards to “dev-cards” (optional) Jill is attracted to the site Jill is persuaded to donate Jill makes a donation Jill donates a little more Saturday, December 1, 12
1.Revisit the storymap backbone and feature set. Still accurate? 2. Work with “devs” to generate card from UI. 3. Attach/Map feature cards to “dev-cards” (optional) Static Landing Page Jill is attracted to the site Jill is persuaded to donate Jill makes a donation Jill donates a little more Saturday, December 1, 12
1.Revisit the storymap backbone and feature set. Still accurate? 2. Work with “devs” to generate card from UI. 3. Attach/Map feature cards to “dev-cards” (optional) Static Landing Page “Donator- meter” Jill is attracted to the site Jill is persuaded to donate Jill makes a donation Jill donates a little more Saturday, December 1, 12
1.Revisit the storymap backbone and feature set. Still accurate? 2. Work with “devs” to generate card from UI. 3. Attach/Map feature cards to “dev-cards” (optional) Static Landing Page “Donator- meter” Process credit card payments Jill is attracted to the site Jill is persuaded to donate Jill makes a donation Jill donates a little more Saturday, December 1, 12
1.Revisit the storymap backbone and feature set. Still accurate? 2. Work with “devs” to generate card from UI. 3. Attach/Map feature cards to “dev-cards” (optional) Static Landing Page “Donator- meter” Process credit card payments Make payment via SMS Jill is attracted to the site Jill is persuaded to donate Jill makes a donation Jill donates a little more Saturday, December 1, 12
1.Revisit the storymap backbone and feature set. Still accurate? 2. Work with “devs” to generate card from UI. 3. Attach/Map feature cards to “dev-cards” (optional) Static Landing Page “Donator- meter” Process credit card payments Make payment via SMS Jill is attracted to the site Jill is persuaded to donate Jill makes a donation Jill donates a little more Saturday, December 1, 12
prediction of what I’ll need to survive for 2 months in the middle of nowhere. Experiment: - Trek into nearby woods and camp out for a few days. Measurement/Learning: - Did I use more/less food than I expected in 3 days? Did I discover gear I needed but didn’t have with me? etc. MVP Design Saturday, December 1, 12
prediction of what I’ll need to survive for 2 months in the middle of nowhere. Experiment: - Trek into nearby woods and camp out for a few days. Measurement/Learning: - Did I use more/less food than I expected in 3 days? Did I discover gear I needed but didn’t have with me? etc. MVP Design UX: How do we design effective experiments? Saturday, December 1, 12
MVPs should be core to modern UX Practice. - Light-weight prototypes can be your first experiment, but good to quickly follow with a code-based experiment. - MVP design usually draws on a combination of strategies. Saturday, December 1, 12
pain point that can be removed with the least amount of effort. Great for: Enterprise systems, esp. when replacing a legacy system. Saturday, December 1, 12
the customer is not directly paying for. Great for: Consumer products, esp. with domain-specific content/ features. Image source: http://www.creativedreamincubator.com/images/products/buynow50.jpg Saturday, December 1, 12
system operations. Great for: Products with complex algorithms, back-end operations. Image source: http://en.wikipedia.org/wiki/File:Tuerkischer_schachspieler_racknitz3.jpg Saturday, December 1, 12
it (Archetypal Lean Startup Landing page) Strategy: Once a final product is imagined, market it, measure interest, and adjust based on market response. Great for: Any product with a high degree of uncertainty about customer interest. Saturday, December 1, 12
Be sure estimate is informed by UI Exploration - Be present, prepared to speak up and negotiate - Understand the estimation units (e.g. points) Saturday, December 1, 12
UX Dynamics of Agile Projects) Opening Game End Game Mid Game Short, intensive Alien territory for many UX designers Validate, reflect, adapt. Saturday, December 1, 12
Apply Agile approach to planning to ensure that whole team is designing together. - Can also be applied to field research, usability testing and other UX activities. Saturday, December 1, 12
Apply Agile approach to planning to ensure that whole team is designing together. - Can also be applied to field research, usability testing and other UX activities. Saturday, December 1, 12
- Create paper prototypes that allow for completing the donation process. - I’ll initiate “User Fridays” cadences. - Ask users how much they’d be willing to donate and track your donation and upsell totals. Saturday, December 1, 12
envisioning product. - “Is this user-friendly?” vs “Would you pay for this?” - Enables integrating with Agile methods through continuous rather than up-front research. Outcome-Driven Research Saturday, December 1, 12
and improvement. - Start with action items from previous retrospective. - What worked? Didn’t work? What questions do you have? Saturday, December 1, 12