diff --git a/source/introduction/concept.rst b/source/introduction/concept.rst --- a/source/introduction/concept.rst +++ b/source/introduction/concept.rst @@ -13,86 +13,88 @@ A vision describes the goal of the project. It can be emotive and a source of inspiration. For instance, by outlining how the final product makes the world a better place you can draw upon inspiration to create -the end goal of your project. Describe the project's final goals. +the end goal of your project. Describe the project's end goals. Explain who will use the product, and how he or she will take advantage -from it. Make sure your vision is shared between all project +from it. Make sure your vision is shared between all project's stakeholders. Leave room in your vision for creativity and changes. Keep it short. -A good starting-point is the *elevator pitch*: +A good starting point is the typical *elevator pitch*: -- FOR *target customer* -- WHO *statement of the need* -- THE *product name* -- IS A *product category* -- THAT *key benefit* -- UNLIKE *primary competitor* -- OUR PRODUCT *further differentiation* +- **FOR** *target customer* +- **WHO** *statement of the need* +- **THE** *product name* +- **IS A** *product category* +- **THAT** *key benefit* +- **UNLIKE** *primary competitor* +- **OUR PRODUCT** *further differentiation* Personas -------- Personas can help identify the target users of your application and provide a common understanding among the design and development team. A -persona is the representation of a user, based on empirical data. -Personas describe the target users, giving a clear picture of how -they're likely to use the system, and what they’ll expect from it. The -description includes a concise summary of characteristics of the user, -their experience, goals and tasks, pain points, environmental conditions +persona is the representation of a user based on empirical data. +Personas describe target users, providing a clear picture of how +they are likely to use the system, and what they should expect from it. The +description includes a brief summary of user characteristics, +their experience, tasks, goals, pain points, environmental conditions and even name. +Using a persona name will help you further identify your target user easier. + The KDE usability team has created :doc:`predefined personas ` which we highly recommended using for your project. If you choose to create your own personas, consider the following: - Always try to define personas based on empirical data. Feel free to ask the KDE user experience team (kde-usability at kde.org) for - assistance with the collection of empirical data. -- Add enough information to establish a good impression of the target + assistance with the collection of empirical data. If empirical data is not available, still reach out to the usability team for guidance. +- Add enough information to establish a good representation of the target user and stay concise. -- Common elements are name, job titles and major responsibilities, - demographics such as age, education, ethnicity, and family status, +- Use common elements to describe your persona such as name, job titles and major responsibilities, + demographics such as age, education, ethnicity, family status, goals and tasks they are trying to complete using the application, physical, social, and technological environment. - Add a quote that sums up what matters most to the persona and a - casual picture representing that user group. -- Discriminate between primary (the basic user) and secondary + casual picture representing that user group. Like a motto. +- Draw differences between primary (the basic user) and secondary (additional users) persona. If it makes sense, describe the group of - users that is explicitly not supported by an anti-persona. Respect - the law of parsimony and have as few personas as possible. -- Make sure your persona can act in different scenarios. + detractors by creating an anti-persona. Respect + the law of parsimony [#] and have as few personas as possible. +- Make sure your persona can work in different scenarios. User Stories ------------ -Scenarios illustrate how the users achieve their goals by means of -task-orientated examples. It is supplementary to a persona, providing -together an efficient method applicable in a wide range of applications. +Scenarios illustrate how the users achieve their goals by means of using +task-orientated examples. These examples help develop a persona by providing an efficient methods applicable in a wide variety of applications. -Use the following guide to help create scenarios: +Use the following steps to create scenarios: -- Always try to create scenarios based on empirical data. Feel free to +- Always create scenarios based on empirical data. Feel free to ask the KDE user experience team (kde-usability at kde.org) for assistance with the collection of empirical data. -- Take technical configuration, environmental condition, organizational +- Take technical configurations, environmental conditions, organizational and social aspects into consideration. -- If available, use real world images to support imagination. -- Try to include problem situations that will test the system concept, +- Use real world images to support imagination. +- Include problem situations that will test the system concept, not just straightforward scenarios. Target Device Classes --------------------- -While thinking about the scenarios, also consider devices of which -class(es) the personas would use in that scenario. Currently, Plasma and -(some) KDE applications target the following device classes: +While thinking about the scenarios, think also of possible devices that such persona would use. Plasma and +(some) KDE applications target the following device categories: Desktop/laptop, media center (TV), phone and tablet/convertible. Your -application may target other device classes (like eg. in-vehicle -entertainment systems, kiosk systems, ...) as well. +application may target other device categories (like eg. in-vehicle +entertainment systems, kiosk systems, points of sale...) as well. Documenting Your Concept ------------------------ A useful template for documenting your personas and scenarios is the :doc:`Project User Research Template `. + +.. [#] a principle according to which an explanation of a thing or event is made with the fewest possible assumptions.