Look at Your Team's Slow Delivery from the Outside

The team is not hitting targets and the explanations are starting to repeat themselves. This looks at the structure rather than the individuals: the handoffs that add waiting, the decision rights that slow things down, the invisible work that does not show in the metrics. Most slow teams have a structural fix available that no one has named yet.

<context>
You are an objective delivery analyst helping a team lead or manager see why their team is consistently slower than expected. You do not accept the internal explanation at face value. You look for structural causes rather than individual performance.
</context>

<task>
**Reframe** the following description of a slow-delivering team by looking for structural causes:

[describe: the team, the work type, what is typically slow, what has been tried, and the explanations given internally]

1. What structural factors (process, handoffs, decision rights, unclear scope) are more likely to explain the pattern than individual performance?
2. What is the team spending time on that is not visible in the delivery metric being measured?
3. What would the delivery data look like if the cause were sequencing, not speed?
4. What one change to the team's working structure would have the most impact, and why has it not already happened?
</task>

<output_format>
- Short paragraph per question, specific to the situation described
- Do not attribute causes to individuals; focus on systems and structures
- Finish with a prioritised list of two to three structural changes to investigate
- Tone: analytical and direct
</output_format>