Sean Rosensteel on the Journey from v1 to v2

· Posted by Leon in Interviews and tagged , , · 1 Comment

sean_rosensteelOur latest champion is Sean Rosensteel. He is the co-founder of Bravo, a web-based tool for recording customer videos for marketing campaigns.

Sean reached out to us via email, writing, "Wondering if Balsamiq would like to do a story on Bravo Video, as we recently launched an entirely new website + interface using Balsamiq for wireframes. Without your software, we wouldn’t have been able to plan such an intuitive interface for our customers :)"

I corresponded with Sean and loved how well he was able to articulate his product development process and the role that Balsamiq Mockups played in it. He is a long-time Mockups user and an experienced entrepreneur. Sean told me, "I’m an extremely organized person, and that’s probably why I love Balsamiq so much. I like to plan and measure twice before executing. "

I think you'll enjoy his interview responses, so let's get right to it...

Q&A with Sean Rosensteel

Who are you and what do you do?

I’m the Co-Founder of Bravo, a software product that enables businesses to capture video from customers, users and fans - right over the web. I’m responsible for most of the marketing initiatives, as well as keeping our agency partners happy and up-to-date.

What trends do you see in your role or industry?

We’re seeing the adoption of user generated video by consumers and businesses alike.

We’re seeing the adoption of user generated video by consumers and businesses alike. It’s really quite exciting. When we first launched our software in 2011, user generated video was in its infancy stage. A few years later, and we’re seeing people of all ages participate in these raw video campaigns. Because of this shift in consumer behavior, I think more and more companies - especially the marketing departments within these companies - will start to see the importance of capturing customer feedback through authentic, user generated video.

What sets you apart from other people/companies that do what you do?

I believe the simplicity that our product offers really sets us apart. Balsamiq aided us greatly in wireframing the new interface, and we built it purely for marketing folk. It’s incredibly intuitive, and it’s so simple you can launch a user generated video campaign in less than a minute.

What’s challenging about your job and how do you deal with it?

I’d say the most challenging aspect of my job is figuring out why our product works so well for certain people while others who use it end up not taking it very seriously. We see some user generated video campaigns succeed with flying colors while others fail. We’re doing our best to start capturing data and feedback within the app to better understand what makes certain customers who are using it so successful. If you have any recommendations for user-based analytics software, I’m all ears!

What do you like most about what you do?

On occasion, I’ll manage a customer account. I love hearing how customers are using the software, learning more about the challenges they’re facing and then providing them with some insights and direction to help them achieve their goals. I don’t get a lot of time these days to work one-on-one with our customer base, but it’s something I’d like to do more of this year.


Comparison of Mockups and final implementation of the Review screen (click to enlarge)

What inspires you?

Customer stories. It’s so refreshing to learn about some of the fun and creative ways people are using Bravo. One of our customers is a non-profit, and they’re organizing an event this summer where people will ride bikes over 100 miles in a 2-day event for charity. They’re spending the night at a half-way point, and during their stay they’ll watch raw videos of their friends and family wishing them luck, cheering them on, and providing them the inspiration/motivation needed to finish the ride strong on day 2. The non-profit who is sponsoring this event is using Bravo to capture and organize all of the videos for the riders. It’s stories like this that convince you to forge ahead and continue doing great work.

What mistakes have you made, and what did you learn from them?

We’ve made a ton of mistakes...The important thing is that you’re learning from them.

We’ve made a ton of mistakes, and I’m sure we’ll continue to make them in the future. The important thing is that you’re learning from them. We’re still recovering from the mistake we made at the beginning of the year: We were launching a new interface, and we didn’t provide the option to existing customers of staying on the old platform. The vast majority of our customers were thrilled with the new interface, but we definitely had to smooth over some unhappy customers who were really used to the old one. Not that we’ll be launching a new platform anytime soon, but if and when we do we’ll definitely be sure to make the transition “optional”.

Have you made any “pivots” with your product along the way? Can you tell me about one?

Yes. For the first few years our product was focused solely on video testimonials. After receiving hundreds of request for more video contest-centric features, we release a video contest widget with user voting functions. This was a little victory for us because we could now support video contests in a feature-rich way whereas before, when we were only focused on video testimonials, it was a bit cumbersome.

Why do you use Balsamiq Mockups?

I’m a big fan of whiteboards, as I like to visualize from a high-level before getting into the smaller details and executing a plan. Balsamiq acts as our digital whiteboard, and allows us to visualize the concepts of a strategy before we put emotions and design in place. We enjoy its simplicity, and we find it very, very easy to use and adopt.

Can you tell me about a specific project where Balsamiq was especially useful?

When we originally launched Bravo v1 we made the mistake of NOT using wireframes. We were so excited to jump into the design stage that we made the decision to forge ahead, but it was costly. Not only did it create additional time revising the designs, but once it was developed it took even longer to make edits since we were dealing with live code. I’d say that to this day it was our one major mistake - because we immediately had customers using a software that wasn’t optimized very well for usability. Had we taken the time to wireframe, we could have streamlined the customer experience ahead of time and had happy customers from the start.

Had we taken the time to wireframe, we could have streamlined the customer experience ahead of time and had happy customers from the start.

When we were planning the release of Bravo v2, we knew that wireframing played an important role of the success of the new release. This time around, we invested quite a bit of time wireframing the new interface, uploading our wires into InvisionApp for a realistic user experience, etc. This allowed us to make a ton of on-the-fly revisions before we put our ideas into design.

What has been your experience showing your mockups to other people, for instance team members or clients?

Our team members absolutely love it, because they feel like they’re an important part of the planning process (which they truly are). As I mentioned in the answer above, we usually upload our wireframes into InvisionApp, which makes them come alive in a web browser.


Comparison of Mockups and final implementation of the Capture screen (click to enlarge)

Do you have any suggestions for how we could improve our product or features you’d love to see?

I think it would be awesome if you could upload Balsamiq files directly to InvisionApp, but I believe that’s a feature that InvisionApp would have to add to their software (I’ve already recommended it, by the way). I think the only recommendation I could make is to make it easier or more intuitive to add images to a wireframe. For whatever reason, I always have a hard time figuring out how to do this!

Do you have any memorable negative experiences with it to share?

I use the Mac desktop app, and for whatever reason it always opens up the last file I was working on. Usually, when I open it, I want to start a new project or work on a new file…so I always have to close out the last tab that’s open and start with a new one. Not the end of the world - pretty minimal negative experience - but overall we’re really pleased with it.

What is your favorite Mockups feature?

I’m not sure if it’s a feature per say, but I love the templates [UI controls] that are provided. They save so much time, and it’s nice that you can simply drag and drop a pre-existing module right into your wireframe.


Thank you, Sean, for sharing your stories and perspective. You are a Champion!

Are you a Champion who wants to be featured on our Balsamiq Champions blog? Send an email to champions@balsamiq.com with your stories or blog posts!

Dan Olsen on Becoming a Lean Product Ninja

Dan OlsenDan Olsen has traveled the country teaching people how to become "Product Ninjas" by introducing Lean product development processes into their organizations. He also consults with startups on how to create better products and processes. I was fortunate enough to get some time with him recently to discuss his insights and what he's excited about right now.

Dan's recipe for building great products

We started out by going through some of the concepts he covers in his presentation "Building Great Products the Lean Startup Way," which you can watch below. (You can also see a similar version without audio here.)

Product-market fit

When talking about his presentation, Dan started off by summing it up this way: "my talks are about distinguishing problem space vs. solution space and achieving product-market fit."

He says that determining what problem to solve is key and that the problem is conditional on identifying a target customer. You need to have someone who not only has that problem but is willing to pay you to help them solve it.

"You put your product out there, it's like bait on a hook. It's going to attract a certain kind of fish."

He likens product strategies to fishing. He says, "you put your product out there, it's like bait on a hook. It's going to attract a certain kind of fish." In one model, you may have bait that you know attracts the type of fish you've determined that you're going after, but "sometimes you throw your hook in the water without a good sense of what you're fishing for." In this case you end up with whatever fish responds to the kind of bait you have.

