Back to resources

Shortening the Feedback Loop to Improve Collaboration

Internal Communication
Productivity
Feedback
Prioritization
Health / Stress / Burn-Out

4 April, 2022

Rui Ferreira
Rui Ferreira

Change Management Expert at Typeform

Rui Ferreira, Change Agent at Independent, describes how he structured a feedback loop between cross-functional teams.

Difficulties of a Long Feedback Loop

I worked in a company where the certification process was done externally to the team. Typically a team that was closer to the business end of things focused on the certification after the development was completed.

I was acting as a scrum master of this team, and the certification process was causing issues for the team members. Specifically, individuals became frustrated because they were building things and then waiting weeks until they heard feedback on these features or tools. When they listened to the feedback on their project, my team was already working on another task. It only caused more problems when the team needed to iterate on previous activities that had not received feedback yet.

The long delay in feedback made it necessary for the team to constantly switch what they were working on. Sometimes, if they were building upon a previous feature, they had to scrap their work altogether when they received the feedback.

Shortening the Certification

To overcome this situation, my team proposed an idea where we had certification dates. For example, a team that has an iteration of four weeks would reserve the last two or three days to focus on the certification with the external team. In my case, the team set a physical environment and invited the dev teams, business analysts, and anyone that could accept the project to provide feedback.

It was exciting to see a process that previously took weeks of back and forth communication combined into a productive two or three days. Other than the increased pace of the feedback loop, there were other positive outcomes.

For one, the collaboration between teams increased. When testing was happening, and someone identified what looked like a bug, a member from my team could communicate directly with the other teams to determine if it truly was a bug.

While everything was not solved during these few days, the team managed to prioritize the most important items in the backlog. The impact of this process was much larger in comparison to the previous method.

Discover Plato

Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader


Related stories

Managing Different Time Zones: Inclusive Collaboration Methods

19 May

Jonathan Belcher, Engineering Manager at Curative, shares an unknown side of synchronous communication tools and advises managers on how to handle a team that’s spread across the globe.

Remote
Internal Communication
Collaboration
Cross-Functional Collaboration
Jonathan Belcher

Jonathan Belcher

Engineering Manager - Patient Experience at Curative

Managing Remotely: Balancing Team Cohesion and Focus Time

26 May

Jonathan Belcher, Engineering Manager at Curative, explains how to balance team cohesion and individual focus time, tapping into his experiences of working remotely for seven years.

Remote
Micromanagement
Meetings
Internal Communication
Productivity
Psychological Safety
Performance
Jonathan Belcher

Jonathan Belcher

Engineering Manager - Patient Experience at Curative

Streamlining Product Processes After a Reorganization

16 May

Snehal Shaha, Lead Technical Program Manager at Momentive (fka SurveyMonkey), details her short-term technical strategy to unify processes among teams following an acquisition.

Acquisition / Integration
Product Team
Product
Building A Team
Leadership
Internal Communication
Collaboration
Reorganization
Strategy
Team Processes
Cross-Functional Collaboration
Snehal Shaha

Snehal Shaha

Senior EPM/TPM at Apple Inc.

Navigating Disagreements When It Comes to Priorities

9 May

Pavel Safarik, Head of Product at ROI Hunter, shares his insights on how to deal with disagreements about prioritization when building a product.

Innovation / Experiment
Product Team
Product
Dev Processes
Conflict Solving
Internal Communication
Collaboration
Convincing
Strategy
Prioritization
Pavel Safarik

Pavel Safarik

Head of Product at ROI Hunter

The Optimization and Organization of Large Scale Demand

4 May

Kamal Qadri, Senior Manager at FICO, drives the importance of setting expectations when optimizing large-scale requirements.

Managing Expectations
Delegate
Team Processes
Prioritization
Kamal Qadri

Kamal Qadri

Head of Software Quality Assurance at FICO

You're a great engineer.
Become a great engineering leader.

Plato (platohq.com) is the world's biggest mentorship platform for engineering managers & product managers. We've curated a community of mentors who are the tech industry's best engineering & product leaders from companies like Facebook, Lyft, Slack, Airbnb, Gusto, and more.