conversation is an engine

Engineers aren’t the only ones who love to correct you

I’ve been repeating myself recently to different people and groups within my client’s shop.

I’ve been saying aloud the oral version of a dumb sketch. I’ve been telling and retelling the story of how I thought one thing but then in conversation with different experts, came to see what I thought was really not so at all, but something different. I know this is terribly abstract and I apologize: We’re working on a new proprietary idea at the moment, so I cannot be too specific.

I thought X was like Y. But it turns out that X is very like Z. And when I tell that story—of trying and failing and trying—my listeners get it. They learn something. They jump to Z and each gets pretty excited about Z—they had not seen Z before. But now that Z is named and out there, Z may just change everything (and not in a breathless marketing-hype way, but really change how people move forward in this particular industry) (Which I cannot name.) (Sorry.) Each mini-audience put the pieces together and then leaps forward in a way my didactic, linear, word-driven paragraphs did not succeed at.

The point of a dumb sketch is to be not-finished. A sketch is the opposite of the heavily produced diagram or slide. The “unfinishedness” of a sketch is the very crux of usefulness as a communication tool. By being unfinished, the sketch invites collaboration and improvement. And people seem to not be able to turn away—at least from the oral version. Failure is built right into my story, and who can resist gawking at a car wreck?

Maybe this is an engine behind John Stepper’s notion of “working out loud.” Maybe this is a key to how we collaborate with each other. We already do this with friends and family, but what if we extend our try-fail-try circle to include many others?

###

Dumb sketches: Kirk Livingston