Results — Proof That It Works

Progress you can point to.
Outcomes from software organizations installing a light weekly rhythm across Product, Engineering, CS & Sales.

Typical outcomes

  • Net Revenue Retention (NRR) up; churn down. 4–8 p.p. within 1–2 quarters.

  • Activation faster. Time‑to‑first‑value (TTFV) ↓ 15–30%; onboarding conversion ↑.

  • Flow improves. Lead time ↓ 25–45%; deploy frequency ↑ 1.5–2.5×; incident recovery (MTTR) ↓ 30–50%.

  • Less overload, more finish. WIP drops; completion rate rises within two cycles.

  • Alignment at scale. One Objective & 3–5 KRs; one weekly cadence across 10+ teams.

Results vary by context. We install behavior and cadence; your teams make the magic.

Evidence snapshots (anonymized)

DevTools scale‑up (±120 FTE)

Goal: accelerate onboarding activation & reduce rework.
What changed: one Objective (activation), 5 KRs, 20‑min weekly review, two bets on “first value” moments.
Outcome (8 weeks): activation conversion +18%; lead time −30%; weekly review adherence >85%.

“We stopped debating and started deciding. Movement within weeks.” — VP Product

Fintech SaaS (9 squads)

Goal: stabilize reliability & improve customer trust.
What changed: one Objective (reliability), 4 KRs (MTTR, change failure, incident rate, comms), weekly review.
Outcome (quarter): MTTR −42%; deploy frequency ×1.8; Net Revenue Retention (NRR) +4 p.p.

“Weekly commitments aligned CS and Product; faster activation, fewer incidents.” — COO

B2B SaaS (CS ↔ Product alignment)

Goal: reduce avoidable churn; increase expansion.
What changed: Objective (revenue durability), 5 KRs (NRR, logo churn, expansion, health score, time‑to‑first‑value).
Outcome (2 quarters): churn −15%; Net Revenue Retention (NRR) +7 p.p.; TTFV −22%.

“The weekly rhythm kept the focus real—two bets per KR, every month.” — CPO

Platform & product (12 teams)

Goal: unblock flow across dependencies.
What changed: one Objective (flow), 4 KRs (lead time, deploys, blockers cleared, cross‑team SLAs*), weekly review with triage.
Outcome (6–10 weeks): lead time −28%; completion rate +21%; incident recovery −35%.

“Same Objective, same cadence, fewer handoff stalls.” — Head of Engineering
*“SLAs” here = simple expectations for handoffs/ownership (no bureaucracy).

How we measure (simple & shared)

We keep measurement light and useful—one scoreboard, owned by your teams.

  • Net Revenue Retention (NRR): expansion + contraction + churn from existing revenue (excludes new logo).

  • Activation / TTFV: time from signup to first verifiable value (your definition).

  • Lead time: commit → production (DORA).

  • Deploy frequency: how often changes reach users (DORA).

  • Incident recovery (MTTR): acknowledge → recover (DORA).

  • Finish rate & WIP: how much starts vs. how much finishes each cycle.

  • Weekly review adherence: did the meeting happen and did decisions land?

Why results show up

  • One Objective, 3–5 KRs becomes the shared choice architecture.

  • Weekly review (20 min) creates on‑time decisions and visible progress.

  • Two live bets per KR turn ideas into learning (and kills what doesn’t work).

  • Ownership is explicit so work finishes.

Testimonials (selected)

“We created hyper focus and it has delivered huge value… collaboration has increased which is leading to more confidence in our most ambitious targets.”
— Ciprian Diaconasu, VP Engineering, Mambu

“Bart differentiates himself by combining business acumen with technical expertise to get software engineering organizations delivering real value… he helped us form new habits and define metrics to track progress.”
— Phil Mander, Head of Engineering, Harver

“Bart helped us at BinckBank to introduce many employees to OKRs and guided teams in sharpening their objectives… teams voluntarily decided to start using OKRs.”
— Christiaan van Laecke, International Business Manager, Saxo Bank

“We introduced OKRs to support our new strategy; Bart helped with our BHAG and the company and team OKRs.”
— David Vermeulen, CEO, The Inner Circle

“Next to a great engineer, he actively improves ways of working… teams gained insights into choices and long‑term impact.”
— Maurits Cieremans, Head IT Mortgages NL, ING

See similar results in your org

Pick the entry point that fits your urgency:

  • Start with the Diagnostic (≤2 weeks) → decision‑ready brief, Objective + 3–5 KRs, 90‑day plan.

  • Install Activation (2–4 weeks) → weekly review, on‑time decisions, two bets running, hand‑off.

  • Train‑the‑Trainer (6–8 weeks) → internal Guides to scale to 10+ teams.