liveBook · Manning

Leadership style

As explained in Think Like a Software Engineering Manager

A leadership style is a characteristic pattern in how a leader or manager guides, supports, and influences other people.

A new engineering manager may find that one engineer wants clear task assignments while another does their best work with autonomy. A leadership style is the pattern of decisions, guidance, and support a manager uses with a team. Defining that pattern helps set expectations, but using it well means adapting it to the people and situation. section 1.3 section 2.2.4

Six common styles offer different benefits and trade-offs:

  • Autocratic: makes decisions quickly under time pressure, but can be poorly received by team members. section 1.5
  • Democratic: brings people together for consensus, but takes time. section 1.5
  • Delegative: gives work to others; it works best when the person receiving it is senior enough, and less well when they need more direction. section 1.5
  • Transactional: can improve business and development metrics while weakening collaboration and morale. section 1.5
  • Transformational: emphasizes the future, but needs balance so present needs are not neglected. section 1.5
  • Servant leadership: helps team members feel motivated and engaged. section 1.5

You do not have to pick one style and keep it forever. Consider your experience, the team’s size and preferences, the project phase, company culture, and time constraints. A hybrid approach may fit better: a deadline that does not call for consensus, for instance, may favor a mix of decisive direction and delegation. If an approach stops working, change it. section 1.3.7

Adjust to the person, not just the plan

A manager began with a rule against micromanaging, then discovered that a strong engineer was struggling without clearer assignments. In one-on-one meetings, the manager learned what each person needed. They gave that engineer direct tasks while coaching them to choose future work from the backlog that matched their interests. The engineer returned to strong performance. section 2.2.4

To develop your style, observe managers and mentors, notice which approaches fit your experience, and ask team members for feedback in one-on-ones or surveys. Check whether your choices support team morale and goals. Which approach helps this team now—and what would tell you it is time to adjust? section 2.4.3 section 3.3.1 section 1.4

How Think Like a Software Engineering Manager covers it

How deep it goes
Compares six styles and their trade-offs, then gives situational selection guidance rather than a fixed decision procedure.
Examples
Uses deadline decisions, an engineer needing clearer assignments, and reflection on past managers to make style choices concrete.
What it assumes
Introduces the styles for people exploring or entering engineering management, without assuming an established personal management style.
What you can do after
Practice/perform it by choosing a situational or hybrid approach, seeking feedback, and revising the approach when team needs change.
How it connects
Links leadership style to delegation, one-on-one meetings, team morale, and engineering manager success metrics.

Also explained in

Compare how 3 books explain leadership style →

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.