MarketingSherpa Blog

Here at MECLABS, we talk a lot about the testing process.

How to optimize and improve emails, landing pages, lead generation forms, shopping carts … all things Web. But, the testing process isn’t just a way to improve website performance. The general principles are transferrable to so much more.

One thing I’ve been particularly interested in recently is how to use testing to improve office and employee productivity.

Consider you’re a manager and have an employee who has been having problems meeting deadlines.

What do you do?

Step #1. Identify the problems with productivity

You’ve already identified the overall problem – missing deadlines.

Most people immediately jump to solutions and try to answer this question: “How do I get this employee to stop missing deadlines?”

Obviously, it’s because they need more resources, right? Maybe it’s because they weren’t clear on the requirements and what was expected of them. Or maybe, they just didn’t see the point and weren’t properly motivated.

That’s the same thing as saying, “My Landing Page isn’t converting,” and immediately jumping to solutions like, “I need to change the offer, add a video, or add more testimonials.”

But, what step did we miss in that jump … Analysis!

Step #2. Dive deeper to identify the elements that impact productivity

You can’t solve a problem unless you have a deeper understanding of the root cause.

For a website, we’ve been trained to ask, “What problems or obstacles are impeding a conversion on this page?”

Thankfully, we have a handy Conversion Sequence heuristic to help us identify the elements that impact conversion by asking the right questions during analysis:

• Is it because there’s a lack of value?
• Is the value clearly communicated?
• Is the process is too confusing?
• Are people concerned about what’s going to happen with their information?

All of these answers could be the possible culprits to your low conversion rate, but you’ll never know without identifying these possible issues and testing possible solutions.

The same thing goes for your people.

For someone missing deadlines, the question isn’t “How do I fix this?” Instead, the first question needs to be “Why are they missing deadlines?” or:

• Are they confused with the exact date/time of the deadline?
• Do they have a clear understanding of all the steps involved in the project?
• Do they know all of the resources they’re going to need?
• Are they able to build a timeline backwards from the deadline with reviews and milestones?
• Do they not understand the impact the missed deadline will have on them personally or the company?

As you can see, the list of questions goes on and on, just like for your website.

Read more…

One of the most common questions and debates we have here at MECLABS is, “How radical do we go?”

Let me explain – for every test, we have an objective we’re trying to accomplish and a set of metrics we’ll use to judge the performance and success of the test. If we “go radical” and change lots of different elements on the page, we might hit it big, or we might tank. But, either way, we wouldn’t know the true impact of any specific change.

If we “go conservative,” we’ll be able to directly tell what the impact of changing a specific element was, ensuring we learn something, but might never be able to hit that lofty conversion goal our team has set.

So, which approach is right? Well, the short answer is they both are. The long answer is the rest of this post.

The right blend between radical and conservative tests

That may sound like a cop out, but a successful test strategy needs to find the right blend between radical and conservative tests. Let’s try an analogy …

Let’s say you just started playing baseball. You’ve had batting practice with your coach and just can’t seem to connect on any pitches. So, your coach starts tweaking. Widen your stance. Lift your elbow. Tilt your head. Tweak, tweak, tweak. But you’re still not hitting anything.

Then, you try something radical. You walk to the other side of the plate and take the first pitch into the outfield. Turns out you bat lefty. That would have been good to know an hour ago. Chances are, you were never going to succeed with small tweaks, because there was something fundamentally wrong with your approach.

The same goes for testing. If you’re making progress with small tweaks, a headline here, button color there, you may never reach your true potential.

We always want to get a solid learning from every test we perform, but looking back through the archives, a lot of the largest wins we’ve ever achieved don’t come from single factorial tests, or variable clusters where we try to focus in on specific elements of the MECLABS Conversion Sequence heuristic like friction or value.

Instead, they come from radical redesigns, where we test a totally new approach or simultaneously improve numerous elements we identified as issues with the page.

Read more…