Using Data to Make Informed Product Decisions

Lincoln Ritter of Animoto

Lincoln Ritter, director of engineering at Animoto, shares how they use data to make more informed product decisions.

  • Here's what to listen for:
  • 02:01 What can we do with data?
  • 04:21 Why should a company care about data and trends?
  • 08:02 How can you become more data-driven?
  • 12:28 How can you get more people involved in caring about data?
  • 16:41 What are the tradeoffs when it comes to agility in software development?
  • 18:29 How do you combat paralysis and help people on your team understand the data better?
  • 20:58 Is data-supported a better term than data-driven?
  • 22:50 What’s the difference between data engineering and data science?
  • 24:59 How do you get data in the right format?
  • 25:59 What kind of question might you have that requires information from multiple sources?
  • 30:13 How do you decouple, consolidate, and keep data separate?
  • 33:01 Do you think real-time data is necessary?
  • 35:06 How would Animoto look at data and make a product decision?
  • 39:04 When is split-testing useful and not useful?

"I think the question always has to be: what’s the return on investment?"

"What do you really think that data is going to be useful for at your company?"

"We looked at the key behaviors that we wanted to get a handle on and started instrumenting those."

"It felt like we weren’t building an intuition: if we wiggle this, how does this other thing react?"

"We didn’t want to make decisions based on a pure hunch."

"It’s all about improving confidence that we’re doing the right thing."

"Pick a metric or key report and get that number in front of people."

"You’re going to have technical challenges and cultural challenges."

"Try to form the linkage in people’s minds between their activity and the data."

"Essentially what we have is a clone of all our data on a single instance."

"Often there’s many assumptions, and you just try to control for as many as possible."