4 ms·

While I believe that it works for you, your "early product design" process doesn't sound anything like interface design. It's just a subset of branding. Design

While I believe that it works for you, your "early product design" process doesn't sound anything like interface design. It's just a subset of branding. Design is solving problems, not just choosing what the buttons on your website will look like before you have your product or any kind of context (the order of which sounds backwards to me.) > And it’s not all about looks, you know. You say this, and maybe I'm missing the point of your post, but you continue to describe how this process is entirely about how things look. Additionally, I have an issue with this: > Over time, you’ll build up a collection of “liked” work that you can show to any designer to give them a concrete idea of the style you like. This sounds like a horrible idea. Any decent designer out there knows that Dribbble exists and doesn't need you to point that out to them. They likely have their own "style" (if we're reducing "design" to just aesthetics for the purpose of discussion) and won't like you showing them what "style" you want them to adopt. Their job as a designer is to solve problems, not make things look pretty in Photoshop according to your taste parameters. Everything they produce should adhere to your brand guidelines, but that's it.

ThomPete 13y ago
The job of the designer is to solve problems and help their client maintain their identity. It does not matter whether the designer have their own style. Most aren't hired for that and shouldn't be.
wlesieutre 13y ago
I think the takeaway is that it lets developers be the designers. Most programmers I know are pretty good at solving problems, but they don't always have an eye for visual details aspect of it. The style guide gives them a framework to work in, and can hopefully prevent a UI atrocity. Maybe hiring an outside designer to do the whole app would get you better results, but if you're going to toss all of that as the app changes, it might not be worth the expense. Assuming your devs aren't bad at user interaction stuff, this gets you most of the way there at a small fraction of the cost.
- goldvine 13y ago
  Very well said. Thank you for jumping in.
harlanlewis 13y ago
Articles like this one come up regularly, so let's not discount the method just because the word "design" doesn't mean anything. "Design" can mean anything from Illustrator graphics to market research, interaction design, or even implementation. It's a dangerous trap to assume skill and experience in some of those areas equates to skill and experience in all of them. The author of this article has clearly identified the intersection of need/acceptable cost, he just happens to be using an excessively generic term to describe the role. It's still a valid model, especially if the team already has talented product thinkers who are capable of following a style guide.

ThomPete 13y ago

The job of the designer is to solve problems and help their client maintain their identity. It does not matter whether the designer have their own style. Most aren't hired for that and shouldn't be.

wlesieutre 13y ago

I think the takeaway is that it lets developers be the designers. Most programmers I know are pretty good at solving problems, but they don't always have an eye for visual details aspect of it. The style guide gives them a framework to work in, and can hopefully prevent a UI atrocity. Maybe hiring an outside designer to do the whole app would get you better results, but if you're going to toss all of that as the app changes, it might not be worth the expense. Assuming your devs aren't bad at user interaction stuff, this gets you most of the way there at a small fraction of the cost.

goldvine 13y ago
Very well said. Thank you for jumping in.

harlanlewis 13y ago

Articles like this one come up regularly, so let's not discount the method just because the word "design" doesn't mean anything. "Design" can mean anything from Illustrator graphics to market research, interaction design, or even implementation. It's a dangerous trap to assume skill and experience in some of those areas equates to skill and experience in all of them. The author of this article has clearly identified the intersection of need/acceptable cost, he just happens to be using an excessively generic term to describe the role. It's still a valid model, especially if the team already has talented product thinkers who are capable of following a style guide.