Wireframing has held sway over UXers for the past 20 years. From its metaphoric origins in filmmaking to its pinnacle in countless UX books, wireframing stood as a key approach in defining both structure & interaction. In recent years, however, wireframing has come under attack. UX thinkers propose replacing wireframes with sketches and prototypes; yet we need to understand that bridge between idea and specification.
Lean engineering for lean/balanced teams: lessons learned (and still learning...Balanced Team
Bill Scott, PayPal
How do you take a gigantic organization and begin to transform the products? One key is to change the way teams work together to build experiences by following a Lean UX methodology. However, essential to this is to have engineering fully onboard as an integrated partner in the process. In this talk, Bill Scott will share 6 principles gleaned from the last two years to transforming engineering and the technology stack to support this working model.
Lean engineering for lean/balanced teams: lessons learned (and still learning...Balanced Team
Bill Scott, PayPal
How do you take a gigantic organization and begin to transform the products? One key is to change the way teams work together to build experiences by following a Lean UX methodology. However, essential to this is to have engineering fully onboard as an integrated partner in the process. In this talk, Bill Scott will share 6 principles gleaned from the last two years to transforming engineering and the technology stack to support this working model.
HTML5 seems to stuck in a rut: we got people very excited about it but at the same time we told them it doesn't work and needs a special environment and all kind of other quick shots. Now is the time to look at HTML5 closer again and take a look at where we stand. We're in good shape, we just need to look at the mirror again.
6 Principles for Enabling Build/Measure/Learn: Lean Engineering in ActionBill Scott
Presented at Lean Day West - Portland, OR. Sept. 17, 2013
How do you take a gigantic organization like PayPal and begin to transform the experiences? Engineering is often the key blocker in being able to achieve a high rate of innovation. In this talk, Bill Scott will give specific examples on implemented Lean UX in a 13,000 person company, re-factored the technology stack and changed the way engineers work with design & product partners. In addition, Bill will provide additional examples that go back to his early days writing one of the first Macintosh games to his more recent work at Netflix and the power of treating the user interface layer as the experimentation layer.
Rapid video prototyping for connected productsMartin Charlier
Slides from a workshop on using video as a rapid prototyping tool for connected products run by Tom Metcalfe and Martin Charlier at Interaction16 conference in Helsinki.
Given at Agile Camp 2013, San Jose, CA. Sept. 21
How do you take a gigantic organization like PayPal that was entrenched in a culture of a “”long shelf life”” and transform it to a culture of rapid experimentation? Bill will give 3 principles applied to PayPal engineering to make it a full partner with Lean UX. This will be illustrated by showing how they re-factored the tech stack and changed the way engineers work in Lean streams with design & product partners and how it plays with agile.
As a backdrop Bill will discuss several historical factors in the field of software engineering that are antithetical to the Lean Startup mindset but still find their way into most large enterprises. By understanding this historical context and applying lean principles he will demonstrate how a lean transformation can take place in any enterprise.
Any of these happen to you?
* Tasked to develop a user interface with an incomplete design spec, so had to make guesses such as where to position on-screen elements?
* Worked on a small team without a full-time designer, and requested to “just put a screen together for a demo”?
* Been asked to consult with a user interface designer, but don’t know what types of questions to pose?
Nowadays, everyone wants attractive, easy-to-use interfaces, so if you’re more comfortable sifting through Java or C# code than OmniGraffle or Visio mockups, learn about topics that can assist in creating more usable desktop applications, mobile apps, and websites. This talk provides easy-to-implement hints that can improve even a bad or “so-so” user interface. Areas of focus include the need for consistency; “negative space”; location, location, location (it’s crucial in screen real-estate, too!); contrasting colors; and the importance of action verbs.
This talk looks at the challenges we are facing when prototyping for mobile and gives an overview about the tools and handy helpers that you can use to deliver tappable, sharable and testable prototypes.
Lean Engineering: How to make Engineering a full Lean UX partnerBill Scott
In 1999, PayPal's name was synonymous with innovation. In fact, the so called PayPal Mafia (original founders) went on to establish Tesla, SpaceX, YouTube, Skype and other startups. They also provided the early investments of many of the most innovative companies on the internet today. But over time that innovation slowed to a crawl.
In 2011 a number of things begin to come together for PayPal that started its journey back to innovation. This is the story of that reboot and how engineering has played a key role in partnering directly with product and design to move from a culture of products having a long shelf life, to one of rapid experimentation.
In this talk, Bill will outline the principles of Lean Engineering; principles for engineering that enable learning. Drawing from his experience leading User Interface Engineering at both Netflix & PayPal, Bill will walk you through the key principles your engineering team will need to adopt to be that enabler for product and design in your organization. This talk will not just inspire you, but it will also give you some hard earned advice on making this a reality in your organization.
As presented at @media Ajax in London on 19th November 2007.
So we spent years learning our craft - specialising - reading the CSS specs in bed, hardwiring the Photoshop keyboard shortcuts into our brains, working up a usability test subject patter and playing with sticky notes. Then along came Ajax. Until that point we could safely silo ourselves, locked away in our niche specialities. But producing good _applications_ requires more than that. Yes, we need our specialist skills but without a thorough understanding of both ends of the Ajax equation the result will be an unholy mess.
Interface designer Mike Stenhouse will discuss how his working life has changed, what we need to know to produce good applications for the modern web and how many times he's thrown his toys out of his pram and whined "But I'm a bloody designer!"
Fundamentals of Lean UX, Agile on the Beach 2014Adrian Howard
Lean UX sits at the intersection of the Agile, Lean Startup & User Experience communities of practice.
This workshop will introduce you to the basics of the Lean UX approach, and take you through the process of applying Lean UX techniques at different stages of the product/business development process.
Learning outcomes:
* Lean UX and its relation to Lean Startup, Agile UX & general Lean
approaches the common myths and misunderstandings about Lean UX
* How to apply Lean UX approaches within your own company
* How the hypothesis/experiment model differs from traditional requirements
* How Lean UX can be used to understand customers better, discover new
product ideas, and reduce risk in new product development
Prototyping - 2015 PhillyCHI UX Workshop SeriesMatthew Thomas
Slides for prototyping workshop I facilitated for the 2015 PhillyCHI Workshop Series. Covers overview of prototyping, methods, and considerations when considering prototype fidelity.
Out of My Brain on the 5:15 | Practical User Research for the Enterprise UXerjsokohl
In some ways, this talk is a simple one, designed to provide a single solution to a core problem facing all us UXers: Too many project managers, product managers, project sponsors, and so on balk at the idea of performing ANY user research.
Two key objections arise when user research is proposed:
“Our users don’t have time to go to a focus group or a conference room and spend hours listening to someone or doing inane exercises.”
“We can’t spend tons of project time for six months just fiddling around with talking to users…who need to be doing their jobs, by the way.”
To cut through this barrier, I came up with the method I call “”5:15.”” Put simply, it involves asking a person to commit to answering five questions in only 15 minutes.
Almost no one can spend two hours out of their workday talking to a user experience researcher; almost everyone has 15 minutes. Even asking someone for an hour of their time seems excessive, especially in enterprise settings. However, that request for 15 minutes seems innocuous.
We’ll look at how these questions work well, how you can gain insights easily, and why you should never take NO to research plans as an answer.
HTML5 seems to stuck in a rut: we got people very excited about it but at the same time we told them it doesn't work and needs a special environment and all kind of other quick shots. Now is the time to look at HTML5 closer again and take a look at where we stand. We're in good shape, we just need to look at the mirror again.
6 Principles for Enabling Build/Measure/Learn: Lean Engineering in ActionBill Scott
Presented at Lean Day West - Portland, OR. Sept. 17, 2013
How do you take a gigantic organization like PayPal and begin to transform the experiences? Engineering is often the key blocker in being able to achieve a high rate of innovation. In this talk, Bill Scott will give specific examples on implemented Lean UX in a 13,000 person company, re-factored the technology stack and changed the way engineers work with design & product partners. In addition, Bill will provide additional examples that go back to his early days writing one of the first Macintosh games to his more recent work at Netflix and the power of treating the user interface layer as the experimentation layer.
Rapid video prototyping for connected productsMartin Charlier
Slides from a workshop on using video as a rapid prototyping tool for connected products run by Tom Metcalfe and Martin Charlier at Interaction16 conference in Helsinki.
Given at Agile Camp 2013, San Jose, CA. Sept. 21
How do you take a gigantic organization like PayPal that was entrenched in a culture of a “”long shelf life”” and transform it to a culture of rapid experimentation? Bill will give 3 principles applied to PayPal engineering to make it a full partner with Lean UX. This will be illustrated by showing how they re-factored the tech stack and changed the way engineers work in Lean streams with design & product partners and how it plays with agile.
As a backdrop Bill will discuss several historical factors in the field of software engineering that are antithetical to the Lean Startup mindset but still find their way into most large enterprises. By understanding this historical context and applying lean principles he will demonstrate how a lean transformation can take place in any enterprise.
Any of these happen to you?
* Tasked to develop a user interface with an incomplete design spec, so had to make guesses such as where to position on-screen elements?
* Worked on a small team without a full-time designer, and requested to “just put a screen together for a demo”?
* Been asked to consult with a user interface designer, but don’t know what types of questions to pose?
Nowadays, everyone wants attractive, easy-to-use interfaces, so if you’re more comfortable sifting through Java or C# code than OmniGraffle or Visio mockups, learn about topics that can assist in creating more usable desktop applications, mobile apps, and websites. This talk provides easy-to-implement hints that can improve even a bad or “so-so” user interface. Areas of focus include the need for consistency; “negative space”; location, location, location (it’s crucial in screen real-estate, too!); contrasting colors; and the importance of action verbs.
This talk looks at the challenges we are facing when prototyping for mobile and gives an overview about the tools and handy helpers that you can use to deliver tappable, sharable and testable prototypes.
Lean Engineering: How to make Engineering a full Lean UX partnerBill Scott
In 1999, PayPal's name was synonymous with innovation. In fact, the so called PayPal Mafia (original founders) went on to establish Tesla, SpaceX, YouTube, Skype and other startups. They also provided the early investments of many of the most innovative companies on the internet today. But over time that innovation slowed to a crawl.
In 2011 a number of things begin to come together for PayPal that started its journey back to innovation. This is the story of that reboot and how engineering has played a key role in partnering directly with product and design to move from a culture of products having a long shelf life, to one of rapid experimentation.
In this talk, Bill will outline the principles of Lean Engineering; principles for engineering that enable learning. Drawing from his experience leading User Interface Engineering at both Netflix & PayPal, Bill will walk you through the key principles your engineering team will need to adopt to be that enabler for product and design in your organization. This talk will not just inspire you, but it will also give you some hard earned advice on making this a reality in your organization.
As presented at @media Ajax in London on 19th November 2007.
So we spent years learning our craft - specialising - reading the CSS specs in bed, hardwiring the Photoshop keyboard shortcuts into our brains, working up a usability test subject patter and playing with sticky notes. Then along came Ajax. Until that point we could safely silo ourselves, locked away in our niche specialities. But producing good _applications_ requires more than that. Yes, we need our specialist skills but without a thorough understanding of both ends of the Ajax equation the result will be an unholy mess.
Interface designer Mike Stenhouse will discuss how his working life has changed, what we need to know to produce good applications for the modern web and how many times he's thrown his toys out of his pram and whined "But I'm a bloody designer!"
Fundamentals of Lean UX, Agile on the Beach 2014Adrian Howard
Lean UX sits at the intersection of the Agile, Lean Startup & User Experience communities of practice.
This workshop will introduce you to the basics of the Lean UX approach, and take you through the process of applying Lean UX techniques at different stages of the product/business development process.
Learning outcomes:
* Lean UX and its relation to Lean Startup, Agile UX & general Lean
approaches the common myths and misunderstandings about Lean UX
* How to apply Lean UX approaches within your own company
* How the hypothesis/experiment model differs from traditional requirements
* How Lean UX can be used to understand customers better, discover new
product ideas, and reduce risk in new product development
Prototyping - 2015 PhillyCHI UX Workshop SeriesMatthew Thomas
Slides for prototyping workshop I facilitated for the 2015 PhillyCHI Workshop Series. Covers overview of prototyping, methods, and considerations when considering prototype fidelity.
Out of My Brain on the 5:15 | Practical User Research for the Enterprise UXerjsokohl
In some ways, this talk is a simple one, designed to provide a single solution to a core problem facing all us UXers: Too many project managers, product managers, project sponsors, and so on balk at the idea of performing ANY user research.
Two key objections arise when user research is proposed:
“Our users don’t have time to go to a focus group or a conference room and spend hours listening to someone or doing inane exercises.”
“We can’t spend tons of project time for six months just fiddling around with talking to users…who need to be doing their jobs, by the way.”
To cut through this barrier, I came up with the method I call “”5:15.”” Put simply, it involves asking a person to commit to answering five questions in only 15 minutes.
Almost no one can spend two hours out of their workday talking to a user experience researcher; almost everyone has 15 minutes. Even asking someone for an hour of their time seems excessive, especially in enterprise settings. However, that request for 15 minutes seems innocuous.
We’ll look at how these questions work well, how you can gain insights easily, and why you should never take NO to research plans as an answer.
I spent several years as a manager, a booking agent, a road manager, and a radio DJ in one of my pasts. Several key ideas from that life apply directly to my UX world.
How do we move from research to design to development without losing sight of the user experience. This session looks at specifying UX artifacts for team members to glean meaning from our work. How does experience design specify its output in a way that developers can code and business can understand how the UX relates to business requirements?
"When we said we wanted a house at Bear Creek," client Lillian Kaufmann said to Frank Lloyd Wright, "we didn't imagine you would build it ON the creek!"
To which Wright replied, "In time you'd grow tired of the sight of creek...but you'll never grow tired of the sound."
And he was right. Fallingwater stands as the most recognized house in architecture. yet it's not just a landmark...it was a home. The Kaufmanns' loved it.
Similarly, owners of other Wright-designed buildings may have struggled with the architect, the implementation may have had flaws, the builders and other constructors may have gone behind Wright's back to fix perceived design flaws... but they all loved the buildings. The architect's vision remains inspiration to this day.
This presentation looks at three Wright landmarks— Fallingwater in Ohiopyle, the Pope-Leighy house in Alexandria, and Taliesin West in Phoenix— and the experience architecture inspiration they hold for experience designers.
I also believe that, through Wright's examples, we can learn elements that take our approaches to experience architecture to newly useful and inspiring levels for our clients and the users of our work.
During this presentation, we'll take a look at pictures and principles from these three sites. We will explore analogs to our practice through these elements:
* Context: How does the site selection integrate with user needs and desires?
* Clients: What do Wright's relationships with his clients teach us? Where did he innovate, and where did he fail?
* Connection: How does the architect connect the lives of the clients with the results of the design? Expect lots of pictures.
Make it or Break It: Evolutionary or Throwaway Prototypingjsokohl
Prototyping is a key tool for improving the user experience and defining a product. What's the best approach: incrementally use the target development environment to create the code, or use a technique that explores design ideas without delivering on the prototype platform?
As Agile teams struggle with how to address the user experience, they often look to models that tack UX activities on to their process. UX architects & designers spend time begging for a place at the Agile table, while developers & PMs & product owners scratch their heads, wondering what these weird folks are doing on their teams.
Yet rather than asking, "How do we tack UX onto Agile?" let's let’s ask, “Do we want to define projects with users in mind? If we do, then who should be responsible for that task?” This session looks at how user experience is taken into account in projects, why user requirements should lead project development, and how addressing UX provides key business value.
Agile team professionals often find themselves working on projects with tight deadlines, tighter budgets, and unreasonably high expectations for success. Too often user research, usability, and design processes are compressed or even cut entirely for the sake of time, while development and business analysis time is increased. As UX professionals become more involved with agile development methods, we have discovered novel approaches to user-centered design that are adaptable to any budget or deadline.
This discussion will explore how user research, usability, IA and interaction design practices are adapted and thrive in agile projects.
Focusing on their experiences at Agile 2009 in Chicago this past fall, they will discuss:
* How to provide timely and valuable UX support to stressed web development teams
* How to let go and modify research/design/development dogmas
* How to advocate for users when time for user research and usability are unavailable
* How to balance rigor, quality, and speed
How Can You Be in Two Places at Once: Designing Across Space and Timejsokohl
Design often is considered an in-person collaboration. Perhaps, however, we can leverage key principles and base tools to enhance our lives as well as our designs. Not only do we work with people across the hall, across town, and across the country, but we also work with people we never meet.
Technology has provided us the ability to work in many ways, telecommute to save fuel and frustration, reduce travel costs, and use various forms of communication. The promise is there, yet the reality sometimes eludes us.
An old presentation about what human-computer interaction is, what usability is, and how it fits into development. Pondering now just how well this stands up. It seems to...but....
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.
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.
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.
Kill Your Darlings: Solving Design by Throwing Away Your Prototypes
1. Kill Your Darlings
Solving Design by Throwing Away Prototypes
October 24, 2014
Joe Sokohl
@RegJoeConsults @MojoGuzzi
2. What We’ll Talk About
§A brief history of wireframing
§The benefits of prototyping
§Why throw away your work?
§A case study showing a redesign process as an
archetypal and practical approach
@RegJoeConsults!2
11. What is a prototype, anyway?
Representa)ve
model
or
simula)on
of
the
final
system
Todd
Zaki
Warfel,
Prototyping:
A
Prac//oner’s
Guide
@RegJoeConsults!11
12. Why Should We Prototype?
@RegJoeConsults!12
Reduced
risk
Smaller
systems
Less
complex
systems
Reduc)on
in
creeping
requirements
Improved
visibility
13. Why Should We Prototype?
@RegJoeConsults!13
Genera)ve
Show,
tell
&
experience
Reduc)on
of
misinterpreta)on
Savings
in
)me/effort/money
Reduc)on
of
waste
Real-‐world
value
17. As
I
see
it,
knowing
how
to
prototype,
test,
and
evaluate
results
quickly
is
the
most
valuable
skill
for
designers
of
persuasive
technology.
BJ
Fogg,
“Crea)ng
Persuasive
Technologies:
An
Eight-‐Step
Design
Process”
http://www.flickr.com/photos/rosenfeldmedia/3978302604/ @RegJoeConsultsI17
Cycle of Design
18. The Perils of Prototyping
Which is harder to change: a program with 1000 lines
of code or a 1000 square foot slab of concrete?
§ The concrete is ten inches thick and has steel reinforcing rods
criss-crossing within it. Every cubic foot of it weighs almost 100
pounds.
§ The software has almost no physical existence at all. It weighs
nothing. It consumes no space. A few microamps and those bits
flip from zero to one without a second glance.
The answer to my question seems a simple one,
doesn’t it?
http://www.cooper.com/journal/2008/05/the_perils_of_prototyping
@RegJoeConsults!18
19. This is the first one. This is it exactly. This is my hand-wired
prototype, not a real Apple I or Apple ][ PC board. There are 4
white 2KB EPROMs on the upper board - that's how I developed
BASIC and all the other routines of the Apple I. This is an Apple ]
[ prototype. I can tell by how few chips it is. The Apple I had a
computer board attached to my video terminal board, in the
prototype stage." __Steve Wozniak
hUp://www.geekculture.com/joyoWech/joystuff/apple1cake/firstapple.jpg
@RegJoeConsults!19
20. Use evolutionary prototypes (EVPs) when…
§User requirements are (almost) defined.
§Few interaction and visual design problems exist,
and information architecture is defined.
§UX team is highly experienced.
§UXers also create the deployable front-end code.
§Usability testing is summative, not formative.
§ Project requires little documentation.
!20
21. Use throwaway prototypes (TAPs) when…
§User requirements are ill-defined.
§Major interaction or visual design (or both) issues
remain, and the IA is not well defined.
§You have less experienced UXers.
§UX does not do development.
§Usability testing is formative and occurs multiple
times throughout the project.
§ Project requires detailed documentation.
!21
22. Screen
comps
Axure/Balsamiq/
iPlotz/iMockup...
Hand-‐coded
HTML
TAP TAP/EVP
@RegJoeConsults!22
TAP EVP
Paper
Sketchflow/Expression
Edge
Fireworks
23. !23
Case Study
Melding sketches, quick wireframes, and prototyping
24. The Project: Redesign site into a modern, user-centered experience
@RegJoeConsults!24
From this… To this…
25. We Did…
§Heuristic analysis
§Data analysis
§Market research analysis
§ Personas
§Mood boards & visual design
§ User journeys/scenarios
@RegJoeConsults!25
28. Digital Exploration
!28
Carrier 12:00 PM
Page Title
http://www.domain.com Google
1 Classic w/Trip +
2 Classic
3 Basic
Benefits Coverages
Up to 150%
of amount
purchased
Up to 150%
of amount
purchased
$356
$326
$256
Up to 150% of
amount
purchased
Trip interruption
protection
Trip interruption
protection
Trip interruption
protection
Trip interruption
protection
Trip interruption
protection
1 2 3