This latter model is growing in popularity with the greater availability of data and analytics that allow you to more easily discover who's buying your products, and the rise of concepts like Lean and Agile, where iteration cycles can be shorter and product teams can respond more quickly to feedback.

He cautions that just because you may have a lot of data about your customers doesn't mean that you really know them. You can get all kinds of demographics on gender, location, age, etc., but it can be hard for this data to be actionable. He thinks that talking to customers (the "fish" you've caught) directly can be greatly valuable. What works in practice, he says, is "you see what you catch and you talk to them... and you discover what they have in common." This helps you begin to learn which people value the benefits that your product provides relative to the other products out there.

He describes this as a kind of circular logic, yet it works. You put your product out there with a specific problem in mind that you're solving. Then you see who buys it and you iterate on your product by learning more about the problems those customers face, which may or may not be in the problem set you initially set out to solve.

Now that you've learned more about which customers are interested in buying your product, you can stop targeting the ones who aren't.

A consequence of this is that some attributes of the customer demographic that you had in mind initially will inevitably "fall out", meaning that they're no longer primary audience attributes for your product and shouldn't be targeted going forward. This completes the cycle; now that you've learned more about which customers are interested in buying your product, you can stop targeting the ones who aren't.

Making the leap to solution space

Once you've established a clearer idea of your target audience and their problem space, it's time to focus on the solution space, which is where design and wireframing come into play. Dan says, "design is the creative leap from problem space to solution space."

A lot has changed in this world as well. When consulting with or talking to Product Managers he will start by talking about the traditional role of a PM, saying that the old model was that a PM would write a large Product Requirements Document (PRD) and then hand it off to the development team. He says that PMs used to get by "living in [Microsoft] Word" but that's no longer the case.

Many companies are going Agile, writing user stories, and following the Lean Startup methodology. Yet that alone doesn't lead to better solutions. "When you have dozens of user stories it's hard to get a sense of what the heck is going on."

He says that wireframes and a UX presence in the organization help "tie it all together."

"You give developers text, what do you expect to get? You're going to get whatever UI they come up with. And that's not their fault."

When talking to PMs his advice is to hire a UX designer if they haven't already and to start including wireframing in the design process. In the old model of PRDs and similar documents, "you give developers text, what do you expect to get? You're going to get whatever UI they come up with. And that's not their fault."

In place of the PRD in modern organizations he says that now "the combination of annotated wireframes or mockups plus the user stories become the spec."

Dan's model of a "fully staffed product team" includes PM, UX design (specializing in information architecture and interaction design), visual design, and development (front end and back end). He says, "that's the continuum of skills you need" and, ideally, each role knows a little bit about the adjacent ones to facilitate communication between them.

He calls this the product A Team.

a-teamCredit: "How to Be a UX Design Army of One"

Having a UX designer on your team doesn't mean that you no longer need to create wireframes.

Finally, Dan advises that having a UX designer on your team doesn't mean that you no longer need to create wireframes. Wireframes are essential as a means of communicating design ideas to other members of the team. He believes that wireframes are so important because they're usually the first non-textual design artifact that's created. Without wireframes, "you and I can violently agree on 10 user stories, but in your head you're thinking of one UI and I'm thinking of a completely different UI."

The current state of UX

We then shifted gears because I wanted to hear his thoughts on the state of UX design as someone who is steeped in it every day. I asked him about the recent spike in interest in "Customer Experience" as well as his observations on the maturity of UX in the organizations he sees.

On "Customer Experience" (CX)

Dan confirmed what I had observed casually, that User Experience discussions are now being broadened to include the entire Customer Experience. He said, "CX is growing in prevalence in job titles" and mentioned that he has seen positions advertised with titles like "Chief Customer Officer" and "VP of CX".

I asked him why he felt this was happening.

Dan said, "I think the bar is being raised" because customer expectations are higher and there is more competition across all aspects of the experience. He feels that this is true for both for user experience and customer experience overall.

Customer expectations are higher and there is more competition across all aspects of the experience.

Additionally, you can no longer just release a product and leave it at that. "You need to get feedback and see what's going on."

He continued by saying that customer experience can mean different things based on the industry. A small app developer, for example, may not really think in terms of "CX" because for that developer "the Venn diagram of what is CX that is not UX is small," but large companies that sell products in stores have so many more customer touchpoints, including retail, call centers, etc. These companies are likely to think about customer experience more broadly.

For these large companies, aggregating data across disparate experience channels can be a huge challenge. But having a voice-of-the-customer channel can be incredibly powerful. When somebody first catalogs the customer's experience across the different touchpoints it can be a shock, he says, because they are so different. "Usually when you do that first audit it's pretty eye-opening."

On design maturity in the real world

Finally, I asked Dan about the state of User Experience across the organizations he talks to and works with. He explained to me why he is such a big fan of wireframing, and why it's the first thing he recommends to most of his clients, by talking about the different levels of his design maturity model.

ux-design-gapCredit: "How to Be a UX Design Army of One"

Dan talks about the UX design gap in many organizations. "The most common situation you see are teams that only have developers, there's not even a product person. There's certainly no designer." The next level up is developers and a PM. In both cases they are probably not creating wireframes, so you get a lot of different ideas about what the product is going to be. He continued, "even when you add a visual designer, they go straight to Illustrator and Photoshop," so the communication barriers during the development process still exist.

"The most common situation you see are teams that only have developers, there's not even a product person. There's certainly no designer."

He said that frequently, "it's not until you get a UI designer or a PM who knows [Balsamiq Mockups] that you get wireframing as part of the process." This is one of the reasons why he calls Balsamiq Mockups "the best $79 you'll spend," because wireframing is something that anyone can do, but that many small or new organizations don't do or even know about.

Even within teams that have a UX designer, he said that many companies are far from mature. I mentioned the UX blogs I follow and how they can make it seem like everyone is really pushing the envelope in UX. He said that's not the norm, saying, "it's a typical bell curve. You're looking at the 3 sigma people. Those are the people writing about it and debating the finer points of doing it this way vs. that way."

He's observed the same thing for programming languages and technology choices. The business or idea people he talks to just want their idea executed on, they don't necessarily know or even care about the technology used to build it. He told me that for a lot of non-technical founders, the decision about which language to use should be driven more by practical support for it, the ecosystem around it, and the availability of developers who know it.

It's a great time to be building digital products

We wrapped up our conversation by discussing what Dan is most excited about right now. He told me, as someone who has been creating software for 20 years that now is a great time to be building products because of the tools that are available. These tools not only optimize workflows for specialists, they also mean that for small teams, you don't have to be an expert in everything.

There are a lot of tools available now, and many of them are very good. He said, "good tools are popping up left and right... Within the A/B testing space alone, there's all this competition." He continued, "just like customers benefit when there's competition in a product market, product builders benefit when there are a lot of choices and competition in the tools market."

"Just like customers benefit when there's competition in a product market, product builders benefit when there are a lot of choices and competition in the tools market."

Comparing today to the old ways, he said, "I've been there when Marketing is asking Dev to change some HTML. Marketing is frustrated that their little HTML change request has to go through the normal product pipeline - get prioritized, who knows when it's going to get launched - and Dev is frustrated, they're like, 'Are you serious? I want to be coding cool algorithms, I don't want to be changing HTML. That's not even coding'."

But with today's tools, like modern CMS systems, "now, all of a sudden, Marketing can make those changes. Everyone is happy."

He also mentioned the trend towards increasing integration across tools and services. "Most people think about integration right out of the gate," he said. "You can integrate a lot of these tools to help you optimize your product easily."

Finally, he said he's excited about the data that you can get out of the tools. Product debates no longer have to be so subjective. In the past it could come down to people's opinions about a feature. "Someone would win and that's what you would launch. Now you can actually get data with A/B testing. That's also raising the bar." He concluded by saying, "if you can get answers, instead of having to speculate, then the products are going to get better."


