Why brainstorms need at least 60 minutes.

We’re in the middle of a redesign for Kindling. It kicked off several months ago, motivated by some significant new features we’ll be rolling out later this year, and with the redesign comes a frenzy of activity. There are implications for sales, direction and (obviously) the team of developers and designers who embrace the vision and bring it to life.

How do we get more of THIS?

As a result of all this activity, we find ourselves squeezing important decisions into 30 minute meetings. Unable to bear entire days spent in conference rooms, we cheat and schedule quick half hours. But this is not working.

As proof, a 60-minute brainstorm last week on a proposed design for the new Kindling. After spending several weeks picking at it when we had five minutes here, twenty minutes there, we got in a room and projected the design on the wall. With the luxury of 60 full minutes, we allowed ourselves to circle the design and some fundamental issues for the first half. And then, incredibly, the knot came undone when we passed the 30 minute mark. Sufficiently warmed up, great ideas were flying until finally, exhausted, we leaned back in our chairs to admire our work.

It was so good.

This theme, that of allowing time to push past pleasantries during a brainstorm, continues to appear on a daily basis. The easy part is identifying the solution: dedicating more time to the creating process. The hard part comes in finding and making the time to do so.

About the Author

Jen is Kindling's Product Manager, though she also contributes to the team as a UX designer. She plays traffic cop to the feature requests, hopes and dreams that the world has for Kindling. She is also a Director at Arc90. She loves her job. View all posts→

Leave a Comment