liveBook · Manning

Team vision

As explained in Think Like a Software Engineering Manager

A team vision is an articulated desired future state that gives a team shared purpose and strategic direction.

An engineering team can be busy yet unsure where its work is leading. A team vision articulates the future the team is working toward. It gives people shared purpose and strategic direction; clear goals then make that direction useful for planning. section 1.1.3

To make a vision useful, an engineering manager can:

  • Learn how the team prefers to work, including its appetite for cross-functional collaboration. section 1.1.3
  • Engage stakeholders to understand company goals rather than setting direction in isolation. section 1.1.3
  • State the vision clearly and concisely, then provide goals for the coming years so team members can see a path forward. section 1.1.3
  • Communicate the vision and goals openly, showing how they align with the company’s mission and vision. section 8.4.1

Direction versus hands-off empowerment

One manager learns the team’s preferences, talks with stakeholders, and sets a clear direction. Team members gain motivation and strategic clarity. Another assumes the team can set its own course and struggles to connect with partners; projects meet pushback and the team pivots frequently. Empowerment does not remove the need to articulate a vision. section 1.1.3

A vision is not a substitute for an open, supportive workplace. Communicating it alongside team goals can help people feel included and connected to a purpose. If direction is unclear, ask whether the team understands both where it is headed and how that direction relates to company goals. section 8.4.1 section 1.1.3

How Think Like a Software Engineering Manager covers it

How deep it goes
Explains the value of a clear vision through contrasting manager behaviors and practical actions, without providing a formal drafting template.
Examples
Contrasts a manager who consults stakeholders and sets direction with one whose hands-off approach leads to project pushback and pivots.
What it assumes
Assumes an engineering-team leadership context but introduces vision setting through concrete manager behaviors rather than management theory.
What you can do after
Practice/perform vision setting by learning team preferences, engaging stakeholders, stating a clear direction, and communicating aligned goals.
How it connects
Connects team vision to stakeholder engagement, cross-functional collaboration, company goals, employee motivation, and workplace culture.

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.