Quantcast
Viewing all articles
Browse latest Browse all 150

Notes on Winning UX Workshops with Austin Novella

(From uie.com’s All You Can Learn library, requires highly-recommended subscription.)

Image may be NSFW.
Clik here to view.
Screen Shot 2018-07-11 at 12.43.14 PM

Frame the Question

4 things frame collaboration:

  • What you’re doing
  • What you’ll end up with when you’re done
  • Why it’s important
  • How you’ll do it

This sets up 3 important expectations:

  • Makes others feel like participators and shifts them from observer to collaborator mode
  • Knowing what they’ll end up with and why it’s important encourages them to invest in the discussion and pay attention
  • Explaining what you’re doing and what to expect allows the team to trust you while you work towards your goal

Plan the workshop so that you finish with an outcome, either a single thing or a list of things:

  • Words
  • Diagrams
  • Sketches
  • Worksheets or canvases

Sample set up:

Image may be NSFW.
Clik here to view.
Screen Shot 2018-07-11 at 12.59.57 PM

Facilitate the Discussion

Facilitation has four stages:

Open & generate (divergent thought)

  • Open-ended questions
  • Anything goes!
  • Create as many options/ideas as possible—you’ll edit them later

Analyze

  • Sift through options to learn more about each one
  • Probe w questions such as
    • What is this made of?
    • How does this work?
    • Where does this come from?
    • Can you provide an example?

Synthesize (convergent thought)

  • Discover affinities among various options
  • Probe w questions such as
    • How are these options similar?
    • Different?
    • Related?
  • Create docs such as affinity maps, diagrams, relationships across time etc

Decide & close

  • Which ideas are most important?
  • Most feasible?
  • Which do we like the most?
  • What are we carrying forward?
  • Prioritize and vote on the outputs of the workshop

Probing

Probe at both divergent and convergent points to help the team understand the problem space

Ask questions to create new possibilities:

  • What have we missed?
  • Are there other ways to think about this?
  • Can we apply similar ideas from other contexts?
  • Are there additional possible inputs—or new ways to think about existing inputs (divergent)?
  • In what ways can we compare inputs (convergent)?

Sample Activities

  1. Wrongs activity
  • What do you hate about the current system?
  • What’s broken?
  • Missing?
  • Outdated?
  • Insufficient?
  • Annoying?

2. Goals activity

  • Captures goals from every indv in the group so nothing gets lost
  • Analyze goals as you collect them and group by similarity
  • Prioritize and vote on goals to achieve the project’s goals—probably short term, medium and long term goals probably aren’t decided here

Collaboration

Image may be NSFW.
Clik here to view.
Screen Shot 2018-07-11 at 1.29.39 PM

Austin’s website has more resources on running UX workshops so check it out at agux.co

About Austin Govella (from uie.com): Austin Govella is an Experience Director with Avanade Digitalwhere he helps enterprises reinvent how they connect with employees and customers. Prior to Avanade, Austin worked for Comcast Interactive Media where he worked on early versions of Comcast Xfinity. In 2009, he co-authored the second edition of Information Architecture: Blueprints for the Webfor New Riders/Peachpit, and he’s spent the last few years studying how agile teams, lean companies, and user experience designers can work better together.

Austin Govella has designed successful user experiences for the web and mobile since 1998.

 

 

 

 

In running international seminars, Bruce McCarthy asked attendees to write break-up letters with their current roadmapping process, which highlighted many real-world current issues:

  • No defined process
  • Not tied to business strategy
  • Not enough customer input
  • Lack of stakeholder alignment
  • Unclear prioritization
  • Broken promises
  • Overly incremental
  • Shiny object syndrome
  • No clearly defined target
  • Poor use of data
  • Groundhog Day phenomena

Roadmapping 6 months out doesn’t sync well with Agile processes and can be a no-win scenario

Yet roadmaps are a way of clearly expressing a product strategy and setting a budget

Jared Spool suggests roadmaps shift focus from planning feature releases/dates to reflecting an understanding of what the customer is looking for and solving those problems. Jared thinks these new roadmaps can be a company’s competitive strategic advantage

Relaunching roadmaps

A roadmap should:

  • Put plans in a strategic context
  • Focus on delivering value
  • Embrace iterative learning and evolution
  • Rally the org around a single set of priorities
  • Get customers excited

A roadmap shouldn’t:

  • Make promises you’re not sure you can keep
  • Act as a project plan or a release plan
  • Require wasteful up-front design and estimation

What is this new roadmap?

  • A strategic communication tool
  • A statement of intent and direction, not a promise of deliverables
  • Lays out where you’re headed and what the obstacles might be without getting into product specifics
  • Could be a Kanban board, spreadsheet, slide deck—whatever works for your team to hold your product’s vision
  • It’s NOT a release plan:

Image may be NSFW.
Clik here to view.
Screen Shot 2018-07-09 at 2.19.27 PM

Roadmap components:

Image may be NSFW.
Clik here to view.
Screen Shot 2018-07-09 at 2.21.40 PM

The primary components are compulsory; the secondary provide color and context for stakeholders; the complementary provide other contexts that aren’t part of the roadmap (but may be part of the release plan)

Primary components

Image may be NSFW.
Clik here to view.
Screen Shot 2018-07-09 at 2.26.37 PM

