Metrics Must Follow Strategy

strategyleadership77% Medium

Occurrences

79%

Success Rate

4.0

Avg Rating

Description

When shifting team priorities or strategic direction, the communication alone will not drive behavior change. Engineers may acknowledge the new direction but continue existing behavior patterns without clear, explicit metrics holding them accountable.

Typical Approach

Pair any strategic priority shift with explicit new metrics. Be forceful about establishing what the new metrics are and make it clear that you expect the team to be driven towards them.

Trigger Conditions

Keywords:

priority shiftstrategic directionteam prioritiesautomationbehavior changenew initiative

Constraints: team-level change, requires sustained effort

Last applied: November 3, 2026

Created: January 12, 2026

Example Decisions (54)

GDC targeted-CVE builds - what fits the existing build machinery ships Monday, everything else is quoted work, slips are attributed to the customer constraint, and a rough estimate is enough

Nov 3, 2026 · strategy

Metrics Must Follow Strategy

Description

Typical Approach

Trigger Conditions

Example Decisions (54)

GDC targeted-CVE builds - what fits the existing build machinery ships Monday, everything else is quoted work, slips are attributed to the customer constraint, and a rough estimate is enough

Datacenter business needs its own team and deals that pay now - stop signing engineers up for work far outside their remit

Keep Stratum out of the Core42 IRIS deployment - take the win we have; Stratum can go into Grenoble

2027 engineering budget - current reqs plus only two unallocated heads, one org-wide gathering every six months, cloud spend modeled as growth-tied

Tim Pepper - push now for an RESF board or leadership role, paid not volunteer, with Peter carrying it to Greg and Bjorn

GDC new ask after landing Anthropic - write down what we believe, parrot it back, give an ETA assuming funded, and use it to win the added 300K without slowing the base contract

GDC full kernel with IBT off is not just sign the kmod - say no unless it fits, do not reopen the contract, Peter and Kelly own the Tissa conversation

Apptainer - hold Bjorn to zero engineering hours and let things fall on the floor so the maintenance cost becomes visible

Core42 - hold to the SOW: stock Kubernetes plus Fuzzball before Oct 31, no CIQ-installed CozyStack, technical pushback routes to Peter

Get CIQ onto the embargoed security lists, Linux first - treat the absence as our failing; give upstream hours from the Stratum engineers to wherever Tim directs, and let Tim move without waiting on Peter

Justin org becomes the platform team - and for more than Linux; deep Linux knowledge is needed to build the platform, not to run it

Justin - now is the cheapest time to break things; bring every go-faster option to Peter and Bjorn, even the ones you would veto

Core42 Kubernetes - never let anyone at Core42/G42 say CIQ cannot do Kubernetes; ask questions only, route Stratum to Bjorn

Desktop - all investment behind one opinionated desktop; stock upstream GNOME ships only as a zero-investment bridge for 10.2 and Everfox

Greg research team - no management role for someone who will not take a defined role; a research function exists only with Greg running it

Desktop - enterprise GNOME and an opinionated AI desktop ship together, not as separate SKUs; AI is non-negotiable; open 1-2 desktop reqs now

Core42 is a CIQ Engineering engagement, not Support - Ryan on point, Peter, Wolford and Nathan stay on the calls

Get Core42 a Kubernetes demo from the head of the Kubernetes team - in person in Abu Dhabi if his schedule allows

Desktop V1 - a minimum-requirements section from Product, a December to first-week-of-January window, latest-only as the working assumption, and an accepted black eye

Put dates out even at low confidence so the board shows reality, and leads keep evolving their metrics - dropping the ones that get gamed

Endorse forward-deployed Fuzzball AI outright; make observability a buy/partner/build discussion after the functionality is written down; ask for a written path to profitability on existing products

GDC term sheet - balance the background-IP clause so it never reads as claiming Google shared code, and approve the live-patch quote as written

Six-month push for CIQ to be a better steward of its open-source work beyond Rocky - Tim Pepper advises, with full transparency and a seat in the Stratum open-core call

Endura goes into RLC-H as a feature, not a standalone product - and no public noise until engineering has audited and stands behind it

Joint with Bjorn: every Fuzzball deployment is white-glove for now - owned by Ryan org through workload verification, with FDE headcount added as needed

No live-patch signing for Google until they pay - CIQ does no more goodwill engineering work ahead of a contract

Protect the inked Core42 deal - no Stratum and no new commitments until we have done discovery with the end customer

Unhold the security-engineer req and carry it to Greg in conversation rather than clicking approve

Documentation and training stay in Ryan org - development work does not belong there

Take the customer breakage now at 100 customers rather than at 300 - but run it through Ryan and sales before it ships

Adopt Bjorn no-US-eyes-only call as the operating assumption - and force the principle question to be settled separately from its effects

Refuse to build the non-OS Core42 work on top of Ubuntu - getting moving is fine, doing the work entrenches the competitor

Justify the internal LLM fleet on Fuzzball dogfooding rather than cost savings - fund it even at parity

Ignore AMD until someone escalates - and decline to have an opinion on whether to confront them

Cap Binarly at validation-size investment - portfolio status buys no lower evidentiary bar

Make the bleeding-edge driver the RLC-AI default over Dawson stability objection - explicitly a 3 to 6 month posture

Constrain the AMD commitment to lab validation on an MI300 rather than promising CIQ will acquire one

Cover the OpenELA TSC seat gap personally with Nathan and Leigh, and put Tim Pepper on the RESF relationship question

Own the Google GDC answer personally, commit nothing to Google, and require Hassan to put the ask in email

Refuse to guarantee Oct 5 for Core42 if CIQ is deploying Ubuntu - give a likely range unless the customer demands a guarantee

Defend the net-new engineering reqs to Greg by naming them - and pay for them with an explicit churn commitment

Take the KT 9.8 one-year bridge - engineering will figure it out as long as the million dollars comes with headcount

Refuse an SDLC release-cadence contract that would bind engineering - prioritization authority stays with Product

Refuse to green-light the HPE indemnity escalation - this is a Bjorn call, not an Engineering call

Refuse the 9.10-as-of-today letter for KT - give them 9.6 LTS now with its real support window and a required migration, and correct the numbers publicly when they turn out to be wrong

Put the Core42 deployment on Ryan org to resource - Nathan stays advisor and the unfilled Forward Deployed Engineer goes on the contract list

Hold the Core42 commitment at five weeks, signal two-to-three as likely, and trade the compression for topology data

Attack the live-patching gap through Google co-development as a paid deliverable while keeping the req open - buy the timeline, do not just wait for the hire

Hold the CISO requisition and the September security hire pending the Atomicorp acquisition

Broken-in-production is an automatic fast path - small thing with embarrassing impact jumps the queue regardless of the size of the epic around it

Move the metrics conversation with Nathan off the tooling and onto the why - which metrics, which were discarded, and how the team is told the reason

Refuse to debate the cause of the Rocky download reversal until the metric itself is validated - either it is the number we track and it warrants attention, or we track a different one

Require every five-week org review to show the delta against the prior review and what was done to move it - not a fresh static report

CVE Automation Prioritized Over EUS Daily Numbers