Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Lean UX: Scope - Content

Lean UX: Scope - Content

Sergio Nouvel

July 08, 2013
Tweet

More Decks by Sergio Nouvel

Other Decks in Design

Transcript

  1. LEAN UX
    SCOPE
    1. Scope 2. Content 3. Interface 4. Look & Feel

    View Slide

  2. SERGIO NOUVEL
    @SHESHO

    View Slide

  3. A geolocalized app to help
    firefighters easily find fire plugs.

    View Slide

  4. We'll define the value proposal, the
    target audience and the feature set
    of the project.
    What's defined in this session will guide the complete
    development process.

    View Slide


  5. What do we test at this stage?
    Innovation
    Viability
    Merit

    View Slide


  6. Innovation
    Does the product improve something
    over what already exists?
    * Performance *
    Functionality *
    Design * Taste * Cost *
    Speed * Access *
    Reliability *
    etc.

    View Slide


  7. Viability
    Can the product be done with
    reasonable resources?
    Is technology
    available?
    Are human resources
    available?
    Is there funding?

    View Slide


  8. Merit
    Does the product deserve to exist
    and be made by us?
    Do we love the idea?
    Is it within our skills?
    Is it worthy for the final
    user?

    View Slide

  9. Tool:
    Canvas
    We'll define 9 aspects that are key for
    the business model of the product.

    View Slide

  10. View Slide

  11. Tool
    Elevator Pitch
    Synthesize the value proposal in a
    10-second, no-visual aids pitch.

    View Slide

  12. Define
    Key Hypotheses
    We'll define what the product
    needs to prove true in order to
    deliver value to users.

    View Slide

  13. Definir
    Key Behaviors
    ¿What (actions, habits, moods) do
    we want to stimulate or ellicit in
    the users which prove our
    hypotheses true?

    View Slide

  14. Definir
    Key Motivators
    ¿What do we give back to the users
    in exchange or reward? ¿Is this
    connected with what users really
    want/need?

    View Slide

  15. Tool
    Sprints
    We'll segment the project in
    progressive, minimum-viable
    stages.

    View Slide

  16. Initial
    Idea
    Future vision
    Value proposal
    Scope of this iteration

    View Slide

  17. SCOPING
    Which features will and will NOT
    have the project at this stage?

    View Slide

  18. EMPATHIZING WITH
    OUR TARGET USERS
    What are the priorities of our
    customers?
    How do they think and feel?
    How this product will make our
    customers happier?

    View Slide

  19. Tool
    Storytelling
    We'll tell the "tale" of our app
    inmersed in the world of our users.

    View Slide

  20. TECHNIQUES
    Drawing
    Written text
    Video
    Audio narrative
    1: DEFINING PERSONAS

    View Slide

  21. Our users are human beings.
    Real. Imperfect. They have
    feelings. They have limits. They
    don't have all the time in the
    world. They don't care about our
    product.

    View Slide

  22. DON'T BE AFRAID TO DRAW

    View Slide

  23. DON'T BE AFRAID TO WRITE

    View Slide

  24. LEAN UX
    CONTENT
    2. Content
    1. Scope 3. Interface 4. Look & Feel

    View Slide

  25. We'll define the structure and content
    strategy of our product, describing
    the user flows and how are we telling
    our story to our users.

    View Slide

  26. Our users need to understand
    where they are. Where they can
    go. Feel at home. Intuit rather
    than decide. The product must
    think like they do.
    Not the other way around.

    View Slide


  27. What do we test at this stage?
    Coherence
    Familiarity
    Simplicity of access
    and consumption

    View Slide

  28. Define
    Metaphor
    Which elements of the user's
    world can be applied to the
    product to ease adoption?

    View Slide


  29. Familiarity
    We'll go out and ask
    people for their
    referents.
    Of what we do, which things are
    already similar to something
    familiar to the user?
    Which ones can be unknown or
    obscure?
    How can we make them more
    understandable?

    View Slide

  30. Vocabulary
    What are the key sections and
    actions? How are they named
    by our users? How do they
    expect to be talked?

    View Slide

  31. Tone and style
    If our product was a person,
    how would he/she dress? and
    talk? and behave?

    View Slide

  32. Key places
    Where in the product the key
    hypotheses and behaviors will
    take place and can be
    observed?

    View Slide

  33. Deliverable:
    Sitemap
    We'll structure the user paths in
    form of a flow chart.

    View Slide