liveBook · Manning

No-update-update

As explained in Think Like a CTO

A periodic incident-status communication that reports no substantive change while keeping stakeholders informed.

A no-update update is a brief, periodic message confirming that a visible problem remains unresolved but is still being worked on. It prevents stakeholders from assuming they have been forgotten and gives the team room to focus. section 6.4.1 section 12.8.2

Use the practice deliberately:

  • Set the cadence according to severity; updates every 30 or 60 minutes suit highly visible situations. section 6.4.1
  • Keep each message short: state that work continues, note whether the situation has materially changed, and avoid promising resolution. section 6.4.1
  • Use the update to keep executives informed while preserving the team’s concentration on diagnosis and response. section 12.8.2
  • Escalate significant client, production, or security concerns rather than relying on routine status messages alone. section 6.4.1

A predictable incident rhythm

During a serious incident, send a quick email or text at the top or bottom of each hour: “No resolution yet; investigation continues.” The predictable rhythm reassures recipients without demanding a detailed report every time. section 6.4.1 section 12.8.2

Table 6.2 Rules of engagement (view table figure)

No reporting required

Keeping you informed

Decision required

Interviewing potential candidates

Any problem or issue concerning a client

Final interview of top candidates under review

Internal processes pertinent to the team execution

Any production problem

HR consultation or termination considerations

Team one-on-one meetings; PTO management

Security concerns or issues

Purchase or licensing of tools

Project execution

Changes in how the team interacts with other teams

Any problems with individual team members

Timelines; updates

Change of technology or tools

Use the rules-of-engagement table to distinguish routine updates from matters requiring management involvement or a decision, including client problems, production issues, security concerns, and timeline changes. section 6.4.1

How Think Like a CTO covers it

How deep it goes
Defines the practice, recommends a cadence, and gives message-level guidance, but stops short of prescribing incident-resolution procedures.
Examples
Uses 30- or 60-minute email or text updates and top- or bottom-of-hour reminders during serious incidents.
What it assumes
Assumes responsibility for team communication and teaches how to balance stakeholder visibility with responders’ need for uninterrupted focus.
What you can do after
Apply a predictable, concise status cadence during unresolved client, production, or security problems.
How it connects
Connects stakeholder communication with incident management, escalation, and security incident response.
Cover of Think Like a CTO
liveBookmanning.com
Read Think Like a CTO on liveBook Get the book at manning.com

Related concepts

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.