How the engagement works
The first thirty days, the cadence, and the commercial boundaries.
What we improve
The team is capable. The output does not show it.
Before concluding that you hired the wrong people, it is worth establishing whether the goals, ownership, priorities and visibility around them are sound. Usually they are not.
Symptoms
What you are seeing
- Delivery is slow and the reasons change each time you ask
- Goals are stated but not understood the same way by everyone
- Work has no clear owner, so decisions wait
- Estimates are consistently wrong in the same direction
- A great deal of work is invisible until it is late
- The same arguments recur without resolving
- Management expectations are not grounded in the system's real state
- Technical debt is discussed but never scheduled
- Nobody in the team has done this at the next scale up
Diagnosis
People problems and system problems look identical from the outside
A team missing its commitments looks the same whether the cause is capability, unclear priorities, an unrealistic plan, a delivery system that hides work, or an executive team changing direction faster than anything can be finished.
The distinction matters because the remedies have nothing in common. Replacing people when the problem is the system produces a new team with the same results, several months later and at considerable cost.
The starting assumption here is that the team is competent and the system around them is not. That assumption is tested, not asserted, and sometimes it turns out to be wrong. But it is the right place to start, and it is the one executives most often skip.
Approach
How Kendoo works through it
Observe before intervening
Sit in the planning, the reviews and the incidents. How an organisation actually works is rarely how it describes itself.
Establish baselines
What is genuinely being delivered, how long things actually take, and where work waits. Written down, so later claims of improvement can be checked.
Clarify roles and ownership
Who owns which area, and who decides what. Most delay is not work in progress; it is work waiting for a decision nobody is empowered to make.
Improve planning honestly
Plans that reflect the state of the system, including the parts that are slow because they are fragile.
Define decision rights
Which decisions sit with the team, which with management, and which with Kendoo. Ambiguity here is what produces the recurring arguments.
Coach the leads
Working directly with your leads and managers so the capability stays after the engagement ends.
Strengthen engineering practice
Review, testing and release discipline, chosen for the failures this team actually has rather than adopted wholesale.
Create honest visibility
Delivery reporting that shows risk while it is still cheap, including the parts that are not going well.
Management's part
What is required from your side
This is the half that is usually left out, and the engagement will not work without it.
-
An executive sponsor in the room
Attending the cadence, not receiving a summary afterwards. Priorities that change without the sponsor present do not hold.
-
Willingness to change priorities
Diagnosis usually shows that some current commitments were never achievable. Something has to give, and that is an executive decision.
-
Patience for the first month
Observation and baselining come before intervention. Acting in week one is how you fix the wrong thing confidently.
-
Tolerance for honest reporting
Visibility means bad news arrives earlier. That is the point, and it only works if it is received well.
Indicators
What gets monitored
Chosen per engagement against the baseline. No percentage improvement is promised in advance, because any such figure would be invented.
- How long work waits for a decision, as distinct from how long it takes
- The gap between estimated and actual, and whether it narrows
- How much work is visible before it becomes late
- How often commitments made to the business are met
- Repeat incidents and rework as a share of capacity
- How quickly risk reaches management
- Whether decisions taken by leads stick without escalation
Outcomes
What changes
- Priorities are understood the same way by executives and engineers
- Execution becomes predictable, which matters more than fast
- Risk is visible early enough to act on cheaply
- Technical decisions improve and stop being reopened
- Your leads grow into the decisions they should be making
- Management and engineering stop arguing from different facts
Related
Find out what is actually slowing delivery
Describe what is happening and we will look at whether it is a people problem, a system problem, or a planning problem.