liveBook · Manning

Anonymous survey

As explained in Think Like a Software Engineering Manager

An anonymous survey is a survey that collects responses without identifying the individual respondent.

An anonymous survey gathers team responses without identifying individual respondents. It gives people a channel for candid feedback when one-on-one conversations or meetings may not reveal every concern. section 9.2.5 section 3.3.1

Use an anonymous survey to:

  • Ask immediate team members about cross-functional collaboration and maintain a continuous feedback loop. section 9.2.5
  • Encourage candid feedback about managerial strengths, weaknesses, and growth opportunities. section 3.3.1
  • Assess trust and team dynamics, or clarify team goals and timelines during performance improvement. section 4.5.4 section 9.3.1

A practical feedback loop

An engineering manager sends an anonymous questionnaire about cross-functional collaboration, reviews the responses, and follows up through open conversations when concerns or emotional reactions emerge. section 9.2.5

Treat survey responses as input rather than a complete diagnosis. Combine them with one-on-one meetings, retrospectives, observed team interactions, and regular feedback sessions before choosing corrective action. section 9.2.5 section 9.3.1

How Think Like a Software Engineering Manager covers it

How deep it goes
Explains the survey’s role within broader feedback practices but does not detail questionnaire design, analysis, or response handling.
Examples
Uses questionnaires about cross-functional collaboration, managerial growth, team trust, team dynamics, goals, timelines, and underperformance.
What it assumes
Assumes responsibility for team communication, collaboration, trust, or performance while pairing surveys with other feedback sources.
What you can do after
Apply it to collect candid feedback and identify issues requiring conversation, clearer expectations, process changes, or support.
How it connects
Connects anonymous surveys with continuous feedback, one-on-one meetings, retrospectives, trust, team dynamics, and cross-functional collaboration.

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.