So if you’re still with me, we’ve talked about:

  • Product Ideation
  • User identification
  • User acquisition
  • User verification
  • Conversion testing
  • Surveying

…whew! Now, we’ll go into actual prototyping. You finally get to think about your product again!


The best kind of study is face-to-face. Asking open ended interview questions allows the user to guide you through their experience and lets you glean information without affecting the results. The quickest way to show a user your idea is via prototyping.

When we prototype, we mostly start with a whiteboard or hand drawn sketch. We use tools like FlintoDA.IOor Prototyping on Paper to reveal our ideas in flat, clickable prototypes. Sometimes these are sketches or actual UI. Starting with sketches or lo-fi wireframes allows us to quickly pivot to satisfy a user’s needs. We do lots of different types of exercises (mostly with notecards: ideation, cart sorting, user workflow pathing) to get a users’ ideas articulated.

Notecards are also sort of shaped like screens. We can draw little diagrams that look like apps and guide a user through an experience on the table in front of us. They’re also cheap, portable and easy to play with. You can tear one up when an idea turns sour; it’s cathartic, final and you haven’t wasted time writing good code for a bad idea. I love notecards.

Once we have something to work with, we quickly move into a build phase. Once we’re building, we seek constant user feedback. For user feedback, a few tools…

  • Silverback is a Mac app that allows me to record a user’s screen as well as the iSight camera (meaning I can monitor their face/voice as they navigate an experience).
  • Userzoom is a similar tool, but allows for remote users (meaning they don’t have to be in the room with me).
  • User Testing is a tool that asks anonymous users (so, not your ideal customer) their thoughts about an app or system.
  • Feedback Army is another anonymous user tool, but it gives me 10 user responses for $20. Cheap.

Taking this user feedback allows us to start making decisions on how we build. This leads us to our MVP.

The Minimally Viable Product

On the Centresource UX team, we constantly work through this process via a variety of prototypes. I mentioned paper prototyping but that’s just the beginning. Often times we use paper prototyping merely as a way to validate an idea or workflow internally. We’ll apply a brand style to our paper or HTML prototypes to create a UI prototype. We refer to this internally as the Minimally Viable Concept, or MVC. This concept is clickable and feels like a real experience (especially on an iOS device with Flinto). It’s perfect for user testing or even to show potential investors or partners.

From there, we can further validate and iterate on an idea until it’s ready to be built. We often start with aproduction prototype. This is a front end only prototype that actually breaks our MVC into workable HTML, CSS and Javascript. We can test our assertions for responsive design, identify any holes in the process and create a solid pattern library for all interaction types.

Once we have this in place we can hand the whole piece over to our development team to create the real product. Now, it’s time to ask the key Minimally Viable Product question:

What is the least amount of effort I can expend on creating the most amount of value for my users?

This is a tough question to answer, and it’s why the previously mentioned tools (ESPECIALLY interviews) are important. The concepts and prototypes we’ve created often show the full product experience. Do you truly need all those elements and features to get your product to market?

You should know exactly what your users find valuable and start with only those bare requirements. Using iterative development methods, we can use our user learning to iterate and grow towards our ultimate vision. And now, a little kung fu wisdom:

“It’s not the daily increase but daily decrease. Hack away at the unessential.” – Bruce Lee

The healthy product is the evolving product. Use your base of committed users to tell you what to do next, and don’t be afraid to pivot when you need to.

All the tools we’ve talked about are important, and they should be returned to frequently. This process is iterative and your target constantly moves. Ultimately, by caring about those you serve and constantly checking up on them, you’ll make a truly valuable product.

Last time we talked about the importance of a verified, evolving idea. We talked about how telling a story about your idea would engage users. Then, we talked about how to brainstorm our target users. Now, we need to take those ideas and thoughts and start applying actual data to them.

Research Through Ads

The first way to get started is simple: you dangle your line and see who bites. Tim Ferriss, author of the Four Hour Workweek has a killer case study on this. He took his book title—six of them, in fact—and a variety of tag lines. He setup a week long Adwords campaign, spending about $200 in total, and discovered the winning title. With a little bit of market research, he found his product name and value proposition. Not bad.

Knowing what people are interested in about your product speaks volumes. It lets you choose a name, logo and style. It lets you choose a key feature to center around. And if done right, it also helps you learn about your audience.

With Google Adwords and Facebook Insights, you can learn about who’s interested in your idea, where they’re coming from, and what makes them tick. Heck, you might even get to know actual people. Crazy.

Conversion Testing

Now, you’ll want to know more about these people – that’s where my favorite tool comes in. Optimizely!

Demo time: go visit and see how it works in their sandbox mode.

When you get a user to click on your ad, you’ll want to send them to a well converting landing page. This tool allows you to tweak, test and adjust nearly EVERYTHING on your site without the need to write any code.

On your amazing optimized landing page, you’ll want to capture interested users to an email list. Those folks are going to become very important to you, so make sure you’re using a tailored email solution like Emma orMailchimp to speak to them in style. Here you’ll give them product news, thank them for signing up and stay in touch… infrequently.


After you’ve grown a small email list, it’s time to engage. Reach out to them with a survey. The easiest place is still SurveyMonkey. You can integrate this with your Mailchimp account and do some really simple, powerful things.

This is a place to further quantify your user. You might know about them from our ad targeting, but you don’t know their specific choices and habits yet.

Ask questions about their buying decisions. Why did they find your product interesting? What would THEY like to see the product do? How much would they be willing to pay?

Most importantly, however – you want to ask them for more of their time. Can you speak to them about the product? We’ll get to that more in a second, but this survey should help you identify the main features you want to focus on for your product.

