< KDE Visual Design Group | HIG Revision as of 14:56, 11 March 2014 (view source)Htietze (talk | contribs) (→Best Practice)← Older edit Revision as of 12:21, 30 March 2016 (view source) Ochurlaud (talk | contribs) m (4 revisions imported)Newer edit → (No difference) Revision as of 12:21, 30 March 2016 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 Define the vision of your project based on the KDE vision. Retrieved from "https://community.kde.org/index.php?title=KDE_Visual_Design_Group/HIG/Vision&oldid=59551" Categories: UsabilityStructureTask Flow Content is available under Creative Commons License SA 4.0 unless otherwise noted.