survey for Korean app users

Worldwide survey of mobile app users

http://infogr.am/app-user-survey-0?src=web

Planning your survey (to build new app)

Planning your survey

Before you start jotting down questions to ask users, spend some time thinking about the work your team will be doing in the coming year. Are you planning new mobile apps or a responsive redesign? Then questions about devices used and behaviors around mobile devices might be in order. Rethinking your content strategy? Then you might want to ask a few questions about how your customers consume content.
You can’t predict all of the projects you’ll be working on in the coming year, but tuck a couple of sections in your survey about the projects you’re certain about. This will give you the research you need to start new projects with solid foundational data.
Google Drive is a great place to start collaboratively building survey questions with colleagues. Questions that seem crystal clear in your head get challenged, refined, or even expanded quickly when the entire team can chime in.
As you craft your survey, try to consider how you’ll filter it once all of the data is compiled. Do you need to see responses by industry, by age of an account, by devices used, or by size of company? Adding the right filter questions can help you discover fascinating patterns in user segments. Filtering on responses to a few questions can surface insights like: customers in non-profit companies with more than 100 employees are 17% more likely to use an Android phone and are most attracted to features A, D, and F. A designer working on the landing page for a non-profit would love to have concrete information like this. Filter questions are key, so consider them carefully. But don’t go overboard — too many of them and you’ll start to hurt your survey response rate.
Multiple choice questions are the heart of most surveys because respondents can complete them quickly, which increases response rate, and researchers can analyze them without a lot of manual categorization. Open text field questions are valuable too, but be careful not to add too many to your survey. You’ll hate yourself after the survey’s done and you have to sort through and tag thousands of open responses so patterns become visible. Oy vey!
An open-ended question works well towards the end of the survey. At this point respondents have a lot of topics swirling around in their head and tend to say weird things that will pique your interest. This is where you’ll find the outliers who are using your product. They’ll be fascinating to interview, and on occasion will help you see your work in a brand new way.
Conclude your survey with a question asking permission to get in touch for a followup interview so you don’t pester people who want to be left alone.
With your questions nailed down, it’s time to build out that survey and get it ready for sending!

Building your survey

There are dozens of apps you could use to build your survey, but SurveyMonkey is the one that I prefer. It lets you pass in variables for each respondent such as user ID and email address. Metadata about respondents is essential if you’re going to do any follow-up interviews with your customers in the coming year. SurveyMonkey also makes it easy to set up question logic, showing questions to customers only if they responded in a certain way to a prior question. This helps you avoid asking irrelevant questions to some respondents.

http://24ways.org/2013/data-driven-design-with-an-annual-survey/

Different types of wireframing, prototyping

Hand drawn sketches

Are a very quick and fast way to convey a layout to others that can be changed rapidly. They are the best precursor to computer aided drawing and their low-fidelity format encourages experimentation and honest critique.

 

Collaborative sketches

The only real difference here is that a team produces the wireframes together. It helps the group to discuss reasoning behind solutions and iteratively sketch solutions. Several solutions helps the team explore different approaches and it provides a framework for participants to articulate their ideas.

Annotated wireframes
They are produced to describe the functional elements to development teams. Elements are explained in small paragraphs alongside the diagram and this enables the wireframe to be understood without verbal explanation. They are valuable tools to clarify function and focus on a page.

High fidelity wireframes
Mainly produced to canvas opinion from users in interviews about a layout or concept. They should always require a usability expert to explain the context and purpose of the diagram. It really is the nearest step before presenting the surface design of the solution. The line between wireframe and functional prototype is a thin one here, it may be better using resources on a working prototype.

http://userpathways.com/2008/06/the-what-when-and-why-of-wireframes/