Difference between revisions of "KDE Visual Design Group/HIG/Vision"

Jump to: navigation, search
(Created page with "__NOTOC__ == Purpose == 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 t...")
 
(Move notice)
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
  
== Purpose ==
+
{{Note|This page is now on [[https://hig.kde.org/introduction/concept.html https://hig.kde.org/]]}}
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. It is roughly similar to purpose or aim, and guides through the development.
 
 
 
== Guidelines ==
 
* Describe the project's final goals with your vision.
 
* Explain who will use the product, and how he or she will make advantage of it.
 
* Make sure the vision is shared over all stakeholders, developers and users.
 
* Write the vision with enough room for creativity.
 
* Keep the vision as short as possible.
 
* A good starting-point to describe the vision is the ''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>
 
== Best Practice ==
 
* Consider the [http://techbase.kde.org/Projects/Usability/Principles/KDE4_Vision| KDE vision] in your project.
 
 
 
[[Category:Usability]][[Category:Structure]][[Category:Task_Flow]]
 

Latest revision as of 19:59, 5 February 2019


Note-box-icon.png
Note
This page is now on [https://hig.kde.org/]

This page was last edited on 5 February 2019, at 19:59. Content is available under Creative Commons License SA 4.0 unless otherwise noted.