Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Sign up for free
Menu
Search
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Pricing
Search
Sign in
Sign up for free
Lean UX: Scope - Content
Search
Sponsored
·
Your Podcast. Everywhere. Effortlessly.
Share. Educate. Inspire. Entertain. You do you. We'll handle the rest.
→
Sergio Nouvel
July 08, 2013
Design
520
3
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
Lean UX: Scope - Content
Sergio Nouvel
July 08, 2013
More Decks by Sergio Nouvel
See All by Sergio Nouvel
Involúcrate
shesho
0
170
Transformación Digital: lo que hay y lo que falta
shesho
1
860
Diseño de Servicios centrados en el Ciudadano
shesho
2
910
Transformación Digital: de consumidores a creadores de tecnología
shesho
1
850
Transformación Digital y UX: El comienzo del viaje del héroe
shesho
5
1.3k
Scope Canvas (keynote)
shesho
6
1.2k
UX y Transformación Digital
shesho
2
1.1k
Emprendiendo al Revés: El caso Get on Board
shesho
39
16k
Fuck-up Nights: The Get on Board Way
shesho
0
350
Other Decks in Design
See All in Design
【CEDEC2026】派手さと見やすさは両立できる!『Shadowverse: Worlds Beyond』エフェクト・3D背景の超進化したビジュアル設計
cygames
PRO
1
1.9k
Where Imagination Ends AI Begins
r5ni4
0
380
もう迷わない!“なんとなく”を卒業するフォントの選び方【村田俊英】
toshihidemurata
0
950
明日から真似できる、AIでデザインシステムを活用する方法
vivion
0
560
分散するデザイン組織をつなぐ デザインミートアップの取り組み/nikkei-tech-talk49
nikkei_engineer_recruiting
1
200
個人理念(自分の言葉)の言語化ワークショップ
kakukoki
1
210
デザイナーがいない部署にハーネスを設計する
kenichiota0711
1
1.9k
富山デザイン勉強会_ブラッシュアップデザイン.pdf
keita_yoshikawa
0
120
AI-Slopなデザインを生まないためのデザインプロセス戦略
takanorip
10
5.9k
【CEDEC2026】『Shadowverse: Worlds Beyond』続編開発におけるUIデザイン・アニメーション演出の「超進化」 ~継承と挑戦を両立するデザイン手法~
cygames
PRO
3
5.2k
組織で働く大人が「知らないままにやってみる」を取り戻す方法とその意味〜企業で働く実務家による実践知の言語化を事例とした考察〜
chiemitaki
1
380
1000人規模の組織でデザインハーネスを導入するための第一歩
pkshadeck
PRO
5
3.9k
Featured
See All Featured
Game over? The fight for quality and originality in the time of robots
wayneb77
1
270
Embracing the Ebb and Flow
colly
88
5.2k
Navigating the Design Leadership Dip - Product Design Week Design Leaders+ Conference 2024
apolaine
2
430
How to audit for AI Accessibility on your Front & Back End
davetheseo
0
530
Designing for humans not robots
tammielis
254
26k
Design and Strategy: How to Deal with People Who Don’t "Get" Design
morganepeng
133
19k
We Have a Design System, Now What?
morganepeng
55
8.3k
The #1 spot is gone: here's how to win anyway
tamaranovitovic
3
1.2k
Accessibility Awareness
sabderemane
1
210
B2B Lead Gen: Tactics, Traps & Triumph
marketingsoph
0
240
How to Create Impact in a Changing Tech Landscape [PerfNow 2023]
tammyeverts
56
3.5k
Public Speaking Without Barfing On Your Shoes - THAT 2023
reverentgeek
1
560
Transcript
LEAN UX SCOPE 1. Scope 2. Content 3. Interface 4.
Look & Feel
SERGIO NOUVEL @SHESHO
A geolocalized app to help firefighters easily find fire plugs.
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.
✔ What do we test at this stage? Innovation Viability
Merit
✔ Innovation Does the product improve something over what already
exists? * Performance * Functionality * Design * Taste * Cost * Speed * Access * Reliability * etc.
✔ Viability Can the product be done with reasonable resources?
Is technology available? Are human resources available? Is there funding?
✔ 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?
Tool: Canvas We'll define 9 aspects that are key for
the business model of the product.
None
Tool Elevator Pitch Synthesize the value proposal in a 10-second,
no-visual aids pitch.
Define Key Hypotheses We'll define what the product needs to
prove true in order to deliver value to users.
Definir Key Behaviors ¿What (actions, habits, moods) do we want
to stimulate or ellicit in the users which prove our hypotheses true?
Definir Key Motivators ¿What do we give back to the
users in exchange or reward? ¿Is this connected with what users really want/need?
Tool Sprints We'll segment the project in progressive, minimum-viable stages.
Initial Idea Future vision Value proposal Scope of this iteration
SCOPING Which features will and will NOT have the project
at this stage?
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?
Tool Storytelling We'll tell the "tale" of our app inmersed
in the world of our users.
TECHNIQUES Drawing Written text Video Audio narrative 1: DEFINING PERSONAS
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.
DON'T BE AFRAID TO DRAW
DON'T BE AFRAID TO WRITE
LEAN UX CONTENT 2. Content 1. Scope 3. Interface 4.
Look & Feel
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.
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.
✔ What do we test at this stage? Coherence Familiarity
Simplicity of access and consumption
Define Metaphor Which elements of the user's world can be
applied to the product to ease adoption?
✔ 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?
Vocabulary What are the key sections and actions? How are
they named by our users? How do they expect to be talked?
Tone and style If our product was a person, how
would he/she dress? and talk? and behave?
Key places Where in the product the key hypotheses and
behaviors will take place and can be observed?
Deliverable: Sitemap We'll structure the user paths in form of
a flow chart.