• Categories


    • Culture
    • Design
    • Marketing
    • Podcast
    • Twitter


  • Projects


    • About
    • Contact
    • E-Mail Subscription
    • ROOM Installation
    • Art Show Down
    • MUSES Book
    • France Book
    • Love Drug


  • Tags


    advertising art Blogging brand branding Case Study CGM cloud CRM customer satisfaction Design Engagement Applications Facebook health humor identity Marketing 2.0 Mobile MySpace OpenID phtography Product Design promotion prototype psychology public relations research roadmap sales SEM SEO social media social network Social Networking strategy Sustainability touchpoints Twitter UGC user experience viral visualization web web design WordPress


  • Archives


    • August 2010
    • April 2010
    • February 2010
    • January 2010
    • December 2009
    • November 2009
    • October 2009
    • September 2009
    • August 2009
    • July 2009
    • June 2009
    • May 2009
    • April 2009
    • March 2009
    • February 2009
    • January 2009
    • December 2008


« Previous
Next »

A Prototyping Conundrum

A good friend and I are working on an invention that we believe will solve a problem faced by urban bikers. I can’t say much more than that, but that’s probably all you really need to know in order to consider my prototyping conundrum. It deals with a common problem, I believe, that arises when prototyping to test your concept versus prototyping for manufacture.

When should we be thinking in terms of the final (manufactured) design and when should we be thinking in terms of the design that is required to test and get feedback on the concept? You see, we’re planning on doing a short run of the device (say 100 units) so we can do some testing and it doesn’t make sense to have them cast. Following this, we have to change some elements of the design to accommodate manufacture by other means.

Should we have two separate prototype paths?
In reality, the details aren’t THAT different but it can be confusing because we haven’t been good as saying “with respect to the testing prototype, I think we should …” My gut tells me that we just need to add some structure to our process to resolve this issue for now. But, you do have to wonder how to balance your time and effort between the two prototypes.

Is it a marketing issue?
Some of the details in question are purely aesthetic or at least partially aesthetic and it’s unclear how much weight to give them. Though clearly, that’s more of an issue with the manufacturing prototype. There’s also the issue of cost of goods sold and how our choices will effect that. Our designs have evolved quite a bit so we haven’t had the chance to speak with potential manufactures about the impact of our choices. My partner is an engineer, but still we don’t really have a sense of if we’re talking about dollars per unit or cents for some of our choices.

When should we think about cost? For me, and with regard to this device,  it boils down to the fact that no matter what we do our device will cost significantly less than other devices in the same category …. so I’m not really worried about cost too much at this point. Maybe that’s wrong, but it seems to me that we should come up with the “best” solution and try to control costs from there. I guess this stems from my belief that people are willing to pay for great products and that pricing is in large part irrational (refer to Predictably Irrational if you want more on why).

I welcome your thoughts!

This entry was written by Roland Smart, posted on February 11, 2010 at 6:12 AM, filed under Design and tagged Design, prototype. Bookmark the permalink. Follow any comments here with the RSS feed for this post. Post a comment or leave a trackback: Trackback URL.
« Previous
Next »

Post a Comment

Your email is never published nor shared. Required fields are marked *

*
*
Podcast Powered by podPress (v8.8)