Thank you, Dan, for generously sharing your knowledge and expertise. You are a Champion!

Interested in hearing more of what Dan has to say? Follow him on Twitter, LinkedIn, or check out Olsen Solutions. You can also see many of his presentations posted on SlideShare. Readers in the San Francisco Bay Area can join Dan's new Lean Product & Lean UX Meetup group, where he will be speaking on March 18th.

Are you a Champion who wants to be featured on our Balsamiq Champions blog? Send an email to champions@balsamiq.com with your stories or blog posts!

Jon Matthews on Using Mockups to Clarify Your Ideas

Jon MatthewsOur latest Champion, Jon Matthews, recently tweeted about how well Balsamiq Mockups works for drawing decision trees, like the one below. He has used it for a long time to help him design his products as well. He told me, "Mockups is just one of those tools I go to again and again. It's amply paid for itself when I've done actual mockups, stuff like [using it for decision trees] is all a bonus."

He continued, "I really like the look of how they came out, and it was much easier to use for this stuff than the other software I've got that could do something similar. Snap to grid that actually works is not to be underestimated :)"

brokenLinkTree
A decision tree on how to fix broken links

His most recent use of Mockups for UI design was for CloudTrawl, where ease of use was targeted as a key differentiator. Rather than using it as a tool for communicating his ideas to others, he relied on it primarily to help him clarify his own ideas and get right to the good ones when it was time to start coding.

Q&A with Jon Matthews

Who are you and what do you do?

I'm Jon Matthews, I run Deep Cognition Ltd, a one person software company specializing in tools for web developers. Our mission statement is "Saving the web, one site at a time" which pretty much covers it. We do website monitoring and checking tools.

Our first product is DeepTrawl, a desktop app which checks sites for common errors like broken links, spelling mistakes, invalid html & css plus a lot more. We've recently added a unique new on site SEO feature, which modestly, I think is awesome. :)

We also have a premium website monitoring service called CloudTrawl. This monitors uptime, sends alerts for downtime and schedules checks for broken links & images.

LinkCheckReport
An early mockup for CloudTrawl

What trends do you see in your role or industry?

There's a big trend towards SaaS. I don't make a generalised value judgement on this. The split should ideally be "horses for courses." I see a lot of businesses making the mistake of trying to make a pay monthly cloud service out of something which a user does irregularly. To me this makes no sense. On the other hand when something is used regularly, and especially when it's used from a lot of different machines, SaaS through the browsers is a natural fit & those who do it well deserve the (sometimes large) rewards they get. I can't live without DropBox now, I never begrudge those guys their monthly payment.

A lot has been made recently about the commoditization of software, i.e. app stores pushing down prices and encouraging the lowest common denominator. While that does seem to be having an effect in consumer software, it's less worrying in B2B where I think people tend to think more in terms of ROI.

What sets you apart from other people/companies that do what you do?

As a very small company, service and support are something that's much easier to do really well. With a larger company it's unlikely one of the developers of the software will spend hours trying to work through a difficult problem with an individual customer. This is something that not only can small developers do, but they should have it as a top priority. Everyone benefits.

My attitude is: come to us for the link checking, buy from us because of the other stuff it does.

Technically, I've always tried to move the products less towards being single purpose and more towards being as broad as possible within the remit of the company. In the case of DeepTrawl, there are a hundred link checkers out there, but none that do the range of other stuff it does. Sometimes our customers don't know they need the other stuff until they see it working. So my attitude is: come to us for the link checking, buy from us because of the other stuff it does.

What's challenging about your job and how do you deal with it?

Probably the sheer amount of hats I have to wear. It's very easy to get dragged off into writing code where things are safe and predictable when in reality I should be concentrating on marketing. I also find it hard to do anything else when I know a tricky support question is hanging over my head. Every now and again something comes up that means I'm distracted thinking about an issue when I should be paying attention to my wife / family / friends. Luckily my wife is very understanding :)

What other tools do you use for your job?

For code I love Eclipse and the EJ Technologies tools (Install4J / JProfiler). Actually JProfiler is awesome. In the early days (between DeepTrawl v1 and v2) it allowed me to speed up some operations literally by hundreds of times.

I'm also using Google Drive more and more. Everything else goes into DropBox, which is indispensable but Drive allows me to do some things much more easily. For simple word processing and spreadsheets, Drive is now my go-to-tool.

What do you like most about what you do?

Freedom to do things properly without office politics. The business is also still at a stage when each sale or signup that comes in makes me smile. There's no better feeling than seeing someone liked my stuff enough to click the buy button.

Why do you use Balsamiq Mockups?

I never have a need to share my designs with others, they simply help me to clarify my own thoughts

I used to struggle a lot with writing code for screens, then never being able to make them function like they did in my head. Essentially this was because what was in my head just wasn't practical & thought through correctly. I don't know how common this is with Balsamiq's customers, but I never have a need to share my designs with others, they simply help me to clarify my own thoughts and stop me writing code that needs to be thrown away later.

It's also becoming my favourite tool for general diagramming. For example, in this article I used Mockups for creating things like node arc diagrams and a decision tree. There's two reasons I chose Mockups for these tasks:

  1. It's a well implemented drawing tool. There's nothing more frustrating than snap to grid that doesn't work quite right, which I see in so many tools.
  2. I love the look of the output, the hand drawn style says to the reader that they're looking at something conceptual, kind of like a chalkboard at school.

Can you tell me about a specific project where Balsamiq Mockups was especially useful?

Yes. CloudTrawl came out a year ago so that design process is still pretty fresh. It helped a lot there. I took a look around our competition and found their usability really sucked, it just didn't make any sense. I usually push hard on usability but here it was an easy win.

I used to end up ripping up screens I'd implemented in code because in real life they didn't and couldn't work as I'd imagined.

I already had Mockups from an earlier project and it helped map out pretty much every inch of the webapp. It saved me an unquantifiable amount of time in implementation. So frequently in the past I used to end up ripping up screens I'd implemented in code because in real life they didn't and couldn't work as I'd imagined. Now I have Mockups that no longer happens. It's a fantastic time / frustration saver.

I still have a folder full of mockups from that time and when I look at them now the actual screens are functionally identical to what's in the mockup. Even the layouts are almost entirely the same. For me this is the power of the tool. It pushes design iteration from the code (which is a slow place to iterate & therefore expensive) to mockups (which is a very fast place to iterate).

LinkCheck
An early mockup for CloudTrawl

Thank you, Jon, for sharing your story and thoughts. You are a Champion!

Are you a Champion who wants to be featured on our Balsamiq Champions blog? Send an email to champions@balsamiq.com with your stories or blog posts!

Wayne Chen on Avoiding Common Mobile Product Mistakes

Wayne ChenOur latest Champion is Wayne Chen. He wrote an article recently that caught my eye called "Top 10 Mobile Product Management Mistakes And How To Avoid Them (Part 1)".

He introduces his article by saying that there's no magic formula for success in the mobile world, but "there are a few mistakes that almost certainly guarantee failure." To start, innovative products don't come from marketing and sales teams, he says. "Even smart customers don't necessarily know what they want...As an innovator, that's your job"

He continues:

"Top product managers often combine engineering and business backgrounds. When they see an unmet need, they can envision new and innovative possibilities. Meanwhile, product marketing should communicate what the product does to the target market, and support sales with the tools to sell effectively."

On the other hand, Wayne's advises product teams against "innovation for innovation's sake." We've all seen products with plenty of sizzle and good execution that failed in the marketplace because they didn't solve a real problem or meet a need better than what people were already using. He warns that "Passion when not directed properly becomes a pitfall" and says that "innovation needs to happen in the context of a vision and printed strategy."

