The Signal Cadence

The steerco update your board will actually believe.

Mode decides how we engage. Technology decides what we deliver. The Signal Cadence is how the sponsor knows it is working. It is the communication, thought leadership, and team-assembly discipline Manuel runs on every engagement, from day one to handover.

Why the cadence is the product.

Mid-market programmes do not stall because the technology is wrong. They stall because nobody senior is telling the sponsor the truth on a rhythm the sponsor can rely on. Steerco reporting turns green-amber for two cycles. The RAID is a spreadsheet nobody reads. The squad rotates without warning. By the time a board paper lands, the delivery lead and the sponsor are reading different books.

The Signal Cadence is the fix. It is the named rhythm of written communication, thought leadership, and named-role team assembly that Manuel applies to every engagement. It is what a Rescue delivers inside thirty days and what a Build is built around for the full programme.

Three surfaces

Communication, thought leadership, team assembly.

The Signal Cadence runs on three surfaces. Each has an artefact, an owner, and a rhythm. None of them slip.

01

Communication rhythm

Weekly, fortnightly, and monthly written updates in formats the sponsor can forward to the board without rewriting. The weekly is one page. The steerco pack is five. The monthly narrative is three. No slide theatre. No colour-only reporting. Owners named on every line.

  • Weekly one-pager
  • Five-page steerco pack
  • Monthly sponsor narrative
  • RAID written in plain English
02

Thought leadership

Manuel writes the decisions down. Not slides, not decks — written artefacts on scope, architecture, sequencing, and trade-offs. Each one is signable. Each one holds up in a room Manuel is not in. The sponsor can read them, act on them, and defend them on their own.

  • Scope & sequence notes
  • Architecture decision records
  • Trade-off memos for the sponsor
  • Board-ready written briefs
03

Team assembly

The squad is the delivery instrument. Manuel assembles named specialists from a short list he has shipped alongside before. Roles and people are declared up front. No offshore pyramid. No mid-programme resource swaps. The same people from charter to handover.

  • Named roles, named people
  • Specialists Manuel has delivered with
  • Stable from charter to handover
  • Knowledge transfer from week one
What the sponsor sees, when

The rhythm, written down.

  1. Day 1 to 5 — ground read

    A written ground-read lands in the sponsor's inbox inside the first five working days. Artefact review, stakeholder interviews, real conversations in the corridor. No survey instruments. No pre-packaged maturity model. No deck.

  2. Day 5 to 10 — scope on one page

    A single-page scope statement. What is in, what is out, what was pretending to be in. Signed by the sponsor. This becomes the document every downstream conversation refers back to.

  3. Weekly — the one-page update

    Every Friday. One page. What moved this week, what did not, what the next week needs, what the sponsor needs to decide. The same format for the entire engagement.

  4. Fortnightly — demo and decisions

    Working demo every fortnight when a Build is under way. Three decisions per demo, logged with owners and due dates. The demo is not a theatre piece. It is the evidence the week produced something.

  5. Monthly — steerco and board narrative

    A five-page steerco pack and a three-page sponsor narrative. The narrative is what the sponsor takes to the board. Manuel writes both. The sponsor edits, signs, and sends.

  6. Quarterly — written reset

    A written review against the original charter. Three questions: what did we say, what did we do, what do we change. The sponsor reads it, challenges it, co-owns the answer. This is where programmes stay honest over long engagements.

What you will not see

The Signal Cadence is as much about what we cut.

  • Status decks that take three days to build and nobody reads.
  • RAID logs that are really just meeting minutes.
  • Colour reporting that hides the one red line that matters.
  • Junior-resource rotation that resets context every three weeks.
  • Vendor-led steerco where the partner sets the agenda.
  • Monthly packs that are a compilation instead of a narrative.
  • Any reporting Manuel would not personally defend in an audit.
Why sponsors stay

The cadence outlasts the engagement.

Most engagements end when the programme ships. The Signal Cadence is designed to survive the handover. The weekly one-pager, the decision log, the written narrative — your internal team picks them up and keeps running them. That is why the Signal Cadence is the third pillar, not an engagement extra.

Sponsors quote the cadence back to the business after Manuel is gone. That is the point. The artefacts are yours, not ours. The rhythm is a habit, not a deliverable.

Questions people ask

Signal Cadence FAQ.

What is the Signal Cadence?

Company31's named delivery discipline. The weekly, fortnightly, and monthly communication rhythm between Manuel and the sponsor, the way the squad is assembled around the programme, and the written artefacts that tell the truth about where the programme actually is.

How is it different from normal programme reporting?

Normal reporting is designed to survive the steerco. The Signal Cadence is designed to survive the audit. Reports are written in English a CFO can act on, owners named on every line, and the weekly update is the same document the sponsor can forward to the board without rewriting.

Does the Signal Cadence apply to Rescue and Build equally?

Yes. Mode decides how we engage. Technology decides what we deliver. The Signal Cadence is how the sponsor knows it is working. It lands on day one of every engagement.

Is this a framework we can license?

No. The Signal Cadence is a delivery discipline Manuel runs personally. It is not a methodology document, a certification, or a tool. It is written into every engagement because Manuel writes every artefact.

What does the sponsor see in the first week?

A written ground-read, a single-page scope statement, a RAID with owners named, a revised steerco agenda, and a plain-English weekly update in the format the sponsor will receive for the rest of the engagement. No slide theatre.

See the cadence in your programme.

Book a thirty minute call. Manuel will ask what the current reporting rhythm is, where the sponsor is blind, and who on the programme is actually writing the decisions down. If Company31 is the right fit, a scoped proposal follows inside forty-eight hours.

Book a call Download the Self-Check (PDF)