Abstraction can be used at the beginning of a project to facilitate communication and reflection in order to establish a shared framework. This clarifies goals for decision makers and gives direction to the production team – preventing the project from getting stuck in the weeds.
In our everyday work, as people who create digital products, we are under a lot of pressure from clients/employers to produce concrete outputs – often with little clarity concerning goals. This leads to stress and ineffectual outcomes.
Looking at the course of human history, people have always used methods of abstraction to make sense of a complicated world (like mapmakers). As IAs we can take advantage of this natural human tactic to abstract the complex, in order to bring clarity to our work by using tools such as maps, blueprints, and personas.
My presentation at WebVisions Portland in May 2012. Speaker notes / narrative included! Please forgive the cues & odd little notes to myself for presenting purposes.
Here are some tips for effective brainstorming:
- Defer judgment. Don't criticize ideas as they're being generated.
- Encourage wild ideas. Unusual, even seemingly ridiculous ideas can spark better ideas.
- Build on ideas. Improve and combine ideas from others instead of proposing your own at every turn.
- One conversation. Don't have side conversations that exclude others.
- Stay focused. Keep ideas related to the topic to keep the brainstorm productive.
- Go for quantity. Generate as many ideas as possible to increase the chances of good ideas emerging.
- Record all ideas. Capture all ideas to avoid losing potentially good ones.
The goal of brainstorming is to generate a
UX Basics Workshop at General Assembly London by Tricia OkinTricia Okin
The document summarizes a UX basics workshop presented by Tricia Okin, a web and UX designer. The workshop covers topics such as audience definition, user personas, mindmapping, wireframing, paper prototyping and storyboarding. It provides examples of each technique and discusses how to apply them to define users and solve problems. The workshop is intended to give attendees an introduction to foundational UX design methods and tools.
Presentation from a talk I gave at UX Brighton. There were a bunch of other folks talking on the same night about other aspects of meshing / mashing UX into Agile projects, so this one focusses a bit more on how you can do Lean UX (a little).
The document discusses emerging topics in mobile design and interaction. It begins by noting that mobile presents an opportunity to invent new ways for users to interact with information. It then outlines three emerging mobile topics: 1) Shapeshifting, where devices and interfaces can change form; 2) A Brave NUI World, where natural user interfaces replace graphical user interfaces; and 3) Comfortable Computing, where mobile devices are used for leisure in addition to tasks. The document explores each topic in more depth and provides implications and challenges for designers. It encourages thinking of content as a design material and focusing on how mobile experiences can unfold for users.
Here are the key screens for the new intelligent traffic system for New Delhi:
- Home Screen: Shows live traffic updates, parking availability, public transport schedules etc. Users can plan their journey
- Parking Screen: Allows users to check parking availability near their destination, book slots in advance, pay online etc.
- Navigation Screen: Provides turn-by-turn navigation to their destination considering live traffic conditions
- Emergency Screen: Allows users to report traffic accidents, breakdowns etc. Alerts are sent to the control room
- Control Room Screen: Allows traffic authorities to monitor live traffic, respond to emergencies, manage parking lots etc.
Let me know if you need any other details on the proposed
Huge Inc Intro to UX/UI lecture at Campus Londonnikkiguna
Huge is a full-service digital agency founded in 1999 that employs 550 people across multiple global offices. They help brands transform and grow their businesses through a focus on user experience design. Huge takes a three-step approach to designing user experiences: 1) listening to users through ethnographic research to understand their needs and behaviors, 2) prioritizing features to focus on the most important goals and tasks, and 3) testing designs iteratively with users to identify issues and drive continuous improvement.
My presentation at WebVisions Portland in May 2012. Speaker notes / narrative included! Please forgive the cues & odd little notes to myself for presenting purposes.
Here are some tips for effective brainstorming:
- Defer judgment. Don't criticize ideas as they're being generated.
- Encourage wild ideas. Unusual, even seemingly ridiculous ideas can spark better ideas.
- Build on ideas. Improve and combine ideas from others instead of proposing your own at every turn.
- One conversation. Don't have side conversations that exclude others.
- Stay focused. Keep ideas related to the topic to keep the brainstorm productive.
- Go for quantity. Generate as many ideas as possible to increase the chances of good ideas emerging.
- Record all ideas. Capture all ideas to avoid losing potentially good ones.
The goal of brainstorming is to generate a
UX Basics Workshop at General Assembly London by Tricia OkinTricia Okin
The document summarizes a UX basics workshop presented by Tricia Okin, a web and UX designer. The workshop covers topics such as audience definition, user personas, mindmapping, wireframing, paper prototyping and storyboarding. It provides examples of each technique and discusses how to apply them to define users and solve problems. The workshop is intended to give attendees an introduction to foundational UX design methods and tools.
Presentation from a talk I gave at UX Brighton. There were a bunch of other folks talking on the same night about other aspects of meshing / mashing UX into Agile projects, so this one focusses a bit more on how you can do Lean UX (a little).
The document discusses emerging topics in mobile design and interaction. It begins by noting that mobile presents an opportunity to invent new ways for users to interact with information. It then outlines three emerging mobile topics: 1) Shapeshifting, where devices and interfaces can change form; 2) A Brave NUI World, where natural user interfaces replace graphical user interfaces; and 3) Comfortable Computing, where mobile devices are used for leisure in addition to tasks. The document explores each topic in more depth and provides implications and challenges for designers. It encourages thinking of content as a design material and focusing on how mobile experiences can unfold for users.
Here are the key screens for the new intelligent traffic system for New Delhi:
- Home Screen: Shows live traffic updates, parking availability, public transport schedules etc. Users can plan their journey
- Parking Screen: Allows users to check parking availability near their destination, book slots in advance, pay online etc.
- Navigation Screen: Provides turn-by-turn navigation to their destination considering live traffic conditions
- Emergency Screen: Allows users to report traffic accidents, breakdowns etc. Alerts are sent to the control room
- Control Room Screen: Allows traffic authorities to monitor live traffic, respond to emergencies, manage parking lots etc.
Let me know if you need any other details on the proposed
Huge Inc Intro to UX/UI lecture at Campus Londonnikkiguna
Huge is a full-service digital agency founded in 1999 that employs 550 people across multiple global offices. They help brands transform and grow their businesses through a focus on user experience design. Huge takes a three-step approach to designing user experiences: 1) listening to users through ethnographic research to understand their needs and behaviors, 2) prioritizing features to focus on the most important goals and tasks, and 3) testing designs iteratively with users to identify issues and drive continuous improvement.
We were invited to talk at the Balanced Team event at Adaptive Path's offices in Austin, Texas during SXSW 2012. Paul Sims our service design lead took the floor for a 10 minute lightning talk about our take on Lean and service design at MxM.
Bill Scott, Director from the UI Engineering team at Netflix shows ways to use RIA to enhance the User Experience. If you take more interest in the field of design patterns than drop by at www.interaction-patterns.org.
1. The document outlines Team Inferno's approach to the case study competition, including conducting industry and competitor analyses, developing insights about consumers, and creating a product based on those insights.
2. It provides an overview of the Indian movie industry and emerging trends like short films and the growth of internet and smartphones in India.
3. Primary research insights from potential customers indicate a need for a platform to launch, promote, and find information about short movies as well as generate new movie ideas.
Agile2011 Session
Agile Education by Object Game
Most HISSATSU Way to understand it.
This session has an another article, Object Card. please download with it
A presentation which covers the do's and don'ts of business outsourcing from someone who has experience in outsourcing Accounting, various bookkeeping and software development.
Behaviour Driven Development (BDD) is an approach than encourages teams and stakeholders in general to reason about requirements in terms of “executable specifications”, and focus on implementing features with demonstrable business value. BDD is more than just a development technique: in fact, it introduces a whole new dynamic to interactions between team members and stakeholders, a dynamic that increases communication, improves productivity and reduces waste. Through ongoing conversations between business stakeholders and team members, a team applying BDD principles will explore the business goals, capabilities and behaviour that the stakeholders need. They then propose features that the system will need to deliver these capabilities, and use concrete examples and counter-examples to explore and understand these features more fully. In this talk, you will learn about the principles and benefits of BDD for the whole team, how BDD works in practice, and how it affects the various team members in a project. Finally, you will discover the relationship between behavior driven development and automated acceptance testing.
Workbook Advanced Patent Analysis Using TRIZ and Other TechniquesNavneet Bhushan
Crafitti Consulting (http://www.crafitti.com) conducts innovation ignitions workshops using our innovation frameworks based on TRIZ, LEAN, Inventive and Systems Thinking
What is the game? How is it changing? Who are the innovators? How to innovate in today’s world ... inspiring keynote from Peter Fisk, first presented in Budapest, January 2012
Web Visions PDX '12: Applying Behavior DesignChris Risdon
The document discusses the emerging field of behavior design and persuasive technology, which involves designing products and services with the intent to change users' behaviors or attitudes. It provides examples of how data collection and feedback loops now enable real-time personalized persuasion at scale. The document argues that designers should be transparent about their persuasive intents and ensure their designs provide clear utility or value to users.
The document discusses whether online interactive projects should be considered "social films" or "social experiences". It provides arguments for both perspectives, discussing aspects like budgets, interactivity, and episodic nature. After considering multiple viewpoints, the document concludes that terms like "Kill Cam Live" and "The Inside Experience" are better defined as social experiences rather than social films, primarily due to their episodic nature and interactivity which differs from typical films.
How 5 people with 4 day jobs in 3 time zones enjoyed 2 years writing 1 bookErin Dees
The story of writing the JRuby book together, with lessons for freelancers, telecommuters, and remote collaborators everywhere. Slides from Open Source Bridge 2011.
The document announces a "Nightmare" 3D and 2D art challenge run by CGArena, requiring entrants to submit work-in-progress images for feedback, with a deadline of May 15th to submit final entries, and prizes to be awarded in the 3D and 2D categories.
IAS13: Metadata in the Cross-Channel Ecosystem: Consistency, Context and Inte...aungstad
Metadata enables consistency, context and interoperability in a cross-channel context by managing, describing and exchanging information objects.
This presentation explores 3 different types of metadata: administrative, descriptive, and structural, and their role in UX practices including content strategy, responsive design, rich snippets, and web forms.
We’ll then look at the cross-channel ecosystem, understanding media, channels, interactions and touchpoints. We’ll explore The Internet of Things, and furthermore the importance of information exchanges in cross-channel service design.
From there we learn about the nuts and bolts of an information exchange, including semantics, syntax and lexicon, and how these are documented in schema. Then we’ll look at some of the common standards used to specify schema for information exchanges and semantic markup. Last but not least, we’ll explore how linked data and ontologies enable us to progress from the Web of Documents to the Web of Data.
Presentation for the Information Architecture Summit in Baltimore, Maryland April 6th 2013. I had a great time & welcome feedback to further the discussion. Thanks everyone!
The document discusses the need for a new paradigm in how we think about and build products for the Internet of Things, as relying only on existing models like mobile apps will not be sustainable as more smart devices proliferate. It proposes moving to a model focused on discovery of nearby smart devices, controlling them through simple interactions like web pages rather than apps, and coordinating data and functionality across devices through open standards. The document argues this approach will be needed to truly realize the potential of the Internet of Things.
Ghost in the Shell - Information Architecture in the Age of PostdigitalAndrea Resmini
The document discusses the theme of the 2013 IA Summit in Baltimore - "Information Architecture in the Age of Postdigital". It explores how information architecture has evolved from the digital age to the current postdigital age. In the postdigital age, computing is ubiquitous and integrated into all aspects of life. Things are increasingly complex, smeared across multiple contexts. Information spaces have become fluid and dynamic architectures. The document argues that information architecture is the architecture of these new postdigital information spaces, shaping reality and creating places for human experience.
Web Governance: Where Strategy Meets StructurePeter Morville
The document discusses the topic of web governance. It suggests that web governance is needed to address issues like fragmentation and findability on websites. It presents a framework for web governance that includes establishing a web governance board, having a unified web strategy, and utilizing network intelligence. The framework also discusses establishing local governance structures. It provides examples of levers that can be used to drive change, such as designing for connection, utilizing organizational charts, and establishing pods/teams.
Web Governance: Where Strategy Meets StructureLisa Welchman
This document discusses web governance and how it relates to strategy and structure. It provides examples of how governance helps sustain digital presences over long periods of time by establishing norms, regulations, and standards. Governance frameworks include defining strategy, policies, stakeholders, and teams. Strategy includes principles, funding, and desired outcomes. Policies cover various technical and legal standards. Stakeholders provide input and make decisions. Effective governance facilitates collaboration and growth by outlining how execution will occur.
From systematic studies over the decades, the smart home’s main functionalities have evolved from home automation to remote monitoring and controlling, then to context awareness. All the smart home products have a mainstream type in a certain period. However, have these mainstream functionalities covered all the needs of the users?
Through 3 rounds of research conducted across 3 different markets (China, EU, and Bay Area in the US) during a two-year span, Veronika and her colleagues at frog have found some new surprising uses and work-arounds that users invented, which have definitely inspired them in surfacing the hidden and essential needs in smart homes.
Fancy to know what kind of uses and work-arounds users have created?
In this talk, through some research finding anecdotes, Veronika will lay out 3 key lenses that were used to uncover the hidden needs and JBTDs in the smart home space, and talk about how to transfer these hidden needs into some new smart home product and service design opportunities.
This document provides an overview of Google Cloud's offerings for generative AI. It begins with a primer on large language models and generative AI, explaining what they are and how they have evolved. It then outlines Google's role in pioneering developments in the field like BERT and Transformer models. The rest of the document details Google's portfolio of products and services for generative AI, including foundation models like PaLM, experiences for consumers and enterprises, and tools for developers and AI practitioners. It emphasizes that Google aims to support a wide range of needs through its family of generative AI models and applications.
We were invited to talk at the Balanced Team event at Adaptive Path's offices in Austin, Texas during SXSW 2012. Paul Sims our service design lead took the floor for a 10 minute lightning talk about our take on Lean and service design at MxM.
Bill Scott, Director from the UI Engineering team at Netflix shows ways to use RIA to enhance the User Experience. If you take more interest in the field of design patterns than drop by at www.interaction-patterns.org.
1. The document outlines Team Inferno's approach to the case study competition, including conducting industry and competitor analyses, developing insights about consumers, and creating a product based on those insights.
2. It provides an overview of the Indian movie industry and emerging trends like short films and the growth of internet and smartphones in India.
3. Primary research insights from potential customers indicate a need for a platform to launch, promote, and find information about short movies as well as generate new movie ideas.
Agile2011 Session
Agile Education by Object Game
Most HISSATSU Way to understand it.
This session has an another article, Object Card. please download with it
A presentation which covers the do's and don'ts of business outsourcing from someone who has experience in outsourcing Accounting, various bookkeeping and software development.
Behaviour Driven Development (BDD) is an approach than encourages teams and stakeholders in general to reason about requirements in terms of “executable specifications”, and focus on implementing features with demonstrable business value. BDD is more than just a development technique: in fact, it introduces a whole new dynamic to interactions between team members and stakeholders, a dynamic that increases communication, improves productivity and reduces waste. Through ongoing conversations between business stakeholders and team members, a team applying BDD principles will explore the business goals, capabilities and behaviour that the stakeholders need. They then propose features that the system will need to deliver these capabilities, and use concrete examples and counter-examples to explore and understand these features more fully. In this talk, you will learn about the principles and benefits of BDD for the whole team, how BDD works in practice, and how it affects the various team members in a project. Finally, you will discover the relationship between behavior driven development and automated acceptance testing.
Workbook Advanced Patent Analysis Using TRIZ and Other TechniquesNavneet Bhushan
Crafitti Consulting (http://www.crafitti.com) conducts innovation ignitions workshops using our innovation frameworks based on TRIZ, LEAN, Inventive and Systems Thinking
What is the game? How is it changing? Who are the innovators? How to innovate in today’s world ... inspiring keynote from Peter Fisk, first presented in Budapest, January 2012
Web Visions PDX '12: Applying Behavior DesignChris Risdon
The document discusses the emerging field of behavior design and persuasive technology, which involves designing products and services with the intent to change users' behaviors or attitudes. It provides examples of how data collection and feedback loops now enable real-time personalized persuasion at scale. The document argues that designers should be transparent about their persuasive intents and ensure their designs provide clear utility or value to users.
The document discusses whether online interactive projects should be considered "social films" or "social experiences". It provides arguments for both perspectives, discussing aspects like budgets, interactivity, and episodic nature. After considering multiple viewpoints, the document concludes that terms like "Kill Cam Live" and "The Inside Experience" are better defined as social experiences rather than social films, primarily due to their episodic nature and interactivity which differs from typical films.
How 5 people with 4 day jobs in 3 time zones enjoyed 2 years writing 1 bookErin Dees
The story of writing the JRuby book together, with lessons for freelancers, telecommuters, and remote collaborators everywhere. Slides from Open Source Bridge 2011.
The document announces a "Nightmare" 3D and 2D art challenge run by CGArena, requiring entrants to submit work-in-progress images for feedback, with a deadline of May 15th to submit final entries, and prizes to be awarded in the 3D and 2D categories.
IAS13: Metadata in the Cross-Channel Ecosystem: Consistency, Context and Inte...aungstad
Metadata enables consistency, context and interoperability in a cross-channel context by managing, describing and exchanging information objects.
This presentation explores 3 different types of metadata: administrative, descriptive, and structural, and their role in UX practices including content strategy, responsive design, rich snippets, and web forms.
We’ll then look at the cross-channel ecosystem, understanding media, channels, interactions and touchpoints. We’ll explore The Internet of Things, and furthermore the importance of information exchanges in cross-channel service design.
From there we learn about the nuts and bolts of an information exchange, including semantics, syntax and lexicon, and how these are documented in schema. Then we’ll look at some of the common standards used to specify schema for information exchanges and semantic markup. Last but not least, we’ll explore how linked data and ontologies enable us to progress from the Web of Documents to the Web of Data.
Presentation for the Information Architecture Summit in Baltimore, Maryland April 6th 2013. I had a great time & welcome feedback to further the discussion. Thanks everyone!
The document discusses the need for a new paradigm in how we think about and build products for the Internet of Things, as relying only on existing models like mobile apps will not be sustainable as more smart devices proliferate. It proposes moving to a model focused on discovery of nearby smart devices, controlling them through simple interactions like web pages rather than apps, and coordinating data and functionality across devices through open standards. The document argues this approach will be needed to truly realize the potential of the Internet of Things.
Ghost in the Shell - Information Architecture in the Age of PostdigitalAndrea Resmini
The document discusses the theme of the 2013 IA Summit in Baltimore - "Information Architecture in the Age of Postdigital". It explores how information architecture has evolved from the digital age to the current postdigital age. In the postdigital age, computing is ubiquitous and integrated into all aspects of life. Things are increasingly complex, smeared across multiple contexts. Information spaces have become fluid and dynamic architectures. The document argues that information architecture is the architecture of these new postdigital information spaces, shaping reality and creating places for human experience.
Web Governance: Where Strategy Meets StructurePeter Morville
The document discusses the topic of web governance. It suggests that web governance is needed to address issues like fragmentation and findability on websites. It presents a framework for web governance that includes establishing a web governance board, having a unified web strategy, and utilizing network intelligence. The framework also discusses establishing local governance structures. It provides examples of levers that can be used to drive change, such as designing for connection, utilizing organizational charts, and establishing pods/teams.
Web Governance: Where Strategy Meets StructureLisa Welchman
This document discusses web governance and how it relates to strategy and structure. It provides examples of how governance helps sustain digital presences over long periods of time by establishing norms, regulations, and standards. Governance frameworks include defining strategy, policies, stakeholders, and teams. Strategy includes principles, funding, and desired outcomes. Policies cover various technical and legal standards. Stakeholders provide input and make decisions. Effective governance facilitates collaboration and growth by outlining how execution will occur.
From systematic studies over the decades, the smart home’s main functionalities have evolved from home automation to remote monitoring and controlling, then to context awareness. All the smart home products have a mainstream type in a certain period. However, have these mainstream functionalities covered all the needs of the users?
Through 3 rounds of research conducted across 3 different markets (China, EU, and Bay Area in the US) during a two-year span, Veronika and her colleagues at frog have found some new surprising uses and work-arounds that users invented, which have definitely inspired them in surfacing the hidden and essential needs in smart homes.
Fancy to know what kind of uses and work-arounds users have created?
In this talk, through some research finding anecdotes, Veronika will lay out 3 key lenses that were used to uncover the hidden needs and JBTDs in the smart home space, and talk about how to transfer these hidden needs into some new smart home product and service design opportunities.
This document provides an overview of Google Cloud's offerings for generative AI. It begins with a primer on large language models and generative AI, explaining what they are and how they have evolved. It then outlines Google's role in pioneering developments in the field like BERT and Transformer models. The rest of the document details Google's portfolio of products and services for generative AI, including foundation models like PaLM, experiences for consumers and enterprises, and tools for developers and AI practitioners. It emphasizes that Google aims to support a wide range of needs through its family of generative AI models and applications.
The document discusses apps available on the Apple App Store. It notes that over 800,000 apps are available to approximately 50 million users, with the average user having 48 apps but 98% of apps being discarded within 60 months. Key considerations for developing successful apps include providing value beyond what's available via browser, ensuring a good user experience, and consistently delivering new value with each release.
1) The document discusses different approaches to user testing, including moderated vs unmoderated testing, prototyping full apps vs prioritized stories, and personalized vs aggregated feedback. It suggests balancing these approaches to learn quickly.
2) It recommends prioritizing the riskiest assumptions and most important things to learn when deciding how much of a design to prototype.
3) For quick prototyping, it suggests focusing user stories into specific tasks that can then be tested through a personalized scenario walkthrough. This allows learning patterns across participants.
Exploring the future of the IT industry and the next generation CIOJessvin Thomas
1) The digital revolution is driving changes that require IT organizations to shift from administrators of technology to innovators who add value through distinctive capabilities.
2) To attract and retain top talent, IT teams must adopt aspects of startup culture like cross-functional collaboration, agility, and self-management.
3) A successful service model in the future will be customized, allow for interoperability across solutions, and be designed for ease of use to meet changing employee expectations around technology use.
This document discusses user experience (UX), agile product management, and delivering software that meets user needs. It advocates for an iterative development process that incorporates UX research and testing. Product managers are advised to work closely with UX designers to validate assumptions through usability testing, measure outcomes, and prioritize addressing UX issues. An agile, lean approach that rapidly builds and learns from user feedback is presented as the best way to deliver innovative products that customers want and provide a competitive advantage.
daqri: Brian Mullins "State of Augmented Reality" at ARDevCampSDDAQRI
This document summarizes Brian Mullins' presentation about augmented reality (AR) at the ARDevCamp SD 2011.
1) Mullins defines AR as enhancing the real world with computer-generated graphics overlaid onto it.
2) He discusses the differences between location-based and vision-based AR, noting that both have value.
3) Mullins presents on Daqri, the AR company he founded, which aims to make AR experiences practical for companies and individuals through tools for content creation and cloud delivery of AR content.
The Laws of User Experience: Making it or breaking it with the UX FactorEffectiveUI
This document outlines notes from user interviews conducted about a network monitoring application called the TriGeo Console. Key points discussed include:
- Six users were interviewed by phone and notes were taken on their usage patterns, pain points, and wishes for improvement.
- Common activities included monitoring alerts, logs, reports and the overall network security status. Users accessed multiple windows and tabs.
- Issues noted were that tabs took up too much space, navigation was not task-focused, and primary tasks were hidden in menus.
- Suggested improvements included a customizable dashboard, ability to customize the view, more consistent workflows, and improving filtering and report capabilities.
Acxiom Interactive Marketing Summit 2011- Real-World Perspectives on Real Ti...Acxiom Corporation
Acxiom Interactive Marketing Summit 2011- Real-World Perspectives on Real Time Decisioning
Scott DeAngelo, Marketing Strategy Practice Leader Acxiom Global Consulting Group
Group Partners provides consulting services to help clients navigate complex changes and challenges. They offer strategy development, innovation services, leadership training, and guidance through mergers and acquisitions. Their approach is impartial, analytical, and focused on discovering the right solution through collaborative workshops and frameworks. They create visual tools and documents to support clients in implementing strategies.
Brian Donohue - Why Product Managers Should Own a Job, Not a Set of Features ...Productized
The document discusses how product managers should focus on understanding the "jobs to be done" (JTBD) by customers rather than individual features. It emphasizes that products naturally tend towards disorder and mediocrity over time, so product teams must fight entropy by using JTBD to maintain clarity on customer needs and prevent feature creep. JTBD provides a framework to understand user problems independently of technological solutions and helps prioritize the smallest improvements that provide the most value. The document advocates using JTBD to guide product strategy and development instead of focusing on a feature roadmap.
Sharepoint in a Complex Business ContextSarah Barrett
Through the lens of a case study for a highly successful transition to Sharepoint 2013, this talk will give attendees a framework for integrating UX techniques into an Agile Sharepoint process. Relying on best practices and industry standards works well in a relatively simple business context, but when a business gets more complex, it’s vitally important to make sure the design process is iterative, that deliverables are structured to get meaningful consensus, and that business, design, and technical stakeholders can agree on functionality and priorities. The case study will take you through a project that was going off the rails, and how it was pulled back into a success that eventually led to users tackling the project sponsor with hugs. It will share what we did right, what we did wrong, and what we learned along the way to make every Agile Sharepoint project more successful.
This document discusses business model generation for machine-to-machine (M2M) applications. It emphasizes starting with customer insights to define the value proposition and highlights key success factors like perceived value, willingness to pay, partnerships, and cost management. Business models must balance value and price while allowing for evolution. The customer experience is more important than technical aspects, and individual needs must be addressed for mass market appeal.
How To Write A Case Study Essay. Online assignment writing service.Antoinette Williams
I apologize, upon further reflection I do not feel comfortable making a broad claim about an entire industry without sufficient evidence or context. Different transportation sectors likely have varying impacts and records.
The document provides information about Unit 43 - Use Office Equipment. It discusses the different types of office equipment like computers, telephones, printers, and photocopiers. It explains how each type of equipment is used and the importance of following organizational instructions and health and safety procedures when using office equipment.
The document discusses user stories for software requirements. It provides tips for writing good user stories, such as starting with user goals, writing smaller stories for soon-to-be-implemented functionality, keeping the user interface out of stories initially, and having the customer rather than developer write stories. It also identifies "smelly" user stories, such as those that are too small, interdependent, include too many details, or are written too far in advance.
What is ? Modern business questions 2014Exo Futures
What is:
- Important
- Innovation
-- Is it only technology innovation?
- Entrepreneurship
- Money
- Cloud
-- Is it more than the internet?
- Mobility
- Big data
- Business Model
How to Successfully Exploit the Power of the Matrix - ENT225 - re:Invent 2017Amazon Web Services
Leading Edge Forums (LEF) has labelled the synergistic combination of cloud computing and machine intelligence (MI) as ‘the Matrix’: the combination of cloud services such as IaaS, IoT, MI, and edge computing. For companies to thrive, they need to know the answers to the following questions: How are successful companies harnessing the power of the Matrix? How do they structure their organizations? What makes them so agile? How do they attract and retain skilled employees? LEF studies successful businesses and learns what makes them great. Our 6-month research program has dived deep with multiple AWS customers to understand not only their use of the technology, but also the business transformation program that allowed them to maximize the value that AWS provides. Attend this session to learn more about the research that has been done, client examples, observations that the LEF has made and how this can be used to help drive your transformation program.
Session sponsored by DXC Technology
Ähnlich wie Using Abstraction to Increase Clarity (20)
How to Successfully Exploit the Power of the Matrix - ENT225 - re:Invent 2017
Using Abstraction to Increase Clarity
1. Using Abstraction to
Increase Clarity
Kaarin Hoff
Information Architect, The Understanding Group (TUG)
#AbstractionforClarity
#AbstractionforClarity
2. Abstraction:
the intentional filtering of
information to focus a
conversation on the core goal(s)
#AbstractionforClarity
5. Abstraction Best Practices
• If its going to distract from the conversation, don’t
include it
• Use a model that fits the information, not vice versa
• Clearer: not necessarily less, could even be more
• Allow your models to combine information from
multiple sources
#AbstractionforClarity
6. Too often we are asked to
jump to the detailed
#AbstractionforClarity
7. Thoughtfully using
abstractions can avoid a lot
of this pain and keep projects
from getting stuck in prior
assumptions
#AbstractionforClarity
8. We must choose carefully the
model we use to facilitate
conversations
#AbstractionforClarity
9. We must choose carefully the model through
which we hold conversations
Marriot
#AbstractionforClarity
10. We must choose carefully the model through
which we hold conversations
http://ffffound.com/home/vvva/found/
#AbstractionforClarity
11. We must choose carefully the model through
which we hold conversations
www.google.com
#AbstractionforClarity
12. We must choose carefully the model through
which we hold conversations
#AbstractionforClarity
13. We must choose carefully the model through
which we hold conversations
Employment | News | Contact Us | Investor Relations
EdR Logo
NYSE-EDR: 1.03%
Services
Services Properties About EdR
Home >
Services
Financing
Introductory content about the variety of services available and the customization that is
available, exclusively through EdR Trust. Lorem ipsum dolor sit amet, consectetur adipiscing
Development
elit. Duis laoreet egestas neque, quis viverra ipsum vehicula ac.
• Sed non justo odio. Acquisitions
• Phasellus eleifend vulputate tellus sed varius.
• Integer blandit tempus volutpat. Property Management
Sed adipiscing consequat lobortis. Donec ultrices, erat vitae posuere porttitor, felis velit tempus
magna, vel venenatis neque lectus in eros. Nam vitae pharetra dui. Etiam tellus velit, mattis a Case Studies
pulvinar nec, gravida id nunc.
Financing Development Acquisitions Property Management
Abbreviated content specific to Abbreviated content specific to Abbreviated content specific to Abbreviated content specific to
each service offering. Lorem each service offering. Lorem each service offering. Lorem each service offering. Lorem
ipsum dolor sit amet, consectetur ipsum dolor sit amet, consectetur ipsum dolor sit amet, consectetur ipsum dolor sit amet, consectetur
adipiscing elit. Duis laoreet adipiscing elit. Duis laoreet adipiscing elit. Duis laoreet adipiscing elit. Duis laoreet
egestas neque, quis viverra ipsum egestas neque, quis viverra ipsum egestas neque, quis viverra ipsum egestas neque, quis viverra ipsum
vehicula ac. vehicula ac. vehicula ac. vehicula ac.
Learn more about Financing Learn more about Development Learn more about Acquisitions Learn more about Property
Management #AbstractionforClarity
14. We must choose carefully the model through
which we hold conversations
#AbstractionforClarity
18. Concrete
Abstracted
Plausible
Improbable
Narrative
User Visual
Client X Chapter 1 Chapter 2
Customer Journey Example 1
External
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed
do eiusmod tempor incididunt ut labore et dolore magna
User
aliqua. Ut enim ad minim veniam, quis nostrud exercitation 8
ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis
aute irure dolor in reprehenderit in voluptate velit esse cillum
dolore eu fugiat nulla pariatur. Excepteur sint occaecat
cupidatat non proident, sunt in culpa qui officia deserunt mollit
IA
anim id est laborum.
Property #3
3
2 10
Nostrud exercitation ullamco laboris nisi ut aliquip ex ea
commodo consequat. Duis aute irure dolor in reprehenderit in
voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Excepteur sint occaecat cupidatat non proident, sunt in culpa
9
qui officia deserunt mollit anim id est laborum. 3
Brain Chapter 1: Something happens 5
5
Property #2
Nostrud exercitation ullamco laboris nisi ut aliquip ex ea
commodo consequat. Nostrud exercitation ullamco laboris nisi
ut aliquip ex ea commodo consequat. 6
Chapter 2: Something else happens 4
Nostrud exercitation ullamco laboris nisi ut aliquip ex ea 7
commodo consequat. Duis aute irure dolor in reprehenderit in
voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Excepteur sint occaecat cupidatat non proident, sunt in culpa
qui officia deserunt mollit anim id est laborum.
Property #1
4 2 11
User 1
12
User
#AbstractionforClarity
19. Client X Chapter 1 Chapter 2
Customer Journey Example 1
External
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed
do eiusmod tempor incididunt ut labore et dolore magna
aliqua. Ut enim ad minim veniam, quis nostrud exercitation 8
ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis
aute irure dolor in reprehenderit in voluptate velit esse cillum
dolore eu fugiat nulla pariatur. Excepteur sint occaecat
cupidatat non proident, sunt in culpa qui officia deserunt mollit
anim id est laborum.
Property #3
3
2 10
Nostrud exercitation ullamco laboris nisi ut aliquip ex ea
commodo consequat. Duis aute irure dolor in reprehenderit in
voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Excepteur sint occaecat cupidatat non proident, sunt in culpa
9
qui officia deserunt mollit anim id est laborum. 3
Chapter 1: Something happens 5
5
Property #2
Nostrud exercitation ullamco laboris nisi ut aliquip ex ea
commodo consequat. Nostrud exercitation ullamco laboris nisi
ut aliquip ex ea commodo consequat. 6
Chapter 2: Something else happens 4
Nostrud exercitation ullamco laboris nisi ut aliquip ex ea 7
commodo consequat. Duis aute irure dolor in reprehenderit in
voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Excepteur sint occaecat cupidatat non proident, sunt in culpa
qui officia deserunt mollit anim id est laborum.
Property #1
4 2 11
12
1
#AbstractionforClarity
21. Client X Chapter 1 Chapter 2
Customer Journey Example 1
IA
External
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed
do eiusmod tempor incididunt ut labore et dolore magna
aliqua. Ut enim ad minim veniam, quis nostrud exercitation 8
ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis
aute irure dolor in reprehenderit in voluptate velit esse cillum
dolore eu fugiat nulla pariatur. Excepteur sint occaecat
cupidatat non proident, sunt in culpa qui officia deserunt mollit
anim id est laborum.
Brain
Property #3
IA
3
2 10
Nostrud exercitation ullamco laboris nisi ut aliquip ex ea
commodo consequat. Duis aute irure dolor in reprehenderit in
Stakeholder
voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Excepteur sint occaecat cupidatat non proident, sunt in culpa
9
qui officia deserunt mollit anim id est laborum. 3
Brain Chapter 1: Something happens 5
5
Property #2
Nostrud exercitation ullamco laboris nisi ut aliquip ex ea
commodo consequat. Nostrud exercitation ullamco laboris nisi
ut aliquip ex ea commodo consequat. 6
Chapter 2: Something else happens 4
Nostrud exercitation ullamco laboris nisi ut aliquip ex ea 7
commodo consequat. Duis aute irure dolor in reprehenderit in
voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Excepteur sint occaecat cupidatat non proident, sunt in culpa
qui officia deserunt mollit anim id est laborum.
Property #1
Dev-
4 2 11
12
1
eloper
#AbstractionforClarity
27. Abstraction Best Practices
• If its going to distract from the conversation, don’t
include it
• Use a model that fits the information, not vice versa
• Clearer: not necessarily less, could even be more
• Allow your models to combine information from
multiple sources
#AbstractionforClarity
28. Try it out, keep the
conversation going
Kaarin Hoff Group
kaarin@understandinggroup.com #AbstractionforClarity
@kaarinh Slideshare
#AbstractionforClarity
Hinweis der Redaktion
I’ve been at TUG for about year and I’ve been so impressed how they accomplish so much in a conversation – goal alignment, relationship building- the end of a meeting is just always so positive. Not the pangs of regret and frustration due to conversation derailment I was used to from previous jobs.
When I say abstraction, I’m talking about it in terms of the intentional filtering of information in a model to focus on the core goal of a conversation. Restructuring the information to focus the conversation. Abstraction is not about making things simpler, but making them clearer.
Richard Saul Wurman’s diagram of the Tokyo subway is a great example of the power of abstraction. He stripped away the geography layer and focused only on what people riding around underground would need to know. How the rails connect matters to the passengers. This diagram makes it clear that if you get on at Osaki, you can switch trains in Shinjuku and reach the Imperial Palace. Obviously this map wouldn’t work for the subway maintenance crew – but it serves its purpose by focusing the viewer on what’s important in this circumstance.
What the subway system would look like with geography…
Work in progress…
We often don’t have the luxury of time. We are asked things like “Make a thing that does this and we’ll discuss it in the meeting Tuesday”And then what happens? The whole meeting is spent on nit-picky things like “Can we change the font?” or “There is a typo in the word ‘example’”Or worst, there this is a re-design of an existing product that people are attached to and the status quo bias sets in – I liked the old formatting better.Then 2 months later it becomes clear through analytics and user feedback that the thing wasn’t the right thing to make in the first place. And you’re left wishing that discussions could have focused on what the product needed to accomplish instead of silly details.
When we rush ahead it often causes more work in the end. Thoughtfully producing an abstraction to guide a conversation at the beginning of a project can help avoid a lot of this pain: aligning your team, focusing the project, and resulting in better outcomes.
We get different conversations from depending on the medium we present things in. For instance we talk about different facets of a city if we discuss this
Picture of Baltimore or if we
Discuss this hand-dawn city map that abstracts the city to focus on major buildings and rivers
Or we have a very experience giving directions like this
Or like this
We certainly discuss different elements looking at something like this-Actually the wireframe discussion started with the client from this concrete point, instead of from the sketch. And you know what feedback I got? “The content is too dense” – so I had to go back and add bullet points in the loremipsum. There was never discussion around larger, experience type targets.
Or this
Now I’d like to dig deeper using 2 examples.First, let’s discuss the value of a customer journey as an abstraction of user tests.
Concrete section: raw data collected from user testingIf you give the all raw data, or even a more condensed version of it, to the stakeholder they are likely to succumb to confirmation bias. People come to the design table with assumptions and naturally attempt to fit data into the boxes based on their beliefs previous to testing. Its simple human nature.
Providing them with an abstraction to base a conversation around will help to facilitate conversations that will illuminate key issues and guide the project forwardBy getting past preconception and filtering out all but the most relevant information
Picking lanes importantLike WurmanJorge “diagrams so rich that it starts suggesting the solution
The desired outcome would be everyone on the project being on the same page
So if you do a bunch of stakeholder interviews you hear a lot of information, needs, and wants. All these inputs are important.
But what if one of those people is the boss? Maybe only their voice matters once that is revealed. But that gets us so far from the goal of understanding the true goals of this project. It can’t be dictated by one person since everyone’s input adds something important.
So if instead of showing the notes in general and saying “should we build to accomplish this?” It is helpful to distill those down into a goal list that is abstracted away from that original data. Now no one is more important than another. Now the realm of possible goals is clear. Taking this list back to the stakeholders and asking “is this right?” – often the priority is re-arranged, but always goals that weren’t on the boss’s radar become salient and are given a voice.
Now everyone feels heard. Everyone knows where the project is heading.