Try our conversational search powered by Generative AI!

Kevin Schofield
Mar 27, 2024
(3 votes)

Lessons in Experimentation from Sesame Street

A few months ago, I was watching Sesame Street with my four-year-old son. The Sesame Street team was building two cardboard ramps for Elmo and Rosita to race ping pong balls. After the first race ended, everyone celebrated Elmo’s victory – but Rosita wanted to know why Elmo’s ball was faster than hers. 

Fortunately, there was a framework in place to answer these types of questions: 

  • I wonder… 
  • What if... 
  • Let’s try! 

Elmo, Rosita, and Julia started talking about the differences in the two ramps. They were both made of cardboard, and they had the same ball roll down them. However, Julia noticed that Elmo’s ramp was higher than Rosita's.

This bit of knowledge helped Rosita form a hypothesis. If she built her ramp as high as Elmo’s, her ball just might go as fast as Elmo’s in the next race. From there, the team raised Rosita’s ramp to be the same size and they put this theory to the test.  

Mission accomplished. Rosita and Elmo tied, all thanks to the Sesame Street team’s experiment. 

The notion of “experimentation” may trigger different thoughts for different people. To some, an experiment involves scientists working in a lab. Other people will think of an artist who likes to change up the color, depth, or tone of their artwork to spark different reactions. And some people will envision a marketing team launching two ads for the same promotion to see what resonates most with their customers.  

On the surface, these three hypothetical examples may seem extremely different, but they have one thing in common: they all follow the same basic experimentation framework that was outlined in Sesame Street. 

  • I wonder – The team is starting to define what the problem is. They draw on all they can see and even past experiences/experiments to create a solution. 
  • What if – The team creates a hypothesis to solve the problem. They walk through what they think they need to do to solve the problem.
    Let's try! – The team implements their changes to see if that solves the problem. They run the experiment and then socialize the results.  

Experimentation doesn't need to be a massive undertaking, or scary to start. This simple concept provides a framework for thinking and helps lay the foundation for testing in digital platforms with tools like Optimizely Web Experimentation. And the best part? It shows that getting started with experimentation doesn’t have to be complicated! 

Mar 27, 2024


Please login to comment.
Latest blogs
Optimizely and the never-ending story of the missing globe!

I've worked with Optimizely CMS for 14 years, and there are two things I'm obsessed with: Link validation and the globe that keeps disappearing on...

Tomas Hensrud Gulla | Apr 18, 2024 | Syndicated blog

Visitor Groups Usage Report For Optimizely CMS 12

This add-on offers detailed information on how visitor groups are used and how effective they are within Optimizely CMS. Editors can monitor and...

Adnan Zameer | Apr 18, 2024 | Syndicated blog

Azure AI Language – Abstractive Summarisation in Optimizely CMS

In this article, I show how the abstraction summarisation feature provided by the Azure AI Language platform, can be used within Optimizely CMS to...

Anil Patel | Apr 18, 2024 | Syndicated blog

Fix your Search & Navigation (Find) indexing job, please

Once upon a time, a colleague asked me to look into a customer database with weird spikes in database log usage. (You might start to wonder why I a...

Quan Mai | Apr 17, 2024 | Syndicated blog

The A/A Test: What You Need to Know

Sure, we all know what an A/B test can do. But what is an A/A test? How is it different? With an A/B test, we know that we can take a webpage (our...

Lindsey Rogers | Apr 15, 2024

.Net Core Timezone ID's Windows vs Linux

Hey all, First post here and I would like to talk about Timezone ID's and How Windows and Linux systems use different IDs. We currently run a .NET...

sheider | Apr 15, 2024