Slides for Docacon 2018.
Go over principles and techniques for building user friendly interviews for Docassemble aimed at pro se litigants with the experience of building an interview for tenants who are facing eviction.
The document discusses the benefits of using HTML prototypes for communicating designs. HTML prototypes allow stakeholders to interact with and experience dynamic web interfaces, improving understanding over documentation alone. They can reduce waste by helping the right people make decisions early, testing ideas, and catching problems sooner. HTML prototypes are a platform-independent, cost-effective way to gauge feasibility and get feedback before full development.
This document discusses the importance and benefits of usability testing with low budgets, time, and expertise. It recommends testing early and often during the design and development process. Specific tips are provided for designing simple tests, analyzing results, and taking action to improve based on findings. Affordable software options are listed that allow for remote or in-person usability testing.
1) EBI is redesigning their long-established InterPro website to improve usability, reduce costs, and increase usage.
2) They used a user-centered design approach, gathering user feedback through various methods to understand wants and needs before beginning the redesign process.
3) This involved rapid prototyping, usability testing, and gathering continuous user feedback to iteratively design and refine the new site.
Usability testing involves planning studies to test a digital product. Key steps in planning include defining goals and participants, designing tasks, scheduling tests, and determining testing methods. Tests can be conducted remotely or in-person. Moderated tests involve a moderator guiding participants through tasks while they think aloud. Unmoderated tests use automated tools to gather metrics from participants remotely. Findings are analyzed to identify usability issues and improve the product's design. Mobile testing requires adaptations for its form factor. Fitting research into agile development requires parallel or staggered sprints.
This document discusses various terms related to user-centered design such as user experience design, user interface design, and interaction design. It emphasizes incorporating users into the design process through techniques like usability testing in order to create intuitive products that are successful in the marketplace. The document provides tips for design such as using established patterns while still allowing for innovation, and suggests reviewing requirements, designing, and testing iteratively with users.
This document discusses the importance of user experience and usability testing in website design. It defines usability as how easy user interfaces are to use, and notes there are five key components: learnability, efficiency, memorability, errors, and satisfaction. Early and frequent user testing is recommended to fix issues, test assumptions, and inform the design process. Examples of tasks and questions to use during testing are provided. The benefits of testing with real users and focusing on important fixes rather than minor issues are also outlined.
The document discusses the benefits of using HTML prototypes for communicating designs. HTML prototypes allow stakeholders to interact with and experience dynamic web interfaces, improving understanding over documentation alone. They can reduce waste by helping the right people make decisions early, testing ideas, and catching problems sooner. HTML prototypes are a platform-independent, cost-effective way to gauge feasibility and get feedback before full development.
This document discusses the importance and benefits of usability testing with low budgets, time, and expertise. It recommends testing early and often during the design and development process. Specific tips are provided for designing simple tests, analyzing results, and taking action to improve based on findings. Affordable software options are listed that allow for remote or in-person usability testing.
1) EBI is redesigning their long-established InterPro website to improve usability, reduce costs, and increase usage.
2) They used a user-centered design approach, gathering user feedback through various methods to understand wants and needs before beginning the redesign process.
3) This involved rapid prototyping, usability testing, and gathering continuous user feedback to iteratively design and refine the new site.
Usability testing involves planning studies to test a digital product. Key steps in planning include defining goals and participants, designing tasks, scheduling tests, and determining testing methods. Tests can be conducted remotely or in-person. Moderated tests involve a moderator guiding participants through tasks while they think aloud. Unmoderated tests use automated tools to gather metrics from participants remotely. Findings are analyzed to identify usability issues and improve the product's design. Mobile testing requires adaptations for its form factor. Fitting research into agile development requires parallel or staggered sprints.
This document discusses various terms related to user-centered design such as user experience design, user interface design, and interaction design. It emphasizes incorporating users into the design process through techniques like usability testing in order to create intuitive products that are successful in the marketplace. The document provides tips for design such as using established patterns while still allowing for innovation, and suggests reviewing requirements, designing, and testing iteratively with users.
This document discusses the importance of user experience and usability testing in website design. It defines usability as how easy user interfaces are to use, and notes there are five key components: learnability, efficiency, memorability, errors, and satisfaction. Early and frequent user testing is recommended to fix issues, test assumptions, and inform the design process. Examples of tasks and questions to use during testing are provided. The benefits of testing with real users and focusing on important fixes rather than minor issues are also outlined.
TDD and agile methods originated from attempts to manage large software projects more effectively. TDD involves writing automated tests before code to specify requirements and catch errors early. It helps avoid major redesigns later. Tests should fail initially and then code is written to pass the test, followed by refactoring. Patterns like starting simply, faking dependencies, and generalizing from examples help get code passing tests quickly. Pitfalls include not starting with a failing test or refactoring tests improperly. The session covered TDD history and techniques, with examples and opportunities for further learning.
The document discusses best practices for developing enterprise software using PHP. It recommends using frameworks to provide structure, conventions, testing and other supporting functionality. Rolling your own framework is not advised. Frameworks should be chosen carefully based on their age, flexibility and ability to integrate. The document also stresses the importance of code conventions, version control, bug tracking, formal design/specs, security practices, separating concerns, and hiring a team with the right mix of skills like programming, testing and design. Lessons learned include properly scoping the project, educating all team members, prioritizing testers, valuing designers, and accepting that software takes a long time to develop properly.
This document discusses various methods for conducting UX research for startups, including contextual inquiries, surveys, focus groups, card sorts, usability studies, and A/B testing. It also discusses crowdsourcing options like Usabilla, CrazyEgg, and Amazon Mechanical Turk. Game mechanics and flow theory are covered as ways to track user satisfaction. The concept of Net Promoter Score is introduced for measuring user recommendation likelihood.
The document provides information about conducting usability testing. It discusses what usability testing involves, including setting tasks for test participants and noting any problems they encounter. It provides tips for testing, such as teaming up with a partner, selecting 3-5 test participants, having them complete 2-3 tasks in 30-50 minutes, and one person acting as note-taker and moderator. The document also discusses how to find participants, what to tell them, questions to ask as moderator, common testing errors to avoid, and metrics to capture like completion rates, time on task, errors and satisfaction.
Conducting Usability Research with a Team of One [Revised: October 2009]cmk22
The document summarizes how to conduct usability research with a limited budget and team. It describes how the author conducted pre- and post-redesign usability research for a university website redesign project with minimal funding and assistance. Key hurdles included limited time, manpower, budget, and supervisor buy-in. The author overcame these hurdles by testing users during lunch breaks, using free tools, asking for donations, and illustrating the value of testing to gain support.
Build The Right Thing With The RITE Method | Rapid Usability TestingKyle Soucy
How can you test your designs faster and more cheaply?
How do you gain valuable user experience insights from one test subject?
To answer these questions and more, CTUXPA is proud to introduce Kyle Soucy from Usable Interface, who will take us through what's involved in rapid turnaround testing (aka RITE—Rapid Iterative Testing & Evaluation).
You’ll learn:
how to utilize RITE to test quickly and cheaply
how to evaluate your test results to iterate to your next solution
how to conduct a through observer debrief and report findings quickly
Let’s face it; while moderating a usability test or research study even the most experienced UX researcher can get sloppy and make mistakes. Sharing our mistakes and what we’ve learned from them is one of the best ways we can foster growth in this community. Over the last 13 years in this industry, I’ve moderated 100+ research studies and, more importantly, I’ve made a lot of mistakes and learned from them. I invite you to come and learn from my own moderating mistakes and possibly share some of your own during this fun and interactive session!
Exploratory testing is an approach to testing that emphasizes the freedom and responsibility of testers to continually optimize the value of their work. It is the process of three mutually supportive activities done in parallel: learning, test design, and test execution. With skill and practice, exploratory testers typically uncover an order of magnitude more problems than when the same amount of effort is spent on procedurally scripted testing. All testers conduct exploratory testing in one way or another, but few know how to do it systematically to obtain the greatest benefits. Even fewer can articulate the process. Jon Bach looks at specific heuristics and techniques of exploratory testing that will help you get the most from this highly productive approach. Jon focuses on the skills and dynamics of exploratory testing, and how it can be combined with scripted approaches.
Content Strategy and Product Management (in science education)Roger Hart
Presentation from Content Strategy Applied 2017
When your product is mostly content, product management looks a lot like content strategy. The Royal Society of Chemistry is an academic publisher, and a major provider of educational resources for schools and teachers. So that's certainly true here. Having worked in content strategy and product management, and now helping the RSC develop its product management function, I'll talk about how the disciplines interact.
We'll cover:
- What makes a good strategy, and what it means to be a product
- Innovation, roadmapping, and thinking about services
- Measurement and value when your goals are both charitable and commercial
Usability testing tips for UX DesignersDavid Hamill
This document provides tips for usability testing from a usability specialist at Skyscanner. Some key tips include:
- Conduct small, frequent usability tests with around 6 participants rather than large lab studies
- There is no single best way to do usability testing and you have to sacrifice aspects of the process
- Remember that participants are not like real users in the way they will use the product
- Expect that the initial design will have problems and be prepared to iterate based on test findings
1. This document provides instructions for conducting a usability test of a selected website as part of a web design course assignment. Students are instructed to identify key user tasks, generate scenarios and questions to test 3 of those tasks, find a user to test, and record and submit the test and a reflection.
2. The purpose is to help students identify problem areas on the website to inform their redesign project. Students will be graded on the thoughtfulness of their test, video quality, and reflection analysis.
3. The document includes sample scripts for introducing and conducting the test, which involves getting background on the user, having them explore the site, then working through the 3 scenarios while thinking aloud.
Expecting the Unexpected: Preparing for Successful User Research Sessions (Do...Fiona Tranquada
The document discusses how to prepare for successful user research sessions by anticipating and planning for unexpected situations. It recommends identifying potential issues before a study, such as participants being late or unable to complete tasks. The authors advise establishing backup plans, like scheduling extra participants or creating paper surveys. They also suggest preparing the product, space, and technology to avoid technical problems. Guidelines are provided for briefing participants and observers. The document stresses practicing moderating skills and technical setups to improve sessions. The overall message is that thorough preparation can help user researchers successfully handle unexpected challenges during studies.
You're a pig, but they call you chicken: How to co-opt the Agile methodology ...Jonathan Abbett
Our frustrations as designers about Agile have tended to reinforce our position as outsiders. In reality, we're unusually well-suited to lead Agile software teams, because we're trained to address Agile's biggest blind spot: How do you create a VIABLE PRODUCT on a SCHEDULE and on a BUDGET?
Presented at UX Boston Conference #2 on November 17, 2014
http://www.meetup.com/uxboston/events/192315552/
How do we bake user experience into the Agile process? We'll focus on three areas:
1. OWN THE PRODUCT BACKLOG
2. REDEFINE THE DEFINITION OF DONE
3. GET SKIN IN THE GAME
The usability testing document discusses various methods for conducting usability testing, including remote screen sharing, recording user interactions, and analyzing task completion times, errors, and user feedback. It describes card sorting, task elicitation, and enhanced analytics as alternatives if an evaluator prefers machines over people. The document also provides recommendations for open-ended questioning, eye tracking, and using prototypes during testing. Overall, the summary emphasizes different approaches to usability testing and gaining user feedback.
First users: Heuristics for designer/developer collaborationJonathan Abbett
From the University of Illinois Web Conference 2013.
Ask a web designer who his “first users” are, and he’ll probably name early adopters, stakeholders, or usability testers. Designers rarely consider their actual first users: the web developers they work with to build their designs. Over the last year, I’ve performed an informal user research project where the “users” were software development teams of all shapes and sizes. Drawing on these discussions and my background as a former web developer, I’ve created a set of friendly heuristics (in the tradition of Jakob Nielsen and Louis Rosenfeld) that designers can use to make their design materials far more useful for developers. I’ll show how these heuristics will encourage holistic solutions rather than piecemeal design work, surface critical implementation issues sooner, and establish a stronger basis for designer/developer collaboration.
DIY UX: Give Your Users an Upgrade (Without Calling In a Pro)Whitney Hess
Have you fallen in love with your solution and forgotten the original problem? Are you certain that your product actually makes people’s lives better? Not every company can hire someone like me to help you listen to your users, so you’re gonna have to learn how to do some of this stuff yourself. I’ll show you techniques to find out who your users are, what they really need and how to go about giving it to them in an easy to use and pleasurable way. And it doesn’t have to bankrupt you or kill your release date.
The document provides a quick overview of human-computer interaction (HCI). It discusses who users are, what constitutes a user interface, the importance of usability, and why good usability and designing user interfaces is difficult. Key challenges include understanding users and their tasks, creating prototypes and iterating designs based on user testing, and analyzing systems to evaluate usability. HCI methods like contextual inquiry, prototyping, iterative design, and usability testing are recommended to develop systems with high usability.
TDD and agile methods originated from attempts to manage large software projects more effectively. TDD involves writing automated tests before code to specify requirements and catch errors early. It helps avoid major redesigns later. Tests should fail initially and then code is written to pass the test, followed by refactoring. Patterns like starting simply, faking dependencies, and generalizing from examples help get code passing tests quickly. Pitfalls include not starting with a failing test or refactoring tests improperly. The session covered TDD history and techniques, with examples and opportunities for further learning.
The document discusses best practices for developing enterprise software using PHP. It recommends using frameworks to provide structure, conventions, testing and other supporting functionality. Rolling your own framework is not advised. Frameworks should be chosen carefully based on their age, flexibility and ability to integrate. The document also stresses the importance of code conventions, version control, bug tracking, formal design/specs, security practices, separating concerns, and hiring a team with the right mix of skills like programming, testing and design. Lessons learned include properly scoping the project, educating all team members, prioritizing testers, valuing designers, and accepting that software takes a long time to develop properly.
This document discusses various methods for conducting UX research for startups, including contextual inquiries, surveys, focus groups, card sorts, usability studies, and A/B testing. It also discusses crowdsourcing options like Usabilla, CrazyEgg, and Amazon Mechanical Turk. Game mechanics and flow theory are covered as ways to track user satisfaction. The concept of Net Promoter Score is introduced for measuring user recommendation likelihood.
The document provides information about conducting usability testing. It discusses what usability testing involves, including setting tasks for test participants and noting any problems they encounter. It provides tips for testing, such as teaming up with a partner, selecting 3-5 test participants, having them complete 2-3 tasks in 30-50 minutes, and one person acting as note-taker and moderator. The document also discusses how to find participants, what to tell them, questions to ask as moderator, common testing errors to avoid, and metrics to capture like completion rates, time on task, errors and satisfaction.
Conducting Usability Research with a Team of One [Revised: October 2009]cmk22
The document summarizes how to conduct usability research with a limited budget and team. It describes how the author conducted pre- and post-redesign usability research for a university website redesign project with minimal funding and assistance. Key hurdles included limited time, manpower, budget, and supervisor buy-in. The author overcame these hurdles by testing users during lunch breaks, using free tools, asking for donations, and illustrating the value of testing to gain support.
Build The Right Thing With The RITE Method | Rapid Usability TestingKyle Soucy
How can you test your designs faster and more cheaply?
How do you gain valuable user experience insights from one test subject?
To answer these questions and more, CTUXPA is proud to introduce Kyle Soucy from Usable Interface, who will take us through what's involved in rapid turnaround testing (aka RITE—Rapid Iterative Testing & Evaluation).
You’ll learn:
how to utilize RITE to test quickly and cheaply
how to evaluate your test results to iterate to your next solution
how to conduct a through observer debrief and report findings quickly
Let’s face it; while moderating a usability test or research study even the most experienced UX researcher can get sloppy and make mistakes. Sharing our mistakes and what we’ve learned from them is one of the best ways we can foster growth in this community. Over the last 13 years in this industry, I’ve moderated 100+ research studies and, more importantly, I’ve made a lot of mistakes and learned from them. I invite you to come and learn from my own moderating mistakes and possibly share some of your own during this fun and interactive session!
Exploratory testing is an approach to testing that emphasizes the freedom and responsibility of testers to continually optimize the value of their work. It is the process of three mutually supportive activities done in parallel: learning, test design, and test execution. With skill and practice, exploratory testers typically uncover an order of magnitude more problems than when the same amount of effort is spent on procedurally scripted testing. All testers conduct exploratory testing in one way or another, but few know how to do it systematically to obtain the greatest benefits. Even fewer can articulate the process. Jon Bach looks at specific heuristics and techniques of exploratory testing that will help you get the most from this highly productive approach. Jon focuses on the skills and dynamics of exploratory testing, and how it can be combined with scripted approaches.
Content Strategy and Product Management (in science education)Roger Hart
Presentation from Content Strategy Applied 2017
When your product is mostly content, product management looks a lot like content strategy. The Royal Society of Chemistry is an academic publisher, and a major provider of educational resources for schools and teachers. So that's certainly true here. Having worked in content strategy and product management, and now helping the RSC develop its product management function, I'll talk about how the disciplines interact.
We'll cover:
- What makes a good strategy, and what it means to be a product
- Innovation, roadmapping, and thinking about services
- Measurement and value when your goals are both charitable and commercial
Usability testing tips for UX DesignersDavid Hamill
This document provides tips for usability testing from a usability specialist at Skyscanner. Some key tips include:
- Conduct small, frequent usability tests with around 6 participants rather than large lab studies
- There is no single best way to do usability testing and you have to sacrifice aspects of the process
- Remember that participants are not like real users in the way they will use the product
- Expect that the initial design will have problems and be prepared to iterate based on test findings
1. This document provides instructions for conducting a usability test of a selected website as part of a web design course assignment. Students are instructed to identify key user tasks, generate scenarios and questions to test 3 of those tasks, find a user to test, and record and submit the test and a reflection.
2. The purpose is to help students identify problem areas on the website to inform their redesign project. Students will be graded on the thoughtfulness of their test, video quality, and reflection analysis.
3. The document includes sample scripts for introducing and conducting the test, which involves getting background on the user, having them explore the site, then working through the 3 scenarios while thinking aloud.
Expecting the Unexpected: Preparing for Successful User Research Sessions (Do...Fiona Tranquada
The document discusses how to prepare for successful user research sessions by anticipating and planning for unexpected situations. It recommends identifying potential issues before a study, such as participants being late or unable to complete tasks. The authors advise establishing backup plans, like scheduling extra participants or creating paper surveys. They also suggest preparing the product, space, and technology to avoid technical problems. Guidelines are provided for briefing participants and observers. The document stresses practicing moderating skills and technical setups to improve sessions. The overall message is that thorough preparation can help user researchers successfully handle unexpected challenges during studies.
You're a pig, but they call you chicken: How to co-opt the Agile methodology ...Jonathan Abbett
Our frustrations as designers about Agile have tended to reinforce our position as outsiders. In reality, we're unusually well-suited to lead Agile software teams, because we're trained to address Agile's biggest blind spot: How do you create a VIABLE PRODUCT on a SCHEDULE and on a BUDGET?
Presented at UX Boston Conference #2 on November 17, 2014
http://www.meetup.com/uxboston/events/192315552/
How do we bake user experience into the Agile process? We'll focus on three areas:
1. OWN THE PRODUCT BACKLOG
2. REDEFINE THE DEFINITION OF DONE
3. GET SKIN IN THE GAME
The usability testing document discusses various methods for conducting usability testing, including remote screen sharing, recording user interactions, and analyzing task completion times, errors, and user feedback. It describes card sorting, task elicitation, and enhanced analytics as alternatives if an evaluator prefers machines over people. The document also provides recommendations for open-ended questioning, eye tracking, and using prototypes during testing. Overall, the summary emphasizes different approaches to usability testing and gaining user feedback.
First users: Heuristics for designer/developer collaborationJonathan Abbett
From the University of Illinois Web Conference 2013.
Ask a web designer who his “first users” are, and he’ll probably name early adopters, stakeholders, or usability testers. Designers rarely consider their actual first users: the web developers they work with to build their designs. Over the last year, I’ve performed an informal user research project where the “users” were software development teams of all shapes and sizes. Drawing on these discussions and my background as a former web developer, I’ve created a set of friendly heuristics (in the tradition of Jakob Nielsen and Louis Rosenfeld) that designers can use to make their design materials far more useful for developers. I’ll show how these heuristics will encourage holistic solutions rather than piecemeal design work, surface critical implementation issues sooner, and establish a stronger basis for designer/developer collaboration.
DIY UX: Give Your Users an Upgrade (Without Calling In a Pro)Whitney Hess
Have you fallen in love with your solution and forgotten the original problem? Are you certain that your product actually makes people’s lives better? Not every company can hire someone like me to help you listen to your users, so you’re gonna have to learn how to do some of this stuff yourself. I’ll show you techniques to find out who your users are, what they really need and how to go about giving it to them in an easy to use and pleasurable way. And it doesn’t have to bankrupt you or kill your release date.
The document provides a quick overview of human-computer interaction (HCI). It discusses who users are, what constitutes a user interface, the importance of usability, and why good usability and designing user interfaces is difficult. Key challenges include understanding users and their tasks, creating prototypes and iterating designs based on user testing, and analyzing systems to evaluate usability. HCI methods like contextual inquiry, prototyping, iterative design, and usability testing are recommended to develop systems with high usability.
This document discusses UX prototyping and personas as essential tools for creating great user experiences. It provides an overview of different prototyping methods like paper prototyping, digital tools like Balsamiq and Fireworks, and the benefits of each. It also covers what personas are, how to develop them, and how prototyping can be improved by focusing on specific persona goals and needs. The document encourages prototyping as early as possible using whatever tools are available and provides various activities to prototype interfaces using different methods.
WORKSHOP: Making the World Easier with Interaction DesignCheryl Platz
Interaction designers aim to make technology intuitive and easy to use. Their goal is to prevent user frustration by ensuring products function as expected. The presentation discusses interaction design through an example of redesigning a microwave user interface. It encourages brainstorming ideas, sketching prototypes, and testing designs with others. The key is an iterative process of researching user needs, exploring solutions, testing, and refining designs.
This document discusses strategies for handling non-ideal testing situations when adopting agile practices. It addresses problems like lack of test automation, test data issues, legacy reporting needs, geographic distribution of teams, and separation of testers and programmers. The proposed solutions generally involve starting small, using technology to facilitate remote collaboration, targeting important information in reports, and developing relationships between team members.
Faster Usability Testing in an Agile World presented at Agile2011Carol Smith
The sheer speed of an Agile project can be frightening to even the most experienced UX practitioner. This talk covers testing in short, quick, repetitive sessions, without sacrificing quality. The presentation covers strategies and techniques that can be used for speeding up traditional usability testing, on-site, remote and Rapid Iterative Testing and Evaluation (RITE) methods. Topics from planning through analysis, and ways to provide useful and usable recommendations to the team will be covered.
This document discusses important developer disciplines for software development. It begins by introducing the author, Chris Howe-Jones, and his background. It then discusses the complex, multi-disciplinary nature of software development teams and environments. The rest of the document outlines various important developer disciplines like test-driven development, version control, continuous integration, refactoring, design principles and more. It emphasizes the importance of testing in many forms. Overall, the document provides an overview of technical and process disciplines that are important for developers to know.
Introduction to Prototyping - Scottish UPA - June 2011Neil Allison
Presented to the Scottish Usability Professionals Association, Edinburgh, 22 June 2011.
Covering the basics, the benefits, some tools, some tips and a case study.
Design your Modern Intranet using SharePoint PnP Design Assets D'arce Hess
Presentation given at SharePoint Saturday Ottawa. Presentation go over basic design concepts and how to apply them to new designs and concepts in SharePoint
This presentation provides guidance for novice testers on creating a portfolio to demonstrate their skills and experience to potential employers. It recommends including examples of bugs found, technologies tested, and test designs. Open source and crowdsourced testing are suggested as ways to gain experience without a testing job by contributing to projects on sites like SourceForge and uTest. Guidelines are provided on selecting projects, reading documentation, testing, reporting bugs, and following up to learn. Testers are encouraged to think about and document their testing processes.
This document provides guidance on conducting a usability study. It outlines the schedule, expectations for participants, and guidelines for running test sessions. Participants will be divided into groups of 3, with one person acting as the user and two observing. As a user, they will complete tasks while thinking aloud, and observers will take notes on successes, obstacles, and areas of confusion. After each task the group will switch roles. The goal is to evaluate the design and identify ways to improve the user experience.
This document provides an introduction to test-driven development (TDD), including its goals, benefits, and challenges. TDD is an iterative, test-first approach to development where functionality and behavior are defined by tests. Tests are written before code and define the desired API and design. Benefits of TDD include reduced defects, increased initial development time, and easier refactoring and collaboration. Adopting TDD requires practice and a focus on good design principles like separation of concerns.
The document discusses reasons for starting a startup, different startup approaches, and issues with default ASP.NET MVC projects. It promotes ShoelaceMVC as a starter project that addresses common problems. It also provides resources for hosting, source control, analytics and billing for startups.
There are many types of automatic tests, testing tools, libraries and approaches.
Automatic tests can save you a lot of stress but can also became a kind of a nightmare.
This presentation is an overview of what's available and how to use and not to use them to make them really useful.
Examples taken from PHP world. You might be surprised how many tools is available.
Remote Research Workshop, UX Week 2012 - Cyd HarrellCyd Harrell
The document discusses remote user research tools and techniques, focusing on both moderated and unmoderated remote studies. It provides examples of tools for remote moderated research like GoToMeeting as well as unmoderated automated tools like Usabilla. The presenters provide advice on best practices for remote user research including recruiting, study design, note taking, and overcoming challenges with remote methods.
This document discusses various prototyping tools and techniques for creating user experiences, including paper prototyping, Balsamiq, PowerPoint/Keynote, Fireworks, and HTML/CSS. It emphasizes that prototyping should start as early as possible, and that the goal is to test assumptions and explore ideas through usability testing. Personas are also presented as a way to represent different user types and focus the prototype design. A variety of prototyping activities are suggested to allow readers to experiment with different tools.
Using Prototyping to Streamline the Instructional Design ProcessLisa Whalen
Prototyping allows instructional designers to streamline the design process by creating early versions of parts of an elearning project to test design concepts and functionality before building out the full project. This allows designers to receive feedback and make revisions early in the process rather than late in the project timeline. Prototyping can improve estimates, encourage creativity, incorporate feedback flexibly, and integrate quality assurance testing more seamlessly. The presenter provides examples of how prototyping can shorten timelines and relieve end-of-project pressure compared to developing a full project without prototyping. Steps for prototyping include creating micro and full prototypes to obtain approvals before full replication.
"Open" includes users - Leverage their inputRandy Earl
This document discusses various user research methods that can be used to improve open source software and ensure diversity. It begins by explaining the importance of intentionally including a diverse user base to drive innovation. It then provides an overview of common user research methods such as interviews, usability testing, card sorting, and analytics reviews. Specific examples are given around label testing and task-based navigation that resulted in improved user experiences and outcomes. The overall message is that proactively involving and understanding users is critical for the success of any software, including open source projects.
Similar to Creating a Lawyer in a Box: Building User Friendly Guided Interviews with Docassemble (20)
Sangyun Lee, 'Why Korea's Merger Control Occasionally Fails: A Public Choice ...Sangyun Lee
Presentation slides for a session held on June 4, 2024, at Kyoto University. This presentation is based on the presenter’s recent paper, coauthored with Hwang Lee, Professor, Korea University, with the same title, published in the Journal of Business Administration & Law, Volume 34, No. 2 (April 2024). The paper, written in Korean, is available at <https://shorturl.at/GCWcI>.
सुप्रीम कोर्ट ने यह भी माना था कि मजिस्ट्रेट का यह कर्तव्य है कि वह सुनिश्चित करे कि अधिकारी पीएमएलए के तहत निर्धारित प्रक्रिया के साथ-साथ संवैधानिक सुरक्षा उपायों का भी उचित रूप से पालन करें।
Business law for the students of undergraduate level. The presentation contains the summary of all the chapters under the syllabus of State University, Contract Act, Sale of Goods Act, Negotiable Instrument Act, Partnership Act, Limited Liability Act, Consumer Protection Act.
Pedal to the Court Understanding Your Rights after a Cycling Collision.pdfSunsetWestLegalGroup
The immediate step is an intelligent choice; don’t procrastinate. In the aftermath of the crash, taking care of yourself and taking quick steps can help you protect yourself from significant injuries. Make sure that you have collected the essential data and information.
Corporate Governance : Scope and Legal Frameworkdevaki57
CORPORATE GOVERNANCE
MEANING
Corporate Governance refers to the way in which companies are governed and to what purpose. It identifies who has power and accountability, and who makes decisions. It is, in essence, a toolkit that enables management and the board to deal more effectively with the challenges of running a company.
The Future of Criminal Defense Lawyer in India.pdfveteranlegal
https://veteranlegal.in/defense-lawyer-in-india/ | Criminal defense Lawyer in India has always been a vital aspect of the country's legal system. As defenders of justice, criminal Defense Lawyer play a critical role in ensuring that individuals accused of crimes receive a fair trial and that their constitutional rights are protected. As India evolves socially, economically, and technologically, the role and future of criminal Defense Lawyer are also undergoing significant changes. This comprehensive blog explores the current landscape, challenges, technological advancements, and prospects for criminal Defense Lawyer in India.
Creating a Lawyer in a Box: Building User Friendly Guided Interviews with Docassemble
1. CREATING A LAWYER IN A
BOX: BUILDING USER-
FRIENDLY INTERVIEWS WITH
DOCASSEMBLE
Quinten Steenhuis, Greater
Boston Legal Services
@QSteenhuis /
nonprofittechy.com
2. OVERVIEW
Who am I?
What I learned after a year of using Docassemble
Demo
Questions (and interrupt at any time)
6. 7 PRINCIPLES FOR SMART GUIDED
INTERVIEWS
“Dumb” forms are not worth the work
Ask users to state facts, not conclusions
Use visuals
Do the work for the user
Get it right or don’t automate
Give help in context
Test, test, test and iterate, iterate, iterate
16. THOUGHTS FOR DOCASSEMBLE
Fail earlier
Automated testing/fuzzing
Test individual questions (without logic) to just check if the display
code is right
Separating legal rules from interview logic with DMN or other logic-
modelling language
17. MORE INFORMATION
Fork us on GitHub
@Nonprofittechy @GBLSMA https://github.com/GBLSMA/docassemble-
MAEvictionDefense
Docassemble Tutorial at
https://gblsma.github.io/docassemble-MotionTutorial/
or http://bit.ly/2DKyZby
Docassemble Template Builder
https://github.com/GBLS/docassemble-template-builder-addin or
https://bit.ly/2t9fQwW
Nonprofittechy.com @QSteenhuis