New essay: Creative thinking hacks
Here’s a short, fun, hack-centric essay on creative thinking. It’s loosely based on the course I taught recently at the University of Washington.
Here’s a short, fun, hack-centric essay on creative thinking. It’s loosely based on the course I taught recently at the University of Washington.
The fine folks at Google have posted two of the lectures I’ve done at the Google campus over the last two years. Each is about an hour long.
Lessons from the browser wars (youtube)
The myths of innovation (youtube)
Thanks to my hosts at Google, Chad Thornton, Ken Norton and Robin Jeffries. And of course the tech folks who video taped, edited and posted these things.
In case you haven’t noticed, my essay how to detect bullshit hit the top 10 on digg today, and the site is struggling to keep up.
The fine folks at duggmirror have a mirrored copy available.
I don’t write about it often but I’m a huge film fan. For awhile now I’ve known about the works at Overcast Media, but they’ve been in stealth mode, under the radar.
Finally, with this coverage by the Seattle Times, I’m free to tell you: If you’ve ever wanted to create your own DVD commentary, or make commentaries for TV shows or other media, you’re in for a pleasant surprise.
Roger Ebert and others have talked about this idea for years, and finally it looks like someone is making it happen.
Their new beta release is invite only – but you can sign up for an invitation right now.
(Disclosure: Richard Stoakley, Overcast Media’s CEO, is an old friend. He had the office across the hall from mine at Microsoft on the Internet Explorer team, circa 1997)
I’m no brainstorming zealot – there are many ways idea generation techniques out there and they all have their place. However now and then brainstorming, as a concept, gets attacked, which is almost as ridiculous as a war on terror. Recently Marc Andresen had a short post called Brainstorming is a bad idea that deserves a response.
Rarely discussed factors that impact the value of brainstorming:
I’ve yet to see a single study that controlled for, or even mentioned these factors – which is entirely unfair to evaluating brainstorming, or any creative thinking technique. If I’ve missed some research you know of, please leave a comment.
Further reading:
(Thanks to Gernot Ross for the tip)
The book is still getting some great buzz, and I’m on the road much of the next few months talking about the book. Here are some upcoming gigs:
July 25, OSCON, Portland, OR
August 10, Amazon.com, Seattle
August 14, Whitepages.com, Seattle
August 24, Expedia.com, Seattle
Sept 21, Management Week, SpiderProject Inc, Kiev, Ukraine
Sept 25-29, Web Directions South, Sydney, Australia
Oct 21-23, Adaptive Path’s MX-East, Philadelphia, PA
Nov 5-8, User Interface 12, Cambridge MA
If you’re in Seattle and you have a possible venue for me to speak at, let me know.
I’m working w/O’Reilly on an updated 2nd edition of The art of project management.
We’re brainstorming ideas for how to improve the book, but agreed to start with you folks. How can we improve the book? Here are a few ideas, but feel free to add your own.
If you have longer suggestions/gripes or want to help with the 2nd edition, leave a comment.
Hi there. If you’ve noticed I’ve been running all over the place doing talks, interviews, and magic tricks to promote the new book. Well my plans for this summer are as follows: stay home!
Wanted: Venues for a lecture on the Myths of Innovation
When: This summer / early fall
Why: I’m a great speaker, it’s a great book and it’s good for you!
Where: Seattle, eastside, wherever you are
If you work somewhere that has an invited speaker series, or some other way of drawing a crowd, let me know. I can’t promise I’ll speak everywhere, but I’ll give it my best shot.
If you want a flavor of what my talks are like, here are sample videos of me in action.
I’ll be talking about topics from the Myths of Innovation at OSCON (Open Source Convention) on July 25th at 5pm and at Powells Technical bookstore at 6pm on Thursday July 26th.
If anyone wants to meet-up and grab lunch or coffee while I’m in town, leave a comment. Hope to see you.
There are two excellent posts on Dare Obsjano’s blog about innovation in big companies. The first is on innovation lessons from Google, the second on Stupid things big companies do. Two worthwhile reads.
(Thanks to Scott Hanselman for the tip)
FOO Camp saw the power combo of two different social software technologies: Crowdvine, a linked-in type system for pre & post conference connection making, and pathable (which I first saw at Bizjam) for guiding people in finding folks to meet.
Here’s a short review:
It works and its fun. Bravo! The premise is simple: weeks before the event log in, list some tags, and ping people you might know attending the event. It’s easy to find people who share your interests (via tags), read their bios, and ping them if you so desire. There’s a comment system so you can leave notes which was surprisingly active, and public: going to the home page for the site shows all activity, from blog posts made by an individual, to comments sent or received. Anyone can jump in on the threads which was interesting (and I wondered if it’d work for a 500 or 1000 person conference).
At a minimum crowdvine helped me match faces to names before the event which is a big deal for networking or meeting specific people. And it was voluntary – had I been annoyed or less social, I didn’t have to participate at all.
Pathable provided the event badges, fueled by their social matching system – based on tags and other magic they grouped individuals by interest (represented by the color of each badge and the color of the crowdvine profile, see photo above) and created the surprisingly popular matches/opposites lists for every person.
Much like at bizjam, the badges got people talking. It made introducing people to each other much easier as being someone’s opposite or match was an easy way to start a conversation.
Gripes:
Only problems were mild integration issues. There was a wiki for FOO that didn’t integrate with anything else, a photo wall, with tagish Q&A, at FOO that had different photos for people than crowdvine, little things like that that I’m not sure need to be fixed. Someone needs to do a user experience analysis on how many different places and systems ask for personal/social info and check that any redundancies are useful or fun in some way.
After the event I noticed it was possible for me to track what sessions I’d been to in Crowdvine, but wasn’t sure why it was worth the time – perhaps to follow up with people I’d met but didn’t grab their contact info? Not sure.
Summary:
Not sure how much these folks charge, but smart conference organizers should be hiring these folks. Conferences talk the talk about connecting people and building networks, but rarely do anything to facilitate it. Crowdvine and pathable are real tools to help make that stuff happen.
Watching fireworks last night, I wondered about the distance between modern July 4th celebrations and what we’re actually celebrating (more ranting on holidays here). In my lifetime I don’t remember any hint of recounting what happened or why at any July 4th event – it’s just a BBQ, beers and fireworks – that’s the entire substance of the day as far as I can recall. Which is great fun, for sure, but shallow in light of what happened and why.
I asked folks around me when the last time they read the Declaration of Independence or the U.S. Constitution. No one could remember. Few knew they’re so short – 1300 and 7600 words long respectively (about 15 pages) and can be read easily in 15 minutes.
I woke up this morning and read them both. They’re easy reads and I wish somehow reading these things would be part of the July 4th tradition. Can you rally a nation in 1300 words, or define a government in 8000? Now that’s writing.
References:
(Photo by Nobihaya)
No matter what my expectations are for O’Reilly’s annual FOO camp, an intense social/geek/intellectual weekend run by my publisher, O’Reilly Media, they’re always surpassed in amazing ways. Unlike any other conference type event, I leave with a head full of ideas to chase and renewed passion for hunting them down.
I waited a week to write something up to see what stood out after things had time to settle. This year my thoughts were about what other events might learn from the success of FOO – here’s my short list (including some hard to avoid for narrative clarity name-droppings):
Memorable moments:
It was a thrill to be there again and I hope to be invited back.
Background on FOO:
This is a twist – as much as you’d think I should be interviewing him, Guy is a fan of the Myths of Innovation and interviewed me for his site.
This week I’m being interviewed on The Well by Scott Underwood of IDEO and other Well members about The myths of innovation.
You can read the conversation as it develops here and also submit your own questions and comments by e-mailing inkwell at well.com – just mention my last name in the subject line.
Hey folks – apologies if you’ve had problems accessing the site. The last blog post on asshole driven development was a hit. I’ve had more traffic on that then anything I’ve written in history.
If you want more commentary and painfully funny methodologies there are additional comment threads on the three major drivers of traffic: Digg & O’Reilly Radar, And Reddit.
Tiff Fehr has put together an analysis of the different methods and comments to date. Worth a look.
There are still about 120 comments in the queue (out of almost 400 total) – if yours doesn’t get posted, please don’t call me an asshole :) Many of them were redundant, bizarre or beyond my level of comprehension. They’ll all get read, but at 100+ comments I’ve got to filter some stuff out.
Not sure which of you got the run going, but thanks to all who passed my writing around.
One highlight of my research in innovation history is the story of Barnes Wallis and the bouncing bomb of WWII.
In short: The Allies needed a way to destroy Nazi dams and no ordinance of the time was sufficient for the purpose. Barnes developed a way to drop a bomb, on water, several hundred yards from the dam, and have the bomb, weighing several tons, bounce (that’s right) it’s way on the surface until it reached the dam wall.
It’s an amazing story of technology, inspiration, frustration, politics, persistence and eventual success.
I watched it first on the PBS Special Secrets of the Dead, but you can watch parts of the Dangerous Missions series about the bomb on Google Video here. There’s also a feature film from 1954, and rumors (mostly dead) of a Peter Jackson produced remake.
One handy technique I learned years ago at Microsoft was the Rude Q&A (RQA). Whenever we had a major launch, we’d start preparing by writing a document that listed all of the difficult, unfair and perhaps rude, questions we’d rather not be asked, but might come up.
We’d work with PR to draft it and distribute it to anyone who was talking to the public or with journalists. It forced us to think through our message, improve our thinking and at times even realize ways to make the product better.
Why do this?
When to do it
How to create a RQA
[revised and edited 8-16-16]
[Since this was originally posted commenters have added 100+ addition methods – see the comments below. There’s more commentary on reddit]
The software industry might be the world’s greatest breeding ground for new systems of management. From Agile, to Extreme Programming , to Test Driven Development (TDD), the acronyms and frameworks keep piling up. Why?
Some say it’s immaturity: that software is still a young industry and all the change is the path to some true fundamentals. Others say it’s because software people like making things up and can’t help themselves. Well I say this: if we’re going to have dozens of models we may as well have some that are honest, however cynical, to what’s really going on much of the time. There is a happy list of these I’m sure, but this is the cynical one.
Asshole-Driven development (ADD) – Any team where the biggest jerk makes all the big decisions is asshole driven development. All wisdom, logic or process goes out the window when Mr. Asshole is in the room, doing whatever idiotic, selfish thing he thinks is best. There may rules and processes, but Mr. A breaks them and people follow anyway.
Cognitive Dissonance development (CDD) – In any organization where there are two or more divergent beliefs on how software should be made. The tension between those beliefs, as it’s fought out in various meetings and individual decisions by players on both sides, defines the project more than any individual belief itself.
Cover Your Ass Engineering (CYAE) – The driving force behind most individual efforts is to make sure than when the shit hits the fan, they are not to blame.
Development By Denial (DBD) – Everybody pretends there is a method for what’s being done, and that things are going ok, when in reality, things are a mess and the process is on the floor. The worse things get, the more people depend on their denial of what’s really happening, or their isolation in their own small part of the project, to survive.
Get Me Promoted Methodology (GMPM) – People write code and design things to increase their visibility, satisfy their boss’s whims, and accelerate their path to a raise or the corner office no matter how far outside of stated goals their efforts go. This includes allowing disasters to happen so people can be heroes, writing hacks that look great in the short term but crumble after the individual has moved on, and focusing more on the surface of work than its value.
I’m sure you’ve seen other unspoken methods at work – what are they?
Please add to the over 200 reader suggested methods in the comments.
A great interview with Anthony Bourdain about managing and leadership. I mention Bourdain’s book, Kitchen confidential in The art of project management. But this interview goes all out on the similarities between how pro kitchens work and how teams work.
“Every kitchen has one evil genius who’s tolerated—someone you turn to when all else fails—a rule breaker, a scamp who’s willing to make a hard and sometimes unlovely decision for expediency. There’s actually a name for this person—the débrouillard, the person who gets you out of a jam.”
Management by Fire: A Conversation with Chef Anthony Bourdain