Instituted ARR and CVE gap metrics visibility at weekly meetings
Situation
Decided to communicate both current ARR (as determined by finance) and CVE gap metrics at weekly meetings. Proactively communicated this to Bjorn and Greg, anticipating potential concerns but proceeding anyway.
Reasoning
Visibility drives behavior - what gets measured and communicated gets done. ARR is the key business metric and CVE gap is a critical technical/security metric that has been a priority. Regular communication prevents these from being out of sight, out of mind. This operationalizes the H1 planning work done with Chris Baek.
Additional Context
Followed the all-day H1 planning session with Chris Baek. Chris suggested Peter communicate this to Bjorn and Greg, expecting some concerns. Peter chose to proceed and address concerns if they arise rather than seek permission first.
Related Context
slack
I believe if you want to hit important metrics you constantly communicate and show those metrics. So I want both our current ARR as determined by finance, as well as CVE gap communicated at weekly meetings.
Outcome
Welcomed by the teams for providing clarity into progress. Zero pushback from eStaff.
Rating: 4/5
Decision ID: 3fddd79c-ca95-4ff3-a2ed-682c1291ad76