← Back to insights

Apply

The report is late: training or clearer responsibilities?

An illustrative example for a team with limited time and resources: review responsibilities before requesting training, then agree a small step to review without adding unnecessary work.

The report is late again. A reminder asks the team to meet deadlines, followed by a proposal for time-management training. Training may help, but first ask a question closer to the task: where does the report get held up, and what does the person preparing it need?

This is an illustrative example for discussion and practice, not a client case or a study with measured results. It offers a starting point for a small team balancing workload, absent colleagues or limited resources.

Start with one task

Choose one recurring report. Agree what the output should contain, who will use it and when they need it. A usable page delivered at an agreed time may be a clearer aim than “better reporting”.

Record who prepares the draft, who provides the inputs and when, who reviews it, and who approves the final version. Two colleagues may be waiting for each other, or the person sending the report may lack essential inputs. If the discussion does not establish the cause, leave it open rather than assuming one.

Separate a learning need from a work constraint

If the task is unclear, clarify the expected output and responsibility. If inputs or approval arrive late, review that step with its owner. If the inputs and time are available but drafting or analysis needs improvement, identify a specific skill and practise it using a work example.

Several factors may overlap. Keep this conversation focused on the task and available support, without labelling staff or turning it into an automated performance judgement. Listen to the people doing the work.

Try a limited change

For the next report, the team could agree a draft owner, an input deadline and a reviewer. Put these details on a shared page instead of adding a new system or a daily meeting.

Agree what to review: were the inputs complete, was the output usable, and where did waiting remain? Use task-related evidence without collecting sensitive personal information. Review after one reporting cycle, then adapt or stop the change if it adds effort without clear value. This is a proposed trial, not a promise of improvement.

When a development need becomes clear

Use the training-needs matrix to connect the gap to the task, then the staff development plan to agree a learning goal, an application step, support and a review date. Both tools are open to use without registration or sending team data.

If responsibilities or staff onboarding need a broader review, discuss the Team organization & staff onboarding service. Collaboration begins with a fit discussion, followed by agreed outputs, timing and fees. Decisions and staff assessment remain with the organisation and its authorised people.

Before proposing the next solution, ask the person doing the work: what small clarification or practical support would help you complete this task?

Need to turn the idea into practice?Discuss your project with TAS →