A big thank you to everyone who provided feedback on the first draft of the experience strategy – your input was very thoughtful and insightful and we have made great use of it to draft this second version of the strategy.
We think this is getting very close to a strong and workable experience strategy. Please take a moment to read through it and let me know what you think!
Drupal7 Experience Strategy & Goals V2
To make Drupal a tool that is powerful and flexible for content creation and management even for people who don’t write code or speak Drupal-speak without compromising the ability for developers to do their work. Drupal will allow anyone to create complex websites without developer knowledge.
our design principles:
- Make the most frequent tasks easy and less frequent tasks achievable.
- Design for the 80% of current and potential Drupal admin users – 80% of users will only use 20% of the functionality. (Hat tip to Pareto and his Principle)
- Privilege the Content Creator
- Allow for customisation but don’t make the end user do all the work, make informed and thoughtful decisions about the good default settings
- non-coding, non-Drupal experienced users should be able to add/edit and otherwise manage content without confusion, errors or extensive training.
- people should be able set up a site and publish content without having to go into a ‘configuration/setting/options’ type section
- the interface should not get in the way of the developers doing developing (and configuring and other administering) work.
Mark & Leisa’s Personal Goals:
- be so in love with Drupal UX that it becomes our tool of choice for content publishing
- be so confident about the Drupal UX that we recommend putting the ‘Download’ button back on Drupal.org (ref: D.O Redesign Strategies – Why Is It So?)