Group items tagged

Create case studies If you really want to show the value in what you offer, you have to create case studies. The simple ones won’t cut it, you have to give detailed ones… ideally with the exact things you provided and the results. To legitimize the case studies, make sure you put in testimonials from customers. This can be done in the form of video or text and if you happen to go the text route, make sure you include: Their full name Company name Their picture Title at the company If you want to see an example of a good case study, check this one out from Conversion Rate Experts.

Offer a free trial One of the easiest ways to handle price objections is to offer a free trial. Remember, just because you are offering a free trial doesn’t mean you can’t take a credit card up front. With Crazy Egg, one of our biggest objections from people is that our prices are too high. We created a “free trial” offering in which people had to put in their credit card up front. That offer converted at 59% higher than our 30 day money back guarantee offer. Keep in mind that you will get a lot of people who will cancel your service before their free trial is up, so when you a/b test this you have to also include cancelations into your calculations.

Explain the value The easiest way to demand a high price point is to explain how much money you are going to either make a company, or how much money you will save them. If you can explain this in an easy to understand fashion and provide case studies to back it up, it shouldn’t be hard to demand a premium price. A great way to do this is through sales copy. And don’t worry, your copy doesn’t have to be sleazy. I do this with Crazy Egg, NeilPatel.com and I also used to do it for my Quick Sprout Traffic System. You could even spice up your sales copy by including a video incase people don’t want to read your copy.

1. Customers Care More about Service Quality and Attitude than about Service Speed

A recent Gallup study reveals that when it comes to memorable service people tell their friends about, it’s more important that the service provided feels “thorough” and friendly, rather than quick. This was especially true for service in premium or prestigious markets, such as customer support at a bank.

Not only that, in a Customer Experience Report by RightNow, researchers found that the #1 reason customers would abandon a brand was due to poor quality and rude customer service, which were cited 18% more often than “slow or untimely service.”

1. 80/20 rule from Noah Kagan Appsumo’s founder, Noah Kagan, notes that one rule of thumb that they follow is to use 80% of their marketing budget for things that are working and 20% on newer marketing initiatives. One more thing: they go all in when they find marketing channels that work. You can watch one of his presentations where he shares his experiences of growing Mint, Facebook, and AppSumo here.

2. Communicate, communicate, communicate At Treehouse, we work remotely and as you might imagine. There are some that think there is no replacement to working in person while others support it. For us, we’re half and half – we have an office in Orlando and we also have a team up in Portland. The rest of us are distributed. But hey, it works because we communicate a lot. If you don’t feel like you are running enough A/B tests, speak up about it. If you feel like the team needs more developers, speak up. If you feel like an executive decision is going to cost the company money in the long run, talk. People might not always agree with you but it’s your job to communicate. You’re doing the company a disservice if you aren’t being honest. To get you started, here are some tools we use to communicate: Campfire Skype Google Chat Google Hangout GoToMeeting – we use GoToMeeting for our leadership meetings. It’s very simple to use and the video quality is pretty good.

3. Be a voracious reader Although there’s a lot of crappy content circulating the internet, there’s always going to be someone you can learn from. The key is being able to discern signal from noise. For example, if I’m looking to learn more on conversion rate optimization, there are great blogs such as Unbounce, ConversionXL, KISSmetrics, SEOmoz, and more. Just look at the detailed blog posts that they write: 10 Useful Findings About How People Use Websites – ConversionXL 5 Landing Page Conversion Killers – Unbounce The Ultimate Guide to Conversion Rate Optimization – SEOmoz If your goal is to squeeze every penny out of your website, you should be reading conversion rate optimization articles like the ones above. They cost no money to read and stand to help create original ideas that will eventually create more profit for you. This applies to any topic you’re interested in. Using the right tools can go a long way in helping you save time. If you’re on the go and don’t have time to read, you can use Pocket. To help you find relevant topics/articles via Twitter, you can grab curated lists using Listorious. Finally, I like picking off interesting topics from Inbound.org or Hacker News. Key takeaway: don’t read every single blog out there. Find the ones that actually add value and follow them.

"I always thought advertisers were master manipulators / slick bamboozlers / out-and-out liars, but what struck me most in my time here was how earnestly everyone was trying to understand and help consumers." They're nice about it, but that's the idea.

Given that sincerity itself isn't usually very funny, dramatic, innovative, saucy, scene-stealing, or luxurious, it is rarely chosen as the animating spirit of our end-product. But it is totally embedded — indeed, institutionalized — in the process of making advertising. And there's a very good reason for that: without a sincere curiosity about and empathy for the people we hope to reach, we stand no chance of developing a compelling conversation with them. Indeed I would argue that sincerity drives the success of the best and most successful marketing, no matter what the execution may turn out to be.

As Ogilvy's lead for ethnographic research, I head a small team that makes documentary videos about the lives, habits, values and affinities of various groups that our clients hope to reach. In this role I have the rare opportunity to parachute into an incredible range of micro-worlds, both within the US and globally. They are invariably FASCINATING, and so we take bets on when this seemingly endless stream of human interest will run dry — anticipating a day that must come, when one of these projects turns out to be boring. Not too long ago we thought we'd finally arrived: an ethnography of suburban lawn-care. Had to be deadly, right?

