Loading...
Answers
MenuHow do you approach / engage with users to ask them for advice on how to improve your app and other quality information?
This question has no further details.
Answers
You need to build your community from the get-go. Start with your beta testers, creating a community where they talk to each other about issues and come to you with ideas, suggestions and bugs. Encourage them to do this, no matter the issue, and respond quickly.
If you develop a community like this from the start, it's very easy to get your users to give advice on improvements and the like. You'll quickly see the beta users who are very involved, and ask them privately for suggestions of other beta users.
Beta users WANT to provide feedback, and they will provide some of the must useful feedback you can get, so long as they see you responding and taking into consideration at least some of their ideas. If you start this in beta, you'll build a community of users who want to help you succeed and want to help you improve your product, for the long haul.
Tough question without some context to give a succinct answer. Obviously an incremental improvement that will benefit a large group of users can be solicited in a survey. Apps that are "expert systems" delivering knowledge for specific circumstance or user communities may require more thorough engagement, (a first aid app for campers or sailors for instance). Whatever way of gathering use cases or other user suggestions for performance or feature improvement, what is common to all is the need to have a great system for estimating time, sweat and dollars to do it so you don't make false promises and a way to keep everyone focused (a huddle or sharepoint) so that the promises you make are kept.
I've been involved in everything from concept research (Harley-Davidson, Hallmark) to formal usability testing (United, NatGeo) to intercept surveys (Purina, SC Johnson) and so on.
The fact that you are interested in understanding your users' needs puts you ahead of the game already.
As usual, the way to best understand these needs depends heavily on your research objectives, budget, and time frame. There is no one right answer.
So, in the spirit of the Olympics, here are some bronze, silver and gold options.
Bronze #1: Add a button in the app that says "How are we doing?" or "Help us improve..." or similar and link to a simple email form. Language is everything here. If it just says "Contact Us" it will be ignored by everyone except those who have a beef.
Bronze #2: Send an email to your core user base -- the group within the group [1] if you will -- asking them to a couple of well-worded questions. Again, wording the questions is a critical art form that will ensure you're getting "real" answers that you can tie back to addressing your research objectives. Your questions must be clear, focused, and of the appropriate complexity.
Silver #1: Run an intercept survey on your website or if possible within your app. This will typically "cost" more as you'll likely want to spend time planning the survey questions, determining how you are going to screen prospective participants, and deciding how you'll report the findings and recommendations. Depending on the complexity of the survey and number of participants, you may find it worthwhile to engage a 3rd party, which range from simple self-service tools to full-blown research consultancies.
Silver #2: Perform a "guerrilla usability test" or "hallway test." Just Google it. Short version is it's a "discount" way to do a usability test, and often provides a much better value (cost-to-findings ratio) than a full-blown usability study.
Gold #1: Do some concept research. Essentially focus group where you're simultaneously trying to vet concepts before you invest too heavily in building them, and also to solicit ideas from participants. I've seen concept research done with everything from tissue sketches to fully developed products and everything in between (mood boards, functional prototypes, etc).
Gold #2: Perform a full-blown moderated usability study. As with intercept surveys, there are ways to do this for more or less time / money, but usually you'd want to work with a professional as findings from an improperly run usability study can do more harm than good. Unlike intercept surveys, usability studies are more qualitative so you get much richer texture from a much smaller group of people.
Those are really just the tip of the iceberg / knee-jerk examples. If you really wanted to go full-bore with the user-centered design approach you'll start getting into areas more similar to anthropology including ethnographic studies, contextual inquiry, and customer experience modeling and the like.
That said, hope these examples help you to get going in the right direction(s).
TL
P.S. Feel free to reach out to me here if you'd like to talk in more detail about your particular research needs... https://clarity.fm/toddlevy
[1] http://www.shirky.com/writings/herecomeseverybody/group_enemy.html
In my experience, there are two schools of thought. You might not like my answer -
1. Ask them
Take the time to bring them into your office and watch them surf and keep it open minded. Or hire an online video review company that takes videos and screengrabs of the whole thing. It's the advanced technology that a couple businesses provide at a fraction of the cost from only a couple years ago. The trouble is, people don't know what they want. They need it pried out of their minds - seduced out of their emotions. Wyatt Jenkins of Shutterstock is a master at understanding the minds of the consumer - he has written about this some (and about philosophy #2 even more) - but in my opinion, experts who can deliver results through extensive surveys like this are very rare and expensive.
2. Don't ask them (or just ask them by whether they part with their money)
Malcolm Gladwell explains it concisely I think when he discusses spaghetti sauce. Most of the times, your customers do not know what they want. The goal here is to provide your customers with many opportunities in many places to provide their feedback. And then like 37Signals says in their super business guides, just delete their feedback. Ha! Although that's kind of out of context -- the point they are making is that if the customers demand something over and over, you won't miss their demands because they will become repetitive. And then you must deliver and wow them.
I side with philosophy number two because it is more constructive with managing risk and sides well with iterative development. In my experience, focusing on key things, key functions, and doing them better than anyone else is by far the most important. The modern way to do it, is to keep the qualitative feedback from the customer out of it, and just test them by split testing your applications. Then you'll get the "money where your mouth" feedback is, because the revenue and conversions will be driving your decision making...and thus your app's evolution.
On the other side, if you are a boutique brand, and have plans for world domination, then perhaps you should take the chance on an extensive hail mary R&D project. I don't like that idea because of the #1 rule of investing - security.
Related Questions
-
What is the process of productizing a service? Also what are some good examples of productized services that have scaled?
2 different categories come to mind. H&R Block or other tax preparation services. The second is restaurants. This may seem like a product more than a service but I think it truly falls into the category of service, especially if you look at the national chains. Think Applebee's, TGI Fridays etc. The reason people go to these places is because of the experience they receive. The franchisors have created a system that generates nearly identical results nationwide. The first thing you need to do is figure out what makes your service superior to others out there, then you need to figure out how and why this is the case. From there you need to document it and make sure that you have a mechanism in place to ensure compliance. Granted that is a huge amount of work, but the basic premise is quite simple. You want all of the people you hire to do things more or less the way you would do them.MF
-
For a once-off price point of $2,500, what would you expect from an agency-grade marketing package? Consulting, design, digital asset, tool, campaign?
Consider instead where a $2500 price point puts you. I use a selling technique called Monetizing The Problem, and in that process I get the prospect to calculate the size of their problem. Then I charge 5-10% of that figure. There's never any resistance, because they see where the number comes from, how it's based on reality--and a number THEY came up with (not me). So here you are at $2500. Let's be conservative and say that's 5% of the size of the problem. Meaning you are trying to help them make $50K in sales over the next year. What kind of a business has a revenue goal of $50K? A sole proprietor who's just trying to get by? Is that your target customer? Really think about this. A serious SME won't play at the $2500 price point, because it's too low. They know the vendor can't commit enough resources to do the job they really need done. For instance a business with only four high-value employees plus the owner needs to bill at least $60K A MONTH to survive!! Why would they let you touch their marketing collateral (that's their website) for a mere $2500?! Stay at $2500 and you're attracting a really low level of client. If you have the horsepower to achieve more with the skills you have, then I highly recommend going after a better class of customer.JK
-
I'm looking for a great full service app design firm to build my app and help with all design, branding, development, etc. Anyone know any good ones?
Yes. Who I would recommend would depend on what you'd like to see happen. Are you building only for iOS, or only for Android, or both? Will you have a bunch of content/stuff in your app or just a little? Are you thinking game or non-game app? Do you already have a big fanbase or would you be trying to build one while building the app? It's easy to save a bunch of money on mobile development if you know how, and even easier to overspend. Making an app can be a ton of fun or a major headache. I'd recommend the fun. So if you want an outside perspective, give me a ring.AC
-
What product should I build?
You can only solve a big problem that changes the world if you solve a problem that is deeply personal to you. Two great examples and why they worked: Roy Raymond was a sad pervert. He'd buy bras and panties at the department store and all the clerks thought their thoughts about him. Roy felt embarrassed. He wasn't really a pervert. He just wanted to buy lingerie for his girlfriend. So he solved this major problem he was having. He created a space where men could feel comfortable coming in and buying sexy lingerie for their partners. He called it Victoria's Secret. But Roy, by solving this important personal issue for himself, apparently solved the same issue for many other men. First year sales were over $500,000 and he quickly opened up three more stores. In 1982 he sold Victoria's Secret for one million dollars before trying multiple other businesses that ended up failing. One MILLION Dollars. A decade later Victoria's Secret was worth over a billion dollars but Roy Raymund was nearly bankrupt and had missed the huge run-up in it's value. -- Picture New York City in the late 1800s on a rainy day. It was disgusting beyond belief. 150,000 horses transported people up and down the busy streets. Each of those horses, according to Super Freakonomics, dropped down about 15-30 pounds of manure. That's up to 4.5 million pounds of manure A DAY on the streets of NYC. And now imagine it raining. Would you cross the street? How long could this last? How long would the city survive without being infested with crap and all the diseases brought with it. What would happen as population of both men and horses increased? Was someone working on inventing a gigantic manure scooper? How would this problem get solved? It never got solved. Instead, Henry Ford invented the assembly line to mass produce cars. Every horse lost their job. People began to drive cars. Manure problem solved. -- In both cases there is a common theme. Someone outside the industry solved a problem that was personal to them that then changed an industry forever. Roy Raymund wasn't a fashion designer or a retailer. He worked in the marketing department of Vicks, which makes over the counter medications. Henry Ford, I don't think, ever worked in the manure industry. Instead, each person focused on a problem that was important to them. A problem that excited them at that moment in time. Raymund wanted to avoid being embarrassed in the future. Ford wanted an efficient way to make cars. The ONLY way to change the world is to solve a problem that is important to YOU. They had to choose themselves for success before they could save the world. Raymund had to convince himself that he didn't belong in the marketing department of a division of Procter & Gamble. He borrowed $80,000 and took the big risk of starting a business. Ford had to survive numerous failures and bankruptcies in order to find a cheap way to make cars. He would abandon investors, people who supported him, and even companies named after him, in his quest to solve his problem in his own way. Nobody gave them permission. And neither of them set out to change the world. They only wanted to solve a problem that was personally important to them. It's unfortunate that often we forget that choosing ourselves is not something that happens once. It has to happen every single day. Else we lose track of that core inside of us that solves problems and is able to share them in a way that makes the world a better place. Ford forgot this and became obsessed with Jews. Ford is the only American that Hitler mentions in Mein Kampf: "only a single great man, Ford, [who], to [the Jews'] fury, still maintains full independence...[from] the controlling masters of the producers in a nation of one hundred and twenty millions." And what happened to our embarrassed marketing manager that has ignited the passions of men and women for the past 30 years? Roy Raymund saw the value of Victoria's Secret jump from the one million he sold it for in 1982 to over a billion dollars a decade later. He failed in business after business. He got divorced. Then at the age of 46, my age, he drove to Golden Gate Bridge, jumped off it and killed himself. Before you can save the world you have to save yourself. But you have to relentlessly do it every day. Sometimes the train wakes me up at night and I feel scared. What will the world be like for my children? I won't always be able to help them. I don't even know if I do enough to help them now. And then I remember. I'm alive for another day.JA
-
What is the best method for presenting minimum viable products to potential customers?
Whoa, start by reading the Lean book again; you're questions suggest you are making a classical mistake made by too many entrepreneurs who live and breath Lean Startup. An MVP is not the least you can show someone to evaluate whether or not building it is a good idea; an MVP is, by it's very definition, the Minimum Viable Product - not less than that. What is the minimum viable version of a professional collaboration network in which users create a professional profile visible to others? A website on which users can register, have a profile, and in some way collaborate with others: via QA, chat, content, etc. No? A minimum viable product is used not to validate if something is a good idea but that you can make it work; that you can acquire users through the means you think viable, you can monetize the business, and that you can learn from the users' experience and optimize that experience by improving the MVP. Now, that doesn't mean you just go build your MVP. I get the point of your question, but we should distinguish where you're at in the business and if you're ready for an MVP or you need to have more conversations with potential users. Worth noting, MOST entrepreneurs are ready to go right to an MVP. It's a bit of a misleading convention to think that entrepreneurs don't have a clue about the industry in which they work and what customers want; that is to say, you shouldn't be an entrepreneur trying to create this professional collaboration network if you don't know the market, have done some homework, talked to peers and friends, have some experience, etc. and already know that people DO want such a thing. Presuming you've done that, what would you present to potential users BEFORE actually building the MVP? For what do you need nothing more than some slides? It's not a trick question, you should show potential users slides and validate that what you intend to build is the best it can be. I call it "coffee shop testing" - build a slide of the homepage and the main screen used by registered users; sit in a coffee shop, and buy coffee for anyone who will give you 15 minutes. Show them the two slides and listen; don't explain, ONLY ask.... - For what is this a website? - Would you sign up for it? Why? - Would you tell your friends? Why? - What would you pay for it? Don't explain ANYTHING. If you have to explain something, verbally, you aren't ready to build your MVP - potential customers don't get it. Keep working with that slide alone until you get enough people who say they will sign up and know, roughly, what people will pay. THEN build your MVP and introduce it first to friends, family, peers, etc. to get your earliest adopters. At some point you're going to explore investors. There is no "ready" as the reaction from investors will entirely depend on who you're talking to, why, how much you need, etc. If you want to talk to investors with only the slides as you need capital to build the MVP, your investors are going to be banks, grants, crowdfunding, incubators, and MAYBE angels (banks are investors?! of course they are, don't think that startups only get money from people with cash to give you for equity). Know that it's VERY hard to raise money at this stage; why would I invest in your idea when all you've done is validate that people probably want it - you haven't built anything. A bank will give you a loan to do that, not many investors will take the risk. Still, know not that your MVP is "ready" but that at THAT stage, you have certain sources of capital with which you could have a conversation. When you build the MVP, those choices change. Now that you have something, don't talk to a bank, but a grant might still be viable. Certainly: angels, crowdfunding, accelerators, and maybe even VCs become interested. The extent to which they are depends on the traction you have relative to THEIR expectations - VCs are likely to want some significant adoption or revenue whereas Angels should be excited for your early adoption and validation and interested in helping you scale.PO
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.