liveBook · Manning

Self-awareness

As explained in Think Like a Software Engineering Manager

Self-awareness is the ability to recognize and understand one's own traits, behavior, motivations, and effects on others.

For an engineering manager, self-awareness means recognizing strengths and weaknesses, understanding how they shape leadership, and noticing where growth could help the team. Strengths can inspire and guide; weaknesses such as poor communication or micromanagement can undermine trust and collaboration. section 3.3.1

Use practical signals to identify opportunities for growth:

  • Ask team members, peers, and leaders for feedback in one-on-ones; anonymous surveys can encourage candid responses. section 3.3.1
  • Consider team morale as a signal of confidence in your leadership and the work culture. section 3.3.1
  • Reflect on role transitions as learning experiences that can clarify your preferences and support continued growth. section 2.4.3

Core working hours

An engineering manager introduced shared core hours to improve communication. Team feedback revealed that the rigid schedule conflicted with personal obligations and preferred flexibility, uncovering a growth opportunity in the manager’s approach. section 3.3.1

How Think Like a Software Engineering Manager covers it

How deep it goes
Gives feedback-gathering methods and a workplace example, alongside reflection on role transitions.
Examples
Uses an engineering manager’s core-hours decision and feedback, plus reflection on an unsuccessful role transition.
What you can do after
Apply feedback through one-on-ones and anonymous surveys to identify managerial growth opportunities.
How it connects
Connects self-awareness with feedback, leadership style, and career development.

Also explained in

Compare how 3 books explain self-awareness →

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.