Tag: ensemble programming

NOTE: We want to thank the folks at Tuple.app for being so generous with their stories, and supporting the podcast. Visit tuple.app/scrum and share them if you find the app useful! Remember, sharing is caring!

In this episode, Eli Goodman, Head of Product at Tuple, shares insights from his extensive experience in software development and product management. Having transitioned from engineering management to product leadership, Eli reveals the key strategies Tuple uses to develop its remote pair programming service, which is trusted by companies like Figma and Shopify. Tune in to discover how Tuple handles remote team dynamics, customer-driven development, and balances tech debt with client needs, all while maintaining a customer-centric focus.

Introduction to Tuple and Why It’s Unique

Tuple, a remote pair programming service designed by engineers, solves a pain point that its founders, all pairing enthusiasts, experienced firsthand. They were unsatisfied with generic screen-sharing tools that disrupted the flow of coding collaboration. Tuple’s product philosophy is about staying “one inch wide, one mile deep” to ensure the tool stays focused on enhancing the pairing experience without getting in the way.

“The details matter. Generic screen-sharing tools just don’t cut it for productive pairing.”

Managing a Remote Team at Tuple

Managing a distributed team across the U.S. and Europe comes with its challenges. Eli highlights the importance of alignment and ensuring everyone is on the same page, despite working remotely. He emphasizes the role of Product Owners as “connective tissue” and the power of connecting team members with key initiatives. Through personal conversations, Eli uncovers what motivates his team, allowing him to support them without micromanaging.

“What makes you proud? What brings you shame? Understanding these emotions helps uncover what drives our team.”

Ensuring Effective Communication in a Remote Environment

Effective communication is the backbone of remote work, and Eli shares some of the practices that have helped Tuple’s team stay aligned and collaborative. From using spontaneous pairing sessions to fostering a culture of checking in, Tuple has created a remote work environment where conversations are naturally sparked, and collaboration is effortless.

“We have more space in our schedules for spontaneous pairing, which keeps collaboration flowing.”

Lessons Learned from Pairing Remotely

One of the key insights Eli shares is how Tuple has evolved its remote pairing process. In the past, pairing might have felt like a formal meeting, but now it happens more spontaneously. Tuple’s app facilitates this by offering the metaphor of a phone call—engineers can call each other at any time, making collaboration easy, especially when someone is deep into a task and needs quick support.

“At Tuple, engineers only have three meetings a week, leaving the rest of the time open for pairing and creative work.”

Pairing Beyond Programming Tasks

While pairing is typically associated with programming, Eli explains how Tuple uses pairing for other activities, like design or planning sessions. This practice has extended beyond coding, fostering a culture where team members collaborate on various tasks that benefit from shared perspectives and live problem-solving.

“We’ve expanded pairing beyond coding, using it for activities like design reviews and project planning.”

Balancing Customer Feedback with Product Vision

Responding to customer feedback is vital, but it can also lead to losing focus. Eli explains how Tuple balances this by capturing as much feedback as possible, using tools like Product Board to keep track of customer requests. However, instead of building every requested feature, Eli focuses on synthesizing broader patterns and emotional triggers that align with Tuple’s long-term vision.

“Focus on discovery as a product person. Understand the emotional context behind customer feedback—that’s what drives great products.”

Tuple’s Ideal Customer and Core Value

Tuple’s ideal customers are teams that value deep collaboration through pair programming. The platform’s most important offering is the ability to make remote pairing seamless and intuitive, something traditional tools fail to deliver.

“Tuple is built for teams that believe in the power of collaboration and want a tool that enhances their pairing experience, not disrupts it.”

Roadmapping: How to Prioritize the Right Work in Product Development

Looking ahead, Eli shares Tuple’s plans to continue investing in quality and lowering the barriers to remote pairing. One exciting potential direction includes creating a “social layer” within the app to help users feel more connected with their teammates. Another idea is incorporating non-human pairing agents that could assist with specific tasks.

“We want to see if we can make it feel like you’re right there with your teammates, lowering the barriers to start pairing.”

Recommended Resources

Eli recommends The Mom Test by Rob Fitzpatrick, a must-read for anyone working in product management. The book teaches how to talk to customers in a way that gets honest, useful feedback rather than polite responses that don’t help improve the product.

“I thought caring about people was enough to talk to customers, but The Mom Test taught me what not to do during customer interviews.”

About Eli Goodman

Eli Goodman has been working on software teams for 17 years. He’s been a full-stack developer and engineering manager at both large and small companies, including Etsy and Headspace. A few years ago, Eli transitioned to product management and is now the Head of Product at Tuple, a remote pair programming service used by companies such as Figma, Shopify, and many others in the software industry.

You can link with Eli Goodman on LinkedIn, or email Eli at Eli@Tuple.app.