Centercode is the leading platform to manage impactful in-the-wild user tests.
Start for free, scale as your program grows.
Adaptable solutions for teams looking to build better testing programs and launch impactful products.
Schedule a demo to talk with an expert.
Delta is the next generation of beta testing, leveraging Centercode technology to automate time consuming tasks while increasing user engagement and test results.
What is delta testing and how are tech leaders using it to deliver customer insights throughout agile development? This guide has all the answers.
Reading through this blog, you might be looking for advice on your next beta, or perhaps debating whether to run a beta at all. You could be neck-deep in five projects, or speeding through our training materials preparing for your first. No matter your scenario, there are some simple (yet critical) concepts that directly influence your ability to run a successful test.
Many beta testing processes are born out of necessity. Your team needs to run a beta test, so you pull together a combination of tools, spreadsheets, and emails to get it done. As your company and beta program grows, however, this approach can become confusing for your customers, who are trying to remember multiple logins, URLs, and processes.
Testing B2B products is particularly challenging. You may have a small number of customer sites testing your product, but each site could have many people providing feedback or be testing multiple products at the same time. If you’re trying to keep track of all that feedback using email and spreadsheets, data will end up falling through the cracks.
Many of you are familiar with our Beta Resource Library, where we publish detailed content on beta testing best practices. Well, we also have a ton of resources on Centercode’s software and service offerings. So we’ve put together a resource library specifically aimed at helping people determine whether we are the right fit for them.
This is a guest post contribution by James McKey, a beta program manager at Symantec and longtime user of the Centercode platform. In this post, James goes into the pitfalls of beta surveys, including how to use Centercode to give your testers the best survey experience. — Emily @ Centercode We’ve all suffered through survey […]
If you’ve watched our intro video for Centercode Connect, or had a demo, you know how much Connect can do. It’s designed to handle every detail of your beta test, from recruitment to feedback reporting. When you’re first learning about Connect, it can be a lot to keep track of.
We’re excited to announce our partnership with Cincinnati’s nationally-ranked startup accelerator The Brandery. Centercode will be providing beta management software and guidance to The Brandery’s 2012 class of 11 promising startups as they beta test their first products. Each year The Brandery chooses a group of startups to take part in their 14-week accelerator program. […]
There’s a long-standing practice in Marketing, Product Development, and Usability Testing called “following your customer home” Intuit’s famous Follow Me Homes are a great example. The practice is also gaining traction in beta testing, so we thought now would be a good time to discuss some best practices and caveats for scheduling meetings with beta testers. Done correctly, these meetings can have a great effect on participation and open doors to insights that are hard to obtain through other methods.
We’re happy to announce the release of Centercode Connect 9.4 this week, with customer roll-outs beginning today. In this post, we’ll talk about some of the new features and improvements from this release, including a brand new module called Assigned Test Platforms.
At Adobe, we’re always trying to introduce new testers into our prerelease program (that’s what we call beta). There are many benefits to getting new testers into each prerelease cycle. Not only are more testers expected to generate more feedback, they also increase the likelihood that your product is tested by people from different industries, geographies, profiles and with varied system configurations and expertise levels. The challenge for many beta managers, though, is where do these new testers come from? To help, here are 7 tips you can use to grow your tester community — many of which have worked very well for us.
We’re very excited to announce Centercode’s acquisition of Customer Feedback Solutions (CFS, custfeedback.com), a New York-based provider of beta test and feedback management solutions. The executive team at CFS felt that Centercode was a great fit based on our industry knowledge, comprehensive offering, and experience in supporting, complex web-based applications and the needs of their customers.
When you encounter a critical issue in a beta test, things can get out of hand quickly. Your testers are demanding results, your developers are demanding data, and your marketing people are demanding reassurance. What you need is a reliable series of steps to help you maintain control of your beta and reduce the heat you’re feeling. So, we’ve developed something called the ICEGAP protocol for just this situation.
If you want to run an effective beta test, being active and engaged every day is crucial. It can be tough if beta management isn’t your full-time job, but it’s hard to argue with the increased feedback and participation you’ll see from being that involved. And nobody wants to be the person who let critical bug reports go unnoticed for a few days. Luckily, we’ve got some helpful tips to get as much as you can from the time you have to participate.
If you ever find your beta program encountering resistance, take a look at where it fits in the big picture. No man is an island, and the same goes for beta programs. The more disconnected your work is from others, the harder it becomes to see the good you’re doing. But there’s one sure-fire way to get more recognition for your beta tests — sharing your test data with others. There are more teams that could benefit from it than you may realize.
Most people think beta tests serve one very specific purpose — ensuring product quality before you ship. Fixing bugs is important, but if your beta is designed with only that goal in mind, you’re missing out on opportunities to significantly improve the marketing of your product. We’re here to help, though, with four tips to generate valuable marketing data through your beta test.