Product vision: How a specific customer will benefit from your product as it becomes more fully-realized and ubiquitous. Sample (note how the PV is about customer benefit while the rest of the roadmap is about business needs):

Image may be NSFW.
Clik here to view.
Screen Shot 2018-07-09 at 2.28.14 PM

Business objectives are what will be measurably different for the org as you progress towards your product vision:Image may be NSFW.
Clik here to view.
Screen Shot 2018-07-09 at 2.33.08 PM

Timeframes should be kept broad (quarterly for example) rather than having specific delivery dates:

Image may be NSFW.
Clik here to view.
Screen Shot 2018-07-09 at 2.36.30 PM

(Note the even broader timeframe strategy: Now, Next, Later)

Themes are the problems / jobs to be done / needs of customers that you plan to fulfill while you drive towards product vision and business objectives:

Image may be NSFW.
Clik here to view.
Screen Shot 2018-07-09 at 2.42.10 PM

Disclaimers set the expectation that everything is subject to change — it’s even likely to change as you iteratively learn

Back to the sample:

Image may be NSFW.
Clik here to view.
Screen Shot 2018-07-09 at 2.47.00 PM

Note, aside from the hose there are no deliverables on this page

Establishing Product Vision

What is your product vision?

  • Google: To organize all of the data in the world and make it accessible for everyone in a useful way. Other Google orgs’ missions:
    • Chrome browser: To provide a fast, simple, and secure browser for everyone to experience the modern web
    • YouTube: To give everyone a voice and show them the world
    • Android: Helps people around the globe enjoy greater access to information and opportunity than ever before

Objectives & Key Results (OKRs)

A framework for measuring progress

Objectives:

  • What?The outcome you want to see
  • Why?To provide context about the purpose of the work

Key results:

  • What?Numerically-based expressions of progress towards an objective
  • Why?To provide a reference for evaluating how well you are executing on those objective
  • Generally set up quarterly

Roadmap Themes

To achieve our product vision, what themes would have to be solved? Example for SpaceX to get people to Mars:

  • Full reusability of rocketship
  • Refueling in orbit
  • Propellant production on Mars / Correct propellant

Image may be NSFW.
Clik here to view.
Screen Shot 2018-07-09 at 3.10.28 PM

An opportunity solution tree is another way to visualize this:

Image may be NSFW.
Clik here to view.
Screen Shot 2018-07-09 at 3.11.14 PM

The lo-tech version of this tree:

Image may be NSFW.
Clik here to view.
Screen Shot 2018-07-09 at 3.13.34 PM

Prioritize with Math

Three techniques you can research further esp in Bruce’s new book (see below):

Image may be NSFW.
Clik here to view.
Screen Shot 2018-07-09 at 3.15.44 PM

Another technique:

Image may be NSFW.
Clik here to view.
Screen Shot 2018-07-09 at 3.19.40 PM

Bruce suggests using T-shirt sizing here

Add in confidence:

Image may be NSFW.
Clik here to view.
Screen Shot 2018-07-09 at 3.21.19 PM

Example:

Image may be NSFW.
Clik here to view.
Screen Shot 2018-07-09 at 3.22.00 PM

Obtain Buy-in

  • Alignment (different from consensus)
    • Willingness to commit to a decision / directions that you may not agree with to achieve a common goal
  • Consensus (only if absolutely required)
  • Collaboration
    • Folks cooperate to accomplish a common goal
    • Testing validates goals

Shuttle diplomacy

Image may be NSFW.
Clik here to view.
Screen Shot 2018-07-09 at 3.28.53 PM

Image may be NSFW.
Clik here to view.
Screen Shot 2018-07-09 at 3.29.26 PM

Sample of a tool you can use for diplomacy:

Image may be NSFW.
Clik here to view.
Screen Shot 2018-07-09 at 3.31.30 PM

Present & Share

Why share roadmaps internally:

  • Alignment
  • Feedback
  • Inspiration
  • Co-creation

Why share roadmaps with customers:

  • Feedback
  • Avoid overpromise and under deliver
  • Competitive advantage — lead vs play catchup

 

Secondary components

Image may be NSFW.
Clik here to view.
Screen Shot 2018-07-09 at 2.49.17 PM

Be cautious when sharing these, since they are expected to change over time

  • Confidence measures how confident you are in a feature’s durable importance over time
  • Target CMRs are different buckets of customers
  • Dev stage denotes where in the process (discovery, design etc through final testing) something is
  • These details can be added to your existing product screen:

Image may be NSFW.
Clik here to view.
Screen Shot 2018-07-09 at 2.54.00 PM

Great example of a fully realized roadmap from chef.io:

Image may be NSFW.
Clik here to view.
Screen Shot 2018-07-09 at 3.39.32 PM

 

About Bruce McCarthy (from uie.com): It’s not every day that you run across a friendly subject-matter expert like Bruce McCarthy. He’s so invested in helping product managers and UX designers work smarter that his company—UpUp Labs—is launching a tool to help them validate requirements before jumping to design: www.reqqs.com

Bruce’s new book is Product Roadmaps Relaunched

Advertisements

Report this ad
Report this ad

Leave a Reply

Post navigation


Viewing all articles
Browse latest Browse all 150

Trending Articles