Baby Got Backend 2013

The updated 2013 version of "Baby Got Backend," a 60 minute crash course in making content editors' lives suck less.

Transcript

1. 1 Baby Got Backend Why your content editors hate life and how to make it better ! August 19, 2013
4. Karen McGrane, Content Strategy for Mobile 4 “If you create content, the usability of your CMS is as important as your eCommerce transaction flow.
 
 Most CMS’s look like a database got drunk and vomited all over the screen.
5. Editors are your MVPs 5
6. Most of them learn to work with crap. 6
7. Most of them learn to work with crap. 7
8. Most of them learn to work with crap. They need good tools, and they aren’t getting them. 8
9. one size does not fit all. 9
10. How to justify the time (aka money) ‣ Map content to business goals ‣ Reduce the risk of accidents ‣ Amortize the time cost 10
12. 12 Time is money 50 Employees x 5 forms/week x 10 wasted minutes/form x 50 weeks/year
13. 12 Time is money 50 Employees x 5 forms/week x 10 wasted minutes/form x 50 weeks/year $50,000
14. Diagnosing the problems 13
15. Weak tools follow predictable patterns 14
16. Weak tools follow predictable patterns ‣ Newbies get overwhelmed ‣ Work focuses on forms, not tasks ‣ The management tools don’t scale ‣ Approval systems become bottlenecks ‣ Editors get stuck with design tasks 14
17. New and infrequent users get overloaded 15
18. New and infrequent users get overloaded ‣ Label and organize their way, consistently 16
19. New and infrequent users get overloaded ‣ Label and organize their way, consistently 16
20. New and infrequent users get overloaded ‣ Label and organize their way, consistently ‣ Use selective disclosure, sensible defaults 17
21. New and infrequent users get overloaded ‣ Label and organize their way, consistently ‣ Use selective disclosure, sensible defaults 17
22. New and infrequent users get overloaded ‣ Label and organize their way, consistently ‣ Use selective disclosure, sensible defaults 17
23. New and infrequent users get overloaded ‣ Label and organize their way, consistently ‣ Use selective disclosure, sensible defaults ‣ Give next-step prompts when possible 18
24. New and infrequent users get overloaded ‣ Label and organize their way, consistently ‣ Use selective disclosure, sensible defaults ‣ Give next-step prompts when possible 18
25. New and infrequent users get overloaded ‣ Label and organize their way, consistently ‣ Use selective disclosure, sensible defaults ‣ Give next-step prompts when possible 18
26. New and infrequent users get overloaded ‣ Label and organize their way, consistently ‣ Use selective disclosure, sensible defaults ‣ Give next-step prompts when possible 19
27. Work focuses on forms, not tasks 20
28. Work focuses on forms, not tasks ‣ Study processes, understand goals 21
29. Work focuses on forms, not tasks ‣ Study processes, understand goals 21
30. Work focuses on forms, not tasks ‣ Study processes, understand goals ‣ Provide context, preserve state 22
31. Work focuses on forms, not tasks ‣ Study processes, understand goals ‣ Provide context, preserve state ‣ Account for offline workflow steps 23
32. Work focuses on forms, not tasks ‣ Study processes, understand goals ‣ Provide context, preserve state ‣ Account for offline workflow steps 23
33. Work focuses on forms, not tasks ‣ Study processes, understand goals ‣ Provide context, preserve state ‣ Account for offline workflow steps 24
34. Approval systems turn into bottlenecks 25
35. Approval systems turn into bottlenecks ‣ Capture state, then roles, then process 26
36. Approval systems turn into bottlenecks ‣ Capture state, then roles, then process 26
37. Approval systems turn into bottlenecks ‣ Capture state, then roles, then process ‣ Inform users, don’t block progress 27
38. Approval systems turn into bottlenecks ‣ Capture state, then roles, then process ‣ Inform users, don’t block progress ‣ Restrict access to risky actions 28
39. Approval systems turn into bottlenecks ‣ Capture state, then roles, then process ‣ Inform users, don’t block progress ‣ Restrict access to risky actions 28
40. Approval systems turn into bottlenecks ‣ Capture state, then roles, then process ‣ Inform users, don’t block progress ‣ Restrict access to risky actions 29
41. The management tools don’t scale 30
42. The management tools don’t scale ‣ Tackle inventory and governance first 31
43. The management tools don’t scale ‣ Tackle inventory and governance first 31 Search Social Email APIs Print Feeds Web Apps
44. The management tools don’t scale ‣ Tackle inventory and governance first ‣ Provide filtered search, dashboards 32
45. The management tools don’t scale ‣ Tackle inventory and governance first ‣ Provide filtered search, dashboards 32
46. The management tools don’t scale ‣ Tackle inventory and governance first ‣ Provide filtered search, dashboards 32
47. The management tools don’t scale ‣ Tackle inventory and governance first ‣ Provide filtered search, dashboards ‣ Automate repetitive and bulk tasks 33
48. The management tools don’t scale ‣ Tackle inventory and governance first ‣ Provide filtered search, dashboards ‣ Automate repetitive and bulk tasks 33
49. The management tools don’t scale ‣ Tackle inventory and governance first ‣ Provide filtered search, dashboards ‣ Automate repetitive and bulk tasks 33
50. The management tools don’t scale ‣ Tackle inventory and governance first ‣ Provide filtered search, dashboards ‣ Automate repetitive and bulk tasks 34
51. Editors get stuck with design tasks 35
52. Editors get stuck with design tasks ‣ Take a hard look at responsibilities 36
53. Editors get stuck with design tasks ‣ Take a hard look at responsibilities ‣ Manage priority, emphasis, grouping 37
54. Editors get stuck with design tasks ‣ Take a hard look at responsibilities ‣ Manage priority, emphasis, grouping ‣ Tailor the WYSIWYG vocabulary 38
55. Editors get stuck with design tasks ‣ Take a hard look at responsibilities ‣ Manage priority, emphasis, grouping ‣ Tailor the WYSIWYG vocabulary 38
56. Editors get stuck with design tasks ‣ Take a hard look at responsibilities ‣ Manage priority, emphasis, grouping ‣ Tailor the WYSIWYG vocabulary 38
57. Editors get stuck with design tasks ‣ Take a hard look at responsibilities ‣ Manage priority, emphasis, grouping ‣ Tailor the WYSIWYG vocabulary 39
58. Here comes the hard part 40
59. BYOB Toolkit: Build Your Own Backend ‣ Fields: Field Groups, Custom Validations, Widgets ‣ Dashboards: Views, Workbench, Panels ‣ Actions: Views Bulk Operations, Flag, Actions, Rules ‣ State: Workbench Moderation, Workflow, SPS ‣ Everything else: jQuery, custom modules 41
60. Your new bedtime reading list 42 Don’t Make Me Think Mental Models Card Sorting
61. Tools, patterns, and communities 43 ui-patterns uxmag designingwebinterfaces
62. Your secret weapon: two hours and a pizza ‣ Get your editors involved early ‣ Ask what they want and hate ‣ Watch them do real work 44
63. Your tools will evolve: Ask, build, and iterate. ‣ You can never solve it all in one go ‣ Iterative refinement lets you learn ‣ Your solutions will not be universal 45
64. It pays off.
    Really. 46