Brainforge Knowledge

pairing-health-and-reassignment-framework

6 min read

Pairing health and reassignment framework

Purpose: Provide a structured, evidence-based way to assess whether a CSO/SL pairing is working on a given account — and, if not, what the right intervention is. Replaces feel-based judgment calls in 1:1s with a repeatable, fair process.

This framework applies to CSO/SL pairings. It is not a performance improvement plan (PIP) tool — that is a separate HR process. This is a delivery operations tool: it identifies pairings that are creating friction, distinguishes pairing fit from individual capability, and guides remediation.

The principle

A person can belong at Brainforge and be well-suited to their function while being a poor fit for a particular pairing. Pairing friction is not always a performance failure. But it is always a delivery risk that must be addressed.

The goal is to identify it early, diagnose it correctly, and intervene before the client or the team absorbs the cost.

Pairing health dimensions

Assess each dimension on a 1–3 scale:

ScoreMeaning
3Working well — consistent positive evidence
2Inconsistent — some evidence in both directions
1Not working — consistent negative evidence

D1 — Narrative alignment

Question: Does the CSO’s client story stay consistent with the SL’s technical reality?

Evidence:

  • CSO-SL alignment meeting notes
  • Whether the client narrative and Linear board tell the same story
  • Whether side-channel commitments have occurred
  • Whether client promises were blocked late by SL because technical readiness was not surfaced early

D2 — Mutual escalation trust

Question: Does each role trust the other to surface risks in time?

Evidence:

  • Whether CSO flags scope changes to SL before committing
  • Whether SL flags technical risk to CSO before it becomes a client issue
  • Whether either role is working around the other
  • Whether ICs are receiving conflicting direction and being forced to choose between client optics and technical order

D3 — Decision routing discipline

Question: Are decisions flowing through the right role at the right time, per the RACI?

Evidence:

  • Whether IC escalations are hitting the right first stop (SL for technical, CSO for client-facing)
  • Whether CSO is answering technical questions unilaterally
  • Whether SL is making client commitments without CSO visibility
  • Whether client requests are handled on first touch with clear CSO/SL routing instead of requiring a call to establish ownership

D4 — Quality gate integrity

Question: Is the SL completing technical sign-off before client-visible outputs leave the team?

Evidence:

  • PRM prep: did the SL sign §5 before the CSO presented?
  • Deliverable review: are quality reviews happening before client hand-off?
  • Bug rate and rework volume as proxy
  • Reopened “done” tickets caused by quality issues after SL sign-off

D5 — Communication load balance

Question: Is one person carrying disproportionate coordination burden?

Evidence:

  • Who is initiating CSO-SL alignment, and who is showing up prepared?
  • Is the CSO doing SL work (technical triage, IC direction) because SL is absent?
  • Is the SL managing client sentiment because CSO is not engaging?

Scoring and interpretation

Sum the five dimensions. Total range: 5–15.

TotalPairing healthRecommended action
13–15StrongNo intervention needed. Flag as model pairing.
10–12ModerateCoaching conversation with both; identify which dimension(s) are weak; set a 4-week check-in.
7–9FragileActive intervention required: structured reset conversation, specific behavioral agreements, tracked 4-week improvement.
5–6FailingPairing reassignment conversation. Conduct individual capability assessment (see below) before moving.

Individual capability assessment

Before reassigning a pairing, distinguish: is the friction a pairing issue or an individual capability issue?

Ask for each person in the pairing:

QuestionCSOSL
On a different account, does this person demonstrate the role’s core behaviors?Y/NY/N
Is the friction specific to this pairing dynamic, or does it appear on other accounts?Y/NY/N
Has this person received clear, documented feedback about the specific gap?Y/NY/N
Have they had a reasonable opportunity to correct?Y/NY/N

If the friction is pairing-specific (works well elsewhere): reassign the pairing, no performance process.

If the gap follows the person across accounts: this is an individual performance conversation, not a pairing swap.

If neither person has received clear feedback yet: feedback must come first. Do not reassign before the person has been told what “correct” looks like.

Reassignment process

When a reassignment is warranted:

  1. HoD documents the assessment — which dimensions failed, what evidence was used.
  2. Conversation with both parties — conducted by HoD, separately if needed. Framing: “This pairing is not working for this account. That is not a verdict on either of you.”
  3. New pairing assignment — HoD assigns based on capability fit and account needs.
  4. Transition period — outgoing CSO or SL stays on for one week overlap to preserve client continuity.
  5. Client communication — if the role change is visible to the client, CSO owns the narrative (even if they are the one being rotated out; HoD approves framing).
  6. Record filed — brief note in knowledge/clients/{client}/resources/ documenting the change and reason (internal only).

Review triggers

Conduct a pairing health assessment when:

  • Routine: quarterly for all active pairings with ≥ 60 days of joint history
  • Triggered: any of the following observed in real-time:
    • CSO-SL alignment missed for 3+ consecutive weeks
    • Standards miss flagged in two consecutive weekly operating reviews for the same pairing
    • IC escalation to HoD that should have been caught by CSO or SL
    • Uncontrolled client escalation to founder
    • Client bypasses CSO and goes to founder because progress, risk, or next step is unclear
    • Demo or milestone is stopped by SL after CSO has already created client expectation
    • IC receives conflicting direction from CSO and SL and the conflict is not resolved in writing

Combined CSO/SL accounts

For small clients where one person holds both roles (see operating allocation audit):

  • The single-owner risk is documented at kickoff.
  • HoD conducts a solo health check (same dimensions, adjusted: “Is this person maintaining both functions without one cannibalizing the other?”).
  • Escalation path must be documented: who does the combined owner escalate to when they are blocked or need a check-in? Default: HoD.
  • If either function is degrading, the first intervention is role split (assign a second person to one function), not performance.
  • PM-focused IC / project manager should understand that the same person holds both hats and help keep client narrative decisions distinct from technical readiness decisions in the project record.
  • Combined CSO/SL should not be the default for larger or more complex clients.

Last updated: 2026-04-27

Graph View

Backlinks