Another framework or technology won’t fix your team. The last one didn’t either.

Every friction has an obvious fix. Most of them work, and the cost quietly turns up somewhere you were not watching.

The Fundamentals First Repair System is a diagnostic system for teams where the framework looks right and adaptation still doesn’t happen. It sits under whatever you already run, Scrum, SAFe, Kanban, or your own hybrid, and repairs the fundamental underneath the friction instead of installing another process on top.

For managers, team leads, and anyone responsible for at least one team.

At Strobbo, the fix started with the leader, not the team. A year on, a new group had gone from a delivery cycle of several months to shipping every two weeks, independently documented by Scrum.org. Read the story →

The meetings happen.
The board is updated.
The backlog exists.
And still, decisions don’t improve.

What Fundamentals First does

It isn’t a maturity model or a transformation program. The bet underneath it: behavior creates professionalism, not frameworks. It’s a diagnostic you run on a real team, in four moves:

Step 1

Spot the friction

Step 2

Name the weakened fundamental

Step 3

Try one repair move

Step 4

Observe what shifts

Friction is recognizable. The fundamental underneath it is fixable. That’s the whole bet. The full system, worked end to end, lives on the How It Works page.

The eight fundamentals

These apply to any team, regardless of the framework you use. They’re what a team needs to adapt honestly.

The eight fundamentals fundamentalsfirst.eu An empirical loop that keeps a team in contact with reality, upheld by how the people work, powered by what the team can deliver. THE LOOP inspect, adapt, repeat Reality Transparencyone honest picture of the work Honest Inspectionname the gap, out loud Decisive Adaptationactually change something POWERED BYDELIVERY CAPABILITY FOUNDATION Skill Completenessevery skill the work needs Commitment to Qualityhold the bar under pressure UPHELD BYPROFESSIONAL TEAM DYNAMICS Trust and Candorsay the hard thing with respect Outcome Ownershipown the result, not the task Decision Mandatedecide, don't escalate

Empirical adaptation engine

Reality Transparency

The team shares one honest picture of the work, the bad parts included. You can’t inspect what’s hidden or dressed up.

Honest Inspection

The team looks at that reality without flinching and names what it sees. Inspection without candor is just a status update.

Decisive Adaptation

When inspection surfaces a problem, the team actually changes something. Adaptation without consequence is theater.

Professional team dynamics

Trust and Candor

People say the hard thing to each other’s faces, and it’s safe to do so. Otherwise the real conversation happens in the hallway.

Outcome Ownership

The team owns the result, not just its tasks. “Not my job” is where outcomes go to die.

Decision Mandate

The team can decide and act on what it owns. Responsibility without authority is just blame waiting to happen.

Delivery capability foundation

Skill Completeness

The team has the skills it needs to deliver without waiting on someone outside it. Every handoff is a place for work to stall.

Commitment to Quality

The team holds a standard for “done” it won’t quietly lower under pressure. Quality that bends on a deadline was never a standard.

It’s not just your team. The gap is measurable.

What teams usually say

“We’re doing all the ceremonies. We just aren’t getting the benefit.”

The gap between “we’re doing the ceremonies” and “we’re getting the benefit” shows up in the research, not just in your standup:

  • Leaders and their teams look at the same work and see different things. In Axios HQ’s 2025 State of Internal Communication, 80% of leaders said communication was clear. Only 50% of employees agreed. Same artifacts, two realities.
  • Visibility isn’t the cure people hope it is. In Digital.ai’s 18th State of Agile (2025), 55% of organizations reported complete visibility into what’s being built, yet 63% still struggle to deliver reliable software, up 12 points in a single year.
  • Tools don’t rescue weak fundamentals. DORA’s 2025 research calls AI an amplifier: on teams without solid foundations, adding it pushed defects, incidents, and review times sharply up, not down.

The ceremony was never the problem. The fundamental underneath it was.

What a repair looks like in one team

Strobbo, a Belgian workforce-management platform, was running Scrum by the book and getting little back. The Friction Signal: knowledge lived in people’s heads, nobody challenged the work out loud, and Sprint Reviews had no real stakeholders in the room. Just the team, talking to itself about technical detail. The Weak Fundamental underneath was Reality Transparency. Everyone was busy, and almost no one shared the same picture of the work.

The Repair Move was small and specific: put a real stakeholder in the next Sprint Review. They started by having one team play stakeholder for another, then brought in help desk, onboarding, and sales. Eventually Protime’s CEO joined a review, was impressed, and came back to the next one on his own. That one change did more for transparency across the company than anything else they tried.

And the reason it worked: Steven coached the leader, Co-Founder Bert Neels, week by week, rather than running the teams himself. Bert carried each change to his teams. Within a year, go-to-market time was down and the teams owned their own deployments.

Field note · Strobbo

“We’ve significantly improved our go-to-market time, and teams now take full responsibility for deploying and rolling out new features… We’re closer to our customers through regular interviews… and there’s less ‘us vs them.’”

Bert Neels, Co-Founder, Strobbo