Similarly, many products are doomed from the start because they try to do too much ("boiling the ocean" in Wayne's words). He suggests a lean approach by keeping the scope small, wireframing at a low fidelity, and starting with one platform or version before expanding to others.

Another common problem he mentions - and one that can't be repeated enough, in my opinion - is to avoid saying yes to every customer request. Granting that this is much harder than it sounds and that it can often lead to customer frustration, he says "Listening to customer pain points and seeking to understand what drives their behavior will go a long way to alleviate those situations and find a solution that doesn’t compromise you but still keeps them happy." He also suggests addressing rejected customer requests directly by explaining why you aren't adding the feature, or at least why you're not doing it right away.

From a process perspective, Wayne provides some ideas for keeping things moving and staying on track. His recommendations:

  • Start with a fixed timeline and stick to it
  • Make resource and task assignments clear
  • Agree on a common format for documents and assign one person to incorporate the final changes
  • Have a daily scrum meeting
  • Over-communicate when time is short

To see all of what Wayne has to say, read his article here.

I've seen many of the mistakes Wayne mentioned in my previous positions, so I truly enjoyed reading his strategies for preventing them. I reached out to Wayne, who happens to be a big fan of Balsamiq Mockups, to learn more about the experiences that have taught him these lessons.

Q&A with Wayne Chen

What do you do and how do you differentiate yourself?

I run Pocket Square Media, a mobile product and digital consulting practice. I split half my time turning napkin ideas into pilot or commercial-ready products for small and Fortune companies.

On the other end, I help treat struggling apps with new product, user experience, and marketing strategies. Many mobile companies and software shops practice the software development lifecycle, but often forget or fail to incorporate a strong marketing strategy to win and engage customers. I evaluate, design and guide clients through user acquisition and engagement, which is critical to their overall mobile success.

What trends do you see in your role or industry?

Mobile app marketing is becoming a high priority for many companies, product managers, and developers. Getting downloads used to be easy but those days have faded. To be competitive in a red ocean, managers must have a clear product and marketing strategy that meet app discovery, engagement, and loyalty standards of their target audience.

What tips do you have for someone looking to succeed in your role or industry?

Be willing to listen. Many of us think that our idea, design, and app are perfect. Reacting well to constructive criticism can therefore be tough if not welcomed. While becoming defensive is easy, it is important to take a step back and see if there is a grain of truth in the opinions of others. Obviously, not everyone gives good advice, but some feedback can add value and insight to your product strategy. By actively soliciting feedback, you also show humility, which is a greatly underrated quality.

What's challenging about your job and how do you deal with it?

The top two challenges that I have learned from my agency and start-ups include the stakeholder buy‐in and staying focused on value-driven activities. I believe these are fairly common and here is how I deal with them:

  1. Customer / Stakeholder buy-in: Getting stakeholders’ buy‐in for your product is nearly impossible if they don’t see what’s in it for them. Overcome this challenge by understanding their pain points and craft your initiative to benefit theirs. Then communicate this information clearly and consistently. Remember, your success isn’t just about the product launch or numbers, but about the people who back your endeavor and how you treat them throughout the process.
  2. Value-Driven Activities: Collaborative teams can spend a great deal of time brainstorming in meetings, but they are counter productive if no one acts on the action items. Challenges arise when the teams spin their wheels on technical or even design activities, which devour precious time from the overall delivery and cost. Try to move the team to the state of action and reflection by posing the following questions:
    • Does the activity directly meet the need of the current objective or goal?
    • Is there an alternative solution that will do the job?
    • Will it affect the end‐user if BLANK feature slated for another release?
    • Do we have the time, resource or budget to solve this now or later?

What other tools do you use for your job?

I have worked with many tools over the years, some are good, but there are a few that truly standout and make a difference in the overall product and project development cycle. In addition, many of these tools are free, inexpensive and/or time‐savers. Here are the tools that I have found most useful.

  • Basic Mockup & UX: Balsamiq, Omnigraffle and Paper Pad!
  • Testing & Management: TestFlight, UTest, and Jira
  • Mobile Advertising: mMedia, TapJoy, and JumpTap
  • Project Management: LiquidPlanner, OmniPlan, Google Drive, and BaseCamp
  • User Engagement: Social Networks and App Growth Engine by Hook Mobile.

What do you like most about what you do? / What inspires you?

I love solving problems, especially if it involves working with talented individuals toward a shared vision or dream. One of the best things about working in mobile is that it allows me to apply my creative ideas and structure to improve the lives of people and organizations. Many people working in start‐ups probably share that passion: we all want to make a difference, such as volunteering at a veteran’s hospital and helping them transition from the military to the civilian world.

Why do you use Balsamiq Mockups?

Whenever Balsamiq is not used, clients waste tens if not hundreds of hours of work by going over little details before agreeing to the final work flow and then coming back to change it.

I've used Balsamiq Mockups regularly since early 2009. It is a rock solid product and saves my team time, which is critical in getting the work done in the world of mobile. Today, I use it primarily for mockups and workflows, which many designers and customers struggled with conventional design tools and iterations. As consumers and owners, we expect to see everything in pixel perfect layouts. Unfortunately, this creates bottlenecks in project delivery and stakeholder buy‐in.

Whenever Balsamiq is not used, clients waste tens if not hundreds of hours of work by going over little details before agreeing to the final work flow and then coming back to change it.

The product shines when it comes to agile development and communication, it cuts down time and forces the customer and developer, product and design team to look and feel the app purely from the user experience perspective. Most end-users will care more about your app experience than about the background’s hue.

Anyone who knows how to use PowerPoint can be a Balsamiq Rock Star in minutes.

Balsamiq is also great for those who are not Photoshop or Illustrator experts; anyone who knows how to use PowerPoint can be a Balsamiq Rock Star in minutes. In fact, I actually make it an effort to get non-technical or design stakeholders to experience the creation of a simple wireframe in five minutes via WebEx or in person.

Overall, it is a super useful tool for anyone who wants to envision the final product. In my start up days, I have seen angels and investors pitched solely on their Balsamiq designs. Can't disclose who but they are doing well. ;‐)

Can you tell me about a specific project where Balsamiq Mockups was especially useful?

I was already knee‐deep in three mobile projects when we won another project for a well‐known Fortune firm asking an aggressive schedule. I could not afford to lose the client; mobile engineers suggested Balsamiq. I checked out the product and was quickly amazed at the rapid UI wireframe features and how easy it was to use for web and mobile.

After the project ended, I conducted a project review and noted that Balsamiq reduced our overall design efforts by 60 percent, which I was very happy about on the project profitability end. The client was equally thrilled when they saw how good the app wireframe without spending weeks perfecting the wireframe and graphic design when using mainstream design tools. In fact, the VP of Engineering loved the tool and mandated all internal designers and product managers to use it moving forward.

Thank you, Wayne, for sharing your insights and recommendations. You are a Champion!

Interested in hearing more of what Wayne has to say? Follow him on Twitter @WayneChenNY or @MobiWayne, or on his website pocketsquaremedia.co.

Are you a Champion who wants to be featured on our Balsamiq Champions blog? Send an email to champions@balsamiq.com with your stories or blog posts!

Glenn Murray on Using Mockups for Copywriting

· Posted by Leon in Articles and tagged , , · 6 Comments

Glenn MurrayOur latest Champion, Glenn Murray, is not a prototypical Mockups user. He's a copywriter (although perhaps not a typical copywriter either). He recently wrote an article that opened my eyes both to the world of copywriting and to uses of Mockups that I wasn't aware of. So, why would someone who writes words for a living use a visual user interface tool like Balsamiq Mockups?

He answers that question on his blog in an article called "What's a copy deck? And how important is it for a copywriter?", an amusing critique of traditional copywriting. In it, he describes the standard copywriter's deliverable, the copy deck, which he has never used. He explains why he has broken the mold by creating his deliverables using Balsamiq Mockups, which helps him write better copy and pleases his clients more than showing them his text in isolation.

As a UX designer, I can relate to Glenn's use of Mockups. Reading about the conventional copy deck reminds me of the user interface specification documents I used to read (and write, pre-Mockups) – rigid and lifeless. Using Mockups for writing, as well as UI design, not only makes the author's/designer's ideas clearer, but also brings them to life.

Coincidentally, we recently redesigned our homepage and also used Mockups to hone the copy because we wanted to see it in the context of the page as a whole. Reading Glenn's article, I learned that this approach isn't unique to us.

Q&A with Glenn Murray

What is your title or job description?

I’m a website copywriter. I write mostly high level stuff – Home, About Us, Products, Services, etc. My company is Divine Write.

What trends do you see in your role or industry?

Definitely the biggest trend right at the moment is towards SEO copywriting and high volume ghost-blogging. But I think that’ll be relatively short-lived. As a title or label, anyway. It’ll evolve naturally back to simply writing high quality content. Google’s getting way too smart to be gamed by simplistic tactics. What I think will be a much bigger and longer-lasting trend is the overlap of web copywriting into user interaction design and information architecture.

Web copywriters – good ones anyway – tell a story about a business. About its products and services. Not necessarily a ‘once-upon-a-time’ sort of story (although those can definitely work). More a ‘this-is-what-we-can-do-for-you’ sort of story.

Now in most cases, the web copywriter is the main story-teller. The designer plays a big part too, of course, but it’s usually a supporting part. I don’t mean their work is less important by any stretch. I simply mean the story is usually extremely complex, and the design can only tell part of it.

This means the copywriter will usually have a better grasp on the finer points of that story. And on the audience, and their needs. They know what will effectively fulfil the reader’s needs, meet their expectations, educate them, motivate them and compel them to act.

And as websites are becoming more and more important and sophisticated, and readers are expecting more of them, the finer points of the story are starting to become the real differentiators. The websites that incorporate those finer points into their interaction design and information architecture are the ones that stand out from the crowd.

In other words, the sites that tell the same story across the board are the ones that convert better. Calls to action, menus, site structure, page segmentation, image content, buttons... All of these elements – and their relative prominence – need to tell exactly the same story as the copy.

So it makes sense that they have the same story-teller.

NOTE: Obviously there are big companies out there that engage dedicated user interaction designers and information architects. But they’re few and far between. The vast majority of websites are for SMBs, who are lucky to have a web designer and copywriter on-board. They’ve never heard of – and don’t have the budget for – user interaction designers and information architects. So it’s all down to the website copywriter.

Why do you use Balsamiq Mockups?

About 5 years ago, I started adding rudimentary buttons, text callouts, menus, visual calls to action, and so on, to my copy deck. It wasn’t long, though, before I discovered that as a wireframing tool, Microsoft Word makes a great word processor. I was spending way too long moving and formatting boxes, so I started looking for alternatives. That’s when I discovered Balsamiq. Now I use it for almost all my home page copy, and quite a bit of sub-page copy too. And my clients love it! In fact, I’ve won clients because of it.

I’ve spoken to a lot of other copywriters who are experiencing the same frustrations I was when trying to write only the ‘pure’ copy. When I introduced the Balsamiq idea to them, they instantly went for it. It’s like they were already at a tipping point. And although I like to tell my wife I’m the smartest copywriter in the world, I’m sure there are others out there who’ve come to the same conclusion without any help from me!

I chose Balsamiq because it’s easy and intuitive to use, fast, reasonably priced and does exactly what I need, without any unnecessary bells and whistles to complicate things.

What tips do you have for people who do what you do?

As a minimum, use Balsamiq when writing your home page copy. Ideally, use it to write other pages too, and link them together in interactive PDFs for client review. Like this:

What sets you apart from other people/companies that do what you do?

I take the time to do it right. Partly because I’m a perfectionist, partly because I’m really good at it, and partly because I have a good reputation and a great search ranking, so I have the luxury of passing on the low-budget jobs. Plus I think of myself as a businessman, not just a copywriter. I think like my clients do, so I can put myself in their shoes. I’ve also spent a lot of time consciously putting myself in the reader’s position; I was a technical writer in the software industry for 9 years, before I started Divine Write. And technical writing’s all about identifying and bridging knowledge gaps.

What's challenging about your job and how do you deal with it?

The single biggest challenge is finding enough time to write and to market my business. I’m still a sole operator, so I have to do everything. When I get busy, I have no time to focus on my SEO. When my ranking slides, things get quieter, and I have to invest time in my SEO again. Then I get busy, and we’re back to square one. The other major challenge is educating clients about the value of what I do. Most people think copywriters simply string together pretty sentences. Nothing could be further from the truth. In fact, on many jobs, the actual writing component is a small part of the job. This difficulty has only increased as I’ve moved more and more into interaction design and information architecture. If I mention those terms to my clients, I may as well be speaking Latin!

What do you like most about what you do?

Creating new stuff out of nothing. An awesome new website or mobile app out of thin air. I also love the business side of things, and being (virtually) surrounded by amazing, intelligent, inspiring people. And, of course, I love being able to work from home, spend more time with my wife, and watch my children grow up.

What has Mockups allowed you to do for your customers or teammates that you were not able to do before?

As discussed above, it’s allowed me to do more than just write the ‘pure’ copy. I can now have a hand in all the other important parts of the story. Plus I can now give clients a much better insight into how the copy will be presented, and how it will integrate with the other elements on the page.


An example of Glenn's "WYSIWYG" approach to copywriting (click to enlarge)

What has been your experience showing your mockups to other people, for instance team members or clients?

They love it. Without exception. I’ve even won jobs because of it. My clients see examples of wireframes on my site, and it just clicks with them. A few agency-type copywriters have raised questions about whether presenting copy in this format is the right way to go. But most web copywriters work in a very different environment from an agency. So, while I respect their viewpoint, I definitely disagree.

What do you do for fun outside of work?

When I’m not doing the family thing, I create stuff. Like www.propertyblurbs.com and www.carblurbs.com. They’re websites that automatically write sales copy. I also love reading, movies, music, I run whenever I get the chance, and I like pina-coladas, and getting caught in the rain.

What inspires you?

  • My wife (I wish I had her patience).
  • My kids (I wish I had their free thinking).
  • Amazing peers and colleagues who are super intelligent and just go for it (like Noam Chomsky, Luke Wroblewski, Bill Slawski, Fred Schebesta and my business partner, Ian Butler).
  • Amazing products that solve everyday problems in elegant ways (like Evernote, Remember The Milk and my Kindle).
  • Everyday problems (that I can’t help but try to solve myself).

Do you have any feature ideas or suggestions for how we can improve our product(s)?

  • I’d LOVE to be able to create HTML versions of my wireframes.
  • I’d love to be able to save things as templates. E.g. Save a combination of objects (a container, a button, and a paragraph of text) as a template, insert that templates on other pages, change the original, the change propagates across the other pages too. [Editor's note: We do offer this, it's our Symbols feature]
  • A better way of creating drop-down menus. At the moment, I simply create a duplicate of the page and add the drop down to the duplicate, then link to the duplicate page from the top level menu item on the original page. See my screencast above to see this in practice.

Thank you, Glenn, for sharing your process and helping us better understand the work you do. You are a Champion!

Are you a Champion who wants to be featured on our Balsamiq Champions blog? Send an email to champions@balsamiq.com with your stories or blog posts!

Yarone Goren on Validating Product Ideas with Mockups

· Posted by Leon in Interviews and tagged , · 1 Comment

Yarone GorenYarone Goren (LinkedIn profile) is the founder and CEO of Iteration Group, a product firm that relies heavily on Balsamiq Mockups for its projects. Yarone told me that of the 10 or so employees "we have about 5 people at the company who use Balsamiq Mockups at least 3-4 hours a day."

I spoke to him to learn more about the way he works and how he helps startups and other companies create products that are successful in the marketplace.

He described his company this way:

We are a boutique product development firm. There's a lot of dev shops out there, and a lot of designers and agencies, but not a lot of people focused on product UI/UX. That's all we do. We help customers nail their product vision.

We do work for startups (partnering shoulder-to-shoulder with the founders) and also established businesses who are looking for startup folks like us to help them innovate (build new products or re-imagine existing products).

Yarone gave me a typical scenario when a potential customer comes to him with an idea:

You're 45 years old, been in business for a while, made a little money, you have this idea that you've had for a year... and you want to get it built. I think the lay person doesn't know what ought to happen next. They say 'I've got this idea, I want to build it'. So they go finding a developer, or if they're enlightened, they're looking for a designer. And so, somehow I meet them, through my network. They say 'Oh, you've got an idea, go to talk to Yarone'.

Let's make sure we build something people actually want.

So they come to me... [And I say] let's spend some time right now to figure out if people care about what you're talking about [before building it]. Let's make sure we build something people actually want. I convince them to buy in to this idea.

We do research to understand the space. We meet with users or target users, do competitive analysis, etc. We nail the product vision. Then we start wireframing, The core UX, 4-5 screens. Once we've done a few rounds of that, we start filling out the user experience.

Here is a video from a series by Docstoc of Yarone describing why they encourage customers to go through this process before starting to build anything.


Read more about this video on the Iteration Group blog

Just like Michael Bourque, Yarone believes strongly in wireframing the complete application before a single line of code is written.

We would rather spend a ton of time up front wireframing than in development.

We would rather spend a ton of time up front wireframing than in development. Development is hard, it's costly [in terms of time], it's expensive. You should never build something until you have a really good feeling that it's something that people actually want. For us, wireframing makes all the sense in the world.

We do mockups of every screen. We're militant about it, every permutation of every screen. Then we meet with a visual designer and make it look good, slice it up for CSS, etc. Balsamiq is 90% of what we do.

In this video Yarone talks in more detail about his design process.


Read more about this video on the Iteration Group blog

I then asked Yarone why he uses Balsamiq Mockups.

Balsamiq for me changed everything. Finally there was a product that gave me what I wanted.

I used pencil and paper for probably 10 years. I used Visio for the longest time. I used Powerpoint. All of them had their problems. With pencil and paper, I used to cut out screens and use a copy machine to tile them on top of one another. [With Visio] once you start putzing around with alignment, colors, icons, images, it looks too real, so it was a problem.

Balsamiq for me changed everything. Finally there was a product that gave me what I wanted. I hit myself, thinking 'why didn't I come up with this years ago'.

Balsamiq is low fidelity enough that no one's going to assume that it's final work. But it's clean enough that it's presentable and respected. Balsamiq has been the backbone of our business, it's been great.

He also mentioned some things he'd like to see in the product that aren't there now.

The number one issue is definitely controls. [Mockups] really doesn't have support for [modern mobile] interfaces and interactions. [The Google mobile app] bounces, shows tiles, it flips, you can swipe to remove. I don't know how to express that [in Mockups].

We're starting to do more user testing.

That's one opportunity, more controls, more types of buttons. It may hurt the product, it may benefit the product, I don't know. I'm complaining that I don't have enough controls with Balsamiq, but, on the other hand, I don't want it to go too far.

What I'd like to see more of, aside from controls, we're starting to do more user testing, it would be great if you could improve your tools for taking mockups and turning them into something testable.

Thanks, Yarone, for opening up and talking about your process and workflow. You are a Champion! If you enjoyed Yarone's videos, you can view the other two in the series on his blog (part 3 here, part 4 here).

Are you a Champion who wants to be featured on our Balsamiq Champions blog? Send an email to champions@balsamiq.com with your stories or blog posts!

JR Harrell on the State of Design in 2013

· Posted by Leon in Interviews and tagged , , , , , · 1 Comment

JR HarrellJR Harrell is a Denver‐based UI/UX designer. He regularly uses Balsamiq Mockups in his design workflow. He contacted us by email and wrote:

As a UI/UX designer, I have used Balsamiq as my wireframing tool for a couple of years and am amazed over and over again at how flexible it is! Trends come and go, but Balsamiq is here to stay in my box of design tools.

Lately he has been using Balsamiq Mockups to create "flat"-style wireframes. Here are some examples:

Sign up page
Samples from JR's dribbble site (click to enlarge)

JR's website is drawnn.com. I interviewed him recently to learn about his process and the secrets of his success, and to get his perspective on the state of digital design in 2013.

Q&A with JR Harrell

What is your title or job description?

UI/UX Web & App Designer

What industry do you work with?

It varies quite a bit. I have worked with startups at Y Combinator, techstars, Startup Chile and other ambitious startups as well as medium to large sized organizations that have been featured on TechCrunch, Mashable, ABC, FOX, NBC, USA Today and more.

What interesting trends do you see in your role or industry?

Undeniably, the world is moving towards 'mobile first' design as Luke Wroblewski so famously said. Depending on their needs, I am suggesting to more and more clients that we start our Balsamiq wireframe workflow with a mobile-centric mentality.

Interestingly enough, starting our UI within mobile screen sized constraints actually yields better website results. I believe the reason why (as Luke also argues) is that this forces you to make important (and often tough) design decisions up front regarding what you can do away with and what you must keep.

Also, flat design is a huge trend. I will talk more about that later. [Editor's note: JR's thoughts on flat design are featured on here our UX blog.]

Almost everyone is asking for responsive design even if they don't know exactly what it's called.

As far as trends go, responsive design has to be right up there with flat design. Almost everyone is asking for responsive design even if they don't know exactly what it's called. Clients often articulate it to me something like this: 'the website design needs to automatically change its shape and content based on which device my users are on or which way that they turn the device.'

My favorite responsive design platform by far is Twitter Bootstrap. It's fast, fluid and fun. Beautiful apps and websites can be built with it versus traditional approaches. I can only hope that amazing apps like Jetstrap will eventually offer a Balsamiq Mockups extension whereby users can import their .bmml files to create turnkey Twitter bootstrap CSS & HTML. I would love that. I would go crazy over that. Responsive design makes me want to delve deeper into front end development. Maybe I will.

Also, regarding shifts in what clients are asking for, as of two weeks ago, I started getting new and existing clients asking me to take existing designs and make them into a flat design. I am even redesigning my own iPad app called Showboat (which hit #23 in just 2 days in the App Store) into a flat style design.

What suggestions do you have for someone looking to succeed in your role or industry?

First things first: it's all about audience. If you don't have access to or if you don't build an audience, you simply won't have the kind of leads that you want and you simply won't thrive.

If you don't have quality leads you can't even begin to think about all the other things that come after that.

If you don't have quality leads, and an ample amount of them, you can't even begin to think about all the other things that come after that like optimizing your design workflow, setting up efficient invoicing methodologies, focusing on customer satisfaction and so forth.

Let's talk about audience. There are three ways to gain access to an engaged client audience. One is to buy it. The second is to earn it. The third is a combination of the initial two. You must have all three in order to be successful.

Sortfolio is, in my experience, the best way to buy access to a captive web and app design customer audience. The quality and quantity of the click through traffic and leads are excellent. The site is laid out nicely so that it's sticky. It has lots of credibility with customers all around. It offers the best bang for your buck when you are looking to buy access to a client audience in this industry.

Secondly, you can earn an audience through portfolio sites like Behance. If you can score a coveted dribbble invite, it can serve as a magic carpet ride towards building an audience as a designer if you work diligently at it. Also, I can't emphasize enough the importance of a well diversified, well managed and well earned social media presence. It probably goes without saying, but, I would also classify repeat business and referrals as part of your earned audience too.

Lastly, you should be constantly improving on your wireframes and designs that you post on all of these sites or you just won't earn the leads that you truly want from the first two audience channels.

Work on all three audience approaches every day if you can. Then gather metrics on it and repeat the process until you are booked solid with good work and stay that way consistently.

What sets you apart from other people that do what you do?

Hopefully, my portfolio work first and foremost. I want it to be able to stand on its own and serve as that bridge to me for my audience.

Regarding my portfolio, people tell me that they love seeing my before and after wireframe to Photoshop designs the most. My before and after Balsamiq wireframe drawings are designed to put a handle on concepts that are otherwise quite difficult to grasp. They give folks something solid to grab onto.

Balsamiq wireframePhotoshop compBalsamiq wireframes to Photoshop (click to enlarge)

Balsamiq wireframes and the experiences that I can depict with them to potential clients are a huge part of what attracts the audience, builds the bridge and then generates leads for me.

After that, what sets me apart is my self developed engagement and design workflow that I have spent five years refining. It's streamlined, comfortable and just simply works. I take the same workflow approach every time and then tailor it to the project's specific needs. This approach has been well received across many disciplines, cultures and organizations of varying shapes and sizes around the world. This approach allows customers to bolt me right onto their existing organization with ease.

I typically start delivering work for folks within one or two business days after our initial contact. Most of the time, the initial work involves Balsamiq Mockups wireframes of some sort.

Why do you use Balsamiq Mockups?

I use Balsamiq Mockups for three reasons: it's accessible, flexible and extensible.

As I mentioned before, Balsamiq wireframes are very accessible and easy to understand. They give my potential clients something that they can grab onto and bring to me in one way or another to help build a bridge when we first talk.

For my existing clients, it provides a consistent approach for me to quickly take their verbal and written ideas and turn them into wireframes, user interfaces and user experiences in a way that they are very comfortable with and understand.

Balsamiq Mockups is very flexible because I use it in so many ways to visually convey so many things. It's an all in one tool that I can use over and over again to draw sitemaps, wireframes, workflows, you name it. That's incredibly valuable to me.

Lastly, Balsamiq Mockups is extensible. I use the Mockups output for video walkthroughs, user acceptance testing and for many other use cases.

A video walkthrough using Balsamiq Mockups

Which Balsamiq product(s) do you use (Mockups for Desktop, myBalsamiq, etc.)?

I use Balsamiq Mockups for Desktop on my dual screen iMac and Thunderbolt display setup.

What other tools do you use for your job?

I skin my Balsamiq Mockups drawings in Photoshop. I also use Illustrator quite a bit. I collaborate on Balsamiq wireframes with my clients using Basecamp, Skype and iPhone. I have an entire box of tools that I use side by side with Balsamiq and Photoshop. The tools that I use daily are Slicy, ColorSchemer, LittleSnapper, Screenflow, Candybar, Preview, Photobulk, Fontcase, Analog and, most recently, Coda.

What is your favorite Mockups feature?

The humble geometric shape tool is my most used Mockups feature nowadays.

With flat design becoming ever more popular, the humble geometric shape tool is my most used Mockups feature nowadays. It allows me to create mockups that are an unbelievable facsimile of what a final flat design will look like. I have even begun to post my flat design wireframes as standalone portfolio pieces thanks to this feature and the flexibility of Balsamiq.

What has Mockups allowed you to do for your customers that you were not able to do before?

Mockups has allowed me to be able to quickly and consistently transform even the faintest of notions into tangible frameworks that are designed with all of the respective project stakeholders in mind.

These stakeholders can be developers, marketers, sales people or even C Level people. Each stakeholder has specific goals in mind. Mockups empowers us to all literally get on the same page and meet the project goals.

I have gone around the wheel with a number of mockup tools, but none of them hit the sweet spot for me or my clients the way that Balsamiq Mockups does. It allows us to get to a meaningful, honest 'yes' sooner than later.

What has been your best experience using it?

My best experience has been designing a mobile first app called TrainingAlone for Sue Aquila. Sue is a world class Ironman competitor, Triathlete, USAT Certified Coach, USA Cycling Coach, and successful restaurant chain entrepreneur.

She wanted to develop a web based app that would help prevent tragedies like the well known Aron Ralston story that was depicted in the movie "127 Hours" featuring James Franco.

The app runs on the Ruby on Rails platform and has an incredibly robust, smooth and intuitive Twillio SMS integration.

Designing the experience and interface for that app was my best Balsamiq Mockups project yet not only because of how great it is to work with Sue, but because I believe that it will help so many people in so many ways to prevent tragic, unnecessary outdoor training accidents.

What has been your experience showing your mockups to other people, for instance team members or clients?

As mentioned earlier, Balsamiq mockups are often my best sales tool.

Balsamiq wireframes do a lot of the talking for me before I ever even speak with a potential client. They help frame the initial discussion.

Balsamiq wireframes do a lot of the talking for me. They help frame the initial discussion.

When most folks contact me, you can literally hear the relief in their voice that they have found not only the right person for the job, but also the right tool for the job through Balsamiq. Once we get into the project, I often get feedback like "amazing, splendid, just what I was hoping for, it's spot on,'" and so forth regarding the Mockups. It feels so great to hear that.

Do you have any Mockups tips or tricks that you'd like to share?

I create a huge workspace from the start so that I can give my ideas plenty of room to run. I typically add a geometric shape, select the square shape and then size it to 4000px X 4000px. That way I have lots of space to design with.

Do you have any feature ideas or suggestions for how we can improve our product(s)?

It would be amazing to be able to group drawing sets from my 4000x4000 screens into individual PNG outputs with preset pixel space sizes.

Example: Highlight drawing bits > group as an export set > file > export all sets > Balsamiq exports 5 individual PNG files all optimized for 1024px x 600px in landscape and / or portrait.

Thank you, JR, for sharing your insights and opening up your design process! You are a Champion!

Are you a Champion who wants to be featured on our Balsamiq Champions blog? Send an email to champions@balsamiq.com with your stories or blog posts!

From Product Trainer to Product Owner: Craig J Willis's Story

Craig J WillisOur latest Champion is Craig J Willis. Craig is a long-time Mockups user who has used it in both enterprise and, now, startup environments. He wrote to us to tell us one of his Mockups success stories that resulted in him taking a big leap and scoring some major UX victories within his previous company.

After Craig told me his story, I thought it would be useful to share since it demonstrates how he was able to transform a development culture by focusing on the user experience and designing around it. His story also highlights that people most often suited to fix something are those who use it every day, which frequently aren't the developers or "owners" of the product.

But it is also a bit of a cautionary tale, exposing conflicts between ideals and realities of shipping commercial software (especially enterprise software) and explaining why User Experience can still be a tough sell in some organizations.

Seeing usability problems first-hand

Craig was on the education team for an enterprise software product with a large company. His job was to train customers on how to use the product. He knew how powerful and genuinely useful it was, but also knew that new features were continuously being added while the number of requests was growing daily. It was becoming increasingly difficult to consider the impact of every change. Something had to give.

All of the effort was being put into the business logic and very little into how everyday users might actually use it. This meant that all of its idiosyncrasies and faults became magnified every time a new feature was added. Craig said that in the focus to satisfy every customer request there just wasn't enough thought about the future of the product among the development team, they just kept adding on while making sure that everything still worked. "There were a lot of stop‑gaps."

That's not to say that the team was clueless or mis-guided. It can be hard to know about a product's usability problems without using it regularly, yet involving customers in the process can also be troublesome. Customers have a hard time imagining a different way for the product to behave, so they are more apt to ask for features rather than workflow improvements. But having the input of someone who teaches it to others can be very useful. They have to explain how to do things with it over and over and can't help but think of ways that it could be improved. Craig was just that person.

Craig had become frustrated trying to explain to customers the convoluted workflows and work-arounds required to use the product, knowing that there was no satisfying explanation for it. He also thought about how much time and money was being wasted getting customers up-to-speed on what should have been intuitive actions. He frequently complained, but wasn't in the right position to have any influence.

I was like 'guys, we've got a much bigger problem.'

One day he overheard some people from the product team talking about hiring a design firm to give it a design overhaul. He got very excited. As Craig told me "I made sure to get invited to that meeting." In the meeting he was amazed to hear them spending "lots of time talking about fonts and colors." He knew that a fresh coat of paint wasn't going to solve the usability problems he knew all-too-well. He told me "I was like 'guys, we've got a much bigger problem.'"

In the meeting, when he said that the product was hard to use, he didn't get very far. But when he showed how it could be made better, people immediately saw what was wrong with the current product. He used Balsamiq Mockups to redesign a few screens so that he could show them how the workflow could be improved. Much like Michael Bourque, Craig used Mockups to tell a story about his vision for the product. This approach was so successful, in fact, that he was asked to take charge of the product right then and there. Craig told me: "I showed them what I was talking about and they made me Product Manager."

Thrust into the spotlight

Craig's promotion to Product Manager cast him in a very different role. He was now responsible for seeing through all the changes he had been suggesting. He learned how difficult it would be to put his obese product on a life-changing diet.

'No' wasn't a word the team was used to hearing.

He began by saying no to a lot of feature requests, which didn't make him very popular. He says "I became one of the most disliked people at the company. Previously we had accepted and queued up every request. 'No' wasn't a word the team was used to hearing, but now they had to hear it from me, frequently."

This wasn't the only change. Craig was using visual mockups to communicate the development plan, whereas in the past they had used giant specification documents containing only a few screen shots, so it took some effort to convert people to this leaner way of doing things.

He persisted. He extolled the virtues of User Experience Design by quoting Don Norman's "The Design of Everyday Things" in meetings and by educating people on the difference between aesthetics and User Experience. This slowly got him the approval to spend development time to improve the User Experience.

To get the redesign rolling, again he turned to Balsamiq Mockups. Craig told me that they created mockups for 70-80% of all the screens in the product, which was a lot. Using them, he reached out to the sales team to vet his ideas. He then involved the development team to assess the feasibility of his designs. This iterative approach helped bridge the gap between the teams who knew what customers were having problems with and the teams who knew what was achievable in the time they had.

Don't think about what it looks like, look at what it's doing.

While most people got very excited when talking over Mockups, from time to time he'd still get asked "why does this look like a sketch?" Craig had internalized all of the User Experience literature he had read and would respond by saying "don't think about what it looks like, look at what it's doing". Again and again, he went through this process until everyone was on the same page and they had "ironed out" the usability and technical tradeoffs associated with the new design.

In fits and starts, the product began to transform into a more usable product that fit its users mental models better, yielding major UI improvements. It was released earlier this year and has been very well received by customers. Here are some screenshots of one of the mockups and the corresponding final product:

Mockup


Final

Lessons learned, applied to a new endeavor

Armed with both his experience as a product trainer and product manager, Craig and a partner recently ventured out on their own to improve the experience of capturing requirements for Agile development teams. They are setting out to fill in some of the gaps they've seen over the years in tools designed to support Agile development. Their new product is called Skore. It is a visual tool that makes writing and creating Agile user stories quick and easy. It cuts out many of the steps and simplifies it to the point that stories can be created in real time during meetings and conversations. Learn more about it at the-skore.com.

Are you a Champion who wants to be featured on our Balsamiq Champions blog? Send an email to champions@balsamiq.com with your stories or blog posts!

Apps for Good in the Media

· Posted by Leon in Articles and tagged · Add a comment

Our friend Mark Littlewood just wrote a great article on his Business Leaders Network blog about his visit to the Apps for Good awards presentation evening. In the article, Mark envisions a future, 30 years from now, where women and minorities are much more represented in technology than they are now, partly due to programs like Apps for Good.

We've highlighted Apps for Good on this blog before, but we wanted to mention them again because Mark's first-person report on the evening was very insightful and it included two wonderful interviews he did asking some of the kids about Balsamiq Mockups. We thought it was too good not to share. The videos from it are below.

Also, here is a video describing what Apps for Good is all about. It's an awesome program. If you pay close attention you'll see some Mockups sightings in it.

Are you a Champion who wants to be featured on our Balsamiq Champions blog? Send an email to champions@balsamiq.com with your stories or blog posts!

Ubuntu Uses myBalsamiq for Community Designed Mobile Apps

· Posted by Leon in Articles and tagged , , · 2 Comments


Ubuntu weather app

I recently came across a blog post by Jono Bacon of Ubuntu called "Community Driven Ubuntu Phone Core Apps". It describes the Ubuntu for phones project, which, in the spirit of Open Source, invites community contributions from not only software developers, but also designers. For the design of their core apps, they are using myBalsamiq, provided free as part of our free for Open Source projects program.

His article talks about all the various pieces in the Ubuntu for phones project and how they all fit together. The last piece of that puzzle is the designers themselves, whom he is reaching out to in his post.

Jono writes:

So, we have a good set of developers assigned for each app, but we would like to invite our community to contribute design ideas for each of these apps. We have already defined a set of user stories and functional requirements, and for each app we have also defined a set of the core screens and functionality that we will need design for. We would like to invite you wonderful designers out there to contribute your design ideas, and these ideas can provide food for thought for the developers.

myBalsamiq works for this project because it provides the ability to contribute designs as well as track feedback and revisions. Ubuntu already has a set of app design guidelines and most of the visual design is provided by the SDK, so what's primarily needed is design at the wireframe level. myBalsamiq makes it easy to flesh out the design concepts before they ever get to code. Ubuntu founder, Mark Shuttleworth, has also been a long-time promoter of Mockups and has several designs done in Balsamiq Mockups on his own blog.

This project is the stuff of Champions because it is open and generous, and it allows people of all backgrounds to participate and work together. It also exposes a process that is often hidden from view for the betterment of anyone who's interested. And, just like Open Source code contributions, it breaks down barriers in that it doesn't matter where you live, who you work for, or what your business card says you are (if you even have one). Anyone with ideas is welcome. There are even roles for non-designers. Using comments in myBalsamiq, anyone is invited to give their feedback on the designs that are submitted.

The comments reveal the design process as it happens. For example, here's a snippet from the comment thread on the weather app:

Mitu replied 4 months ago, re: Sergey's Version 8 from 4 months ago
On the panel with today's weather I would suggest not to use the word "Today".

It would be nicer to place the date on the upper right or under the city name (using a litlle smaller font). And next to the sun image just place a short "Sunny" form.

I would prefer an option to turn off the indicator.

Sergey replied 4 months ago, re: Sergey's Version 8 from 4 months ago
@Mitu, You are right, when i removed word "Today" i got some free space in right region.
I added date under the temperature.
I added option to switch off\on weather indicator: https://ubuntu.mybalsamiq.com/projects/ubuntuphonecoreapps/Weather+App+-+settings

Homero replied 4 months ago, re: Sergey's Version 11 from 4 months ago
Good concept, simple to use and understand. For the top bar indicator, what do you think in putting only the current temperature?

e8hffff replied 4 months ago, re: Sergey's Version 11 from 4 months ago
If the clock, tasks, calendar and alarms, were all brought into a time-line chart, then the weather also could be mapped over the day periods of the time-line chart.

Sergey replied 4 months ago, re: Sergey's Version 11 from 4 months ago
@Homero I think it need option to configure information in indicator, becouse one user want information about temperature, but second user want only information about weather(sun, rain, etc)

This is interesting (to me, at least) because it provides a window into how a lot of software development is done these days - non-co-located people communicating asynchronously, using tools optimized for this way of working. You can actually watch the design improve (and get refined) as more people get involved. It's a victory for ideas over ego in design.

And, in the true spirit of community, this project is not only a way for Ubuntu to get awesome designs from a disparate collection of passionate designers. It reciprocates by allowing those designers to work together, practice their skills, and learn from each other.

Awesome stuff, Ubuntu, we're happy to support it! You guys are Champions!

Check out their myBalsamiq Ubuntu Phone Core Apps project site.

Are you a Champion who wants to be featured on our Balsamiq Champions blog? Send an email to champions@balsamiq.com with your stories or blog posts!


Next Page »