liveBook · Manning

Engineering meeting

As explained in Think Like a CTO

A recurring meeting in which an engineering group receives shared updates about progress, releases, customers, processes, and organizational changes.

An engineering meeting is a recurring whole-group update that keeps engineers connected to progress, releases, customers, processes, and organizational changes. Schedule it weekly or biweekly, keep it to 30 minutes, and use a steady format so participants know what to expect. section 6.7.2

Use the meeting for shared, high-level information:

  • Celebrate major releases and customer acquisitions. section 6.7.2
  • Communicate customer losses, process improvements, and structural changes. section 6.7.2
  • Protect the 30-minute limit to reduce fatigue and preserve the meeting’s value. section 6.7.2

A steady update rhythm

A group can meet every other week for 30 minutes, following the same format while reviewing a major release, a customer change, a process improvement, and an organizational update. section 6.7.2

How Think Like a CTO covers it

How deep it goes
Defines cadence, duration, audience, topics, and format, but stops short of detailed facilitation guidance.
Examples
Uses releases, customer changes, process improvements, and structural changes as update topics.
What you can do after
Operate a predictable whole-group update meeting within a 30-minute limit.
How it connects
Distinguishes recurring engineering meetings from town halls and team meetings.
Cover of Think Like a CTO
liveBookmanning.com
Read Think Like a CTO on liveBook Get the book at manning.com

This explainer was generated by Manning's knowledge graph from the text of Think Like a CTO. The section links point to the parts of the book it draws on.