liveBook · Manning

Collaborative problem-solving

As explained in Think Like a Software Engineering Manager

A problem-solving approach in which people jointly analyze issues and develop resolutions.

Collaborative problem-solving brings people together to analyze an issue, understand different perspectives, and agree on a workable resolution. It is especially useful when a team must manage expectations, resolve conflict, or establish better ways of working. section 11.4.3 section 9.2

Reducing meeting fatigue

After excessive meetings burdened an engineering team, the team used a sprint retrospective to examine the problem together. They created a meeting bill of rights requiring clear agendas and expected outcomes in every invitation, with the organizer responsible for applying it. The shared solution helped the team regain control of its time. section 11.4.3

A practical collaborative problem-solving process includes:

  • Establish clear goals and assumptions, then agree on a viable path toward the shared objective. section 11.4.3
  • Invite differing perspectives, identify common ground, and discuss what works and what does not. section 9.2
  • Let the team decide its working methods, and iterate when the first approach does not fit. section 9.2
The Forming-Storming-Norming-Performing model for team development
sidebar figure

Use the Forming-Storming-Norming-Performing model to understand how teams build trust, negotiate working relationships, and move toward a shared mission. section 9.2

How Think Like a Software Engineering Manager covers it

How deep it goes
Develops a practical process involving goals, perspectives, common ground, negotiation, autonomy, and iteration rather than technical implementation.
Examples
Uses sprint retrospectives, meeting bills of rights, agendas, expected outcomes, and negotiated team working methods.
What it assumes
Assumes a shared objective and willingness to communicate, while developing the practices needed to navigate disagreement and negotiate solutions.
What you can do after
Apply it in retrospectives and team discussions to create workable agreements, improve communication, and address emerging hurdles.
How it connects
Connects managing expectations, conflict management, cross-functional teams, team development, and shared missions.

Also explained in

Compare how 2 books explain collaborative problem-solving →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.