• Save
Little Big Systems (Interlink edition)
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Little Big Systems (Interlink edition)

on

  • 4,098 views

It’s really easy to understand the lure of small, artisanal projects that we can polish to a satin finish: they offer a sense of craftsmanship, a human scale for our work, and the chance to get ...

It’s really easy to understand the lure of small, artisanal projects that we can polish to a satin finish: they offer a sense of craftsmanship, a human scale for our work, and the chance to get something really *right*. But larger projects and bigger systems can often feel soulless and unsatisfying, even when we’re excited by the causes and ideas behind them. So is there a way to work on an ambitious scale without losing the purpose and handcraftedness that makes more intimate gigs so much fun? (Hint: yes.)

Via the craft of content strategy and its intertwinglements with design and code, this talk follows the connections between making small-scale, handcrafted artifacts and designing big, juicy systems (editorial and otherwise) that encourage both liveliness and excellence.

Statistics

Views

Total Views
4,098
Views on SlideShare
3,897
Embed Views
201

Actions

Likes
6
Downloads
0
Comments
1

8 Embeds 201

http://localhost 99
http://zekefranco.com 45
http://steventoala.xtrweb.com 30
http://lanyrd.com 12
http://www.twylah.com 6
http://www.steventoala.xtrweb.com 5
http://192.168.1.100 3
http://habrahabr.ru 1
More...

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • Is everyone else seeing the last word of almost every slide cut off? Until about 50 slides in I thought this was intentional.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • \n
  • Sackboy\n
  • Sackboy\n
  • Sackboy\n
  • \n
  • Kevin Cornell, Kristina Halvorson, The Discipline of Content Strategy, \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • If you’re someone who really cares about craft, systems design can seem kind of unappealing.\n
  • http://www.flickr.com/photos/n1ke/4205658305/sizes/o/in/set-72157622925823109/\n
  • http://www.flickr.com/photos/zigazou76/3665789236/sizes/o/in/photostream/\n
  • Mastery, excellence, and a human scale (not yet why it matters)\n
  • \n
  • OED\n
  • Framework\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Framework\n
  • -- why does that matter? We can’t afford to let the streams separate\n
  • We need good work\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • wagashi\n
  • \n
  • \n
  • \n
  • Window place. In architecture, we have patterns in which this happens quite naturally. Online, getting it right often involves pushing pretty hard against established norms, and is frequently incremental. WaSP did it, via serious organization.\n
  • \n
  • Nestle factory in Dubai\n
  • \n
  • Krenov, 6 years olf, jacknife, toys, studied in Sweden under the father of Swedish furniture design\n
  • A true achievement is to make a fine cabinet—elegant, graceful, one with real character—and fit it with drawers and doors that work properly the year round. That requires skill rather than showmanship. >> Cabinet is a dynamic system, too\n
  • Bad delivery kills great content.\n
  • \n
  • \n
  • \n
  • \n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • \n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • …often by way of mistakes, listening to the material, coming upon unexpected signals.\n
  • \n
  • Bad delivery kills great content.\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Which are HORRIBLE. But consider the consumer-centric WordPress\n
  • Wordpress installs\n
  • \n
  • \n
  • \n
  • Framework\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • A true achievement is to make a fine cabinet—elegant, graceful, one with real character—and fit it with drawers and doors that work properly the year round. That requires skill rather than showmanship. >> Cabinet is a dynamic system, too\n
  • Bad delivery kills great content.\n
  • \n
  • Bad delivery kills great content.\n
  • I LOVE YOU. \n
  • Bad delivery kills great content.\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • “Too slow? It all depends on what you want to do and how you do it. One fellow bangs away and gets things done. Another tap, taps—and he too, gets things done. The question is, on what level? What did the doing take, and what did it give?” >> from the work, from the users, from you: did it kill you? did it enrich the product?\n
  • \n
  • Framework\n
  • \n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Bad delivery kills great content.\n
  • Now imagine giving this edict to a writer\n
  • \n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • \n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • Bad delivery kills great content.\n
  • \n
  • \n
  • \n
  • \n
  • Bad delivery kills great content.\n
  • Ship small but excellent\n
  • \n
  • “Innovate as a last resort” — Charles Eames\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • “if you get the doing right…then the result rights itself to that. You do what you are. No more, no less. You develop, and your work develops: there’s a play between doing things in a way that feels good—and getting good results.\n
  • \n
  • \n
  • Respect deep knowledge \n
  • \n
  • \n
  • “one of the great lies of craft education: that finesse is only for dreamers.” People will tell you that the values and rhythms of craft are for idealists. But I look around and I see proof that this is not so. \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n

