Comments on: 7 ways designing in public can improve your business

By: Beta Alfa » Blog Archive » Noterat 2009-04-11

Beta Alfa » Blog Archive » Noterat 2009-04-11 — Sat, 11 Apr 2009 04:00:35 +0000

[...] 7 ways designing in public can improve your business – Bokardo [...]

By: acne treatment systems

acne treatment systems — Fri, 27 Mar 2009 20:25:57 +0000

Awesome. Thanks for mentioning about this, designing in public is great. I also agree with Jeremy’s comment.

By: paydayadvances

paydayadvances — Wed, 18 Feb 2009 14:53:46 +0000

Good steps. Especially first) Thanks for information.

By: Monday, January 19, 2009 — shiner.clay

Monday, January 19, 2009 — shiner.clay — Thu, 12 Feb 2009 20:48:51 +0000

[...] 7 ways designing in public can improve your business [...]

By: Johnny Holland - It’s all about interaction » Blog Archive » Design in the open: baring your wireframes in public

Wed, 11 Feb 2009 18:00:06 +0000

[...] Porter’s blog entry for a full explanation of the 7 [...]

By: What’s wrong with this picture? « Pintarget

What’s wrong with this picture? « Pintarget — Mon, 02 Feb 2009 20:25:48 +0000

[...] was fascinated to read more about this on Bokardo.com. Companies like 37signals use their followers and communities to [...]

By: Josh

Josh — Fri, 09 Jan 2009 19:54:05 +0000

@Dave: thanks for adding that…I like the grey box comps!

By: Dave Tufts

Dave Tufts — Fri, 09 Jan 2009 14:47:13 +0000

We were getting over-aggressive in flattening the architecture, basically moving all pages up to a single level. Dan from Raka suggested that we move our bios below the About Us page, instead of having top-level pages for About Us and Team. We did. We also got great feedback when we posted grey box comps.

By: BrianOberkirch.com – Sundries

BrianOberkirch.com – Sundries — Fri, 09 Jan 2009 12:59:47 +0000

[...] Porter reprints a great note from Garrett Dimon on designing in [...]

By: Josh

Josh — Fri, 09 Jan 2009 11:31:57 +0000

@Tiff – awesome! That’s a great example of how designing in public not only explains what you’re doing, but helps others explain it to even more people. And I bet that many folks have a problem with “out of the box” type issues…can this product really do what *we* need it to do? Talking about the design publicly would certainly open those communication channels much more than not.

By: Josh

Josh — Fri, 09 Jan 2009 11:30:06 +0000

@Dave thanks for mentioning your experience doing this. I actually remember those blog posts! Can you tell us what idea the commenter had that you incorporated into the imarc web site?

By: Tiff Fehr

Tiff Fehr — Fri, 09 Jan 2009 07:20:23 +0000

To add another aspect to the benefits of public designing, Garrett’s posts about the design and features of Sifter gave me enough detail lobby my colleagues to adopt it. Watching the product evolve let us consider how it would fit our workflow and needs in greater detail than bullet point features. The posts even let us help shape the product to fit. It was much better than worrying if the product would fit our detailed needs out of the “box”.

By: Dave Tufts

Dave Tufts — Fri, 09 Jan 2009 02:44:13 +0000

Agreed - designing in public is great. 18 months ago when my firm redesigned our site, we wrote about each step as it was happening. The end results was a ten-part blog series starting here. After posting IA ideas in part 3, one of the commenters suggested a great idea that we incorporated. Like Garrett said, putting the process in the public realm made us really think through and justify each decision. But mostly, I agree with Garrett's first point: it was just more fun.

By: Jack Christopher

Jack Christopher — Thu, 08 Jan 2009 22:44:40 +0000

It’s also a good exercise to ask the contrary question, what are the reasons we *shouldn’t* design in public?

Or more exactly, in what situations is it better to design in private?

I can come up with a few answers to that, but I want to design *my answer* in private; We can test a more general case of this theory right now.

By: Valgeir Valdimarsson

Valgeir Valdimarsson — Thu, 08 Jan 2009 18:15:03 +0000

Related: an interesting post from Mark Boulton Design about the ongoing and very public redesign process of Drupal.org