← Projects/Usability/HIG/Vision You do not have permission to edit this page, for the following reason: The action you have requested is limited to users in one of the groups: Users, Administrators, trusted, KDEDevelopers. You can view and copy the source of this page. __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 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]] Template used on this page: Template:Moved To Community (view source) Return to Projects/Usability/HIG/Vision. Retrieved from "https://techbase.kde.org/Projects/Usability/HIG/Vision"