As a company, we really have two goals: We want every one of our customers to love ProtoShare, and we want every one of our customers to love the experience of working with us.  Seriously. We’re always trying to get closer to the “love” on both of these goals.

Prototyping is a key element to the requirements discovery, definition, and validation process when building web applications. However, it’s all too common for teams to spend too much time in the prototyping phase, thereby defeating the purpose of creating a prototype in the first place. Here are several best practices to ensure you and your team get the most from your prototyping process.

This week we have our final Team Spotlight installment. Josh (yep, we have a couple) is really good at learning what people’s pain points are in the interactive development process and communicating the benefits and best practices of collaborative prototyping. And despite the Irish temper stereotype, Josh is really a laid back guy.