Little Big Systems (Interlink edition) Presentation Transcript

  • 1. LITTLE BIG SYSTEMS Embiggening the magic of craft Erin Kissane @kissaneThursday, June 21, 2012
  • 2. HI, LITTLE FELLAThursday, June 21, 2012
  • 3. Thursday, June 21, 2012
  • 4. Thursday, June 21, 2012
  • 5. MAKING SYSTEMSThursday, June 21, 2012
  • 6. Thursday, June 21, 2012
  • 7. Mars Needs Content StrategistsThursday, June 21, 2012
  • 8. Content strategy is weirdThursday, June 21, 2012
  • 9. Content strategy is system designThursday, June 21, 2012
  • 10. We don’t (just) make thingsThursday, June 21, 2012
  • 11. We make systems that make thingsThursday, June 21, 2012
  • 12. We don’t make thingsThursday, June 21, 2012
  • 13. We make systems that make thingsThursday, June 21, 2012
  • 14. The values of craftThursday, June 21, 2012
  • 15. MAKING SYSTEMSThursday, June 21, 2012
  • 16. “A set or assemblage of things connected, associated, or interdependent, so as to form a complex unity”Thursday, June 21, 2012
  • 17. Thursday, June 21, 2012
  • 18. Thursday, June 21, 2012
  • 19. Thursday, June 21, 2012
  • 20. Adjusting bad fitThursday, June 21, 2012
  • 21. Thursday, June 21, 2012
  • 22. Thursday, June 21, 2012
  • 23. Thursday, June 21, 2012
  • 24. Thursday, June 21, 2012
  • 25. Thursday, June 21, 2012
  • 26. Thursday, June 21, 2012
  • 27. Thursday, June 21, 2012
  • 28. Tools for makersThursday, June 21, 2012
  • 29. Content management systemsThursday, June 21, 2012
  • 30. Most “software”Thursday, June 21, 2012
  • 31. All big projects are systemsThursday, June 21, 2012
  • 32. Sprawling websitesThursday, June 21, 2012
  • 33. Social networksThursday, June 21, 2012
  • 34. Ecosystems of appsThursday, June 21, 2012
  • 35. Ecosystems of contentThursday, June 21, 2012
  • 36. BRINGING CRAFT TO SYSTEMSThursday, June 21, 2012
  • 37. Systems need craftThursday, June 21, 2012
  • 38. Humans need craftThursday, June 21, 2012
  • 39. 1. RETURN TO THE ARTIFACTThursday, June 21, 2012
  • 40. Thursday, June 21, 2012
  • 41. Thursday, June 21, 2012
  • 42. Thursday, June 21, 2012
  • 43. Thursday, June 21, 2012
  • 44. Thursday, June 21, 2012
  • 45. Intimate knowledge of artifactsThursday, June 21, 2012
  • 46. Thursday, June 21, 2012
  • 47. Thursday, June 21, 2012
  • 48. Thursday, June 21, 2012
  • 49. Intimate knowledge of the artifact = better systemsThursday, June 21, 2012
  • 50. Better systems = better artifactsThursday, June 21, 2012
  • 51. Thursday, June 21, 2012
  • 52. Thursday, June 21, 2012
  • 53. Thursday, June 21, 2012
  • 54. Thursday, June 21, 2012
  • 55. (Look at your fish.)Thursday, June 21, 2012
  • 56. 2. EMPOWER MAKERSThursday, June 21, 2012
  • 57. Thursday, June 21, 2012
  • 58. Thursday, June 21, 2012
  • 59. Thursday, June 21, 2012
  • 60. Thursday, June 21, 2012
  • 61. Content management systemsThursday, June 21, 2012
  • 62. 74 millionThursday, June 21, 2012
  • 63. Systems that prevent excellenceThursday, June 21, 2012
  • 64. Systems that encourage excellenceThursday, June 21, 2012
  • 65. Thursday, June 21, 2012
  • 66. Thursday, June 21, 2012
  • 67. 3. WORK IN CRAFTSMAN’S TIMEThursday, June 21, 2012
  • 68. Big projects suck because of timeThursday, June 21, 2012
  • 69. Craftsman’s time is humane efficiencyThursday, June 21, 2012
  • 70. Thursday, June 21, 2012
  • 71. Project managersThursday, June 21, 2012
  • 72. Thursday, June 21, 2012
  • 73. Now let’s talk.Thursday, June 21, 2012
  • 74. The secret:Thursday, June 21, 2012
  • 75. “No.”Thursday, June 21, 2012
  • 76. “No., but what I can do is this.”Thursday, June 21, 2012
  • 77. It’s better to get a subsystem right…Thursday, June 21, 2012
  • 78. …than the whole system wrong.Thursday, June 21, 2012
  • 79. “What did the doing take, and what did it give?” — James KrenovThursday, June 21, 2012
  • 80. Thursday, June 21, 2012
  • 81. Thursday, June 21, 2012
  • 82. 4. SHIP SMALL BUT EXCELLENTThursday, June 21, 2012
  • 83. Work large to smallThursday, June 21, 2012
  • 84. Ship small to largeThursday, June 21, 2012
  • 85. MVP = small enough for excellenceThursday, June 21, 2012
  • 86. Thursday, June 21, 2012
  • 87. We will serve world- class contentThursday, June 21, 2012
  • 88. Thursday, June 21, 2012
  • 89. We will serve world- class contentThursday, June 21, 2012
  • 90. TOO GENERIC We will serve world- class contentThursday, June 21, 2012
  • 91. We will serve world-class content for plant-loversThursday, June 21, 2012
  • 92. TOO BROAD We will serve world-class content for plant-loversThursday, June 21, 2012
  • 93. Uniquely helpful content for first-time plant-buyersThursday, June 21, 2012
  • 94. Thursday, June 21, 2012
  • 95. Uniquely helpful content for first-time plant-buyersThursday, June 21, 2012
  • 96. BETTER Uniquely helpful content for first-time plant-buyersThursday, June 21, 2012
  • 97. We’ll tell you: • What plants won’t die? • Which do I think are pretty? • How do I care for them?Thursday, June 21, 2012
  • 98. Happiness. We’ll tell you: • What plants won’t die? • Which do I think are pretty? • How do I care for them?Thursday, June 21, 2012
  • 99. We’ll do that by…Thursday, June 21, 2012
  • 100. We’ll do that by… • creating a 20-plant guideThursday, June 21, 2012
  • 101. We’ll do that by… • creating a 20-plant guide • and posting blog postsThursday, June 21, 2012
  • 102. We’ll do that by… • creating a 20-plant guide • and posting blog posts • every weekThursday, June 21, 2012
  • 103. We’ll do that by… • creating a 20-plant guide • and posting blog posts • every week • by our resident gardenerThursday, June 21, 2012
  • 104. Thursday, June 21, 2012
  • 105. 5. RESPECT DEEP KNOWLEDGEThursday, June 21, 2012
  • 106. Reinvent only with reasonThursday, June 21, 2012
  • 107. Seek the deep wells of knowledgeThursday, June 21, 2012
  • 108. Thursday, June 21, 2012
  • 109. Thursday, June 21, 2012
  • 110. I like to employ old people. I believe that a company needs a balance between young and old people. Young people are not necessarily the key to innovation. —Patrizio Bertelli, Prada CEOThursday, June 21, 2012
  • 111. Do the apprenticeshipsThursday, June 21, 2012
  • 112. Thursday, June 21, 2012
  • 113. “if you get the doing right…then the result rights itself to that.” — James KrenovThursday, June 21, 2012
  • 114. (Take apprentices)Thursday, June 21, 2012
  • 115. Bodies of knowledgeThursday, June 21, 2012
  • 116. Thursday, June 21, 2012
  • 117. HANDMADE SYSTEMSThursday, June 21, 2012
  • 118. Things men have made with wakened hands, and put soft life into are awake through years with transferred touch, and go on glowing —DH LawrenceThursday, June 21, 2012
  • 119. I like to employ old people. I believe that a company needs a balance between young and old people. Young people are not necessarily the key to innovation. —Patrizio Bertelli, Prada CEOThursday, June 21, 2012
  • 120. “You don’t have a career. You have a life. Do the work.” — Dear Sugar (Cheryl Strayed)Thursday, June 21, 2012
  • 121. THANK YOU! Thank you.Thursday, June 21, 2012
  • 122. 1. Little Big Planet promo images © Media Molecule & Sony 2. Elephant © Kevin Cornell & A List Apart (http://www.alistapart.com/articles/thedisciplineofcontentstrategy) 3. Type specimen photographed by Flickr user n1ke (http://www.flickr.com/photos/n1ke/4205658305/sizes/o/in/ set-72157622925823109/) 4. Linotype © zigazou76 (http://www.flickr.com/photos/zigazou76/3665789236/sizes/o/in/photostream/) 5. Wagashi © bebot http://www.flickr.com/photos/bebot/3910852271/ 6. Confectioner © Matt Helminski http://www.flickr.com/photos/helminski/429173625/ (used with permission) 7. Wagashi pattern book © capitanjen http://www.flickr.com/photos/capitanjen/5306236824/ 8. Wagashi © skrb http://www.flickr.com/photos/skrb/4349539980/ 9. Aero bars © Zophos http://www.flickr.com/photos/zophos/92638509/ (CC some rights reserved) 10. Nestle factory © Nestlé http://www.flickr.com/photos/nestle/5243945997/ (CC some rights reserved) 11. James Krenov images © James Krenov, Sterling Books 12. Robin Sloan’s Fish: A Tap Essay © Robin Sloan 13. Mast Brothers © Todd Selby http://www.theselby.com/1_8_10_mast_brothers/ 14. Kid with candy © Nina Hale http://www.flickr.com/photos/94693506@N00/1811980892/ 15. Confectioners’ equipment © Matt Helminski http://www.flickr.com/photos/helminski/401847939/ (used with permission) 16. Bread © chebbs http://www.flickr.com/photos/chebbs/5018724198/ 17. Wagashi © http://ouichefcook.com/ 18. Crying baby © kungfustu http://www.flickr.com/photos/kungfustu/5332653962/ 19. Less crying baby © malisonian http://www.flickr.com/photos/malisonian/2797061988/ 20. Wagashi pattern sheets © capitanjen http://www.flickr.com/photos/capitanjen/5306237800/ 21. Prada pattern books © Prada 22. Prada cutter’s hand © Prada 23. Apprentice confectioner © capitanjen http://www.flickr.com/photos/capitanjen/5305646181/ 24. Workbench © Oldwolf Workshop http://insidetheworkshop.blogspot.com/2011_04_01_archive.html 25. Krenov plane © James Krenov, Sterling BooksThursday, June 21, 2012