Modern Techniques A decade later, things have changed since those early days of guerilla user testing. Now there are a few different ways to highlight usability issues and some of them are even easier, quicker, and cheaper to implement that the in-person tests that Nielsen popularized. Here are 4 test types that I’ve used: In person, moderated and lightly scripted: This is the traditional format of a usability test and of the in-person techniques, it’s the easiest one to get started with. A quick definition of terms: in person means that you’re sitting down with the user, moderated means that there’s someone talking to the user and acting as a sort of referee to keep things on track, and scripted means that there’s a fixed set of tasks written down in advance and that the moderator wants the user to accomplish. In person, moderated and unscripted: This is the Listening Lab technique popularized by Mark Hurst. It requires a bit more experience and finesse to pull off in order to gather valid usability insights without turning into a completely unstructured focus group. In it, the moderator asks the user what tasks he or she wants to accomplish before diving into the app, based on their demographic, a loose conversation about their interests, or their impressions of external marketing pages. Remote and moderated (scripted or unscripted): This can be roughly the same as the two techniques above, except the moderator and user aren’t physically present in the same room and use a video app like Skype to connect instead. This is especially a help to early stage projects, when initial early users can come from any part of the world. Remote, asynchronous and heavily scripted: This is the absolute easiest and most newbie-friendly way to try user testing. It’s enabled by relatively new tools like Usertesting.com, where the moderator and user don’t chat in real time and instead, the user is left on their own to follow step-by-step instructions on how to use the site or app in question, while their mouse movement and audio feedback is recorded.

The basic framework of an in-person tests is: Think about what goals you’d like the user to accomplish (yes, even for the unscripted tests because you still want to see if they can complete certain tasks, although in a looser, unguided format). Record everything – at least the audio and screen, if not also their face and body, so you can review later as well as share with the team. It’s a newbie mistake to try to moderate a test at the same time that you’re analyzing it for lessons, and even newbier to ask stakeholders to just listen to a summary when audio/visual feedback can have such a punch. Use about 5 or 6 people – any less has too much noise while any more has diminishing returns. Note that a qualitative research method like this is different from a quantitative one like A/B testing, where the cutoff is much higher and more users is always better. Let people explore and make mistakes on their own while also keeping them on task. Don’t talk so much that you’re explaining everything on the screen like a car salesman, but also don’t morosely sit back and let them feel judged. Try to strike a balance between friendly and observant.

The question The main question in play here is: How thick should clients be? Let me define my terms: I define the Client as the thing which is used by exactly one user, which interacts directly with that user, and which is probably physically close to that person. I define the Server as the thing which is shared by multiple users, which interacts directly with the Client, and which could be physically located anywhere. I define the Pipe as the connection between the Client and the Server. I define the notion of a Thick client as a relative term. Thicker clients have more app-specific code and are less dependent on the Server. Thinner clients leave more of the app-specific work to be done on the Server. There are two main variables in decisions about the thickness of clients: The quality of the Pipe: This includes bandwidth, latency, availability, reliability, and cost The Client side costs: This includes cost of hardware, software development, deployment, upgrades, and maintenance. And, there are two laws which apply: As the quality of the pipe goes up, the client can get thinner. As the client side costs go down, the client can get thicker.

This issue is not new Back in the 1960s and 1970s, when we only had mainframes and minicomputers, there was a distinction between smart terminals (thick clients) and dumb terminals (thin clients). In the 1980s, we got workstations (really expensive thick clients, purchased by people who perceived them as cheap compared to the mainframes and minis) and microcomputers (far less expensive thick clients, purchased by people who previously didn't have a computer at all). In the early 1990s, the high cost of workstations gave rise to X terminals, thin client devices which couldn't do much more than display the graphical user interface. My manager bought one of those fancy new 19.2k modems and actually tried doing Motif widget development from home. In the mid 1990s, web browsers appeared. For a very brief time, this technology was regarded only as a way to collaborate on hypertext documents. This phase of the web lasted for most of an afternoon. Meanwhile, back in Champaign, Illinois, the Unsung Hero and His Eminence were busy building a web browser which had more "stuff" in it. What kind of stuff? The sort of stuff that made web browsers into a platform for delivery of apps. And the technologies of the web have been moving primarily in that direction ever since. Java applets (developed a fatal disease called Swing) ActiveX (declared dead seven years after it went missing) Flash (murdered by Steve Jobs) Silverlight (murdered by HTML5) In the late 1990s, people (Oracle, I think?) tried to sell something called a Network Computer. It was a little PC with a video card, some RAM, an ethernet card, a web browser, and no hard disk. Thin.

HTML5 arrived. Actually, the spec is still a long way from being finalized, but nobody knows that. People needed a name, so they started saying "HTML5" before it was fully cooked. Common usage of the term "HTML5" is actually fairly accurate, at least compared to the way telecom companies use the term "4G". And now, this war has moved to the battlefield of mobile. Smartphones and tablets.