Facilitation

Q: How deeply does Think Like a Software Engineering Manager cover facilitation?

Outlines communication styles, feedback, coaching, and inclusive participation without a step-by-step facilitation method.

As explained in Think Like a Software Engineering Manager

Communication and facilitation are practices for conveying information clearly and helping groups participate in productive decisions and discussions.

An engineering manager may need to explain a project to engineers, leadership, and customers while making sure team members can contribute. Communication conveys information clearly; facilitation helps people take part in discussions and decisions. section 1.1.3

Useful practices include:

Adapt written and verbal communication to technical and nontechnical audiences. section 1.1.3
Give constructive feedback and approach conversations with a coaching mindset. section 1.1.3
Notice communication gaps and encourage diverse viewpoints so team members can participate. section 1.1.3

Participation changes the outcome

A manager who addresses communication gaps helps a new engineer participate. Relying instead on one senior engineer for decisions can leave others feeling disconnected. section 1.1.3

How Think Like a Software Engineering Manager covers it

Cover of Think Like a Software Engineering Manager

liveBook manning.com

Read Think Like a Software Engineering Manager on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Collaborative Software Design: How to facilitate domain modeling decisionsA facilitation process is the sequence of activities through which a facilitator guides a group toward effective communication, participation, or decision-making.
liveBook manning.com

Architecture Modernization: Socio-technical alignment of software, strategy, and structureFacilitating is an interaction mode in which one team temporarily supports another team's goal through focused assistance or skill development.

Compare how 3 books explain facilitation →

Related concepts

technical leadused by · A technical lead is a software engineer who provides technical ownership, direction, coordination, and guidance for a team or project.
conflictaddresses · Conflict is a state of disagreement, opposition, or incompatibility among people, positions, interests, actions, or information.
resistance to changeaddresses · Resistance to change is opposition or reluctance to adopt or participate in a change to established practices, processes, structures, or ways of working.
collaborative discovery and modelinguses · Collaborative discovery and modeling is a group technique in which stakeholders jointly create and refine representations to establish shared understanding of a domain or system.
cognitive biasuses · A cognitive bias is a systematic tendency in human perception, judgment, or reasoning that can distort how information is evaluated and decisions are made.
communicationproduces · Communication is the exchange of information, meaning, or signals between people, groups, agents, devices, or software components.

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.