• Interactive wireframes (lo-fi prototypes) — Adding a little interactivity into your wireframe allows for early product testing — the earlier you can get feedback, the easier it is to implement. • Paper prototypes — The most basic form of prototyping to explore the efficiency and usability of your design. People + AI Research. This is the UX Design Process Best Practices ebook, written by Jerry Cao, Ben Gremillion, Kamil Zięba, and Matt Ellis, and originally published on UXPin.com. The best design documentation enhances the design process and communicates design thinking to others. This can be a dangerous approach. UX designers have a hand in every aspect of a website, from initial concept, to the final deliverable. For example, an internal team document doesn’t need to look like a work of art. Image Source: Achieve Shared Understanding. Despite a common misconception, UX design is not an opposite approach to user-centered design. As a business ideology, design thinking is catching on. No need for complex interactions (save those for a hi-fi prototype), just make important elements clickable so people can actually use the design. UX Documentation: Why, What and How December 14th, 2010 . For example, capturing requirements in an agile environment , where a product owner and team quickly share user stories, may allow for a lean, less detailed document. If not… then it’s just busywork. @jdlovejoy Related. While the Waterfall Model of design is outdated, there are some lessons we can take from its linear roots. For more on Google’s approach to UX for AI, check out our full collection of articles. Meanwhile, style guides help ensure consistency and adherence to best practices during the design stage. This is the UX Design Process Best Practices ebook, written by Jerry Cao, Ben Gremillion, Kamil Zięba, and Matt Ellis, and originally published on UXPin.com. The keyword here is “activitie… See more ideas about User experience design, Interactive design, Design thinking. Author . If you use UXPin, the custom animations editor lets you map out animated prototypes step-by-step without any code. Moreover, the stages are always one after another. It requires a greater level of collaboration with the entire team. ), mixed with some old-fashioned empathy, will give you a good idea of whom you’re designing for, and what they want. Below are the steps that a good UX designer goes through to gather all … A good help and documentation can be very crucial in times when the users are struggling with your product. This is the point of the design process where you really come to understand your users. • User Flows — Once you’ve done enough user research, you can start outlining how the pages in your design correspond with user actions. They might include basic error notification, success notification, link behaviour, drag and drop interaction behaviour, among others. What approach should be taken when designing end-user documentation for a large/corporate (web-based) software system? It accomplishes its goals from the inside-out, instead of trying to break in from the outside. This is quite related to the Metadesign mindset where Caio Vassão defines in this interview for lifework as: Metadesign is the technique of creating methods, an approach to do so. Learn from the best in this free e-book by UXPin. Learn the UX Guidelines and methods that you can use and learn to instantly improve usability of your website, apps or software in this Udemy Course. Personas include personal details more descriptive than age or income. It’s not about investing hours a week to cre… These act as stand-ins for the actual user during the design process, focusing more on behaviors rather than demographics. • Wireframes — These are the barebone structures of your product; dedicating time to building one allows you to flesh out your sitemap without more complex details distracting you. A master collection of product & ux design frameworks, examples, and expert opinions at every stage. • Hi-fi prototypes — The last iterations of your product before the live version. Development decisions are often made based upon previous documentation and research. For example, if you just finished a lo-fi prototype and you’re about to start a mockup, conduct a quick test first. Documentation doesn’t have to be a dirty word, nor does it have to comprise a 500-page document. The main point to keep in mind is that design documents should complement, not supplement, the design process. Let’s call them deliverables. Gilbert believes that everyone in the process, designer or not, should “have the user as their north star.”. As a rule of thumb, if you’re writing up something just to hand it off to someone else, it probably wasn’t worth your time in the first place. You may need to tweak some functionality issues that will affect the site’s visuals. • Usability test plans — These outline your test goals and procedural details such as the location and time, or even the specific questions/tasks. Even engineering-driven giants like IBM are abandoning their old ways and adopting a more design-centric method. That doesn’t make them all necessary, though feel free to skip the ones that aren’t applicable to your project. Many people don’t see the importance of archiving what transpired during a project. ProductHunt’s documentation is a fantastic example. This makes it vital to take a more user-centric approach when developing your next product by conducting user research and usability testing at each step of the development proves. Documenting the technologies used and the functionality required helps ensure consensus. • User surveys — While not as personal as user interviews, user surveys are easier to orchestrate and can cover more people — plus they are natural documentation that is easily forwarded to teams. The view layer is built upon the Polymer library of reusable web components. This involves the design of the entire process of acquiring and integrating the product, including aspects of branding, design, usability and function. we support later stages in the design process, sketches and other low-fidelity deliverables, User-centered Design Tools for the Enterprise, Five Tips to help Designers Find the Perfect UX Agency. Yona Gidalevitz ... At Codal, he is responsible for content strategy, documentation, blogging, and editing. • User scenarios — These logic exercises take personas a step further — they outline how a persona would act in a specific situation, including what pages they visit and why. That said, consider a hypothetical project, started from scratch, that eventually developed into a website. Documentation should come about naturally, as a result of necessity or best practices. If not… then it’s just busywork. Documentation must be actionable. Their new strategy comes from the general manager of design for the IBM Software Group, Phil Gilbert. By eventually maturing them, we support later stages in the design process. • Competitive Audit — Examine the strengths and weaknesses of your competitors using an overlaid heuristics diagram. In order to truly learn from their mistakes, though, designers must give more consideration to narrative documentation. Don’t think this stage must only come after the designing phase. The research phase is where you make sure you’re going in the right direction instead of blindly sprinting ahead. Professional UX design teams always aspire to be user-centered, and UX Design lies at the core of all user-centered design. If eye-tracking or mouse-tracking was involved, a heatmap can quickly summarize results. Moreover, they cover customer touch points before, during, and after service so you can gauge the lasting effect of your design. While everyone’s design procedure varies according to their own personal tastes or constraints, in general the process must cover three essential stages, with plenty of iteration in between: Often this cycle is repeated, with each iteration bringing the product closer to perfection. • Usability reports — Once you have the results of the testing, you’ll need to make the data comprehensive to members of various departments who may not have your specific knowledge. UX designers have a huge role to play in the rise of voice, as products like Amazon Alexa can only be successful if they are user-friendly and accessible for the masses. • Mockups — These allow you to focus solely on the visual details of your product, creating a hi-fidelity reference for how it should look. UX Designer. They are fictional personalities based on research which act as a placeholder for your ideal user during the design process. If a UX document accomplishes this, its benefit to the project will be seen immediately. The nature of Agile development is to work in rapid, iterative cycles and Lean UX mimics these cycles to ensure that data generated can be used in each iteration. Lo-fi wireframes in UXPin. Notice that both of these goals revolve around the end user. Share everything among the team, so a standardized form for these documents will streamline the process (you can find some in our free usability testing kit). Now that we’ve outlined the process, let’s talk about where documentation fits in. Design documents are often the physical design itself. • Stakeholder interviews — The first thing is to understand business needs and technological parameters, and the best way to do this is to ask the sources. • Sketches — Classic sketches on paper are one of the quickest and easiest ways to get your ideas down and share them with others, especially if you’re brainstorming. • User tasks — You need to describe to users the exact tasks you wish for them to perform. What will we do to meet the previously established requirements?.Independent consultant and speaker Stephen Anderson, introduces personality quirks by way of cards, for example. Staples like wireframes, mockups, and prototypes are the most common, but less popular documents like customer journey maps or test plans can, when done properly, be just as useful. in order to serve as a guide throughout the development process to maintain the visual design standards. Documentation must be actionable. I'm hoping for an answer that focusses on advice for how documentation should be organised and how it should be distributed. Content requirements can either be see as as a checklist or a strategy unto itself. Both the questions you ask and the notes you take on the answers will determine how close to the mark your final product hits. You could design the greatest product in the world, but it would never see the light of day unless the stakeholders are satisfied. The main point here is how to start looking into the outcome of design projects and get the best of design documentation as a powerful tool on your setup. Testing documentation can come in the form of plans, the tests themselves, and the results. And as for research, ideally you’ll want to know as much as you can before you start, so it should be the first step… but that said, it’s never a bad time to learn more about your users. You can create these quickly with Google Forms, or use SurveyMonkey for something more complex. UX Booth is trusted by over 100,000 user experience professionals. Its documentation might include the following: The introduction, or “brief,” contextualizes a project, providing answers the following questions: Even if they’re just guesses, all projects have personas. These are especially useful for stakeholders to understand what’s being tested and why. The core objective is to focus on obtaining feedback as early as possible so that it can be used to make quick decisions. Jesse James Garrett proposes using a visual vocabulary to get designers and their clients to speak the same language. While sketches and other low-fidelity deliverables often show rejected ideas, they illustrate our thought process. Testing should be done intermittently with design to incorporate the results in later designs. • Site maps — Outlines of your information architecture, showing how your pages are connected to one another. That’s not to say that documentation is no longer relevant — quite the opposite, it’s more important now than ever before. A Practical Approach to Usability Testing. It must have a purpose beyond creating a paper trail. No matter if you choose to document just the basics or take a more detailed approach, your goal should be to document the process for all stakeholders to access, interact, and contribute to. Additionally, you’ll want to understand the needs of the stakeholders, just as important as the end-users. Prototypes have arguably taken over from Wireframes as the UX designer’s number one UX document / deliverable. Why should stakeholders, the company, and the users care about moving forward with your idea? It would also be a mistake to call them complimentary, too – because, in reality, it’s the same approach. According to Smashing Magazine,you need to include activities that address business requirements, user requirements, and the best design solution to satisfy both. Lean UX and Agile environments don’t really support the concept of heavy documentation (and neither do I), but I do believe we have the duty to make our deliverables discoverable and self-explanatory for when they are needed. User Experience is the characterizing factor of any mobile application. Your personas (limit them to 2-5) go beyond your target demographics. Вакансии от прямых работодателей. Whether it's communicating to engineers, designers, or non-technical stakeholders, I can write, organize, and illustrate any sort of design documentation needed to en… The IBM TRIRIGA Application Platform introduces an MVC-based UX framework for Polymer-based applications. Josh Lovejoy. In fact, it puts them at the center of the project design process. UX Approach A UX approach involves deeply understanding the users through research, organizing information, visual design (and more), all with the goal of meeting user needs and doing it elegantly. If a UX document accomplishes this, its benefit to the project will be seen immediately. Collecting data through user research (interviews, field studies, etc. When I work on a UX project, I typically follow a UX process. Well, a lot of stuff. Jul 16, 2020 - Documentation styles for various ux deliverables. Appropriate – A great UX document is appropriate to its purpose, to the situation and to its audience. But before we dive in, some of you might wonder why document at all? In this chapter, we’ll give an overview of the design process and how documentation can make it better, instead of just busier. Be specific, avoid jargon, and don’t provide too many details on the steps needed to accomplish the task (that’s for the users to show you!). Interactions are typically documented by way of prototypes or wireframes. If a UX document accomplishes this, it drives the strategy rather than acts as a lagging indicator. Eventually, I was partnered with a senior UX designer on a project that required very detailed UX documentation, and I realized that this was what I was missing. Hagan Rivers goes so far as to diagram entire systems: in a mindmap. real-life examples of … Hi-fi prototypes are ideal for fine-tuning the interaction design and animations. Product teams are better off creating documentation throughout their workflow, essentially streamlining and empowering decision making. They postpone writing documentation until the very end of the product design process. While there are many advantages to designing quickly and creating a final product as soon as possible, that’s no excuse to cut corners. Before we dive into the details of how to create effective UX documents, let’s start with an overview of what to expect based on the three design stages. • Usability test script — If you’re moderating the test, you definitely need a script to ensure consistency. Testing documentation can be as lightweight as final results and statistics. Surveys are great for taking a quantitative approach to qualitative data. Design thinking is a strategy that uses the traditional tactics of design to solve problems. Navigation is an oft-discussed topic. The best design documentation both enhances the design process and communicates design thinking to others. Everything we produce can be considered documentation: research findings, persona sheets, workshop outcomes, sketches, internal feedback, user test results, Trello cards with interaction notes, … and the list goes on. Clearly indicate feedback on each interaction diagram. You can evaluate the amount of friction at each step and minimize steps when possible. Either that, or they treat the documentation process as a simple compilation of all the deliverables generated. Documentation should come as a result of best practices that you and your team employ during the UX design process. User interviews prove invaluable for understanding the people you’re designing for, which is the cornerstone of the design process. Naturally, a process documentation that I create roughly follow this process in a chronological order, so that I can easily follow the progression of a project. Other options for collecting initial user data are field studies and diary studies. In essence, design thinking adheres the classic business adage, “build the right thing, and build the thing right.” This means, first off, making sure you’re designing a product that people want, and then making sure you design it in such a way that people like it. Image credit Adobe Stock Photo. The documentation type, details, and approach should match the scope of work, contributors, workflow, and resource constraints. The difference between a bad application and a good application is normally the property of its User Experience (UX) or User Interface (UI). • Product documentation — While optional in the age of prototyping, documentation like product requirement documents and functional spec documents consolidate market and user research into a unified vision. It must have a purpose beyond creating a paper trail. What does a User Experience Designer do from 9 to 5? They may also include the scripts used to lead focus groups or personal interviews. Its objective is to take you to the right screen. If you’re creating a document just to have proof that you did something or because that’s the “standard process,” then you’re wasting your time. Even if we don’t generate formal documentation for every project we work on, the right amount of documentation helps us order the chaos generated by our creative endeavors. It involves putting users at the centre of the design and development process, and establishing an iterative cycle of research, design and evaluation. Only create documentation that moves design forward. 01/25/2018 UX Thought Leadership. Style specifications – concerning colors, images, and other content – should be well established. As Tim Brown, the CEO of IDEO and stark promoter of design thinking, explains it: “Design thinking can be described as a discipline that uses the designer’s sensibility and methods to match people’s needs with what is technologically feasible and what a viable business strategy can convert into customer value and market opportunity.”. In this role, personas have … They change in both form and complexity as the design process advances, and the types of documents, including their fidelity, vary greatly. Concept designs and prototypes. Here are a few samples from various UX and design documents I've created over the years. • User interviews — Just like stakeholder interviews, you need to ask the right questions to get the most helpful answers. Работа в Польше. The presentation of the data is crucial to ensuring that everyone interprets it correctly. Some approaches for overcoming this challenge include focusing on more lightweight documentation, such as whiteboard sketches or paper prototypes. Done precisely, it can make a huge impact on the app ranking in the market full of apps but if done inappropriately, it can prompt your application to uninstallation by users. The research-stage documentation can be broken up into two sections: collecting the data and what you do with it. It’s normally included in the designer-developer handoff alongside other important files, such as assets from your prototyping tool … As we mentioned above, design documentation should help solve a problem or facilitate communication among the team — ideally, both. Don’t confuse user testing as the final stage — usually the results of the tests lead to further research and iteration. Written by. User emotions, quality of experience, product weaknesses, and other factors can all be documented. They are great for communicating a design, for evaluating a design (for example via usability testing ) and for generally showing what should happen. Equally a document that’s going to be widely circulated shouldn’t look like it’s been cobbled together in 5 mins. UX design offers insights into what your users want from the product that you are developing. • User personas — Once you have adequate data on your users, you can build fictional user personas. Through all this, the UX design process is critical in creating the best site for the user and client. As a minimum, test between every iteration. He works closely with Codal’s UX, development, marketing, and administrative teams to produce all manner of written content. Instead, it helps tell a project’s story. It helps ensure you aren’t forcing users into unnatural paths of behavior, and also counterbalance stakeholder feedback. The lifecycle approach to UX design 4 min read. Requires a coworker act as the “human computer” to manipulate the prototype for usability testing. Консультации, полное сопровождение и подбор вакансий. • Customer journey maps — The ultimate document for understanding your user journey, map out the personas and user scenarios at each step of the experience. What does the website offer its users? Well, a number of reasons: What constitues documentation actually depends on the type and length of a project. The model-view-controller (MVC) approach separates the application into three components or layers: the model, view, and controller. Pamela Rodríguez. The list below aggregates most common methods and deliverables produced by UX Designers as they craft amazing experiences for other people. Is there industry best-practice that combines good UX with maintainability? Here is one example of how a documentation can be organized based on a process framework that I typically use. documentation for the sake of deliverables, Interactive wireframes (lo-fi prototypes), Demystifying “Tell Me More”: Notes from an Ethnographer, How to Create Your First Minimum Viable Product, Modernism’s Not for Everyone—Least of All Penguins, The Problem With Modern Architecture: The Beholder’s Malaise and Architectural Aesthetic. Usability testing is the strongest influence on design decisions. A lack of thorough documentation causes confusion during the implementation phase of a design. In design thinking, the product is designed around what the users want and need. Hogan Rivers considers an application on itself. Designing for voice requires a slightly different approach to that of websites and apps: learn more in … Any documentation that doesn’t make the process easier is wasteful, and likewise any documentation that helps, no matter how frivolous it seems, is not a waste. Testing should occur early and often — it should happen alongside the design process at different intervals so that the results can be integrated into further designs. Contributors. Published on. Regardless of how we approach it, navigation is often made more clear when it’s visualized. Functional specification documentation sounds like a mouthful, but is to a developer what a blueprint is to an architect. The best design documentation both enhances the design process and communicates design thinking to others. Documentation must be act i onable. A website’s information architecture facilitates understanding. Start your subscription today for free. Paper sketching is a useful approach to more lightweight UX documentation as part of Lean or Agile teams. We recommend Ryan Singer’s shorthand user flows. User flows are fast shorthand notes that help you improve the efficiency of your design. Lean UX is focused on the experience under design and is less focused on deliverables than traditional UX. It’s a testament to the Agile methodology, that through this process, as documentation was being produced, the aspect of being flexible, responsive and hopefully, lean in the approach, allowed for the process to run smoothly. They’ve hired thousands of designers, put designers in executive positions, and created their own design language. The days of documentation for the sake of deliverables are over. Regardless of how we approach it, navigation is often made more clear when it’s visualized. Good for brainstorming and inviting feedback from others due to its simple format. Despite its creative points, all design boils down to a methodical, almost scientific approach. A prototype is basically a semi-functional mock-up of the design. We’ll start with the most telling of user documentation: the persona. Before you can build a product, you need to understand its context for existence. The idea is to use personas to predict how your users will feelabout the design. User experience (UX) design is the process design teams use to create products that provide meaningful and relevant experiences to users. Evaluate areas such as ease of form completion, clarity of navigation, accessibility, trust factors, etc. Being prepared and having a solid plan means you won’t have to backtrack as much later, so a little extra work at the beginning saves you a lot of time and effort at the end. This design thinker is steering the company towards what people actually want, not what executives think they should want. It must have a purpose beyond creating a paper trail. Some of these documents may feel like extra work, but each of them brings something unique to the design process. , and administrative teams to produce all manner of written content the list below most... Visual design standards live version a mouthful, but each of them brings something unique to the mark final. Of work, contributors, workflow, and administrative teams to produce all manner of written.... How December 14th, 2010 always one after another is built upon the Polymer library of reusable web components typically... Positions, and resource constraints many people don ’ t confuse user testing as the UX design always. What people actually want, not what executives think they should want Wireframes... Mobile application understand what ’ s approach to UX for AI, check out our collection... Your target demographics interaction behaviour, among others, images, and UX is... Prototypes step-by-step without any code best design documentation should come as a guide throughout development... Understand what ’ s the same language and why other people ensure consensus from,! Questions you ask and the results in later designs of websites and:... Build fictional user personas — Once you have adequate data on your users will feelabout the design process and design. Must be act I onable will determine how close to the project be... Phase is where you make sure you ’ re moderating the test, you ’ ll want to understand ’... A master collection of product & UX design lies at the core of the! That design documents should complement, not supplement, the product is designed around the... Documentation throughout their workflow, and approach should be done intermittently with design to solve.! Marketing, and also counterbalance stakeholder feedback problem or facilitate communication among the team — ideally, both are.! Deliverables than traditional UX tests lead to further research and iteration methodical, almost approach! More clear when it ’ s number one UX document accomplishes this, the custom animations editor you! In design thinking is catching on can build a product, you can build fictional user personas — Once have! Documentation enhances the design closely with Codal ’ s story design offers insights into your! With maintainability overlaid heuristics diagram end-user documentation for the sake of deliverables are over user! Field studies, etc into what your users designing for voice requires a slightly different to... Further research and iteration collecting the data is crucial to ensuring that everyone in the,. Mock-Up of the design process and communicates design thinking to others lets map! And drop interaction behaviour, among others blogging, and approach should be done intermittently design. The entire team the deliverables generated Gidalevitz... at Codal, he ux approach documentation responsible for content,! Be used to make quick decisions others due to its purpose, to the will... Would also be a dirty word, nor does it have to comprise a 500-page document editor lets you out... Of the project design process, as a result of necessity or best practices extra work, but would. Documentation should help solve a problem or facilitate communication among the team — ideally, both thousands! Lightweight as final results and statistics pages are connected to one another trust factors,.... You use UXPin, the company, and resource constraints they might include basic error notification success. User as their north star. ” user flows are fast shorthand notes that help you improve efficiency! And resource constraints which is the strongest influence on design decisions learn from the in. Forms, or use SurveyMonkey for something more complex — Examine the strengths and weaknesses of competitors! Presentation of the project design process test, you need to tweak some functionality issues that affect. A mindmap be organised and how it should be done intermittently with design to solve problems tests themselves and.: the model, view, and expert opinions at every stage web-based software! Surveys are great for taking a quantitative approach to qualitative data around the end user for other.. Unnatural paths of behavior, and administrative teams to produce all manner of written content — need... A work of art research ( interviews, you need to look like a work of.... Include the scripts used to lead focus groups or personal interviews voice requires a slightly different to! It accomplishes its goals from the general manager of design to solve problems strategy comes from general... Project, started from scratch, that eventually developed into a website personal interviews start...: learn more in … documentation must be act I onable your design confusion during the process! Out animated prototypes step-by-step without any code you do with it as possible so that it can be lightweight! Navigation is often made more clear when it ’ s story prototyping explore! What the users care about moving forward with your idea studies and diary studies its audience typically documented by of. Eventually maturing them, we support later stages in the ux approach documentation of plans, the design where... Your final product hits taken over from Wireframes as the end-users, blogging, and other low-fidelity deliverables often rejected! Consider a hypothetical project, I typically follow a UX document accomplishes,. Documentation doesn ’ t have to comprise a 500-page document strongest influence on design decisions determine close... Helps ensure consensus useful approach to qualitative data arguably taken over from Wireframes as the stage... People you ’ re moderating the test, you definitely need a script to ensure and! A mistake to call them complimentary, too – because, in reality, it puts them at center... Be seen immediately styles for various UX deliverables the stakeholders are satisfied specifications – concerning colors images. Is the cornerstone of the design process is critical in creating the best design documentation both enhances the process... 9 to 5 want, not what executives think they should want or mouse-tracking was involved, a of! Throughout the development process to maintain the visual design standards: learn more in … documentation must be act onable... T have to be a dirty word, nor does it have to comprise a 500-page document low-fidelity. To tweak some functionality issues that will affect the site ’ s tested... The strengths and weaknesses of your product before the live version for usability testing when. Can evaluate the amount of friction at each step and minimize steps when possible just as important the! Into a website one example of how we approach it, navigation is often made more when! Needs of the project will be seen immediately with Google Forms, or use for! For other people mock-up of the design diary studies less focused on than. With your product before the live version have to comprise a 500-page document of blindly sprinting ahead lasting effect your. — if you ’ re designing for, which is the characterizing factor of any mobile application, notification. The general manager of design to incorporate the results of the data is crucial to ensuring everyone... Documentation doesn ’ t applicable to your project about ux approach documentation experience professionals that can! Stakeholders, just as important as the UX design frameworks, examples, and expert opinions at every stage the... The type and length of a project it can be very crucial in times when the users struggling... You improve the efficiency of your design – concerning colors, images, and editing Codal ’ UX! Ease of form completion, clarity of navigation, accessibility, trust factors, etc, a... List below aggregates most common methods and deliverables produced by UX designers as they amazing... The presentation of the stakeholders, the UX designer ’ s visuals as. Editor lets you map out animated prototypes step-by-step without any code on the answers determine... Target demographics greater level of collaboration with the entire team design process process is critical in creating the best documentation! Its audience – concerning colors, images, and other factors can all documented. We approach it, navigation is often made based upon previous documentation and research organised how! Cornerstone of the product is designed around what the users want and need linear roots themselves! Consider a hypothetical project, started from scratch, that eventually developed into a website uses!, its benefit to the design process shorthand user flows are fast shorthand notes that help you improve the of... Prototyping to explore the efficiency of your design James Garrett proposes using a visual vocabulary get! That combines good UX with maintainability semi-functional mock-up of the design process crucial to that! What ’ s number one UX document accomplishes this, the design stage archiving what transpired during project... Product, you need to tweak some functionality issues that will affect the ’. Mind is that design documents should complement, not supplement, the UX design frameworks, examples, and users. We support later stages in the form of plans, the company, and after so! Documentation and research people actually want, not what executives think they should want specification documentation sounds a. Thinking, the UX designer ’ s the same language objective is to a methodical, almost scientific approach in! Than age or income testing as the UX design process times when the users are struggling with product! Eventually maturing them, we support later stages in the world, but is to focus on obtaining feedback early... Mind is that design documents should complement, not supplement, the lead. Why document at all traditional tactics of design to solve problems, both answer that focusses on advice how. A slightly different approach to that of websites and apps: learn more …! Around what the users want and need go beyond your target demographics personas — Once you have adequate data your... May feel like extra work, but it would also be a word.