Reviewed: 9 October 2026. The workload, people, interview prompts and answers below are original fictional preparation examples. They are not a verified employer question bank, evidence of employee performance or a substitute for the hiring organisation's actual assessment brief.
Prepare an answer with visible managerial decisions
A manager interview answer should make it possible to distinguish the team's work from the candidate's decisions. Explain what needed doing, the available capacity, who had authority to change scope, which work you personally assigned or reviewed and what actually happened. “I motivated the team and delivered everything” offers little evidence unless the actions and completion record support it.
Harvard Law School's manager resource page lists feedback, delegation and coaching among its own development resources. That is a narrow institutional reference. It does not establish Indian employment policy or prove that a particular interview answer or management technique produces better performance. The example below is an original workload discussion, not an adaptation of its linked training materials.
Choose a real experience you can discuss without revealing confidential employee or customer information. If your experience was project coordination rather than formal line management, say so. Do not invent disciplinary authority, direct reports or outcomes to match a job title.
Original workload case: 45 minutes of work, 40 minutes available
The fictional case supplies two contributors, Rohan and Sana. Each has 20 minutes available before a review checkpoint. The estimates below are fixed inputs for the exercise and include the work needed to produce each named deliverable. They are not measured productivity standards.
| Item | Supplied requirement and boundary |
|---|---|
| Task A | A 20-minute stock-count summary, required at the current checkpoint. Rohan is able to perform it. |
| Task B | A 15-minute label comparison, required at the current checkpoint. Sana is able to perform it. |
| Task C | A 10-minute draft handover note with a later deadline. Sana is able to perform it. |
| Initial capacity | Rohan 20 plus Sana 20 equals 40 contributor-minutes. |
| All three tasks | 20 plus 15 plus 10 equals 45 contributor-minutes, exceeding current capacity by five. |
| Authority | The coordinator can propose assignments; the supervisor confirms any revised sequence. |
Task C is indivisible in this supplied case, and its 10-minute estimate is not reduced by assigning extra people. Task A and B use 35 contributor-minutes. Sana then has five minutes left, which is insufficient for C. Rohan has no remaining capacity. Running A and B in parallel does not create the five missing contributor-minutes needed to complete all three before the checkpoint.
A complete past-contribution answer
For the following answer, the fictional completion record adds specific events: the supervisor confirmed that C could be scheduled after the checkpoint; Rohan completed A; Sana completed B; the coordinator checked that the two deliverables were present. C remained pending at the checkpoint. No accuracy audit, measured time saving or customer outcome is supplied.
“In a coordination exercise, two contributors each had 20 minutes before our checkpoint. The three tasks were estimated at 20, 15 and 10 minutes, for a total of 45 contributor-minutes against 40 available. I did not treat parallel work as extra capacity. I checked which deliverables were due at that checkpoint and proposed assigning the stock summary to Rohan and the label comparison to Sana, with the later-deadline handover note scheduled afterwards.
“I put the sequence to the supervisor because I could propose assignments but could not confirm a revised sequence myself. The supervisor confirmed it. I then communicated the owners and checkpoint deliverables, and checked whether the two outputs had arrived. Rohan completed the summary and Sana completed the comparison. I verified that both deliverables were present; the handover note was still pending. I would describe the result as two confirmed checkpoint deliverables under an approved sequence, rather than all work completed or a demonstrated improvement in quality.”
This answer uses “I” for the coordinator's calculation, proposal, communication and presence check. It names the contributors' work and the supervisor's approval separately. Its result does not extend beyond the supplied record.
Follow-up: why not give Sana all remaining work?
“Sana's 15-minute comparison left five of her 20 minutes available. The handover note required 10 minutes as an indivisible task, so the remaining five did not cover it. I would not describe a partial start as a completed handover. The later deadline made a proposed sequence change possible, but I still sought the supervisor's confirmation.”
This response shows the arithmetic and the authority boundary. It does not claim that Sana worked slowly, lacked commitment or should skip a break. The capacity and estimates are supplied facts of the exercise; they do not establish anything about the people beyond this bounded case.
If a real estimate is uncertain, identify its basis and ask the task owner what is included. Do not state a rough estimate with the certainty of measured completion data. In a real account, the fact that a deliverable arrived also does not by itself establish its correctness.
Follow-up: what did you check at the checkpoint?
“I checked whether the named summary and comparison deliverables were present, and recorded that the handover note remained pending. The supplied record does not include an accuracy review. I would need the actual acceptance criteria and authorised review process before claiming that those outputs were approved or error-free.”
This is a useful distinction when an interviewer asks what “done” meant. A received file, a completed task according to its owner and an accepted deliverable can be different states. Explain the state you actually observed. If someone else performed the substantive review, credit that person and distinguish your own contribution.
Separate a hypothetical answer from the past record
Suppose the interviewer asks, “What would you do if Task C also became due at the current checkpoint?” No such event occurred in the supplied completion record. Answer in future or conditional language.
“With the same estimates and capacity, all three tasks would still require 45 contributor-minutes against 40 available. I would explain that shortfall to the supervisor, clarify whether the new deadline was firm and present the options that actually existed. A confirmed reduction in scope, a changed deadline or additional qualified capacity could change the plan. None is supplied here, so I would not promise all three deliveries. I would ask for an authorised priority decision and communicate its effect to the contributors.”
This answer proposes a next action. It does not claim approval, extra staff or a successful recovery. If additional capacity were offered, you would still need to check task compatibility, handover costs and the deadline; a person being available does not prove they can perform a particular task immediately.
Follow-up: how would you give feedback?
Keep the feedback tied to an observed deliverable and its agreed requirement. The fictional case does not supply an employee mistake, conflict or repeated underperformance, so there is no basis for inventing one. A hypothetical feedback answer can explain what you would clarify without fabricating a past conversation.
For example: “If the label comparison lacked an agreed field, I would first identify the actual field and compare the deliverable with the brief. I would discuss the gap with its owner, ask what prevented completion and agree a correction within my authority. I would check the revised output against the same requirement. That is a proposed response; the current case does not establish that a field was missing or that feedback occurred.”
Avoid attaching a performance label to a person based on one hypothetical gap. An interview example should not become an unsupported judgment about an employee. For a real past feedback story, state the specific observation, your actual conversation and the documented outcome you can honestly discuss.
Adapt the example to your own experience
Start with one genuine project and reconstruct its task list, estimates, deadlines and decision authority. Select facts you remember reliably or can verify from material you are entitled to use. Do not copy confidential operational records into an interview preparation document.
Prepare a concise main answer and then rehearse follow-ups about why you chose the sequence, how you obtained approval, what you checked and what remained unfinished. If you cannot verify an exact figure, remove the false precision rather than inventing a number. A smaller truthful example is easier to defend under questioning.
Use the STAR method guide to organise a past example, and the teamwork interview guide to discuss individual contribution within shared work. A manager answer should still explain assignment, capacity, review or escalation decisions that were actually yours.
Frequently asked questions
Can I use a coordination example without being a formal manager?
Yes, as preparation material, if you state your actual role and authority. Whether it meets a particular vacancy's experience requirement depends on that employer's published criteria.
Must every answer end with a measurable improvement?
No invented improvement is justified. State the result you can support, including pending work and limits on what you reviewed.
Should I memorise this answer?
Practise the reasoning and ownership distinctions. Use your own genuine facts in an interview and follow the actual assessment's instructions. This fictional answer does not establish that any employer asks these exact questions.