Upgrade to PRO for Only $50/Year—Limited-Time Offer! 🔥

Baby Got Backend 2013

Jeff Eaton
November 22, 2013

Baby Got Backend 2013

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

Jeff Eaton

November 22, 2013
Tweet

More Decks by Jeff Eaton

Other Decks in Technology

Transcript

  1. 1 Baby Got Backend Why your content editors hate life

    and how to make it better ! August 19, 2013
  2. 2

  3. 3

  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. Most of them learn to work with crap. They need

    good tools, and they aren’t getting them. 8
  6. How to justify the time (aka money) ‣ Map content

    to business goals ‣ Reduce the risk of accidents ‣ Amortize the time cost 10
  7. 11

  8. 12 Time is money 50 Employees x 5 forms/week x

    10 wasted minutes/form x 50 weeks/year
  9. 12 Time is money 50 Employees x 5 forms/week x

    10 wasted minutes/form x 50 weeks/year $50,000
  10. 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
  11. New and infrequent users get overloaded ‣ Label and organize

    their way, consistently ‣ Use selective disclosure, sensible defaults 17
  12. New and infrequent users get overloaded ‣ Label and organize

    their way, consistently ‣ Use selective disclosure, sensible defaults 17
  13. New and infrequent users get overloaded ‣ Label and organize

    their way, consistently ‣ Use selective disclosure, sensible defaults 17
  14. New and infrequent users get overloaded ‣ Label and organize

    their way, consistently ‣ Use selective disclosure, sensible defaults ‣ Give next-step prompts when possible 18
  15. New and infrequent users get overloaded ‣ Label and organize

    their way, consistently ‣ Use selective disclosure, sensible defaults ‣ Give next-step prompts when possible 18
  16. New and infrequent users get overloaded ‣ Label and organize

    their way, consistently ‣ Use selective disclosure, sensible defaults ‣ Give next-step prompts when possible 18
  17. New and infrequent users get overloaded ‣ Label and organize

    their way, consistently ‣ Use selective disclosure, sensible defaults ‣ Give next-step prompts when possible 19
  18. Work focuses on forms, not tasks ‣ Study processes, understand

    goals ‣ Provide context, preserve state 22
  19. Work focuses on forms, not tasks ‣ Study processes, understand

    goals ‣ Provide context, preserve state ‣ Account for offline workflow steps 23
  20. Work focuses on forms, not tasks ‣ Study processes, understand

    goals ‣ Provide context, preserve state ‣ Account for offline workflow steps 23
  21. Work focuses on forms, not tasks ‣ Study processes, understand

    goals ‣ Provide context, preserve state ‣ Account for offline workflow steps 24
  22. Approval systems turn into bottlenecks ‣ Capture state, then roles,

    then process ‣ Inform users, don’t block progress 27
  23. Approval systems turn into bottlenecks ‣ Capture state, then roles,

    then process ‣ Inform users, don’t block progress ‣ Restrict access to risky actions 28
  24. Approval systems turn into bottlenecks ‣ Capture state, then roles,

    then process ‣ Inform users, don’t block progress ‣ Restrict access to risky actions 28
  25. Approval systems turn into bottlenecks ‣ Capture state, then roles,

    then process ‣ Inform users, don’t block progress ‣ Restrict access to risky actions 29
  26. The management tools don’t scale ‣ Tackle inventory and governance

    first 31 Search Social Email APIs Print Feeds Web Apps
  27. The management tools don’t scale ‣ Tackle inventory and governance

    first ‣ Provide filtered search, dashboards 32
  28. The management tools don’t scale ‣ Tackle inventory and governance

    first ‣ Provide filtered search, dashboards 32
  29. The management tools don’t scale ‣ Tackle inventory and governance

    first ‣ Provide filtered search, dashboards 32
  30. The management tools don’t scale ‣ Tackle inventory and governance

    first ‣ Provide filtered search, dashboards ‣ Automate repetitive and bulk tasks 33
  31. The management tools don’t scale ‣ Tackle inventory and governance

    first ‣ Provide filtered search, dashboards ‣ Automate repetitive and bulk tasks 33
  32. The management tools don’t scale ‣ Tackle inventory and governance

    first ‣ Provide filtered search, dashboards ‣ Automate repetitive and bulk tasks 33
  33. The management tools don’t scale ‣ Tackle inventory and governance

    first ‣ Provide filtered search, dashboards ‣ Automate repetitive and bulk tasks 34
  34. Editors get stuck with design tasks ‣ Take a hard

    look at responsibilities ‣ Manage priority, emphasis, grouping 37
  35. Editors get stuck with design tasks ‣ Take a hard

    look at responsibilities ‣ Manage priority, emphasis, grouping ‣ Tailor the WYSIWYG vocabulary 38
  36. Editors get stuck with design tasks ‣ Take a hard

    look at responsibilities ‣ Manage priority, emphasis, grouping ‣ Tailor the WYSIWYG vocabulary 38
  37. Editors get stuck with design tasks ‣ Take a hard

    look at responsibilities ‣ Manage priority, emphasis, grouping ‣ Tailor the WYSIWYG vocabulary 38
  38. Editors get stuck with design tasks ‣ Take a hard

    look at responsibilities ‣ Manage priority, emphasis, grouping ‣ Tailor the WYSIWYG vocabulary 39
  39. 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
  40. 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
  41. 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