Surveys and interviews are powerful tools, but they rely on what a person wants to say versus their actual behavior. Malcolm Gladwell has some great examples on how people speak about spaghetti sauce and coffee: ultimately, that what people say is sometimes not what they truly believe.

Part Three

So you get what makes a user tick. You get what they want…but is it really what they want? The best way to be sure is through usability studies. We’ll dig into these tools and approaches in Part Three of this series on “Testing Your Way To a Better Idea.”

At the core of Centresource, we care about ideas. Ideas create products and services. They connect us to other people. They lead to changing things. When we talk about products, services, people, change, and ideas… we sometimes think about Steve Jobs. He had an uncanny knack for understanding what people would like (and thus what they’d pay for). He also knew how to improve things as technology costs decreased and market penetration increased. He embraced a philosophy of BETTER.

This is an important word for me (and the Web). The work we do is never done. It can always be improved. The same is true with an idea.

People love stories. They especially love stories they can relate to, or that they can empathize with. If you can understand what the story of your idea is, you can communicate it to a user and convert them to being a part of that story.


People are the reason we do what we do. Users. People use our software, buy our products, and sustain our businesses. If we lack empathy for our users, there’s little chance we’ll build something they’ll love. Furthermore, if we don’t listen to them, it’s hard to imagine our relationship improving. Lay’s Potato Chips justran a campaign where they reached out to their users, asking them to submit new ideas for flavors.

Lay's Chips Flavors

Great idea, as this stable of winners proves. These three are all viable products and their customer base told them so. Letting your users show you the way is ALWAYS a good idea, even if you get some silly suggestions, too:

Lay's Chips Joke Flavors

“Frog?” is my personal favorite.

This is still good news – users making these funny posts made a huge splash on social media, drawing more attention to the campaign. Now, I’m not sure what tools Lays used to manage this campaign but I want to walk you through a scenario of tools you might use when launching a new product.

Identifying Users

If you’re Lay’s, you’ve got a massive captive audience and advertising budget to connect with your audience. What if you’re brand new? You need ways to cheaply and successfully acquire an audience to start experimenting on. These users need to be targeted appropriately and you need to know who they are.

Begin with a persona. Who do you think you want to target? Populr, a delightful product started by Centresource founder Nick Holland, started with a wide array of targets in mind. The obvious users are there: marketing managers, PR people, etc… but they also wanted to talk to real estate agents and musicians. They took each user type and started a persona for them.

Recently I’ve been using Personapp to help identify these personas. This tool is a digital version of whiteboard exercise I’ve often facilitated. This app allows you to think through a user’s needs and behaviors, their demographics, and their goals. I often like to add psychographics, too: breaking down a user’s interests, values, attitudes and choices.

You should use this tool to create a rough outline of who you’d like to target. This is an evolving concept and your targets will change over time.

Part Two

In Part Two of this series on “Testing Your Way To a Better Idea,” I’ll dig into an overview of user acquisition and research. We’ll take these persona hypotheses and start verifying our assumptions. It’ll be fun.

Centresource’s approach to product development includes a product planning and prototyping engagement. Bryan Clayton is the co-founder of GreenPal and our neighbor in the Missioner Building in Germantown. In this guest post, Bryan has written about prototyping and what it means to his business.

About 2 years ago, three ambitious friends and I decided to take the plunge and bring our startup idea GreenPal to life. GreenPal is a mobile/web application that enables homeowners to order lawn care for their home fast and easily. We describe is as Uber for Lawn Mowing.

At the time, not one of us knew how to code, but we didn’t let that minor issue get in the way of pursuing our dreams of tech startup success. Our first inclination was to partner with a development shop to build the first version of our product, and then, we would go to work marketing and promoting that product.

Our team met with every development shop in Nashville, and ultimately decided to work with one of them. This was our first critical error in our approach to building version one. We met with the development shop’s team, laid out our product vision, and began to work on a specification document with their team that outlined features and functionality the product would perform. Quite honesty, our team didn’t know what the hell we were doing, and at the time, this seemed like a logical first step.

Fast forward five months, after several meetings and discussions, our team got to sit down and test out the “finished” product for the first time. I remember the sinking feeling in my stomach when I first laid eyes on our user interface… I was immediately terrified to see that our product was difficult to use, non-intuitive, and very different from the vision I had initially had in my head. My team and I began to voice our concerns, but it was too late; they had already built this application front to back so any changes would result in change order expenditures.
Despite the awful user experience and interface, we launched the application in the Nashville area. We then met with every early adopting customer that would meet with us to get the painful feedback on the product we already knew was terrible. We listened to the same issues over and over, noted all the customers’ disappointments, and conducted usability tests with them diving into the minds of our users to figure out the large gap between their expectations and what we had built. The idea in our heads, what was built, and then, what the users expected were all miles apart. Ultimately, we realized that we needed to rebuild the entire application from scratch.

On the second go around, we have taken a different, much smarter approach. We started by creating a prototype which consisted of entirely redesigned screen shots linked together by Solidify, a handy prototyping software. This created a simulated experience that we were able to place in front of users and get immediate feedback. We observed over a hundred usability tests on the newly laid out interface, making adjustments after each group of five testers. We found this iterative process really smoothed out the speed bumps on our product, reduced friction, and added clarity for our users.

After countless of these product iteration cycles, we developed an interface and user experience that we were proud of and that people loved. Then, we handed that off to the developers to build. The best part is that all of the iterations were easily performed in Photoshop on the psd designs, rather than having to adjust hard coding each time.

I strongly recommend any startup to take this approach when creating a new product from scratch. It is easier, faster, and more cost effective. You’ll preserve your sanity and create something you’ll be proud to show your mom. If you do create a prototype, feel free to reach out to me, I would love to try it and give you my feedback.