You'll learn:
How to visualize user needs instead of product features
How to make better decisions when prioritizing a UX backlog
How to align sprints with UX strategy
Lean Startup + Story Mapping = Awesome Products FasterBrad Swanson
To deliver the right outcomes, you need to learn your customers needs and validate your assumptions as early as possible. This means getting an early version of your product completed to start testing, validating and improving. This session will demonstrate how to combine Lean Startup and User Story Mapping techniques to determine where to start and how to learn early and often.
Participants will start with a partially completed Lean Canvas to flesh out and then define a product roadmap by building a Story Map. We will use Lean Startup concepts of Minimal Viable Product (MVP) and validated learning to focus on outcome over output.
Learning objectives:
Understand the importance of accelerated learning and techniques to achieve it
How a Lean Canvas can help shape your product vision and MVP
How to build a story map to create a product roadmap
How to use a story map to validate your users' journey
Epic Alignment - How the best Product Managers work with feature documentsNils Janse
• How can you drive the thinking on what to develop, why and how to do it - leveraging the insights from both team and stakeholders - all the way from idea to deploy?
• This book tries to answer the above question. We interviewed over 300 Product Managers to understand how they work and collaborate around feature development, what problems they face, and the many approaches to solving those problems.
• Epic Alignment describes four broad approaches that we saw help Product Managers excel. business intelligence, design, product management, saas, startups
Slide deck from Bruce McCarthy's Workshop, Roadmapping Relaunched at Business of Software Conference USA 2018. Featuring the TESLA Roadmapping exercise.
Tips for Effectively Applying the Product Owner RoleRoman Pichler
This slide deck offers tips to successfully apply the product owner role. It distinguishes different product owner flavours, explains hope the Scrum product owner role differs from the SAFe one, and how product ownership can be scaled.
Lean Startup + Story Mapping = Awesome Products FasterBrad Swanson
To deliver the right outcomes, you need to learn your customers needs and validate your assumptions as early as possible. This means getting an early version of your product completed to start testing, validating and improving. This session will demonstrate how to combine Lean Startup and User Story Mapping techniques to determine where to start and how to learn early and often.
Participants will start with a partially completed Lean Canvas to flesh out and then define a product roadmap by building a Story Map. We will use Lean Startup concepts of Minimal Viable Product (MVP) and validated learning to focus on outcome over output.
Learning objectives:
Understand the importance of accelerated learning and techniques to achieve it
How a Lean Canvas can help shape your product vision and MVP
How to build a story map to create a product roadmap
How to use a story map to validate your users' journey
Epic Alignment - How the best Product Managers work with feature documentsNils Janse
• How can you drive the thinking on what to develop, why and how to do it - leveraging the insights from both team and stakeholders - all the way from idea to deploy?
• This book tries to answer the above question. We interviewed over 300 Product Managers to understand how they work and collaborate around feature development, what problems they face, and the many approaches to solving those problems.
• Epic Alignment describes four broad approaches that we saw help Product Managers excel. business intelligence, design, product management, saas, startups
Slide deck from Bruce McCarthy's Workshop, Roadmapping Relaunched at Business of Software Conference USA 2018. Featuring the TESLA Roadmapping exercise.
Tips for Effectively Applying the Product Owner RoleRoman Pichler
This slide deck offers tips to successfully apply the product owner role. It distinguishes different product owner flavours, explains hope the Scrum product owner role differs from the SAFe one, and how product ownership can be scaled.
modern approaches share a focus on producing exceptional outcomes and growing an outstanding culture. Today, it makes far more sense to bypass antiquated agility in favor of modern approaches.
Modern agile methods are defined by four guiding principles:
- Make people awesome
- Make safety a prerequisite
- Experiment & learn rapidly
- Deliver value continuously
Customer to Product Idea Iteration by Amazon's Product ManagerProduct School
In this talk, Akshay Kerur from Amazon explored working backwards from the concept/customer to an initial product idea.
Main takeaways:
1. Why it's so important to put your product on paper.
2. Questions you need to know and answer about a product prior to any engineering commitment.
3. Ratifying your product idea through proper customer and internal stakeholder identification.
Lean Portfolio Strategy Part 2: Shifting from Imitation to Real LPM - The Mov...Cprime
Download the associated webinar: https://www.cprime.com/resource/webinars/lean-portfolio-strategy-part-2-shifting-from-imitation-to-real-lpm-the-move-to-true-value-streams/
Lean Portfolio Management (LPM) is touted as a world-changing paradigm. A shift that promises to boost productivity, time to market, quality, customer satisfaction, revenue, and a host of other vital business metrics. It promises to transform the organization to a leaner, more agile version of itself, primed to innovate effortlessly and outperform its competition at every turn.
Most organizations who have tried to establish LPM find the reality to be more nuanced than that. These companies end up implementing “Imitation LPM” where actions and some process changes may be in place and functioning, but the real promise of LPM- the increased agility and reduced waste- is not occurring.
Real LPM assumes that work is funded by value streams with teams organized around delivery of products and services that are valuable to customers. This is, perhaps, the hardest part of implementing LPM.
In part 1 of this webinar we explored how signs of imitation LPM show up in an organization’s approach to strategy. In this second of our series, we join Michiko Quinones (Jira Align Consultant) and Jean Dahl (General Manager, Scaled Agility) to explore:
- How to organize around value streams
- Real world examples of organizations who have successfully shifted from imitation value streams to true value streams
- The impact to funding and budgeting cycles
The Product Visioning Workshop: A Proven Method for Product Planning and Prio...Perfetti Media
Is your team looking for new product concepts to capture a new market? Do you need to establish a long-term product strategy? Are you working to set a direction to drive roadmap decisions?
In this presentation, we will share a proven approach for creating a long-term product vision that your team can understand and rally behind. We will share all of the techniques you'll need to successfully run a Product Visioning Workshop with your product team and business stakeholders.
You will learn how to create a long-term vision for your product, establish consensus and buy-in across your organization, and prioritize features for the product roadmap. Your product managers will come away equipped to create roadmaps that align with your long-term product strategy.
Focus On What Matters - From Product Vision to Product RoadmapOneUp Vitamins
Focus on what matters when going from product vision to product roadmap. Held at the Agile Product Delivery meetups and one of the favourites for our Lunch & Learn sessions..
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.
Product Managers are the visionaries for both identifying solutions, and innovating for the next big thing. But how does one jump from “I have an idea” to “go live”? There’s lots in between.
By putting you in real-world scenarios, this deck was created for a Hearst-wide division workshop that helped various teams through how they can break down their idea into actionable next steps by borrowing agile methodologies.
'How do you know that your product works?': Henrik Kniberg @ Colombo Agile Co...ColomboCampsCommunity
Quality Assurance is a common source of confusion in agile development. What is ‘quality’ and how do we ‘assure’ it? There’s more to it than just putting testers on the team. How do we know that we’re even building the right product? How do we avoid building up technical debt? When is it right to sacrifice quality? What is the right level of test coverage? In this presentation, Henrik looks at some common problems, patterns and misconceptions about agile quality assurance
Roadmapping the Product Roadmap (ProductCamp Boston 2016)ProductCamp Boston
Ask 10 people what a product roadmap is and you will get 10 different answers! This little artifact is an often misunderstood component of product development, but an incredibly important one to get right. Creating a great one is part art and part science. In this session we will talk through the real purpose of a roadmap and how it can be used to get the most out of your project and team. We'll unpack the key steps in the process and shed more light on the tools and frameworks that can be used to ensure a successful roadmapping effort. If all goes well we'll even get a chance to practice a bit so we can see what it means to actually translate this stuff into real-life scenarios.
About C. Todd Lombardo
C. Todd is a leader who wears many hats, all at once: Author, designer, scientist, professor, and visualizer. After originally beginning his career in science, C. Todd shifted his focus to product and design, ultimately innovating, designing, and managing products for countless companies large and small. A teacher and speaker at heart, he frequently speaks at conferences and has directed five TEDx events in two countries. C. Todd serves as Adjunct Faculty at IE Business School in Madrid, and co-authored the book "Design Sprint," published by O'Reilly. Not only is he a chemistry Ph.D. dropout, but he also founded ProductCamp Boston. Those two facts may or may not be related.
Agile Everywhere!
Henrik Kniberg talks about how his journey implementing agile & lean methods at Spotify and Lego helped him apply agility in new & unexpected fields. Henrik will share his vision on how agility may evolve in the future and affect various areas of our lives.
About Henrik Kniberg
Henrik Kniberg is an Agile/Lean coach at Crisp in Stockholm, working primarily with Lego and Spotify. He enjoys helping companies succeed with both the technical and human sides of software development. During the past 15 years he has been CTO of 3 Swedish IT companies and helped many more get started with Agile and Lean software development.
Henrik is former board member of the Agile Alliance and works regularly with Mary Poppendieck, Jeff Sutherland, and other thought leaders. He is the author of “Scrum and XP from the Trenches” and “Kanban and Scrum, making the most of both” and “Lean from the Trenches“. These books are available in over 12 languages, have over 500,000 readers, and are used as primary guide to Agile and Lean software development by hundreds of companies worldwide. Henrik also created the viral animated videos “Agile Product Ownership in a Nutshell” and “Spotify Engineering Culture“.
If you work in Scrum environment or you’re just a team member who is trying to guide a conversation – then these interactive facilitation techniques are for you. In this session focus will be on games which you could use in virtual environment.
Scrum 101 Learning Objectives:
1. Waterfall project methodology basics - what is waterfall and where did it come from?
2. Agile umbrella practices and frameworks - what is agile? what isn't agile? Where does Scrum fit in?
3. Scrum empirical theory - emperical vs. theoretical
4. Parts of the Scrum framework - roles, events / ceremonies, artifacts and rules
5. Features of cultures that use Scrum
User Story Mapping for Minimum Lovable ProductsKelley Howell
I gave this presentation at the UX Agile Summit, 2017.
If you have ever sat there staring at your screen or a white board, wondering where to start. If you've ever wondered how you could possibly organize all these user stories into some kind of well-organized plan for iteratively releasing your product, this talk is for you!
In this talk, I will share a way you can generate user stories, organize your backlog, and plan out releases in a way that will ensure that the product is not just minimally viable, but minamally lovable.
Requirements Engineering for the HumanitiesShawn Day
This workshop explores how requirements engineering can be employed by digital and non-digital humanities scholars (and others) to conceptualise and communicate a research project.
requirementsEngineeringAs the field of digital humanities has evolved, one of the biggest challenges has been getting the marrying technical expertise with humanities scholarly practice to successfully deliver sustainable and sound digital projects. At its core this is a communications exercise. However, to communicate effectively demands an ability to effectively translate, define and find clarity in your own mind.
modern approaches share a focus on producing exceptional outcomes and growing an outstanding culture. Today, it makes far more sense to bypass antiquated agility in favor of modern approaches.
Modern agile methods are defined by four guiding principles:
- Make people awesome
- Make safety a prerequisite
- Experiment & learn rapidly
- Deliver value continuously
Customer to Product Idea Iteration by Amazon's Product ManagerProduct School
In this talk, Akshay Kerur from Amazon explored working backwards from the concept/customer to an initial product idea.
Main takeaways:
1. Why it's so important to put your product on paper.
2. Questions you need to know and answer about a product prior to any engineering commitment.
3. Ratifying your product idea through proper customer and internal stakeholder identification.
Lean Portfolio Strategy Part 2: Shifting from Imitation to Real LPM - The Mov...Cprime
Download the associated webinar: https://www.cprime.com/resource/webinars/lean-portfolio-strategy-part-2-shifting-from-imitation-to-real-lpm-the-move-to-true-value-streams/
Lean Portfolio Management (LPM) is touted as a world-changing paradigm. A shift that promises to boost productivity, time to market, quality, customer satisfaction, revenue, and a host of other vital business metrics. It promises to transform the organization to a leaner, more agile version of itself, primed to innovate effortlessly and outperform its competition at every turn.
Most organizations who have tried to establish LPM find the reality to be more nuanced than that. These companies end up implementing “Imitation LPM” where actions and some process changes may be in place and functioning, but the real promise of LPM- the increased agility and reduced waste- is not occurring.
Real LPM assumes that work is funded by value streams with teams organized around delivery of products and services that are valuable to customers. This is, perhaps, the hardest part of implementing LPM.
In part 1 of this webinar we explored how signs of imitation LPM show up in an organization’s approach to strategy. In this second of our series, we join Michiko Quinones (Jira Align Consultant) and Jean Dahl (General Manager, Scaled Agility) to explore:
- How to organize around value streams
- Real world examples of organizations who have successfully shifted from imitation value streams to true value streams
- The impact to funding and budgeting cycles
The Product Visioning Workshop: A Proven Method for Product Planning and Prio...Perfetti Media
Is your team looking for new product concepts to capture a new market? Do you need to establish a long-term product strategy? Are you working to set a direction to drive roadmap decisions?
In this presentation, we will share a proven approach for creating a long-term product vision that your team can understand and rally behind. We will share all of the techniques you'll need to successfully run a Product Visioning Workshop with your product team and business stakeholders.
You will learn how to create a long-term vision for your product, establish consensus and buy-in across your organization, and prioritize features for the product roadmap. Your product managers will come away equipped to create roadmaps that align with your long-term product strategy.
Focus On What Matters - From Product Vision to Product RoadmapOneUp Vitamins
Focus on what matters when going from product vision to product roadmap. Held at the Agile Product Delivery meetups and one of the favourites for our Lunch & Learn sessions..
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.
Product Managers are the visionaries for both identifying solutions, and innovating for the next big thing. But how does one jump from “I have an idea” to “go live”? There’s lots in between.
By putting you in real-world scenarios, this deck was created for a Hearst-wide division workshop that helped various teams through how they can break down their idea into actionable next steps by borrowing agile methodologies.
'How do you know that your product works?': Henrik Kniberg @ Colombo Agile Co...ColomboCampsCommunity
Quality Assurance is a common source of confusion in agile development. What is ‘quality’ and how do we ‘assure’ it? There’s more to it than just putting testers on the team. How do we know that we’re even building the right product? How do we avoid building up technical debt? When is it right to sacrifice quality? What is the right level of test coverage? In this presentation, Henrik looks at some common problems, patterns and misconceptions about agile quality assurance
Roadmapping the Product Roadmap (ProductCamp Boston 2016)ProductCamp Boston
Ask 10 people what a product roadmap is and you will get 10 different answers! This little artifact is an often misunderstood component of product development, but an incredibly important one to get right. Creating a great one is part art and part science. In this session we will talk through the real purpose of a roadmap and how it can be used to get the most out of your project and team. We'll unpack the key steps in the process and shed more light on the tools and frameworks that can be used to ensure a successful roadmapping effort. If all goes well we'll even get a chance to practice a bit so we can see what it means to actually translate this stuff into real-life scenarios.
About C. Todd Lombardo
C. Todd is a leader who wears many hats, all at once: Author, designer, scientist, professor, and visualizer. After originally beginning his career in science, C. Todd shifted his focus to product and design, ultimately innovating, designing, and managing products for countless companies large and small. A teacher and speaker at heart, he frequently speaks at conferences and has directed five TEDx events in two countries. C. Todd serves as Adjunct Faculty at IE Business School in Madrid, and co-authored the book "Design Sprint," published by O'Reilly. Not only is he a chemistry Ph.D. dropout, but he also founded ProductCamp Boston. Those two facts may or may not be related.
Agile Everywhere!
Henrik Kniberg talks about how his journey implementing agile & lean methods at Spotify and Lego helped him apply agility in new & unexpected fields. Henrik will share his vision on how agility may evolve in the future and affect various areas of our lives.
About Henrik Kniberg
Henrik Kniberg is an Agile/Lean coach at Crisp in Stockholm, working primarily with Lego and Spotify. He enjoys helping companies succeed with both the technical and human sides of software development. During the past 15 years he has been CTO of 3 Swedish IT companies and helped many more get started with Agile and Lean software development.
Henrik is former board member of the Agile Alliance and works regularly with Mary Poppendieck, Jeff Sutherland, and other thought leaders. He is the author of “Scrum and XP from the Trenches” and “Kanban and Scrum, making the most of both” and “Lean from the Trenches“. These books are available in over 12 languages, have over 500,000 readers, and are used as primary guide to Agile and Lean software development by hundreds of companies worldwide. Henrik also created the viral animated videos “Agile Product Ownership in a Nutshell” and “Spotify Engineering Culture“.
If you work in Scrum environment or you’re just a team member who is trying to guide a conversation – then these interactive facilitation techniques are for you. In this session focus will be on games which you could use in virtual environment.
Scrum 101 Learning Objectives:
1. Waterfall project methodology basics - what is waterfall and where did it come from?
2. Agile umbrella practices and frameworks - what is agile? what isn't agile? Where does Scrum fit in?
3. Scrum empirical theory - emperical vs. theoretical
4. Parts of the Scrum framework - roles, events / ceremonies, artifacts and rules
5. Features of cultures that use Scrum
User Story Mapping for Minimum Lovable ProductsKelley Howell
I gave this presentation at the UX Agile Summit, 2017.
If you have ever sat there staring at your screen or a white board, wondering where to start. If you've ever wondered how you could possibly organize all these user stories into some kind of well-organized plan for iteratively releasing your product, this talk is for you!
In this talk, I will share a way you can generate user stories, organize your backlog, and plan out releases in a way that will ensure that the product is not just minimally viable, but minamally lovable.
Requirements Engineering for the HumanitiesShawn Day
This workshop explores how requirements engineering can be employed by digital and non-digital humanities scholars (and others) to conceptualise and communicate a research project.
requirementsEngineeringAs the field of digital humanities has evolved, one of the biggest challenges has been getting the marrying technical expertise with humanities scholarly practice to successfully deliver sustainable and sound digital projects. At its core this is a communications exercise. However, to communicate effectively demands an ability to effectively translate, define and find clarity in your own mind.
Julie Grundy gives an overview of user experience Design, why it's important, guiding principles, UX research overview, and tactics used by UX professionals. November 2015.
Owning the product by owning the user experienceMark Notess
Effective product ownership means owning the user’s experience (UX) of that product. This presentation provides a practical introduction to UX concepts and methods as adapted for Agile software development. Sample deliverables, activities and results will be drawn from the Avalon Media System project, a jointly developed open source system developed by Indiana University and Northwestern University. This was presented at Agile Indy 2014.
"A scenario is a description of a person’s interaction with a system.
Scenarios help focus design efforts on the user’s requirements, which are distinct from technical or business requirements.
Scenarios may be related to ‘use cases’, which describe interactions at a technical level. Unlike use cases, however, scenarios can be understood by people who do not have any technical background. They are therefore suitable for use during participatory design activities." http://infodesign.com.au/usabilityresources/scenarios/
Field Research at the Speed of BusinessPaul Sherman
Field research: to many it's the gold standard of user-centered design. Want to learn more about how your current or prospective customers think, work, live and play? Go observe them.
If you're early or even mid-career, organising, carrying out and analysing the results of field research can seem daunting and time-consuming. This tutorial will provide you with information and resources you can use immediately to start conducting insightful and effective field research.
Presented at UX in the City Oxford 2017, April 2017, Oxford UK.
Infusionsoft Socially Enabled Internal Communication ProposalKimberle Morrison
We're growing and needed a more effective and scalable way to communicate internally. This presentation outlines our process and the rationale behind how and why we decided to go with a socially enabled system for communication and collaboration
The presentation is used to introduce product design and development teams to user story mapping, personas, and scenarios. The technique draws on the work of Jaff Patton who integrates elements of user centered design, agile user stories, backlog management, and product management.
This is part one of the Lean UX workshops outlining in a practical way, the Lean UX processes. These workshops are run as part of the Lean UX Labs experiment.
Design for Covid-19 Challenge Webinar 2: Ideation Phase Aqeela A. Somani
This is our second webinar from Design for Covid-19 Challenge. Our focus for this webinar is on the Ideation Phase. It provides participants with frame works and tools on how to create a solution.
Delight 2013 | Secrets of the UX Team of OneDelight Summit
Leah Buley of Intuit shares advice for UX practitioners looking to get buy in around delightful experience design.
Originally presented at Delight 2013, Oct. 7-8, 2013. http://delight.us/conference
Please visit our online professional network and join our community of Automotive Social Media Marketing professionals at http://www.ADPsocialMarketing.com
Bootstrapping the Information Architecture (Italian IA Summit)Peter Boersma
When I design, it is in the early stages of an interactive system’s life. There are no widgets to place on screens, or menus to collapse or expand. No wireframes, no screen flows, no accessibility or SEO issues. No search, no controlled vocabulary, no settings screens or personalisation options to design. In short: the project needs to be bootstrapped.
I am involved when a lot of things need to be explored and modelled; the scope and environment of the system, the core concepts that make up its parts, their relationships and their names. So what do we produce in that stage? Mostly so-called concept diagrams.
In this talk, I explain what concept diagrams are, referencing other people’s experiences as well as my own, and how they are useful when a design needs to be bootstrapped. I show how I have used variations of them in recent assignments for KLM and the City of Amsterdam, among others. I will try to convince you that you should create one for each and every situation that needs bootstrapping.
Held in conjunction with World IA Day 2018, this practical session was an introduction to the core skills and methods of thinking that you will use as part of your day to day work in IA.
Topics covered include the foundations of IA, the importance of a ‘content first’ approach, thinking like a user and how to present your work to clients.
The session was led by Jon Fisher, Head of UX at Nomensa, an award-winning UX design agency based in London, Bristol and Amsterdam.
Held in conjunction with World IA Day 2018, this practical session was an introduction to the core skills and methods of thinking that you can use as part of your day to day work in IA.
Topics covered included the foundations of IA, the importance of a ‘content first’ approach, thinking like a user and how to present your work to clients.
The session was led by Jon Fisher, Head of UX at Nomensa, an award-winning UX design agency based in London, Bristol and Amsterdam.
This is a free event recommended for those new to IA or looking for a refresher on fundamentals.
Following the event, Nomensa will be providing pizza and beers for delegates to enjoy and continue networking.
If you register, but are unable to attend, please give us 48 hours notice so we can reallocate your place.
Similar to User Story Mapping for Minimum Lovable Products (20)
Evolving your Design System: People, Product, and Processuxpin
You'll learn:
How to create and maintain a design system over several years
How people, process, and product change alongside a design system
Lessons learned from growing the Linkedin design system
How Atlassian builds and manages their design system across their product suite
How the Design System team empowers users by iterating with research and testing
How design and engineering cooperate to be efficient and productive
Accessibility in Design Systems by Allison Shawuxpin
You'll learn:
The benefits of accessibility in a design system
How to create and incorporate accessibility standards
How to improve accessibility across your product suite
UXPin: State of the Union Product Keynote by Marcin Trederuxpin
How UXPin unifies design with code in design systems
Recent design system features in UXPin alongside roadmap
Predictions for the future of design tools.
Consistency vs. Flexibility in Design Systems: A GE Case Study by Ken Skistimasuxpin
A case study from the Predix Design System at GE on how balance consistency and flexibility in a large scale design system.
You'll learn:
Where design systems should be consistent or flexible
How GE Digital handles consistency vs. flexibility in the Predix design system
How to adapt tools and technology to balance both.
- Useful technology and frameworks for a scalable design system
- How to create a design systems process from scratch
- How to collaborate with developers in a design system
Developing UX ROI in Enterprise Land: An ADP Case Studyuxpin
You'll learn:
How to develop a quantitative framework for measuring UX ROI
How to use UX ROI as a strategic alignment tool with CX and other internal customer teams
Best practices and lessons learned
Design systems: accounting for quality and scalabilityuxpin
You'll learn:
How Forumone builds and implements design systems for their clients
How to plan, create, sell, and implement a design system
How to use common design tools to build a design system developers will use
Three's a Party: How Trifectas Help Product, Engineering, and Design Work Tog...uxpin
You'll learn:
How to change your collaboration model for PM, engineering, and design as teams grow
How to define responsibilities, cadence, and activities across every layer of a product organization
How Shopify tackles multi-disciplinary collaboration across product teams
Automating Design Processes for Teams: An IDEO Case Studyuxpin
You'll learn:
How IDEO used bots to help automate user research
How you can use automation to improve team efficiency
The future of automation in design
Calculating the ROI of UX with Standard Financial Modelsuxpin
You'll learn:
- How to create a UX ROI model with decision trees and expected values
- How to forecast the effect of UX on sales
- How to use SUS and NPS to measure the effect of UX
From 6 to 126 in 4 Years: The Story Behind Atlassian Designuxpin
You'll learn:
- How to lead design teams through periods of rapid growth
- How to change design processes, build design culture, and scale teams over time
- How to engage engineering and product teams to create a customer-focused organization
Building a UX Process at Salesforce that Promotes Focus and Creativityuxpin
You'll learn:
- How Salesforce designed a large-scale UX process across teams
- Why certain design activities were chosen over others
- How to preserve design quality at scale
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.
Connect Conference 2022: Passive House - Economic and Environmental Solution...TE Studio
Passive House: The Economic and Environmental Solution for Sustainable Real Estate. Lecture by Tim Eian of TE Studio Passive House Design in November 2022 in Minneapolis.
- The Built Environment
- Let's imagine the perfect building
- The Passive House standard
- Why Passive House targets
- Clean Energy Plans?!
- How does Passive House compare and fit in?
- The business case for Passive House real estate
- Tools to quantify the value of Passive House
- What can I do?
- Resources
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.
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.
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.
5. 5
Jeff Patton’s User Story Mapping
http://jpattonassociates.com/
http://jpattonassociates.com/
6. 6
What’s on tap today
1. What’s so great about user story mapping?
2. Understand the user story
3. Write good user stories
4. Understand the relationship between goals, activities,
tasks, and tools
5. The user story mapping process
7. 7
Why user story mapping?
1. Part of a user-centered design process
2. Visual way to show how people use your product and
what they value most about it
3. Visual representation of your product to help with
- Analyzing requirements
- Planning out iterative releases
- Organizing the development process
9. 9
The Agile Samurai by Jonathan Rasmusson
The Agile Samurai by Jonathan Rasmusson
From Jonathan Rasumussen, The Agile Samurai
10. 10
Purpose of a user story
planning item
token for a longer conversation
method for deferring a longer conversation
represents user needs and identifies user goals
Focuses team on solving users’ problems
11. 11
User stories are also boundary objects
build solidarity by bridging pro-
fessional and disciplinary
boundaries
allow collaboration and
even without clear consensus
12. 12
1. Title - often a verb phrase
2. Description
As a [type of user]
I want to [perform some task]
so that I can [reach some goal]
3. Criteria for user acceptance
4. Add sketches & notes, specifications,
wireframes, mocks
A good user story
13. 13
Do user stories replace requirements?
Tom Hilton @ flickr.com/photos/tomhilton/
14. 14
Do not replace requirements
User stories are tokens for longer, deeper
conversations about what users need
Those conversations are memorialized with
artifacts
Artifacts include what we think of as “traditional”
requirements: spreadsheets, flow diagrams,
wireframes, mocks, scenarios use cases, pseudo
code, storyboards, and more
15. 15
This process helps us avoid this:
Credit: Andrew Stelleman and Jennifer Greene, Applied Software Project
Management, Learning Agile, and more
16. 16
But as well all know….
Credit: Axosoft Scrum Software
Not even team alignment or well-written user stories
are enough to tackle prioritization and release
planning, especially on large, complicated products
21. 21
A method for analyzing and prioritizing a backlog that
reflects the order in which people complete activities
and in terms of the value those tasks bring to the users.
What is user story mapping?
22. 22
center users’ perspectives in our discussions
prioritize in terms of user goals
shows relationships between different users and
their work flows
confirm completeness of a product backlog
work as a team
Benefits of user story mapping
24. 24
1. Brainstorm: as individuals write down all the steps
you take to accomplish your goal, organize in a
timeline
2. Reconvene: reconvene as a group and merge your
timelines
3. Identify Patterns: look for similarities and affinities,
grouping them together in clusters. Apply labels to
the clusters of similar tasks. Remove duplicates.
Instructions for workshop activity
25. 25
4. Order by time: The major clusters are activities. The
team should order them left to right in order people
will do them
5. Decompose tasks: Under each activity, list from top
to bottom the tasks people perform under each
activity. Order them according to how important or
valuable they are to the process.
Example Activity: Showering. Can that activity be done
without shampooing hair? Without conditioning?
Without loofah salt scrub routine? Shaving legs? Etc.
Instructions for workshop activity
26. 26
6. Break out paths: When you notice major difference
in types of users and their tasks, physically separate
those tasks as different paths
Question: Which paths are more important? How
do we know?
Instructions for workshop activity
30. 1. Goal: what I want to
achieve or how I want to
feel
2. Activities and tasks: What I
do to achieve the goal
3. Tools: what I use to
perform tasks
30
Goals - Activities - Tasks - Tools
Goals
Activities
Tools
(apps, sites, software)
Tasks
31. Thinking at the task level
31
Illustration credit: Jeff Patton
From: Alistair Cockburn: Writing Effective Use Cases
Task /Functional - “Sea level”
Can complete at one sitting
Sub-Functional - “Fish level”
Tasks that, alone, don’t achieve a meaningful goal
Activity -- “Kite level”
Longer term goals often with no precise ending.
Too abstract
Too detailed
Focus user-centered
thinking here
32. Task: “Read an email message”
Activity: “Manage email”
Goal: Get information about my
job, my team, and company in
order to earn my salary
Task: “Pull monthly analytics
data”
Activity: “Write monthly report”
Goal: Convince management
team to take some action
32
Goals
Activities
Tools
(apps, sites, software)
Tasks
Goals - Activities - Tasks - Tools
33. 33
Team refines and tests for completeness
Gary Levitt, owner & designer of Mad Mimi
The user story mapping process
35. 35
Sally – changing things up
Sally has been an agent for about
10 years. She’s used to doing
things the old-fashioned way:
holding open houses, advertising,
working her network. But now she wants to
branch out and learn how to use the Web. She’s
been using email and online applications for
awhile. But she’s been lackadaisical about it.
She wants to change up her routine, and make
sure her business doesn’t stagnate because
she’s not keeping up….
36. 36
Trevor – eager entrepreneur
Trevor is a new agent. He just got
his license and he’s really eager
and enthusiastic. Trevor is 37 and
just turned to real estate after a
couple different careers. Trevor is really
ambitious and has aspirations to run his own
brokerage one day. He knows that putting in a
big effort now will mean the difference between
success and failure. Trevor is constantly looking
for more information about how to run his
business….
37. Storyboards: can be used for the major activities to
capture major moments in the narrative.
Scenarios: tell more details stories about the various
tasks users do.
Plot points: include these to reflect decision points
were a user might take a different path
Consider Sally: She often got too busy to go back to use the
product, to see what it could do.
37
Narrative Flow: stories about users
38. … Sally remembers she had seen an email offer for a
free trial. She doesn’t think she can find the email,
instead she looks for the trial offer at Homes.com.
She sees an advertisement for it, clicks it, and signs
up using the form. Then she takes a break to make
lunch. When she returns, she sees that she’s received
email confirming the sign up. In the email, she clicks
the link that will take her to her account. Then, she
is taken to the sign in page. However, she’s forgotten
which password she used, so she uses the “forgot
password” reminder to get a new password. When
she’s logged into her account, she sees that she can
import all her existing listings …
38
Meet Sally
39. 39
Now that you’ve fleshed out the major narrative
flow, arrange the major activities by working from
left to right
Tell the story from the user perspective, working in
the order that your user would perform the
activities
time
Order activities: narrative flow
Major
Activities
Discover
product
Onboard Manage
Listings
40. Break down activities into tasks that comprise the
activity
Don’t get hung up on order or being perfect: goal is
to get it out there
Tweak later
40
time
Decompose activities into tasks
Discover Onboard Manage
Listings
Via email
advert
Signupfor
account
Add new
listing
41. Vertical axis represents necessity
Arrange tasks according to how important they are
to the activity the user is doing
41
Add in necessity
time
necessity
Discover Onboard Manage
Listing
Email
advert
Analyze
Listings
Edit
Listing
Search
Listings
Sort
Listings
Signupfor
account
Add new
listing
Search
engine
Search
marketing
CTA on
site
42. 42
Below each activity are
the child stories that
comprise the activity
Task flow and task decomposition
time
necessity
43. 43
1. Thens / and thens: signal horizontal movement
2. Or: signals vertical movement
3. Vertical overlap: when tasks happening around same
time
ands, thens, ors, and mores
time
necessity
44. Record details so they’re not lost
Tuck under existing task cards
44
time
Sub-Functional or “Fish level”
Tasks that, alone, don’t achieve a meaningful goal
What if you hit “fish level”?
necessity
45. 45
Look for alternatives
What else might users do that didn’t come up in your
scenarios?
Look for exceptions
What could go wrong, and what would the user have to do to
recover? How would our product prevent the problem in the
first place. How would we help them recover.
Consider other users
What might other types of users do to reach their goals?
Might be: people, robots, search engines, other systems
Use workshops to fill in the gaps
48. 48
The user story mapping process
1. Write stories about how people use the product
2. Identify the activities that form backbone of your story
map and organize in the order they are performed
3. Flesh out the tasks people do to accomplish those
activities, ordering them by how necessary they are to
the activity
4. Be sure to explore alternative users, tasks, activity
flows and add in their paths and narratives
5. Slice out tasks according to how they help users
achieve specific outcomes
49. 49
Jeff Patton’s User Story Mapping
http://jpattonassociates.com/
http://jpattonassociates.com/