Defining requirements for your next CMS project

1. Defining requirements for your next CMS project Anthony D Paul

2. Who am I… • Technical lead at Fathom (end-to-end; 5 years) • User experience developer • @anthonydpaul

3. What we'll talk about • High-level design process (refresher) • Focus on requirements definition (importance, context, parts) • Specific tools and methodologies(purpose, pros/cons, samples) • Case study • Determining tools for you

4. Theory behind the design process Behavior = function(Person, Environment) • No control over the person • Can identify the behavior • Simply build environment that elicits the desired behavior, right? Lewin’s Equation

5. The more we know about our users, the more likely we are to meet their needs.

6. High-level interactive process Requirements Definition (info gathering, specification Production (design, development) Delivery (training, launch, maintenance) Testing

7. High-level interactive process Production (design, development) Delivery (training, launch, maintenance) Testing

8. High-level interactive process Requirements Definition (info gathering, specification Production (design, development) Delivery (training, launch, maintenance) Testing

9. Foundation of the end product Visual Design tangible Local Architecture Global Architecture Functionality Objectives (users, business) abstract Derived from: Jesse James Garrett’s "The Elements of User Experience"

10. What does that path look like? What itcould be What itends up being Derived from: Liz Sanders’ "Co-Creation"

11. What does that path look like? What itcould be Derived from: Liz Sanders’ "Co-Creation"

12. Foundation of the end product Visual Design tangible Local Architecture Global Architecture Functionality Objectives (users, business) abstract

13. 3 main components Requirements Definition Audit Processing Spec

14. 3 main components Requirements Definition Ask Audit Think Processing Do Spec

15. So, what do these break down into? Ask Audit • (Objectives) • Wants & needs (user vs. client) • Climate (competition & market) • Content Think Processing • (Functionality) • Stories (humanity) • Behaviors ($$$) Do Spec • Global arch. (taxonomy) • Local arch. (hierarchy) • Visual Design

16. Tools we use to define them Component Tools Ask Audit • (Objectives) • Wants & needs (user vs. client) • Climate (competition & market) • Content • Surveys & interviews • Card sorting • “Make tools” (paper prototypes & collages) Think Processing • (Functionality) • Stories (humanity) • Behaviors ($$$) • Personas • Usage scenarios (task flows) • Mood board Do Spec • Global arch. (taxonomy) • Local arch. (hierarchy) • Visual Design • Sitemap • Wireframes • A/B tests • Digital prototypes

17. Tools: Card sort

18. Tools: “Make tools”

19. Tools: Personas

20. Tools: User scenarios

21. Tools: Mood board

22. Tools: Sitemap

23. Tools: Task flow

24. Tools: Wireframes

25. Tools: A/B tests

26. Tools: Digital prototype

28. Biggest challenges • Content audit • Many stakeholders/users • Sitemap

30. As a testament, one month after launch saw a 1200% increase in average daily page hits.

31. Determining your tools • Project size (budget) • Personal preference • Client need & risk

32. In summary • Requirements definition is required • The process is yours, as long as it works and is methodical • The more touch-points you give your users for feedback, the better you will know them…and the more likely you will meet their needs.

33. Questions? • @anthonydpaul