← Back to Patterns

Route Non-Differentiating FTE Classes to Partners

strategy39% Low

1

Occurrences

N/A

Success Rate

N/A

Avg Rating

Description

When CIQ would otherwise need to staff a function whose work does not differentiate the company — compliance bureaucracy, audit/cert paperwork, ongoing regulatory attestation, etc. — Peter routes the load to a partner who already owns adjacent capability rather than adding the FTE class internally. Org-shape decision dressed as a partnership decision.

Typical Approach

Identify FTE classes whose work is recurring, non-strategic, paperwork-heavy, and not engineering-core. Find a partner whose existing scope can absorb that load (Atomicorp for compliance, others TBD). Expand partner scope rather than open internal headcount. Hold the line even when customer demands surface gaps — gaps surface the partner-expansion lever, not an internal hiring track.

Trigger Conditions

Keywords:
compliancecertificationauditFIPSSTIGFedRAMPattestationregulatorypartner expansionscope expansionatomicorp
Constraints: FTE class would not differentiate CIQ, partner already owns adjacent capability, work is recurring and paperwork-heavy
People: Nathan Blackham (Linux Eng) on compliance scope, Bjorn Hovland (Product) on partner commercials

Created: April 27, 2026

Pattern ID: 121fef96-4a5c-4adf-b617-fbe09ba77c20