SkillScend

Structural diagnosis of delivery problems

Your last transformation didn't fail. It was absorbed.

A delivery problem that keeps coming back is usually structural. Its cause sits one or two levels above the team, in how decisions, priorities and constraints are set up. Fixes aimed at the team buy some movement, and then the organisation settles back.

You may recognise this

None of these is a failure of effort. Each is a failure of targeting: the intervention went to the visible layer, and the structure stayed.

I find which structural condition is generating the problem in one area, and say what to change first. The finding often lies in the gap between how leadership and the teams describe the same system. How the diagnostic works.

Where the problem really is a gap in skills, I also deliver training: Process Communication Model (PCM), Lean Six Sigma, agile role bootcamps, OKRs and Evidence-Based Management. Participants receive a SkillScend certificate with a verifiable digital badge, issued through Accredible. See the programmes.

The Structure Beneath the Symptoms
The full argument: the six structural conditions, the eight patterns they form, and a self-check you can run on your own organisation.

Read the paper

Or try it first: the self-check, or a 90-second game about why nothing gets fixed.


Bogdan Cernea

I have worked on transformation, strategy and coaching since 2013, with everyone from delivery teams to executive boards, including at IBM, LSEG and ING Hubs, and as an associate consultant with Stanton Chase.

Certified PCM Trainer · Lean Six Sigma Black Belt · ICAgile Certified Professional in Agile Coaching · PAL-EBM (Scrum.org)

More about my work

Write to me at [email protected] or message me on LinkedIn. One conversation, a direct answer on whether I can help, and no proposal before the problem is understood.