Consolidated delivery standards
Purpose: Canonical statement of the Brainforge delivery standard: the floor, the excellence layer, and the checkpoints and systems that enforce both.
Use this document first when you need to answer:
- What is the delivery standard?
- What is non-negotiable?
- What is enforced through checkpoints?
- What does great look like beyond the floor?
Supporting detail lives in:
1. The standard: the floor
This is the minimum bar across Head of Delivery, CSO, Service Lead, and ICs. Repeated misses are not style differences; they are performance issues.
1.1 Own the outcome
Literal statement: We own outcomes end to end, not just tasks or handoffs.
Why it exists: Clients do not experience our internal org chart. They experience whether the work moved forward, landed, and created value.
Analogy: In a Michelin kitchen, a station is not judged by effort. It is judged by whether the plate is right when it leaves the pass.
What good looks like: The owner drives work to resolution, unblocks dependencies, and does not treat “I sent the note” as the end of the responsibility.
1.2 No surprises
Literal statement: Risks, slips, and blockers are surfaced early internally and communicated externally in a controlled way.
Why it exists: Delivery trust is lost faster through surprise than through difficulty.
Analogy: In banking and risk-managed institutions, bad news travels early so leadership can respond before the client or market is surprised.
What good looks like: Yellow flags are raised early; internal leadership hears new negatives before the client sponsor does; silence is treated as a risk signal.
1.3 Show up prepared
Literal statement: We enter meetings, reviews, and decisions ready to contribute with facts, context, and a point of view.
Why it exists: Delivery quality compounds when preparation is routine rather than heroic.
Analogy: Michelin kitchens rely on mise en place; elite consultancies rely on preparation before the meeting, not improvisation during it.
What good looks like: Materials are reviewed ahead of time, dependencies are known, likely questions are anticipated, and the person in the room can explain the work clearly.
1.4 Distill complexity into clear action
Literal statement: We simplify complexity into decisions, next steps, risks, and tradeoffs.
Why it exists: Complexity is part of the work; confusion cannot be.
Analogy: Top consultancies are paid not just to analyze complexity, but to reduce it into defensible decisions that leaders can act on.
What good looks like: Updates are structured, tradeoffs are explicit, the next action is clear, and the team does not hide behind jargon or long explanation.
1.5 Deliver tangible value
Literal statement: We optimize for visible progress and real client value, not activity theater.
Why it exists: Busy teams can look productive while failing to create confidence, momentum, or business value.
Analogy: Great agencies make progress legible. Great delivery teams do the same without spinning or over-polishing.
What good looks like: Weekly touchpoints usually include an artifact, decision, demo, or clear capability shift. Work is framed in terms the client can understand and care about.
1.6 Close the loop
Literal statement: Open threads get resolved, acknowledged, or explicitly carried forward with an owner and next step.
Why it exists: Most trust erosion in service organizations comes from dropped loops, vague ownership, and unfinished follow-through.
Analogy: In elite operating environments, dropped balls are not seen as minor admin misses; they are evidence that control of the system is weak.
What good looks like: Questions receive responses, blockers receive owners, decisions are written down, and nobody has to guess whether something is still alive.
2. Why this standard exists
Brainforge delivery should rely on a repeatable system, not charisma, memory, or heroics.
Across top-performing environments, the same truths appear:
- preparation beats improvisation
- ownership beats diffusion
- quality gates beat unchecked optimism
- early escalation beats late rescue
- clear communication beats internal ambiguity
The point is not bureaucracy. The point is dependable work that is easier to teach and easier to trust.
3. Analogical framing
We use analogies to teach the model faster. Policy stays literal.
Michelin-star restaurants
The lesson is not style or prestige. The lesson is mise en place, station ownership, timing, and a hard quality gate before output reaches the customer.
Elite consultancies
The lesson is structured thinking, defensibility, preparation, and synthesis under scrutiny.
Great agencies
The lesson is client-visible momentum, responsiveness, narrative clarity, and making work legible.
Banks and other risk-managed institutions
The lesson is review discipline, escalation discipline, exactness, and no surprises to leadership or clients.
Full mappings and limits live in ../06-reference/delivery-analogies.md.
4. What great looks like
This is the excellence layer. It is not the floor.
4.1 Show up with a point of view
Do not just report facts. Interpret them, frame the tradeoffs, and recommend a direction.
4.2 Think beyond your immediate lane
Understand how your work affects the client, the plan, the team, and the larger system.
4.3 Attack the limiting factor
Identify the real constraint and focus energy there rather than spreading effort evenly.
4.4 Hold the standard for teammates
Do not normalize misses. Coach, challenge, and protect the bar when quality, ownership, or communication slips.
4.5 Raise the bar continuously
Seek feedback, improve the system, and make the next cycle stronger than the last one.
4.6 Manage up, down, and across
Align stakeholders, support teammates, and communicate with leadership without dropping clarity or accountability.
5. Communication discipline
Delivery quality is inseparable from communication quality.
Literal statement
We communicate in a structured way that reflects reality, supports decisions, and protects trust.
Why it exists
When communication is vague, delayed, or misaligned with delivery truth, the team loses control of the narrative and eventually loses trust.
Analogy
Agencies teach the value of clear client narrative; banking teaches the cost of surprise. Brainforge needs both.
What good looks like
- updates use a clear frame: status, risks, asks, next steps
- the client story matches execution reality
- written communication is preferred when it increases clarity and forwardability
- internal leadership hears new negatives before the client sponsor does
- loops are closed
Delivery-specific rules
- CSO is the default external voice for commitments and timeline narrative
- SL and ICs do not side-channel conflicting scope or date commitments in client channels
- weekly touchpoints should include something tangible when possible
- async-first is preferred when it makes the work clearer and reduces performative meetings
Detailed communication doctrine lives in client-communication-standards.md.
6. Project management discipline
Literal statement
We run delivery through defensible plans, honest systems of record, visible ownership, and explicit change control.
Why it exists
Weak planning and invisible drift create most avoidable delivery pain. Strong PM discipline is what turns talent into dependable execution.
Analogy
Consultancies teach defensibility before commitment. Banks teach control and review discipline. Brainforge delivery needs both.
What good looks like
- plans are pressure-tested before hard commitments
- milestones are client-meaningful
- ownership is visible
- risks are surfaced early
- material slips or scope changes go back through review
Core rules
- Plan before promise
- Systems of record reflect reality
- Milestones should mean something to the client
- Visible ownership beats implicit ownership
- Material changes trigger re-review
Detailed PM doctrine lives in project-management-standards.md. Linear-specific detail lives in linear-hygiene-standards.md.
7. How the standard is enforced
Standards are real when the system forces them, not when the language sounds strong.
The enforcement model
- Checkpoints enforce the standard
- Roles carry role-specific accountability inside the standard
- Systems of record make drift visible
- Leadership review decides when a miss is coaching, correction, or escalation
Core enforcement points
- Project Review Meeting enforces plan quality before execution lock-in
- CSO-SL alignment enforces “story matches build”
- Client weekly touchpoints enforce visible value and communication discipline
- Weekly leadership sync enforces portfolio-level risk visibility and escalation
- Re-gating on material change enforces change control
- Linear hygiene enforces execution truth
Detailed checkpoint expectations live in ../02-meetings-and-cadence/meeting-catalog.md.
8. Examples
Ownership
- Good: A blocker appears; the owner identifies the dependency, gets the right person involved, and carries the issue to resolution.
- Miss: “I sent a message” is treated as complete while the work stalls.
Escalation
- Good: A delivery risk is surfaced as a yellow flag early, with a proposed mitigation and owner.
- Miss: The team waits until the deadline is already compromised before naming the problem.
Communication
- Good: An update clearly states status, risks, asks, and next steps.
- Miss: “Everything is going well” is sent while the board and team know the work is off track.
Planning
- Good: A date is pressure-tested before it is presented as real.
- Miss: A commitment is made because it feels directionally right.
Teammate standards
- Good: A teammate notices a repeated miss and coaches or escalates rather than normalizing it.
- Miss: Everyone sees the pattern, nobody names it, and the bar quietly drops.
9. Relationship to roles and supporting docs
This document defines the shared bar. Role docs explain how different roles participate in the same system.
- Head of Delivery: governance, bar-setting, escalation, portfolio review
- CSO: client success, plan narrative, external communication, checkpoint leadership
- Service Lead: technical truth, feasibility, quality, IC accountability
- IC: execution, updates, early escalation, finish
Start from the shared role overview in ../01-roles-and-responsibilities/README.md.
Related docs:
delivery-team-charter.mddelivery-performance-rubric.mdclient-communication-standards.mdproject-management-standards.md../06-reference/delivery-analogies.md
Last updated: 2026-03-24