How a book is made: a short story

Mysteries abound about how books become books. Unlike the Schoolhouse rock episode about how bills in the Senate become bills, there is no well produced, simply-comprehensible by 10 year olds, explanation. It seems easy (you hit Cntrl-P and books come out somewhere, right?) but it’s an intellectual and tedium marathon.

Here, in short author-centric form, is how it goes:

  1. Author writes a proposal for a book.
  2. He picks a publisher and sends it in. (If no favorable response, repeat, or self publish and skip to #3).
  3. Author writes (Imaging calendar pages flying by, bar tabs growing astronomically).
  4. Author sends manuscript to publisher.
  5. Publisher gives feedback (go to #3) or greenlights production.

And then all the work begins – the detail work of production. Much like software its the last 1/3rd has all the crunchy, tricky bits.

Every publisher works differently but for many, production includes:

  • Copyediting the text in the book
  • Obtaining rights for any photos or excerpts
  • Checking references
  • Designing the cover & interiors
  • Planning PR and marketing
  • Promotion

These activities seem like publisher business, not author business, but that’s a rookie mistake. My name goes on the book, not any editor or executive: the complaints get aimed my way. And of course it’s my only book published this year, while any publisher, for all their authorial compassion, publishes dozens. What comprises a minor oversight to publishers has made many an authors suicide note[1].

Copyediting means one thing: review. Endless review. As tortured as the copyeditor must feel, the writer has no one else to blame: its their words! They have to re-read every sentence again, and again, and again, as suggested changes, for all their grammatical correctness, can shift the meaning of sentences or kill any hard fought humor so delicately constructed in earlier revisions. How involved authors are in this process varies, but see previous paragraph.

By the time my first book actually existed as a book, I was so sick of what was in it I couldn’t look inside for long: and every author I’ve asked had similar experiences. It took awhile, if ever, that they liked what was in their book again (Many legendary writers from Hemingway to Henry Miller complained at how they loved writing, but hated what they wrote).

This isn’t meant as a play for sympathy: I mean come on. Every writer in history could have found an easier way to make a living, or if it was really so horrible, quit for sake of sanity. However after my experience, the first time I saw my book in Borders I nearly had a heart attack: after some brief ego-stroking glee, I imagined all of the work it took to make all of the other 50,000 books in that store, and my head exploded. And then I thought of how few are allowed to stay on those shelves for long. It’s a high risk thing to make a book for profit: most don’t sell enough to break even for the writer or the publisher.

If nothing else maybe this little note with give you a new perspective the next time you pick up a book (or consider the “glories” of writing one).

——————-

[1] The one story I’m thinking of is Mellvile’s Moby Dick. Apparently the first edition ommitted the last chapter, and the book was panned by critics. Later, re-publication included the chapter and the book became a classic after the author’s death (not by suicide however).

This week in pm-clinic: the white knight

After a few weeks on hiatus, the pm-clinic is back. With a vengeance. New tales of management challenges and great advice await.
This week in the pm-clinic discussion forum:

I was asked by to take over a troubled project. This group is managed by my boss’ peer so I am now dotted-line-reporting to him for this project. This
senior-level manager is not happy about being forced to use me. The project teams are strong but have been micro-managed by said manager who repeatedly
puts the cart before the horse – one of the major reasons the project is in trouble.

I, as the white knight,” am being asked to keep the listing ship from completely sinking. Expectations for getting it on track are high, while still meeting some of the originally set timelines.

How do I both manage this project and a sponsor who doesn’t want me as the PM?

-Signed, the white knight

Special offer from the book dart folks

My post about book darts was picked up by O’Reilly radar and lifehacker, and wouldn’t you know it: word got round to the makers of these great little things.

Bob Williams, one of the founders of the company, chimed in and made this offer:

Readers of the Berkun Blog, may, if they wish to, buy our Book Darts for the wholesale costs. Order on the reseller side of our site or alert us in the comments box when you order, and we’ll make the adjustment.

Thanks Bob!

Creativity: Supply vs. Demand

Creative people like to create – no surprise there. But most people who create things struggle to get anyone to care about their creations. Once you have made something good, the challenge is no longer creativity, but generating demand for what you make.

curve

Every intro to economics course in the world pummels students with endless variations of curves, like the one above. Right now thousands of MBA students at colleges around the world are watching professors prance around and poke at charts with curves on them, and for good reason. There are basics of commerce that everyone should understand, even in the oversimplified way I’m about to describe.

The demand side of creativity

Assume you are in a market with more supply than demand: you have 20 widgets (or great ideas), but your customer (your boss) isn’t interested in paying much for them.

If we think of the chart there are three choices:

  1. Lower prices, expecting to increase sales.
  2. Create a new diagram, showing infinite demand, and staple it to your boss’ forehead.
  3. Work to increase reasons for demand.

It’s hard to do #1 if you have an employer. #2 is fun, but requires a fast stapler and good aim. Leaving #3. Something has to be done to shift that demand curve to the right.

So how does a creative person increase demand for their work?

  1. Ask. Mention to your customers you want to provide more value. What is it that drives their demand for your work? Ask the question and then shut-up and listen. They’re telling you their values, and if you want their demand you have to work on their turf. You might influence their values, but that’s a tough place to start.
  2. Persuade. The reason why your creative heroes became famous was more than their talent. They marketed themselves, or had friends and supporters who did the marketing for them. Your weakness might be your ability to sell yourself and persuade others on the value of your work.
  3. Tell stories. In your world, who has the strongest demand for your work? Even if you are unpopular, someone likes your work more than others. Tell their story to the rest of your market of why they find what you do valuable. Testimonials are everywhere in marketing for this reason: it demonstrates demand, which creates demand.
  4. Prove your value. Are there before and after pictures you can show? Stats on how your creations have helped sales, raised profits, lowered costs? Start compiling and when you have a good case, spread it around. Take an inventory of all the ideas and creations you’ve had: no matter how you’ve struggled, some efforts will have had more value than others.
  5. Take a a risk / Make a proposal. Once you have stories and proof of value, place a bet on yourself. Put a proposal together: a plan for a new project, a change in how an existing project should be done, something. The better the stories & proof, the more ambitious the proposal. Use those stories and proof of value as collateral, and as part of your pitch for a specific action you want. Imagine the kind of demand you feel your work is worthy of, and craft the proposal to match.
  6. Find a champion. Who has enough influence to raise demand for your work? Enlist them as your advocate. Explain the goal of raising the value of your work, and ask for help. Can they talk to their peers? Recommend you for projects? Or endorse a proposal you’ve made?

You get the idea – someone has to do marketing for your creations, and that’s a different skill, and philosophy, than creation itself. Often this is the role design managers or creative directors are supposed to play, but its rarely as much fun for them as working the supply side.

A more accurate discussion of how supply and demand curves work can be found at netmba or at wikipedia (where the diagram above is from).

Have other demand side activities that creatives can use? Let me know.

How we got here: Legacy of the whole earth catalog

Much of the current web 2.0 vibe was born by the folks who started the Whole Earth Catalog, the WELL (first online community), and Wired magazine.

Well, here in this panel interview are the founders of all three: Kevin Kelly, Stewart Brand, and Howard Rheingold, talking about how it started, why they did what they did, and what they think of where we are today.

80 minutes long in Realvideo format. Skip to ~15 minutes in to bypass the various intros.

wholeearth.jpg

MLK, technology and inspiration

What gets me every time I hear Martin Luther King speak is this: he didn’t have a blog. Nor did he use podcasts, e-mails or iPhones. He was a low tech-man. All he needed was a podium, a microphone and an audience. He was influential because of what he said and how he said it, not the pipe or protocol the message was delivered on.

MLK is a reminder that message transcends technology. The medium might be a message, but it’s not the only message – the McLuhan quote is so twisted and misused in one of the great ironies, as his obfuscated writing makes his message hard to understand.

The inspiration is this: if technology empowers people, where are the powerful, meaningful messages? On a day like today everything that seems so important in the tech and business world seems superficial. How do these messages help people? How does this message enlighten or effect change? What progress does this afford, and for who? (See: Software Is Not Epic)

I’m trying to use MLK as a sanity check:

  • When will I write about what’s important?
  • When will I help good messages, and the people behind them, to find larger audiences?
  • Why am I not volunteering more time for what I believe, rather than what’s popular, fun or lucrative?
  • When was the last time I saw technology help someone in true need? When was the last time I delivered that help?

If MLK could move millions with the spoken word, what should I be able to do with all of this wonderful technology and empowerment at my disposal? Whose message is out there now that I can help spread or support?

“You want to be important? Wonderful. You want to be recognized? Wonderful. You want to be great? wonderful. But recognize that he who is greatest among you shall be your servant.. By giving that definition of greatness it means everybody can be great, because everybody can serve. You don’t have to have a college degree to serve. You don’t have to have to make your subject and your verb agree to serve. You don’t have to know about Plato and Aristotle to serve. You don’t have to know Einstein’s “Theory of Relativity” to serve. You don’t have to know the Second Theory of Thermal Dynamics in Physics to serve. You only need a heart full of grace, a soul generated by love, and you can be that servant.”

From MLK’s, Feb 4th, 1968 sermon

MLK Online: videos, speeches and transcripts
Seattle times MLK special

Martin Luther King Jr. wikipedia entry


In defense of simplicity

Recently two notable design advocates, Don Norman and Joel Spolsky, challenged the value of simplicity in design, and I’m here to offer a late defense.

Confusion

It’s easy to confuse success with quality, and both articles discount our secret inability to make satisfying choices. We are attracted to things with more features, that cost less, or come in larger quantities, despite our inner suspicions that we’re likely to complain about those purchases soon after. We date people, eat food, take jobs and buy products for superficial, misguided reasons all the time. We’re easily seduced, and every marketer knows we always have been and always will be.

But we shouldn’t confuse the success of feature-laden crap as a signal for the irrelevance of simplicity any more than the success of Rocky IV and Burger King signaled the irrelevance of good film-making or fine dining. It just means there are gaps between what we need, what we want, and why we buy, and that the masses are by definition less discriminating than the niches of people with refined tastes for a particular thing.

Joel points out that the i-pod’s success involves factors other than simplicity – but this is true for all products and all things, including failures, successes, complex and simple things. This isn’t an argument in support or against simplicity’s value: it’s just a sound statement of fact – many factors irrelevant to product quality impact success.

Counter-evidence

There are many things in the world that sell well on simplicity: they’re just rarely market leaders. You can find a quality brand that tends to simpler solutions in every market, and at various price points: Bang & Olfsen or Bose, IKEA or Crate & Barrel. These are not the revenue generators Panasonic or WalMart are, but there you go. They exist as viable businesses based on (the attempt at) simplicity. Musicians like Jack Johnson and The White stripes make straightforward, “here i am with my instruments” music, and have done well by avoiding the trappings of over production. They’re not top 20 stars like Brittany Spears or Justin Timberlake, but they deliberately chose not to be.

And then there’s food: what could be simpler than the experience of fast food? McDonalds and Taco Bell even make meal deals: a single number uttered from the comfort of your car, and a swipe of a credit card, brings warm food in minutes. We are convenience junkies and literally die for simplicity, as the thousands of people who find putting on seatbelts or going to the gym too complex or inconvenient to save their own lives.

We all desperately want simplicity. But we’re so well trained to consume that we impulsively expect to buy our way there. We believe to the point of faith that we’ll be complete, or have a simple life, if only we buy the right combination of products.

The trap of visible features

The real trap that consumers are in is that we want proof for what we’re paying for, and engineers and marketers know it. They sell ease of use and simplicity on the back of every box and in every ad: but they also sell it in the products themselves, trying to show ease of use in added buttons, options and the superficials of quality.

Great features do not require user interfaces. If the engineers are thoughtful, they can add code that eliminates the need for UI, instead of adding to it. This is much harder and requires smaller egos, but a great v3 needs less UI than v2: eliminating setup, configuration, simplifying designs, automating things successfully so that users don’t even need to know of them (not just automating my interaction with things). This is much harder and requires real innovation, but is too selfless and long term a philosophy for most to swallow.

zippo.jpgInstead designers and engineers are all too happy to stroke their egos by fighting for their little do-dad, the little button, the in-product advertised feature name, Auto-this, Intellii-that, a signifier to the world for what they worked on all year. And they’re encouraged to do so by marketers and sales, as those visible things make the release easier to sell. But it’s a suckers game and after we buy these things we know it and the the designers know it too. They know it when they hold a Zippo lighter or write in a Moleskine, well crafted things they desperately fetishize: they know they’ll never make something with that much design integrity in their entire lives.

Connoisseurs of anything discern between trash and class. They know that understatement is class’s hallmark: it’s a product, person or design that knows it has substance, and does not need to go far out of its way to prove itself: its core is good. This is part of what drives the lust for Apple’s aesthetics. The trash, the wanna-be, the knock-off has to parade distractions, buttons, gadgets, and modes to compensate for its lack of core design integrity.

But who has the time to become a connoisseur before making a purchase? How much cash is the average person willing to spend for quality for something they don’t know much about? Not most of us, not most of the time. Which explains why mass market leaders are often simplicity demons: they betray the idea of good design by relentlessly abusing our ease of seduction and shoving the pretenses of good design, the magic tricks not the substance, in our smiling faces. Until we’ve been burned by a kind of product, or have never seen the real thing, we don’t think we need to look carefully at the alternatives.

Stupid word semantics

Both articles use the words simple and complex in various ways. If it takes me 30 hours of preparation to make you a cupcake, is that complex or simple? The process of creation might be complex, but the result can still be simple, and vice-versa. The semantics get messy fast.

The way out is experience: if the consumer wants to experience something complex, say a jigsaw puzzle, then the ideal design is a puzzle that provides that experience in the simplest way possible. Any challenge that wouldn’t interest me, say fighting my way through bullet proof plastic wrapping, has been eliminated or reduced.

As Mark Hurst points out, complexity is often desirable if it’s the experience customers desire. Ask a software developer or an airline pilot if they want complex levels of control: of course they do. But they don’t want complexity that annoys, or that distracts them from the experience they want. Simple design doesn’t mean brain death: it means being being as simple as necessary to achieve a great experience for a group of people, but no simpler.

——————-
If this missive wasn’t simple enough for you, LukeW has a nice summary of all the recent simplicity blogging.

Handcrafted software: Jackson Fish

jackson.jpgHillel Cooperman of Microsoft and Tastingmenu fame has started his own software company, called Jackson Fish Market. He was one of my favorite managers, is one of the few die-hard believers in good user experiences, and best of all, he’s hiring developers and designers.

Here’s how they described the plan:

The main goal of Jackson Fish Market is to build a home for passionately creative, super intelligent people who want to ship software, have impact, constantly improve, make good money, and not be screwed with

Even if you’re not looking for work, check out what JacksonFish is doing. They’re blogging the whole experience of starting a new venture, focused on great software, and it will be interesting to watch.

Book review: Dreaming in code

dreaming.jpgI was greatly anticipating Scott Rosenberg’s, co-creator of Salon, new book, Dreaming in code and was happy to get a free copy in the mail.

In short: I enjoyed the book and recommend it – it’s a good, though uneven, book exploring why software is hard to make. I read most of it in one night and finished it off in a second, and despite anything else i say, that’s an endorsement of any book of any kind.

However my take on the book is unavoidably hurt by its lead praise from James Fallows, of The Atlantic, who said ‘The first true successor to Tracy Kidder’s The Soul of a New Machine’, in reference the Pulitzer prize and National book award winner that defined the ‘computer engineering as human narrative’ genre. Kidder’s book was personally seminal and I have respect for Fallows, but it’s misguided praise, and worked to Rosenberg’s disadvantage. I don’t think his intent as an author was to write the same kind of book, and the comparisons in my mind didn’t help. However, as an author I’m ambivalent on the appropriateness, or dangers, of comparing a book based on what it’s blurbs say, so I’ll leave it at that.

Dreaming in code is three books woven into one: one of them is a narrative story of of the Mitch Kapor led project to create a new PIM application called Chandler. The other threads introduce software concepts (e.g. explaining object oriented programming and how Python differs from C++) and explores why software is hard to make. All big topics, and fun ground for Rosenberg’s curiosity and intelligence to explore. The book struggles however with keeping them together: the 3 threads are uneven, and I was often unsure where he was going, or when we’d get back to the Chandler story, the one I expected to be, based on the cover and Kidder reference, the focus of the book.

For example, the book dances between assuming the reader has tech-interests vs. being a layperson, with side threads into esoterics like Hungarian notation and Literate programming, that made me wonder. Most books in this genre don’t go that far, drawing the line around the depth of what a magazine feature article would explain: even Digital woes, a favorite book on why software fails, nails the topic without getting into construction or showing code samples.

Steven Levy’s Insanely Great, about making the Macintosh computer, or Zachary’s ShowStopper, about Windows NT, are classics in this genre, and unlike them Dreaming in code has a higher degree of difficulty: it doesn’t have a star central project at the book’s core. I would never have heard of Chandler without picking up the book. Mitch Kapor and Andy Hertzfeld, industry pioneers and legends, play leading roles which adds some star power, but they’re not the focus.

And without the natural tension of a big well known project, the players in the book feel light: the drama and passion that are integral parts of good projects aren’t there (and it’s something Kidder went to great lengths to capture). I can’t tell if that’s Rosenberg’s polite reporting, or something missing in the project itself, but the emotional commitments of people to each other, and the project, is critical to making good software, and might be the secret Rosenberg seems to seek in the book, but it’s never mentioned.

That said, Rosenberg is smart and insightful, and the book has its share of gems. Ideas from many luminaries are touched on, from Doug Englebart, Fred Brooks, Alan Kay, Richard Stallman, Don Knuth, Watts Humphrey and more. The result is a good, often charming book, that would be good fodder for a team to read together, discussing their own opinions as each chapter unfolds.

But with the rickety management example of Chandler at the book’s core, software management, as a discipline, is portrayed as an immature, misguided, geeky business: perhaps an accurate snapshot of the average team today, but not of the best. Rosenfeld doesn’t give serious context until the last 1/3rd of the book, when Joel Spolsky, 37 Signals, and Google’s theories surface as cautious remedies to the challenges Chandler faced, but the vibe is cynical, and I found myself, especially with Chandler as the example, defensively optimistic about what a good project manager could have done.

As a sweet side note, Rosenberg did uncover thought provokers I hadn’t heard before:

  • Alan Kay’s wonderful software as a doghouse metaphor
  • Linus Torvalds on how you should start large projects
  • Richard Gabriel’s passionate criticism of programming education

Rosenberg’s perspective cuts both ways: his outsider view is an advantage as he asks questions veterans and gurus have forgotten or are scared of, which paves new ground on old topics. But it you want guidance, harder critiques, or expert analysis of what to learn from Chandler, you’ll need to discuss the book with someone else, or look elsewhere.

A Chapter is available online, and it’s worth a look. Also check out the Dreaming in code website or Pre-order at Amazon.com (Out Jan 17th).

When should you take vacation? A strategy

The week between Christmas and New Years, is the worst time to use vacation. The reason is that’s when everyone else will be away. When an office is quiet even the most stressful workplace descends into a calm oasis of interruption-free time. Showing up at work on those days feels like vacation, even though you’ll be paid for it. Of course often family plans demand when you take time off, but if you have a choice you should make it wisely.

I remember when I first entered the full time working world, I was clueless about how to best use vacation, and I followed the herd. This is foolish, as here in the U.S. the annual average vacation time is a measly 13 days (Compared to Italy’s 42 and France’s 37): a pittance if you include time-off needed for weddings, complicated mid-week errands, parole violations and alien abductions. Yet somehow more than 1/3rd of Americans don’t use all their vacation each year. Yikes.

The ideal time to use vacation is when there is peak value, in your own psychology, for escape (say, when you feel creative burnout). This rarely coincides with what everyone else is doing (or in the above case, is the exact opposite of what everyone else is doing), as weekend trips with friends or sports team schedules put heavy emphasis on using Fridays and Mondays, regardless of when it is you need relief.

For awhile I found choosing periodic Wednesdays or Thursdays, every few months, was the best possible value for a spare vacation day: like a happy hour martini, they provided a dose of relief at the peak of a stress, and neatly divide up the working life into more manageable pieces. Catching a matinee, having a late breakfast and wandering my favorite bookstore, going for a short hike, or shopping in the calm of a mid-week crowd, were all low key, super mellow, high value vacation days.

Taken to an extreme, this strategy falls apart: it’d be a mistake to take vacation only at stressful events, or to dodge your responsibilities (“Hey boss, are you ready to present at tomorrow’s presentation for the CEO ?”, “Oh, didn’t I tell you? I’m off tomorrow: it’s all yours”). The goal isn’t to avoid hard work, it’s to maximize the value of time off so you’re of most use when you are actually there.

Consider these factors:

  1. When do you need stress relief the most?
  2. Are you, your friends, or your family, driving the use of your vacation days?
  3. When are other people at work on vacation or away, calming the workplace?
  4. Can you offset your own schedule, arriving at work before/after your coworkers, to make each morning a semi-vacation, free of interruptions or high stress?
  5. Can you make part of your daily schedule include time at the gym, the bar, the coffeeshop, or with friends, breaking up every day with some kind of psychological reprieve?
  6. If work is really so unpleasant that you don’t have enough vacation to survive, perhaps it’s not the vacation that’s the problem, but the job itself.

So what tips and tricks for maximizing vacation days do you know?

Thoughts on 7 days without power

Here’s my notes from the past week’s power outage experience:

  • For all the fears and whining, I thought often, even when cold and tired, that this experience was a cakewalk as disasters go: 1.7 million without power for a few days is a trifle of suffering compared to any recent tsunami, hurricane, volcano, genocide or revolution. You can switch power back on. Frustrating yes. Devistating, no. It seemed Seattle lost sight of this: we’re babies. This was no New Orleans or Darfur.
  • First two days were scary: no gas, no wood, no ice, no stores open. It’s unsettling when the magic trucks that bring sustenance stop coming: it’s a smack in the face reminding us how dependent on distant forces modern lives are. By Saturday stores opened (though wood and gas were gone) – Home Depot proved the best source of firewood, as even if out of bundles, you could buy 2x4s.
  • KIRO 710 AM Radio was fantastic – They provided 24 hour coverage for 4 days straight, replacing talk radio with storm reports, live interviews with officials and powerco reps, and call ins with people giving tips and advice on where to find gas, wood, etc. It was an awesome resource, and they provided a great public service: heroes of the experience.
  • The worst of people. KIRO reported every 10 minutes on the 100s of thousands of folks without power, but that didn’t stop angry callers from claiming how they had been abandoned – crisis makes some people very small and selfish: it was depressing to listen to – suffering doesn’t require having someone to blame.
  • On the other hand, we met many generous neighbors who volunteered time to clear the 100ft tree from our driveway with gas chainsaws, and offer wood and gas.
  • My sleep cycle improved. With no electric lights I easily woke at first light, and went to bed earlier than usual. Jill made the connection and it makes sense: all the computer and TVs screens are likely contributors to my periodic insomnia.
  • I did not miss TV or e-mail. We charged cell phones in the car and that was as high tech as I got. Later on I’d try to write in coffee shops, but mostly failed.
  • It took 2 days to work out the daily chores: starting the morning fire, making breakfast, dousing the fire, walking the dogs, negotiating who would be home by 4pm to start the fire up again (so the room would be warm by 7ish). Once we had the system it wasn’t that hard.
  • There is an art to fireplace cooking: it’s harder than camping as there is a shallow roof over the fire, and we didn’t have grills for the fireplace. The secret is you can’t warm the room and cook: if you cook, you want even temp, if you want heat, you want big flames (I know – duh – but it took me 2 days to sort it out). We tried charcoal in the grill and it worked fine, but log ambers worked just as well. Like camping, lots of soups, chilis, and tin foil wrapped knishes made up many meals.
  • Food was easier in the cold – first few nights were ~30 degrees, so we could keep food from the fridge on the deck. But it warmed up later and we had to trash much of the food. We tried to make ice one night (for the fridge & freezer), leaving out small water filled containers, but it didn’t quite get cold enough.

Lessons:

  1. A pre-storm trip to the store would have done wonders. Refreshing batteries, wood, toping off gas tanks, etc. would have made this much less stressful.
  2. Neighbors matter. Oddly we met more neighbors through this experience than in 7 years of living in this neighborhood (little else forces seattle-ites out of their homes). Pooling resources and skills makes life much easier in a near crisis (duh, but I’d forgotten).
  3. Gadgets are over-rated. I knew this already but had it proven – all I needed was an AM radio, fire and some books and I was happy. With the extra work I needed less entertainment, not more, and was happy just to sit and listen or read.
  4. I have no idea how power works. I spent more time staring at the various electronic bits hanging destroyed from trees and wondered what they all did. What does a transformer do exactly, and why are power lines above ground, not below? I have no clue. I’m trying to find a book on power grids and how they work, suggestions welcome.


The return of power

Power came on late yesterday. We called Puget Sound Energy, our power that morning are were told we wouldn’t have power until late Friday night – but Thursday, ~4pm, the answering machine picked up when I called and I raced on home.

Thanks to all who dropped kind and humorous notes of support or mild mockery – definitely helped get through this.

Death by Christmas Music

I’m on day 8 without power – I’ve become a local geek refugee, fluttering from coffeeshop to coffeshop in search of quiet places to work.

I’ve discovered the neurotic edges of my writing habits: I can’t write a word if I people are talking nearby, fiddling with newspapers within eyeshot, or if there is bad music playing overhead – escpecially the sonic evil that is bad Christmas music.

There is nothing festive about the relentless attack of dull, trite, treekly trash that passes for Christmas music in most stores and cafes. Who thinks this is fun? And do we really need to play it continually, on repeat, unless the goal is to get people to leave (or confess their sins). Can’t we mix it in? Like 1 holiday tune for 2 regular ones?

Or perhaps in the infinity of alternative and world music, there’s something more authentic than cheezy retreads of retreads of Christmas standards?

Storm Survival: Day 6

Today is the first I’ve had access to anything resembling wireless – Day 6 of the Worst windstorm in Seattle in a decade has been less than fun.

Was finally able to get gas (power has been out, meaning gas pumps don’t work) this morning, and the downtown of Redmond, my nearest town, is finally online. My current techno-salvation is Starbucks. Unlike my home on Union Hill, in the woods just past Redmond, where I still can’t see a single house with power.

For fun, here’ s a photo of what I found on my driveway Fri. morning:

stormdec06 058.JPGstormdec06 119.JPG

If I was supposed to return a phone call / e-mail / or do something for you, but didn’t, now you know why :)

Jill, the dogs, and myself are doing ok – hopefully we’ll have power (and some normality) back soon. If nothing else, experiences like this sure hand you back some perspective on technology and innovation (ha ha!). More later.

Cell text messages = the telegraph?

One great read from the innovation book research was Tom Standage’s The Victorian Internet. Among other great histories inside is coverage of the early telegraph, which includes this bit of trivia. Early telegraphers had shorthand, much like today’s cell phone messages, to make best use of the characters sent.

Here’s some of the examples listed:

I I = I am ready
GA = Go Ahead
SFD = Stop for Dinner
GM = Good morning
1 = Wait a moment
2 = Get answer immediately

Despite all our bandwidth and fancy protocols, when it comes to efficiency, we’re right back in step with the 19th century.
Makes you wonder why we think of progress as a straight line when it so often seems more like a spiral.

I want your photographs

With the first draft done on the innovation book, it’s now time to enlist bright creative minds in helping the book be all it can be.

I’m forming a small, elite photography squad to help find fun, clever, amazing photos to appear in the book. Like my first book (collage below), I need strong images to complement the book’s ideas.

collagesmall.jpg

If you’re interested, leave a comment below, include a flickr link if you have one, or follow up directly and I’ll give you the details on how to contribute.

Be warned: I can only pay you in praise, admiration, and chocolate chip cookies.

The mistakes of having a VP of innovation

Hypothesis: if ever a VP of something is created, perhaps a VP of quality or a VP of sarcasm, it means three things:

  1. The company is failing at that activity.
  2. The executives in the company are failing to do their jobs in leading that activity in their divisions.
  3. The company will continue to fail at that activity until a VP dedicated to that activity is no longer needed.

No great company in history, from Amazon to Google, to Apple, began with an innovation team. That word innovation was almost never used early on, as every employee simply built things to solve problems. Innovation, however you define it, in these early efforts isn’t prevented by the lack of a VP in charge of it. Finding new ideas happens simply because people need those new ideas to do their jobs. Just as there’s no VP of Breathing or Thinking people do these things just fine, as needed, to get through the day.

Only when a company has matured and slowed does its culture become conservative and tied to the status quo. This is when the notion of a VP for Innovation becomes even comprehensible. It’s no surprise that the only companies with VP roles focused on innovation are large and slow ones. The most sensible response to to change a company culture is to put people in true leadership roles, managing the major products or services at the center of a company’s business, that are leaders of change. Only by example do cultures progress. But that would require conviction and tough decisions from a CEO about increasing experimentaton, or re-organizing the complany, both highly political and with some risks. However inventing an executive for innovation out of thin air is easy and far less political: nothing much has to change.

These VP of Innovation roles are usually divorced from actual product responsibilities. Somehow from the side, without actually making any products, they are supposed to change the product making culture. How could this work? Common titles include Chief Innovation officers, and VP of Innovation, but they are not the same kind of executive that has to actually ship anything to the world. They also rarely  manage R&D groups that develop specific ideas. Instead they’re supposed to encourage others in the company to be more innovative by what, asking nicely? Throwing innovation parties? I don’t really know (but it’s not clear they know either). Their one certain achievement is they let a company claim they are innovative because they have an “executive” with that word in their job title that clients and the press can talk to.

Like my experience with the Microsoft Values Group (see side story below), it’s flawed to attempt culture change from the side. And I suspect any hard working product team who receives a phone call from a VP of Innovation will be confused as to what their credibility is: “Who are you to tell me what innovation is, or how to do it?” Unless the VP of Innovation has a stellar track record of managing teams that released great products, what credibility can they have? And if they do have that track record, why aren’t they leading by example on an actual product?

The only sensible angle for a VP of innovation to take is to dedicate themselves to eliminating the need for their role (Point #3 above). This doesn’t mean there is no value, only that a healthy creative culture wouldn’t require a VP of Creativity, any more than a VP of Breathing. The VP’s goal then is recovery to health: to help teams rediscover the environments and attitudes they once had about new ideas, reintroducing risk taking and creative dialog, and then getting out of their way. Their job is to use their executive rank to publicize teams that already have healthy systems of innovation in place, and use show others in the company how to learn from their example.

VPs of innovation should have expiration dates. When the company returns to a culture where innovation is natural, or at least comprehensible, the need for a VP of innovation has been satisfied and they should quit and end the role. If innovation doesn’t become a natural part of the environment by the expiration date, then that VP can’t say she’s succeeded, as her role in a progressive company, wouldn’t ever be necessary.

[The kind of a culture a leader who wants creativity must create is explored in Chapter 7 of The Myths of Innovation]

[Side story: Before leaving Microsoft in ’03 I gave a talk titled How not to be stupid: a guide to critical thinking. The title was intended to make people laugh, as humor is a large part of thinking well. Afterwards the director of the Microsoft Company Values Team, a team I did not know existed, contacted me. I was mystified that a team existed with the job of promoting the company’s values to the company. It made as much sense as the suburbs telling the city how to be urban. He suggested I change the title to something less negative and more positive, like “How to be Smart”. This literal, but entirely boring, approach defeated the central premise of what I was trying to say. And his attempt to tell me what the values were had the opposite effect: I considered doing the talk again with a more provocative title. The company I’d known welcomed the free expression of challenging ideas. Perhaps this was just writing on the wall as I left the company months later.]

Book update: inside scoop + 1st draft complete

10 months down the road, the first draft is in the bag.

Although I’ve written nearly 40 posts about innovation here, I’ve kept quiet about book details for sanity reasons: I don’t know how to write the book, and write about writing the book, without frying my small brain.

So as thanks to all you who have helped out so far with comments and questions, here’s the inside scoop:

The Inside scoop on the innovation book

The book demystifies the history of great innovations. In over a year of research I’ve uncovered many popular beliefs about innovators, discoveries and inventions, that are dangerously inaccurate: trying to emulate these false ideas sets up todays innovators and big thinkers to fail: we’re chasing romance, not reality. For example:

  • Newton did not discover gravity by watching apples.
  • Gutenberg did not invent the printing press (Nor did Edison invent the light bulb).
  • Eureka and breakthrough moments are overrated.
  • Technological progress is not guaranteed (todays innovations are not necessarily better than those they replace).
  • Good ideas rarely win on their merits alone.

The book attacks gaps between what we think we know, and what the truth is, about how innovations happen. It calls out these myths, through taunts, name calling and silly faces, showing the reader how to disarm and overcome them. And then the book goes after three things: 1) investigating why these misconceptions are popular, 2) using history to explain the truth and 3) provide lessons based on how innovations in business, technology and science really happen.

