Lean UX - Applying Lean Principles to improve
User Experience in Agile environment. It accomplishes this by getting out of the deliverables business and instead focusing on successful experiences.
The Design Sprints are a 2-5 days process for answering critical business questions through design, prototyping, and testing ideas with customers.
In this keynote I present you the Google Venture Design Sprints Methodology.
Event 5, which focuses on the activity of "Validate," is the final task of a 5-Day Lean Design Sprint. This presentation provides visual checklists and templates that can be used to facilitate the activity of "Validate."
An Engineer’s Essential Tool in Agile: Design ThinkingSoniaMayPatlan
Many engineers are not connected to customers, resulting in solutions that lack high impact and benefit. But by combining design thinking with Agile, we create innovations that delight our customers. Find out, how a design thinking model called Design for Delight is applied within Agile frameworks to deliver thoughtful and inclusive solutions that can change the world.
The Design Sprints are a 2-5 days process for answering critical business questions through design, prototyping, and testing ideas with customers.
In this keynote I present you the Google Venture Design Sprints Methodology.
Event 5, which focuses on the activity of "Validate," is the final task of a 5-Day Lean Design Sprint. This presentation provides visual checklists and templates that can be used to facilitate the activity of "Validate."
An Engineer’s Essential Tool in Agile: Design ThinkingSoniaMayPatlan
Many engineers are not connected to customers, resulting in solutions that lack high impact and benefit. But by combining design thinking with Agile, we create innovations that delight our customers. Find out, how a design thinking model called Design for Delight is applied within Agile frameworks to deliver thoughtful and inclusive solutions that can change the world.
Discover more to learn detail with google design sprint, great tools to maximize and validate your idea with lack of creativity and enhancing collaboration.
The team at GV (Google Ventures) has graciously published a fabulous book, "Sprint," in which Jake Knapp with John Zeratsky and Braden Kowitz comprehensively explain their Design Sprint Methodology. It's a five-day process that spans from Monday to Friday. Design Sprint Events or Activities are respectively Understand-Diverge-Decide-Prototype-Validate. This presentation focuses on Event 1, which is "Understand."
In this presentation, the visual tool of the Design Sprint (DS) Map is used to summarize "Understand" tasks as a visual checklist. In addition, the DS Map is used to present a worksheet that is used to visually collect, organize, select, and test (C.O.S.T.) ideas during a Design Sprint. Included in the presentation are three case studies that illustrate how the "Understand" activity is used on Day (Event) 1 of the 5-Day Sprint.
I gave this to the Melbourne Scrum Users Group. It was an interesting group with a few experience scrum users and many inexperienced people via the ACS, so the talk had to accommodate some Scrum 101 stuff, and went longer than planned with me talking for a bit over an hour.
In the end it went well, and I hope I get some feedback from the audience via the meetup site and ACS website.
We are going full bore on LeanUX at PayPal. This presentation just captures a lot of cautions for our teams. These anti-patterns call out bad behaviors or situations that can become bad which will stifle collaboration.
It doesn’t matter if you’re a one-person freelancer, a budding 5-10 person agency, or an established small to mid-sized company - you will always contend with the challenges of growth. This month, key employees from Raleigh-based web shop Atlantic BT (ABT) will share their experiences on how to build and maintain a foundation for growth in light of pressures from increasing demand.
COO, Software Development Manager, and Creative Director will share some patterns that triggered growth, and how each handled them.
You'll learn:
- How to transition through through inspiration, ideation, and implementation with a global team
- How to turn “statements of intent” into prioritized user stories.
- How to increase team velocity without sacrificing usability
Many information security companies struggle with changing their culture. It can be difficult to get an InfoSec team to focus fully on the issues that are important to the long-term health of the business: customer experience and process improvement. This article (part of a series) looks at some methods to implement cultural change at an InfoSec company in ways that will be sustainable and won’t alienate your team members.
This is a slide deck I originally presented at ALE2011 in Berlin about A3 thinking and Kaizen in the context of a large Lean & Agile enterprise transition.
At LESS2011 in Stockholm a few weeks later, it was even awarded as overall "best session of the conference" (in addition to "best in the Organisation Transformations category".
(also presented at SDC12 and lssc12)
Nov 2011: I want to humbly dedicate this work to Grant (PG) Rule, who suddenly left this world due to a tragic accident.
Mar 2013: Latest News: As a follow-up to the presentation, I created an iPhone/iPad app (called A3 Thinker)!!. It's a set of brainstorming cards to help people create substantially better A3s. see http://a3thinker.com for details. A set of physical cards will soon follow.
24 July 2013: ...and yesterday I released the Android version on Google Play!
Sep 2013: finally! The formidable A3 Thinker action deck is live! http://a3thinker.com/deck
How did we sell DT, how did the workshops with clients and users, which methods work and which ones do not.
Examples of real projects: both successful and not very)
- What is DT and why everyone is talking about it
- Key DT elements
- How DT works in outsourcing
- How the theory differs in practice
- How to sell DT
- How a project with DT fails
By Janet de Acevedo Macdonald
"If you love to show, then wherever Arabian horse lovers gather is a prime travel destination." My observations about Tulsa, Oklahoma, the site of the US National Championship Show for the Arabian Horse Association.
Discover more to learn detail with google design sprint, great tools to maximize and validate your idea with lack of creativity and enhancing collaboration.
The team at GV (Google Ventures) has graciously published a fabulous book, "Sprint," in which Jake Knapp with John Zeratsky and Braden Kowitz comprehensively explain their Design Sprint Methodology. It's a five-day process that spans from Monday to Friday. Design Sprint Events or Activities are respectively Understand-Diverge-Decide-Prototype-Validate. This presentation focuses on Event 1, which is "Understand."
In this presentation, the visual tool of the Design Sprint (DS) Map is used to summarize "Understand" tasks as a visual checklist. In addition, the DS Map is used to present a worksheet that is used to visually collect, organize, select, and test (C.O.S.T.) ideas during a Design Sprint. Included in the presentation are three case studies that illustrate how the "Understand" activity is used on Day (Event) 1 of the 5-Day Sprint.
I gave this to the Melbourne Scrum Users Group. It was an interesting group with a few experience scrum users and many inexperienced people via the ACS, so the talk had to accommodate some Scrum 101 stuff, and went longer than planned with me talking for a bit over an hour.
In the end it went well, and I hope I get some feedback from the audience via the meetup site and ACS website.
We are going full bore on LeanUX at PayPal. This presentation just captures a lot of cautions for our teams. These anti-patterns call out bad behaviors or situations that can become bad which will stifle collaboration.
It doesn’t matter if you’re a one-person freelancer, a budding 5-10 person agency, or an established small to mid-sized company - you will always contend with the challenges of growth. This month, key employees from Raleigh-based web shop Atlantic BT (ABT) will share their experiences on how to build and maintain a foundation for growth in light of pressures from increasing demand.
COO, Software Development Manager, and Creative Director will share some patterns that triggered growth, and how each handled them.
You'll learn:
- How to transition through through inspiration, ideation, and implementation with a global team
- How to turn “statements of intent” into prioritized user stories.
- How to increase team velocity without sacrificing usability
Many information security companies struggle with changing their culture. It can be difficult to get an InfoSec team to focus fully on the issues that are important to the long-term health of the business: customer experience and process improvement. This article (part of a series) looks at some methods to implement cultural change at an InfoSec company in ways that will be sustainable and won’t alienate your team members.
This is a slide deck I originally presented at ALE2011 in Berlin about A3 thinking and Kaizen in the context of a large Lean & Agile enterprise transition.
At LESS2011 in Stockholm a few weeks later, it was even awarded as overall "best session of the conference" (in addition to "best in the Organisation Transformations category".
(also presented at SDC12 and lssc12)
Nov 2011: I want to humbly dedicate this work to Grant (PG) Rule, who suddenly left this world due to a tragic accident.
Mar 2013: Latest News: As a follow-up to the presentation, I created an iPhone/iPad app (called A3 Thinker)!!. It's a set of brainstorming cards to help people create substantially better A3s. see http://a3thinker.com for details. A set of physical cards will soon follow.
24 July 2013: ...and yesterday I released the Android version on Google Play!
Sep 2013: finally! The formidable A3 Thinker action deck is live! http://a3thinker.com/deck
How did we sell DT, how did the workshops with clients and users, which methods work and which ones do not.
Examples of real projects: both successful and not very)
- What is DT and why everyone is talking about it
- Key DT elements
- How DT works in outsourcing
- How the theory differs in practice
- How to sell DT
- How a project with DT fails
By Janet de Acevedo Macdonald
"If you love to show, then wherever Arabian horse lovers gather is a prime travel destination." My observations about Tulsa, Oklahoma, the site of the US National Championship Show for the Arabian Horse Association.
5 Lessons Learned in Product Management by Twitch Senior PMProduct School
Main takeaways:
- How to take a non traditional path to product management
- How to leverage your unique background to differentiate yourself as a Product Manager
- Steps you can take to build your product management skills/portfolio while in other fields
From Product Vision to Story Map - Lean / Agile Product shapingJérôme Kehrli
A lot of Software Engineering projects fail for a lack of shared vision due to poor communication among people involved in the project.
A sound maintenance of the product backlog can only be achieved if all the people have a good understanding of what they have to do (common vision).
Roman Pichler, in a post originally written in Jul 16 2012, has proposed a really interesting approach: use various canvas to create and share product vision and product backlog creation and refinement.
This presentation is a drive through these various boards and canvas that should be designed in prior to any product development: the Product Vision, the Lean Canvas, The Product Definition and the Story Map.
Highest quality code in your SaaS project. Why should you care about it as a ...The Codest
We are launching a SaaS report dedicated to the whole SaaS market.
It is a useful pill of knowledge for the non-technical founders who are struggling with many challenges, especially the technological ones. In the report, we cover the specific problems/dilemmas such as:
- Is it worth making SaaS start-up if you are a non-technical founder?
- What are the biggest challenges to a non-technical founder?
- MVP as the most popular way to deliver product time to market
- Useful tips on how to build a SaaS product in 6 simple steps
Check out the report and make sure to eliminate common mistakes that can hurt your business. Are you a non-technical founder? Don’t worry!
In the short tutorial, you will learn how to successfully build a SaaS product with no programming skills.
Building Delightful Products: A Customer-Centric Approach to Product Strategy...Perfetti Media
In this presentation, Carbonite's User Experience Director, Christine Perfetti, will share proven techniques for quickly exploring new design approaches based on solid customer data. She will share approaches for gathering customer insights, generating new product concepts, and evaluating designs.
Current Trends in Agile - opening keynote for Agile Israel 2014Yuval Yeret
Yuval Yeret, AgileSparks’s CTO will give trends overview session – What is hot, what is not, in the lean agile industry/community – with the aim of exposing people and giving a big picture view that places the different trends as well as sessions in the conference into the right context. We will discuss trends like Scaling Agile (SAFe, Less, DAD), DevOps / Continuous Delivery, Modern Management aspects, Modern Change Management approaches such as Open-Agile-Adoption, What is going on in the world of Kanban, Agile Fluency, Technical Safety / Anzeneering, and maybe more.
http://agileisrael2014.com/current-trends-in-agile/
Why outsource at all, why Scrum and how to find a perfect candidate to do the job?
What are the advantages of reading the e-book?
#Better understanding of basic Scrum, Agile and outsourcing method,
#Understanding of the importance of group work and consequences of that approach,
#Understanding of business value that comes with getting project done in Scrum,
#Better understanding and need of preparedness for making a project in Scrum.
Why outsource at all, why Scrum and how to find a perfect candidate to do the job?
Advantages of reading the e-book:
Better understanding of basic Scrum, Agile and outsourcing method,
Understanding of the importance of group work and consequences of that approach,
Understanding of business value that comes with getting project done in Scrum,
Better understanding and need of preparedness for making a project in Scrum.
Practical Experience with Christensen's Innovation Methodology JOBS(R) Jobs-t...vonreventlow
Clayton Christensen's Jobs-to-be-done approach describe a series of steps to create innovation systematically. This deck describes the application of the methodology to the creation of the Avaya Flare User Experience, the Avaya Digital Video Device and the related enterprise cloud offer. We found key for success is to add focus on emotions. And the result to be a condensed job description as more work is required to detail the solutions that it becomes testable against objectives and barriers.
Between Filth and Fortune- Urban Cattle Foraging Realities by Devi S Nair, An...Mansi Shah
This study examines cattle rearing in urban and rural settings, focusing on milk production and consumption. By exploring a case in Ahmedabad, it highlights the challenges and processes in dairy farming across different environments, emphasising the need for sustainable practices and the essential role of milk in daily consumption.
Transforming Brand Perception and Boosting Profitabilityaaryangarg12
In today's digital era, the dynamics of brand perception, consumer behavior, and profitability have been profoundly reshaped by the synergy of branding, social media, and website design. This research paper investigates the transformative power of these elements in influencing how individuals perceive brands and products and how this transformation can be harnessed to drive sales and profitability for businesses.
Through an exploration of brand psychology and consumer behavior, this study sheds light on the intricate ways in which effective branding strategies, strategic social media engagement, and user-centric website design contribute to altering consumers' perceptions. We delve into the principles that underlie successful brand transformations, examining how visual identity, messaging, and storytelling can captivate and resonate with target audiences.
Methodologically, this research employs a comprehensive approach, combining qualitative and quantitative analyses. Real-world case studies illustrate the impact of branding, social media campaigns, and website redesigns on consumer perception, sales figures, and profitability. We assess the various metrics, including brand awareness, customer engagement, conversion rates, and revenue growth, to measure the effectiveness of these strategies.
The results underscore the pivotal role of cohesive branding, social media influence, and website usability in shaping positive brand perceptions, influencing consumer decisions, and ultimately bolstering sales and profitability. This paper provides actionable insights and strategic recommendations for businesses seeking to leverage branding, social media, and website design as potent tools to enhance their market position and financial success.
Expert Accessory Dwelling Unit (ADU) Drafting ServicesResDraft
Whether you’re looking to create a guest house, a rental unit, or a private retreat, our experienced team will design a space that complements your existing home and maximizes your investment. We provide personalized, comprehensive expert accessory dwelling unit (ADU)drafting solutions tailored to your needs, ensuring a seamless process from concept to completion.
Dive into the innovative world of smart garages with our insightful presentation, "Exploring the Future of Smart Garages." This comprehensive guide covers the latest advancements in garage technology, including automated systems, smart security features, energy efficiency solutions, and seamless integration with smart home ecosystems. Learn how these technologies are transforming traditional garages into high-tech, efficient spaces that enhance convenience, safety, and sustainability.
Ideal for homeowners, tech enthusiasts, and industry professionals, this presentation provides valuable insights into the trends, benefits, and future developments in smart garage technology. Stay ahead of the curve with our expert analysis and practical tips on implementing smart garage solutions.
Book Formatting: Quality Control Checks for DesignersConfidence Ago
This presentation was made to help designers who work in publishing houses or format books for printing ensure quality.
Quality control is vital to every industry. This is why every department in a company need create a method they use in ensuring quality. This, perhaps, will not only improve the quality of products and bring errors to the barest minimum, but take it to a near perfect finish.
It is beyond a moot point that a good book will somewhat be judged by its cover, but the content of the book remains king. No matter how beautiful the cover, if the quality of writing or presentation is off, that will be a reason for readers not to come back to the book or recommend it.
So, this presentation points designers to some important things that may be missed by an editor that they could eventually discover and call the attention of the editor.
Hello everyone! I am thrilled to present my latest portfolio on LinkedIn, marking the culmination of my architectural journey thus far. Over the span of five years, I've been fortunate to acquire a wealth of knowledge under the guidance of esteemed professors and industry mentors. From rigorous academic pursuits to practical engagements, each experience has contributed to my growth and refinement as an architecture student. This portfolio not only showcases my projects but also underscores my attention to detail and to innovative architecture as a profession.
1. Applying Lean Principles to Improve
User Experience in Agile Environment
Darren F. Gideon
Principal Web Developer UI
Citrix Web Services
2. It’s focus is strictly on the design phase of software
development process. Best practice is to use
staggered sprints also known as Cycle 0 and Sprint
Zero.
Design activity takes place one sprint ahead of
development.
3. It is a methodology inspired by “Lean Startup” and
“Agile” for bringing UX designs to light faster with less
emphasis on deliverables and with greater focus on
the actual experiences being designed.
4. It accomplishes this by getting out of the deliverables
business and instead focusing on successful
experiences. It focuses more on creating successful
experiences by:
1. Removing waste from design process
2. Harmonizing the interaction of designers, developers, product manager, QA,
etc. into a transparent cross functional collaboration of all involved parties.
3. Relying on rapid experimentation and measurement to quickly learn how well or
not ideas are meeting the users goals. The designer’s role is one of design
facilitation instead of sole point of view.
5. • Not being judged by the depth and breadth of delivered
documents (delivery of pixel perfect hi-defs and extensive
documentation before presenting to collaborative team,
customer, and or users).
• Being judged by the success of the end-state experience
for the user.
6. It focuses on ensuring the ideas that have the most
value get the most resources via:
1. Experimentation
2. Rapid Iteration
3. Evolutionary Process
7.
8. Hi, HR its Darth Vader
here. I need some
personnel for
a planetary operation.
9. No problem Darth Vader.
Will this candidate do? He
says he knows Photoshop.
10. No, I don’t need a
designer. I need canon
fodder for a ground
assault.
11. Oh, he knows COBOL too.
What if we can outfit him
with Storm Trooper
equipment? Would he fulfill
what you need then?
12. He knows COBOL? He
definitely will be good
canon fodder then.
But I don’t need a Storm
Trooper. The assault is on
the ice planet Hoth.
13. Oh, so you need him
outfitted with cold weather
gear. How about him now
as a Snow Trooper?
14. Perfect!
Get him outfitted with full
Snow Trooper armor,
weapons, and cold weather
gear.
Then put him on the next
transport to Hoth.
Oh, make sure he signs
the proper
“RELEASE”
forms before he
goes.
15. 1. Darth Vader makes a request to fulfill an outcome
2. A “minimum viable product” (MVP) is presented to be
critiqued.
3. The MVP is critiqued and sent back, starting the next
iteration.
4. The MVP is adjusted just enough to prove the concept and
then presented again for critique.
5. Additional rapid iterations happen where the MVP is evolved
until it meets the desired outcome.
6. The MVP is then prototyped and goes through the iteration
process again until approved. It is then sent to Hoth to be
validated in battle.
16. Because the biggest lie in software development is “Phase II.”
A successful experience is a feature that actually ships that
meets the customer and business goal(s). Delivering an
experience that doesn’t do this with a promise of finishing the
experience in Phase II is delivering a bad / incomplete experience
to the end user that might never be rectified.
So why does this happen?
Usually because a team ran out of time and then there never was
a phase II. Or the customer goals change in phase II leaving a
bad / incomplete end-state experience in place.
17. LEAN UX is based on three processes that are used to
reduce waste and achieve a better end-state experience
faster:
1. Design thinking
2. Agile development
3. Feedback loop that where a team works collaboratively
to iterate repeatedly through a path to achieve a
desired outcome
18. Design thinking starts with the goal or what is desired
to be achieved by the user instead of starting with a
certain problem. Direct observation of what “users”
want to accomplish and what they like and dislike
leads to innovation and the achievement of a
successful outcome.
19. 1. Emphasis on individuals and interactions over
processes and tools
2. Working software over comprehensive documentation
3. Customer collaboration over contract negotiation
4. Responding to change over rigidly following a plan.
5. The realization that the initial design will have something
wrong in it. So the goal should be find out what
is wrong as soon as possible, then adjust, and test again.
20. A feedback loop is the process where you create the
minimum viable product (MVP) to quickly test your
assumptions, adjust the MVP based on feedback,
and test again.
Getting your collaborative team and then customer
feedback avoids you making incorrect market
assumptions.
Your design is a hypothesis and your goal is to
validate the solution by team and customer feedback.
21.
22. By providing insight into the design work to your
teammates sooner rather than later you accomplish
the following:
1. It ensure that you’re aligned with the broader team and the business
vision
2. Give developers a sneak peek at the direction of the application
enabling them to spot challenges earlier and speed up development
3. Fleshes out your thinking, since displaying your concepts to others
forces you to focus on areas that you didn’t initially think of
or deemed important
23. 1. Cross Functional teams
2. Progress equals outcomes not output
3. Problem focused not features implemented
4. Remove waste
5. GOOB, the new user centricity
6. Small batch size
7. Continuous discovery
8. Shared understanding
9. Externalizing your work
10. Don’t over analysis
11. Learning over growth
12. Get out of the deliverables business
13. Permission to fail
24. Teams made up of the various disciplines involved in
creating your product. Their involvement should be
continuous from the first day of the project until the
end.
The creation of a diverse team collapses the handoff
process known as waterfall. Allows insight and
foresight on each idea for all those involved. Which
fosters greater team efficiency.
25. Features and services are outputs.
The business goals they are meant to achieve our
outcomes. By managing and measuring against
outcomes we gain insight of whether the features we
are building meat those outcomes.
If a feature is not performing well we can objectively
decide as to if it should be kept, changed, or
replaced.
26. A problem focused team is one that has been
assigned a business problem to solve (or an outcome
to achieve) instead of a set of features to implement.
• It allows for innovation by the team
• It shows trust in the team to find a solution
• It fosters an investment by the team in the
outcome
27. A core tenant is the removal of anything that doesn’t
lead to the ultimate goal. Which is improved
outcomes. You do this because team resources are
limited.
The more waste a team can eliminate, the faster they
can move.
28. “Getting out of the Building” coined by Steven Blank.
Meeting room debates about user needs won’t be
settled in your office. The answers lie out in the
marketplace. So you should give potential users a
chance to provide feedback on your ideas as soon as
possible.
It is better to find out early if you are missing the mark
BEFORE you spent the time and resources to build a
product that nobody wants.
The success of failure of a product isn’t the team’s
decision but ultimately the end user.
29. Create only the design that is necessary to move the
team forward and avoid a big inventory of untested
and unimplemented ideas.
Large batch forces a team to wait for big deliverables.
It also keeps them from learning whether the ideas
are valid or not.
30. The ongoing process of engaging the customer
during the design and development process.
The goal is to understand what users are doing with
your products and why the are doing it. Research
must be frequent and the entire team should be
involved.
The involvement of the team will build empathy and
understanding for the users and the problems they
face.
31. It’s the collective knowledge a team builds up over
time as they work together. The more a team
collectively understands not only what it is doing but
why, the less it has to depend on second hand
reports and detail documents to continue it work.
32. Getting your ides out of your head and into public
view allows everyone to see where the team stands.
This can be done by whiteboards, printouts, etc.
You do this to create a flow of information across the
team. Which helps to inspire ideas off of ones that
have already been shared. It also more quickly
exposes possible issues with ideas that then can be
interated on or discarded.
33. There is more value in creating a first version of an
idea than spending half a day debating its merits in a
conference room.
The most difficult questions will not be answered in a
conference room debate but by users in the field. To
get user input you need to make ideas concrete so
that they have something to respond to.
34. It’s difficult to figure out the right thing to build and
scale a business around it at the same time.
Scaling an idea that is unproven is risky. It might work
and it might not. If it doesn’t work and you scaled it to
your entire user base you have wasted valuable time
and resources.
Ensuring the idea is right on a smaller scale mitigates
this risk (e.g. Canary releases, beta groups, etc.)
35. The focus of the design process should be creating
the successful outcomes not documents.
Documents don’t solve customer problems – good
products do. The team’s focus should be on learning
which features have the biggest impact on their
customers. The artifacts the team uses to gain that
knowledge is irrelevant.
36. In order to find the best solutions to problems the
team needs to experiment with ideas. Most of these
ideas will fail.
The team must be safe to fail if they are to be
successful. So permission to fail means a team has a
safe environment to experiment in which creates a
culture of experimentation and creativity.
Derek Silvers (CD Baby Founder) has a video called
“Why you need to fail” which goes into this.
http://www.youtube.com/water?v=HhxcFGuKOys
37.
38.
39. Here we have our COBOL developer. One of his
hobbies is to race cars, the Mach 5 in this
instance.
40. He is racing on course new to him and he
is taking this corner at speed for the first time. He
likes to use a “heel-and-toe shifing” method but
will it be to fast for this corner?
43. He learned just how fast he can take this corner on
this race track? If he didn’t fail he would never know
how close he can push things to the edge without
failing.
44. Traditional UX design projects are framed by
requirements and deliverables. LEAN UX goal is not
about create a deliverable but to create an outcome
by starting with assumptions instead of requirements.
The main tool for this is the Hypothesis statement
which is made up of these elements:
• Assumptions
• Hypotheses
• Outcomes
• Personas
• Features
45. A high level declaration of what we believe to be true.
It’s a the starting point and the team should be
involved so everyone is on same page.
46. More detailed description of our assumptions that
target specific areas of our product / workflow for
experimentation. Breaking down your assumptions
into hypotheses allows you to test these
assumptions.
• We believe this statement is true
• We will know we’re right/wrong by the following
feedback from users
• [qualitative feedback] and/or [quantitative
feedback] and/or [key performance indicator
change].
47. What we seek from the market / users to help us
validate or invalidate our hypotheses. These need to
be specific to be useful.
48. Models of the people for whom we believe we are
solving a problem.
49. The product changes or improvements we believe will
obtain the outcomes we seek.
Once you have a list of outcomes you want to
achieve then you can start thinking about tactics,
features, products, and services you can put in place
to achieve those desired outcomes.
50.
51. The product changes or improvements we believe will
obtain the outcomes we seek.
Once you have a list of outcomes you want to
achieve then you can start thinking about tactics,
features, products, and services you can put in place
to achieve those desired outcomes.
52. The product changes or improvements we believe will
obtain the outcomes we seek.
Once you have a list of outcomes you want to
achieve then you can start thinking about tactics,
features, products, and services you can put in place
to achieve those desired outcomes.
53. The product changes or improvements we believe will
obtain the outcomes we seek.
Once you have a list of outcomes you want to
achieve then you can start thinking about tactics,
features, products, and services you can put in place
to achieve those desired outcomes.
54. 1. Shifting from output to outcomes
2. Move from limited roles to collaborative capabilities
3. Embracing new skills
4. Create cross-functional teams
5. Create small teams
6. Create co-located collaborative workspaces
7. Eliminate “Big Design Up Front”
8. Speed first, aesthetics second
9. Valuing problem solving
10. Embracing UX debt
11. After LEAN UX transition back to company document standards
12. Be realistic about your environment
55. Teams must shift conversation with leadership from one
based on features to one centered on achieving outcomes.
56. Discouraging cross-functional input encourage
organizational silos which is the death of collaboration.
Need to adopt mantra of “competencies over roles. Every
team member has multiple competencies and skills. Both
primary and secondary.
57. While teams still need core UX and design skills you also
need to add facilitation as a core competency.
Designers must open up the design process. The team not
the individual most own the product design.
Designers must take a leadership role in the team where
they provide leadership and facilitation in a group
brainstorming activities.
58. Collaboration for many teams is a single discipline activity;
developers solving problems with other developers, etc.
Involving everybody in process facilitates communication.
Allows for a broader range of insights and creates a
greater cohesion of all members working toward the same
goal.
59. Large groups are less efficient than smaller groups.
Smaller teams also forces members to work on smaller
problems and be more focused.
Jeff Bezos calls these “two-pizza teams.” If the team
needs more than two pizzas for a meal, it’s to big.
60. Co-locate teams to the same workspace which makes
everybody more visible and accessible. Face to face
conversation is more effective than anything else for
showing some work, discussing, sketching, and
exchanging ideas, understanding body language and facial
expressions (sub-text), when trying to reach a resolution
on something.
61. Instead of documenting and presenting a complete product
from end to end MVPs (minimum viable products) allow for
ideas to be seen much sooner than before. It gives a
glimpse into actual product experience and allows for a
quicker iteration of designs to be more usable and
feasible.
62. Jason Fried, CEO of 37Signals once said “speed first,
aesthetics second.”
He is not talking about compromising quality.
It is creating about creating the MVP (minimum viable
product) to demonstrate something to start the whole
evolutionary cycle of iterations. Your first design will not be
perfect, what you want is it to be useable enough to start
to start the process.
Get it done, get it out there, discuss, modify based on
discussion, and iterate.
63. Companies value problem solving over aesthetics. The
ability to illustrate the path you take to get from an idea to
validated learning to end experience is what is valuable.
64. It’s often the case in agile environment that you do not go
back to improve the user experience.
“It’s not iterative if you only do it once.”
To improve the team needs to do more than refactor code
and address technical debt. The team also has to commit
to evaluating, reworking, and improving the user interface
and experience based on user feedback and testing.
UX debt is the commitment to continuous improvement of
the user experience.
65. Yes, many organizations have strict documentation
standards. However, as hypotheses are proven and design
directions are solidify then transition back to
documentation required by company. Otherwise it is waste
to document something that you might discard after
testing.
66. Change can be disconcerting for many individuals who are
used to do things in a certain way. So in many cases it is
best to ask forgiveness instead of permission.
Proving that you saved time and money or create a more
successful outcome will better make your case than asking
permission and explaining why you think it will produce
better results.