Trend: 'Pulse Checks' Replacing QBRs
A new trend in tech leadership suggests that rigid Quarterly Business Reviews (QBRs) are being replaced by more agile alternatives. According to one analysis, leaders are shifting to shorter, more frequent "pulse checks" — often monthly or bi-weekly — to keep pace with rapid industry changes.
The rigid, backward-looking nature of traditional QBRs makes them ill-suited for the rapid pace of change in the tech industry. By the time a quarterly review occurs, the information presented is often obsolete, leading to missed opportunities and a failure to adapt to evolving market dynamics and customer preferences. More agile "pulse checks" are replacing these outdated reviews, aligning with methodologies that originated in software development that emphasize continuous collaboration and improvement. These frequent check-ins, often weekly or bi-weekly, allow for real-time course correction and a more forward-looking approach to performance management. For executive communication, a "pulse check" can be structured as a concise bi-weekly email update. A practical framework for this includes an overview of the biggest win from the last two weeks, a summary of what's progressing well and what isn't, and a clear outline of any risks or issues where leadership support is needed. The status of key initiatives can be color-coded (Green/Yellow/Red) for immediate clarity. A monthly pulse check with senior leadership can take the form of a more strategic, yet brief, executive summary. This report should focus on a high-level overview of progress against established goals, key performance indicators (KPIs), and any significant challenges or changes in strategy. The goal is to provide leadership with a clear picture of the team's trajectory and any decisions that need to be made. To quantify engineering performance for these updates, engineering managers can leverage the DORA metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, and Time to Restore Service. These four key metrics provide a clear, data-driven view of a team's velocity and stability, translating complex engineering work into a language that resonates with business-focused executives. When presenting to directors, it's crucial to frame engineering work in terms of business impact. Instead of focusing on technical jargon, translate metrics into insights on on-time delivery, resource allocation, and project costs. This approach builds trust and demonstrates a strategic partnership with business leaders. A structured format for a pulse check presentation or document should lead with the most critical information—the "Bottom Line Up Front" (BLUF) approach. Start with a high-level summary of project health, followed by key highlights from the recent period, upcoming priorities, and a clear outline of any critical risks or dependencies that require executive attention. Ultimately, the shift to pulse checks is about fostering a culture of continuous alignment and transparency. By providing a regular cadence of concise, data-driven updates, engineering managers can enhance their executive visibility and ensure their teams' work is clearly tied to broader business objectives.
