We’re releasing ProtoShare 6.0 today, and I want to share with you why I’m so excited about it.  Nearly a year ago we released version 5.0, which changed the way we prototyped. But the changes we made to this release have really transformed our use of ProtoShare, and we hope they’ll transform your usage as well.

Editor’s Note: We’d like to welcome to ProtoShare the newest member of our Customer Service team, Nick Jennings. As a new user of ProtoShare, Nick shares a couple tips others may also find helpful in his first blog post below.

I recently attended InfoCamp Seattle and found it to be an interesting conference; I highly recommend it.  The keynote was by Nishant Kothary. Kothary shared insights about the creative process. What I found most interesting was his discussion of cognitive biases — the way we are “Predictably Irrational“.

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.