That was one team of sixteen. The same chain repaired a forty-person AI-platform group across five teams, where the fix was a full rebuild rather than a single move, and the CEO could finally see the work. Read that story →

And at an agricultural-machinery manufacturer, three teams of engineers who had worked as individuals started having the hard design arguments out loud, and got a real say in timelines and technical calls. Read that story →

That is one team. This is how you find out what is under pressure in yours.

The full diagnostic runs all 160 Friction Signals across the eight Fundamentals. You get the Fundamentals and Characteristics most likely under pressure, the Repair Moves your flagged signals put on the table, and the indicators that tell you whether the one you picked is working.

€349 for twelve months, all taxes included. Run it as often as you like, for as many teams as you’re responsible for.

What Fundamentals First is not

  • Not a maturity model. No levels, no score to climb.
  • Not a certification. No badge at the end. The outcome is changed behavior, not a credential.
  • Not a transformation program. No reorg, no eighteen-month roadmap.
  • Not a framework replacement. Keep Scrum, SAFe, or whatever you run. This works underneath it.
  • Not a sales funnel. The call gives you a real move whether or not we ever work together.
  • Not a coach on a throne. You bring the friction. The system gives you the language and the next step.

Find the crack behind the symptom.

Bring one friction signal your team keeps hitting. Walk away with the likely weakened fundamental and one repair move to try. Yours to keep whether or not we ever work together.

These calls are for managers, team leads, and anyone responsible for at least one team. Not running a team? Send the Leadership Brief to whoever’s accountable for yours.

Start with the book that started this

The system began with Scrum, because that’s where the gap between ceremony and behavior is easiest to see. Scrum. Explained. Finally. runs one honest test across all eleven Scrum elements: is what you’re doing actually producing the behavior the element exists for, or just the ceremony? Seventy-seven small diagnostics, no theory padding, free to download.

And the full field guide is live. The Fundamentals First Field Guide walks all eight fundamentals, with the friction router and the repair loop, free to read on the site.

Common questions

What exactly is the Fundamentals First Repair System?

A diagnostic. You take a friction your team keeps hitting, trace it to the fundamental underneath, and try one small repair move. It isn’t a framework or a methodology. It’s a way to find what’s actually weak and fix it, one move at a time.

How is this different from a maturity assessment?

A maturity model scores you against stages. This finds the one weak fundamental under a friction you actually feel, and hands you a small experiment. No levels, no scoreboard.

Will this work in our setup?

Yes. The fundamentals sit underneath the framework, not inside it. Whether you run Scrum, SAFe, Kanban, or your own hybrid, the same eight fundamentals decide whether the way of working actually delivers.

We already have a coach, or a framework we like. Does this still apply?

Yes. The fundamentals sit underneath whatever framework or coach you have. This gives you a shared language for what’s actually weak and what to try next.

How do I know if my team or organization is ready for this now?

If you can name one recurring friction, you’re ready. There’s nothing to prepare and nothing to install. You start with one team, one friction, this week.

I’m not a team lead. What can I do?

Plenty. Take the two-minute self-diagnostic to spot the weak fundamental yourself, then send the Leadership Brief to whoever’s accountable for how well your team performs. The system is for anyone moving a team forward, not just the person in charge.

Do we have to change our framework or tools?

No. You keep what you run. The repair happens in behavior, not in a migration. If a ceremony or tool is getting in the way you’ll see it, but nothing gets ripped out to start.

How long before we see something change?

A repair move is small enough to run in a single sprint or a couple of weeks. You name the signal that tells you it’s working before you start, so you’ll know quickly whether it moved.

Is this a big transformation program?

No. No reorg, no eighteen-month roadmap, no new framework to adopt. It’s a series of small, honest experiments on real friction. The change compounds from there.

Pass it on

Pass it to your manager. On a team hitting these walls but you’re not the one who runs it? You can still move this forward. Send the Leadership Brief to whoever’s accountable for how well your team performs: your manager, your team lead, whoever the team answers to. It makes the case in about five minutes, and it’s theirs to keep whether or not anything follows.

Pass it to a colleague. Know another team stuck in the motions of Scrum, SAFe, or any other framework and not getting the benefit? They’re running the ceremonies and using the terminology, and it still isn’t working. Send them this page. It helps them find the one fundamental most likely behind what they’re feeling, and a repair to try.

Who’s behind this

Steven Deneir is a professional agile consultant, coach, and trainer. 33 years in the field since 1993, 25 of them coaching teams that had the framework on the wall and little to show for it. His work is growing agility, adaptability, and simplicity with teams, across whatever they run. Fundamentals First is the system he built out of that work. More on who is behind Fundamentals First →

A leader Steven coached, Strobbo Co-Founder Bert Neels, described the shift this way:

“The team’s atmosphere has transformed from pressure to pride, with new starters quickly integrating and making positive impacts. Colleagues enjoy coming to the office! Despite growing to 26 members, my HR workload has decreased. Our Strobbo approach is now a model within Protime, and stakeholders are more engaged and satisfied.”

Bert Neels, Co-Founder, Strobbo