Defined a controlled roll out updating process

In order to reduce friction across cross-functional updates

Peloton Interactive

New York, NY

Updating hardware and software increments for the Tread studio were challenging activities involving impromptu last-minute coordinations, misses, and follow-ups across multiple internal & external parties. These often resulted in cross-functional team conflicts and departmental confusion over timelines and scope of the updates.

My contributions

  • Stakeholder interviews (Engineering, Operations, Testing)
  • Gap analysis
  • Process creation

How I helped

To align all involved parties across Engineering, QA, Studio Operations for both hardware and software updates, I executed a deep-dive assessment to gain an understanding of what the existing pain points and issues were.

After reviewing and discussing, I created a controlled rollout process to address OTA and in-studio updating operations in a systematic format by adopting a slowly evolving batch approach.

By putting together a protocol based on a progression of linear sequencing, acceptable thresholds, suggested dimensional cross-section, and other factors, all of the parties involved understood who, where, and how to collaborate with when a change needs to be incorporated.

Outcome

  • Identified existing bottlenecks and pain points in the process for tread studio updates
  • Worked with Engineering, Logistics, and Studio teams to understand areas of improvement
  • Created framework and reduced cross-functional team conflicts during OTA and in-studio rollouts

Can I help with your business process improvement project?

Let's have a friendly chat and find out