Skip to main content

Storyboard 101



Since I made up my mind to go into the field of user experience and design, I’ve been constantly amazed by how many different concepts and terminologies we have come out in different professions to mean the same thing.

One of them is the concept of a storyboard.

Today I joined a design meetup event by “Design by Night”, the theme of which is to draw a painting to illustrate how we solve a problem using a possible solution. We drew the problem and solution from two boxes and no matter if they make sense to us or not, we have to build the connection.

The problem I drew was mosquitos, and the solution, Jack Ma.

Just the perfect solution.

I can think of a zillion ways how he can solve the problem.

One possible way is for Alibaba to sell Mosquito Repellent to everybody in the world, delivering through ship, plane, truck, motorbikes and even on foot. We will apply them to ourselves and to all animals around us. Mosquitos will have nothing to eat and die.
Another solution is for Jack Ma to give a public speech to all Mosquitos about how much their existence has threaten peoples life, and how they can change their life by joining Alibaba group to deliver products for small and medium sized merchants across the world. Mosquitos will be inspired and join the great army of delivery companies under Alibaba.

Yet another one can be Alibaba to develop a super sonic sound that broadcast through its Taobao and Alipay APP; it kills all Mosquitos on earth. Since the majority of people on earth use some kind of Alibaba product (Taobao; Tmall; Ali Express), all Mosquitos will die.

Just to list out a few.

Towards the end of the Meetup, Lou, the lady who hosted the Meetup, introduced the concept of storyboard. From the way she talked about it, it looks like I am drawing the problem and solution, then figure out the user action which is what users need to do; and then service action which is what the solution does to solve the problem; and of course, eventually, what is the user benefit.

I’ve heard the word of Storyboard many time, so when I came home today, I went online to do a bit more studies on Storyboard.

Appearantly most of the time storyboard means something different. 

For software companies, a Storyboard is a visual representation of the appearance and flow of your application. It is similar to wireframe or part of the interactive documentation. It rather focus on the “Service Action” from Ms Lou.

And thus many things i learnt in my product manager profession applies:  

Have a clear idea of your goals and objectives beforehand.It’s essential to have a clear idea of what you want to achieve by creating a feature or a product. Identify exactly what the user needs to take away from their experience and why they come to you in the first place. Research to find out what needs to be covered and what can be left out, so that you can determine what you are working with in advance.

Know your target audience.Research is key to creating a successful storyboard. Learn as much as possible about your audience while focus on answering the question of why and how will they use your product. Also, assess previous strategies that the client has used to identify what worked and what did not, so that you can develop a more effective storyboard.

Figure out when and how you will assess your audience.While many people might assume that adding assessment is one of the final stages in the planning process, it should actually be one of the first. While you are creating your storyboard figure out where you need to test them, The concept of testing is rather board. you can ask for feedback straightaway, or you can ask a bit of “favor” (e.g. complete profile information; share on Facebook); if users take a positive action it is good indication you are doing well;

Write content for each of your objectives.Writing content for each of your objectives will help you keep your storyboard flow natural and your audience focused. State your topic, explain your idea, focus on key points, and maintain a conversational tone by using simple language, short sentences, examples, or metaphors, and asking questions. 

Be as detailed as possible when storyboarding interactions.As your progress through each screen of your storyboard include every interaction that needs to be integrated into the final design. For example, if you need to redirect to the “add a payment method” under “My Account" when they click on a button, mention that in your storyboard. Do this for every activity, assessment, and navigation icon  so that you don’t run the risk of broken hyperlinks or a disorganized navigational flow.

Prevent cognitive overload.Bear in mind that the storyboard is going to serve as a guide as you move forward in the development process.  So, now it's time to take your final decision about how much content you are going to include on each page and how you are going to deliver the information. If you have a message that may be lengthy or contain an abundance of text, then break it down into more paragraph and only include the key takeaways. By taking cognitive overload into consideration at this stage you can create an application that is concise and cohesive instead of having to make major modifications during the final revision process. 

Map out the navigation.Decide where to put next or back button, what graphics you will use to denote these actions, and how your solution will respond to specific behaviors of your audience. For example, you can outline what will happen if a user clicks on a link that redirects them to a third-party site. Creating an outline for all of these branches will make the design process much easier, as you will already have a clear idea of which navigational elements belong on each page.

Complete Content StrategyI need to decide what to show on what page and on what interaction as it determine how the interface will be built, what calculation is needed, I need to determine what is captured in each step. I can;t emphasize more  how important these things are; consider all the edge cases and how to treat them, at least common situations such as no record found, upload fail; text too long etc; you cannot be vague;  

No matter if it is a mobile app, a website, an open-API, storyboard is very important; or in other words, think through is important; every product is different, and the solution is case specific, but every product should begin with a good storyboard.

Popular posts from this blog

4 Techniques to Make Your UX Review Meetings Successful

As a product manager, I often need to sit down with the executive management team to get their feedback on the new designs. It can be a frustrating process and many times I found that I cannot get things down in the time I am allowed to have.
Nevertheless, not having the sign-off from management is terrible for the team, we face high risk of having to re-work (yes, we always need to re-work, but it feels better if it is an improvement), schedule get delayed etc.
Over my 200+ review meetings, i've came to understand the reasons and learnt skills on how to stir the meeting towards an efficient completion, and I want to share them with you.
There are 4 key reasons of an unsuccessful product review meeting: 
1. Audience Lack the Background Knowledge: especially when introducing a new function, executives don’t know what they are looking at, or how the end users will be using such function, you may have sent the presentation before and again in the meeting invite, it doesn’t matter;

2. T…

What Changes will Machines Bring to us - As Employees

Machine learning to the employment has been a topic in debate. Darrell West, in his paper titled "What happens if robots take the jobs? The impact of emerging technologies on employment and public policy” suggested a list of actions government should take to ensure people whose job has been replaced by machines can live a decent live. The general sentiment seems to suggest a turbulent era as work force transform.

Growing up in China during the time of State owned enterprise reform, I had real experience living through the time of large group of people being laid off because the jobs were suddenly gone. My parent’s generation had to learn new skills for a completely new industry at their 40s and 50s. Few of them made it and even became millionaire, many of them didn’t and the family suffered a lot. I followed the news of Detroit Car manufacturing industry lapse and it shows familiar traits. The fact is, jobs come and go all the time, employee as a group will constantly adapt while …

21 Tops on How to Write a Successful Blog

Hubspot and General Assembly came together to offer a 10 week planner for successful blog. The type of blog discussed in this plan are corporate blogs used to bring people to the site and explore what the company is doing, potentially generate a lead.




Identify Your Target Persona: talk to sales team and research contract dataStart Building Evergreen Content: start with evergreen contents that stay relevant though time; do keyword search to see what people are searchingChoose the Right Content Management Tool: a good tool is easy to use and allow users to track metrics such as conversion rate, page view, and where traffic come fromDesign Your Blog: consistent layout; Focus on Your Content Strategy: basically it is depending on what you wantSet Subscriber Path: there needs to be a workflow for emailing the subscriber, a subscription form and an unsubscribe form. Hubspot is towards the "don’t email your subscribers too often” group while I also heard UI Breakfast Jane Portman talked …