What’s next?

I’m deep in revision on draft 2: rereading, rewriting, and other writerly fun. A small cabal of reviewers have given feedback on draft one, and I’m using that to guide my way.

I’m currently searching for photos for the book – I need good sources of archival photos from the history of technology (although I’m open to other photo concepts for the book). If you have suggestions, or know a good book photo editor, contact me.

If draft 2 goes well, we may still be on track for a late Spring 2007 release. Stay tuned.

Questions? Suggestions? Or take the easy way out, and throw me some love on nailing draft numero uno! (Hint/plea: a simple “go Berkun!” goes a long way towards writing morale)

Why smart people defend bad ideas: the mailbag

To my delight, every now and then the fine folks at slashdot or lifehacker mention an essay of mine, and waves of people swing by, read something, and send feedback mail through the contact form.

I respond to as much of the interesting and thoughtful as I can – but it’s the internet, and some of it’s creepy, incomprehensible or just plain bizarre. I don’t fully know how to respond to many of these little notes I receive.
So for fun, here’s some highlights from the mailbag for the popular essay Why smart people defend bad ideas:

“You sir, are clearly a case of bad person defending a bad idea. You should practice what you preach before preaching to the choir.”

“THIS IS AMAZING. So MANY CLEVEr Things. SO NOW CAN YOU TELL ME HOW TO DECIDE WHAT TO DO WITH MY PARENTS?”

“I liked the essay but smart people are just better, right? So why shouldn’t they just defend whatever they think is best?”

“…loved this. Really loved it. Made me want to get a shotgun and shoot all the asshats.”

“Hey. If you’re so smart why don’t you know that spark plugs can’t cause fires? eh? Tell me that tough guy. You suck rat ass. I want the 5 minutes it took to read your turd back.”

“I printed this in big font and slid it under the doors of the executive floor. But it had no effect. What do I do now you think? Bigger fonts?”

“Perhaps you can help with this. I’m dating two girls at the same time, and keep thinking I want one, but then the other… well I don’t know how to LOGICALLY choose. Write an essay on this! yes!”

“How much can I pay you to stand in my boss’s office with a megaphone and read this essay every time he opens his mouth?”