Managing Project Timelines in Customer Work
A lead's role expands gradually, supported by a senior shadow who observes and gives specific feedback.
A First Engagement Seen From the Lead's Chair
Imagine you are leading a customer engagement for the first time. A more experienced colleague sits beside you on the calls, and you are responsible for the questions, the schedule, and the result. Halfway through the discovery work, that colleague gives you feedback that cuts to the heart of the job: you were asking the questions you had already written down, not the questions the customer's own words were pointing toward.
This article follows a real account of a first engagement. The project was a three-week effort for a mid-market insurance carrier, building a single workflow that summarizes claims for a defined class of claims. The lead came away with three lessons that reach well beyond that project: how leadership is handed over gradually, how to listen well enough to change course mid-interview, and how a schedule can be lost in places nobody planned to look.
Keep the three lessons in mind as you read. Each one is about a different kind of control: control over who is leading, control over what you ask, and control over where the time actually goes.
Who Leads and Who Shadows
A senior shadow is a more experienced person who works alongside a new lead. In the account, the senior shadow was Theo. He attended the kickoff call and the first scoping interview, but he did not speak during the second interview. The gap in his participation was intentional in spirit: the lead needed room to lead, and his job was to observe closely enough that his later feedback would be specific and useful.
The lead and the senior shadow hold different jobs. The lead is responsible for the questions, the schedule, and the result. The senior shadow observes, gives targeted feedback, and then helps the lead act on that feedback. The comparison below summarizes how the two roles differ in this engagement.
| Area | Lead | Senior shadow |
|---|---|---|
| Customer questions | Writes, adapts, and asks the questions during the conversation | Observes the questions and how the customer responds |
| Schedule | Carries responsibility for the schedule | Helps when a delay needs an outside channel |
| Result | Carries responsibility for the result | Gives specific feedback on how the result is being pursued |
| Escalation | Decides what needs escalating and carries the problem | Shows which channel to use, such as the sponsor with authority to unblock the work |
| Feedback | Receives and acts on feedback | Gives targeted corrections at moments that matter |
Responsibilities drawn from the account. The table describes the split in this engagement, not a universal procedure.
How Leadership Grew Across the Engagement
The engagement stretched across two calendar months, February and March. In the first two interviews, the senior shadow was present and the lead was still finding her footing. By the third interview, the lead had taken over the conversation. The later events in March tested a different skill: keeping a schedule and a success target in view when the work ran into obstacles outside the conversation room.
Tracking the shift in leadership across three interviews
Use the account to describe how the lead's role changed from the first interview to the third.
- 1Kickoff and first scoping interview
The senior shadow, Theo, attends. The lead is learning the engagement with an experienced person present.
- 2Second interview
Theo stays silent. The lead runs the conversation herself, and her questions are largely the ones she prepared in advance. The feedback she later receives targets exactly this habit.
- 3Third interview
The lead is carrying the conversation. She still plans ahead, but she now sets the plan aside when a customer answer opens a better thread.
- 4Summary of the change
The lead's share of responsibility grew through the interviews, with the senior shadow's corrections arriving at the moments that mattered most.
The lead moved from being observed to leading, and the change came from the sequence of feedback and practice rather than from a single handover moment.
Adaptive Questioning
Adaptive questioning means changing what you ask based on what the customer has just told you. A prepared question list is useful as a safety net, but it becomes a liability when it pulls the conversation away from what the customer is actually revealing.
The lead's feedback from the second interview was exactly this problem. Her questions were prepared in advance, when they should have been drawn from the customer's last answer. The flow below is an illustrative model of the decision an interviewer makes after each answer. It is not a procedure taken from the source, but it captures the check that the feedback asked the lead to make.
Adaptive questioning is a skill that has to be practiced rather than simply understood. The lead did not stop preparing; she still walked into each conversation with a plan. What changed was her willingness to set the plan aside when a customer answer opened a more useful thread. The account describes her working on this one habit through the rest of the engagement, which is how one piece of feedback becomes a lasting change.
Write your prepared questions as a safety net, not a script. Before asking the next prepared question, check whether the customer's last answer already points to a more useful follow-up.
Schedule Risk and Success Metrics
Two ideas in this engagement determine how far the work still has to go: the schedule and the success metric. The sections below take them one at a time, then show how a problem in one spreads to the other.
How a Delay Cascades
When a schedule delay or a metric gap appears, it does not stay in one place. The diagram traces the path the account describes, from the gap between the metric and its threshold through the revision cycle, the delivery to staging, and the validation that follows. Each step pushes back the work downstream of it.
Why the Remaining Work Outlasted the Fix
The clearest lesson of the engagement is that the fix itself was the small part of the schedule. The model and prompt changes took about three days. The validation extension, which included getting the revised work onto staging and checking it against the metric, took two weeks. The lead named this as the single biggest lesson of the engagement.
Mistakes Beginners Make With Timelines
Common mistake Asking only the questions you wrote in advance
What it looks likeThe second interview, where the lead's questions followed her prepared list while the customer's answers pointed elsewhere.
Why it failsA prepared list cannot respond to what the customer has just revealed, so useful threads are missed.
Do this insteadCheck each answer for a useful follow-up before moving to the next prepared topic.
Common mistake Estimating only the fix
What it looks likeCounting three days of model and prompt revisions and ignoring the delivery to staging and the re-verification.
Why it failsIn this account the validation extension took two weeks, and most of that time was spent getting revised work onto staging.
Do this insteadInclude delivery, re-verification, and metric updates in the estimate.
Common mistake Treating the senior shadow as a passive observer or as the decision maker
Why it failsThe lead carries the questions, schedule, and result, while the senior shadow observes and gives feedback that the lead then acts on.
Do this insteadKeep the lead responsible for the outcome, and use the senior shadow for targeted feedback and for finding the right escalation channel.
Common mistake Leaving the success metric vague
What it looks likeAgreeing only that the workflow should be faster, without a defined measure.
Why it failsWithout a measurable metric and threshold, nobody can say how far the work still has to go.
Do this insteadDefine the metric, such as minutes saved per processed claim, and agree on a threshold before validation.
Practice Reading a Customer Answer
A customer says the claims team has been moving slower since a new intake form was introduced, and that adjusters keep re-entering the same details. Using the adaptive check from this article, decide whether this answer points toward a useful follow-up. If it does, write the next question you would ask, built from the customer's own words. Then name one way the schedule or the success metric could be affected if the issue turns out to be real.
Hints
- Start with the customer's words, such as slower and re-entering details, rather than with your prepared list.
- Think about what a metric like minutes saved per processed claim would measure in this situation.
Summary of the Engagement Lessons
- 1Leadership grows gradually: the senior shadow observes, gives targeted feedback, and steps back, while the lead carries the questions, schedule, and result.
- 2Adaptive questioning means letting the customer's last answer decide whether to build a follow-up or return to the prepared list.
- 3A success metric and its threshold define how far the work still has to go, as the twenty-three percent versus thirty percent gap showed.
- 4Schedule risk often lives in the delivery path to the customer: the revisions took about three days, but the validation extension lasted two weeks.
At a glance
- A lead's role expands gradually, with a senior shadow observing and giving specific feedback rather than taking over the work.
- Adaptive questioning means letting the customer's last answer shape the next question, with prepared lists serving as a safety net.
- A success metric and its threshold define how far the work still has to go, and a gap between them drives the remaining work.
- The remaining work can outlast the fix itself, because delivery to the customer and re-verification often take longer than the revisions.