Another deadline. The same handover problem.

A target is not yet an approach.

The target is fewer delivery delays. The lead can change the handover process for one workstream, but cannot hire staff or change company-wide policy. The strategy must fit that authority.

1. Compare possible explanations.

Late work could reflect capacity, unclear acceptance requirements or changes after handover. The lead examines recent returns and asks the receiving team what was missing. An assertion that people are careless is not a confirmed cause.

2. Choose an approach and a trade-off.

If unclear acceptance requirements appear repeatedly, a possible approach is to agree those checks before handover. The trade-off is some earlier preparation, rather than another status meeting. Capacity remains an alternative explanation.

3. Test the assumption that matters.

With the relevant team's agreement, try the agreed checks on a small, comparable set of work. Record returns, delay and additional preparation effort. Decide in advance what would justify continuing and what would challenge the approach.

4. Distinguish the test from its outcome.

Completing the trial is not proof it worked. If returns fall but preparation creates a different delay, the evidence is mixed. If the sample is too small or workload changes, call it inconclusive. Revise the next step instead of declaring success.

5. Turn the choice into work.

Name the person responsible for each action, the date and the evidence to record. Review what happened weekly. Continue, change or stop based on that record. Keep observations separate from interpretations.

How Sankalpa helps

In the browser app, the participant develops this reasoning into a written strategy and action plan, tests and implements the approach, and tracks the work over 90 days. AI helps draft; the participant decides. Venkat's two scheduled personal reviews challenge implementation evidence at the published stages.

Read the business example