When Supervision Breaks Down
Two reasonable people, eight ordinary steps, and a closing line that reveals the whole thing was avoidable. This is the best-constructed teaching item in the fourteen weeks, and its power is that there is nobody in it to blame.
The scenario
It occupies one slide near the end of the week's deck on writing up, with the response on the slide that follows. It is the only extended failure scenario in the subject that concerns the working relationship rather than the research, and it is worth reading twice before reading anything written about it.
Notice what the scenario withholds. There is no incompetence, no neglect, no bad faith, no unreasonable demand and no rule broken. A failure narrative with no villain is very hard to write, and this one manages it in a single paragraph - which is why it teaches something that a scenario with an obvious culprit could not.
- Suggestion made
- Attempt begun
- Confusion grows
- Criticism without explanation
- Both parties withdraw
- Review forces a meeting
Why nobody in it is wrong
Set the sequence out step by step with both parties' positions side by side, and the failure stops looking like a series of mistakes and starts looking like two coherent readings of the same events.
THE SEQUENCE, WITH BOTH POSITIONS HELD OPEN
| What happens | The student's position | The supervisor's position |
|---|---|---|
| They begin working together, having discussed the project and its theoretical framework | A proper start - the project and its framework are agreed | A proper start, on shared ground |
| They meet a number of times, usually at times arranged by the supervisor | Meetings are happening, and someone else initiates them | Meetings are happening, and I am initiating them |
| The supervisor, a recognised authority in the technique, encourages its use | An expert in this technique thinks I should use it | An interesting idea, offered in passing |
| The student tries it despite being unsure of its suitability | Doing what was asked, in good faith | Trying something out, as researchers do |
| The student becomes confused and troubled about the project | This is not working and I may be the reason | No information - nothing has been said |
| At a later meeting the student criticises the technique, without describing the difficulty | I have raised it | A criticism of an approach I am known for, with no reason given |
| The supervisor is relatively silent and stops calling meetings | I have offended them, or been judged | The student is unhappy with my advice; better to give them room |
| The student stops attending, stops responding to messages, and becomes discouraged | There is nothing to report and nothing to say | The student has disengaged |
| A progress review falls due and a meeting is called | I am being hauled in | A required checkpoint, at the scheduled time |
| The student feels criticised for lack of progress and explodes | Months of accumulated distress, arriving at once | An outburst with no visible cause |
| "You don't have to use that technique, I just thought it might be interesting to try it" | The whole detour was optional | I never asked for this |
The two position columns are this library's reading. The scenario narrates events and a single line of dialogue, and attributes no interior state to either party beyond the student's confusion and discouragement.
Read that column pair again and the structure of the failure becomes visible. At no point does either party hold information the other could have inferred. The student's difficulty is never described. The supervisor's silence has no stated meaning. Each acts sensibly on what they can see, and what they can see is systematically incomplete.
The sentence the whole thing turns on
The supervisor's closing line is the payload of the entire item: the technique was never required. One utterance was made and two different things were heard - a suggestion offered, an instruction received - and nothing in the months that followed corrected the mismatch.
The remedy is trivial in effort and enormous in effect: mark the status of the input at the moment it is made. "Is that something I should do, or something worth trying?" costs one sentence in the meeting and would have removed the entire scenario.
Where the silence compounds
The failure does not accelerate at the suggestion. It accelerates at the criticism that carries no explanation, and then again at the two withdrawals - and both withdrawals are legible as consideration rather than as abandonment.
The student's withdrawal
- Stops coming onto campus
- Stops responding to messages from the supervisor and the department
- Reads as: I have nothing to report, so there is nothing to say
- Is read as: disengagement
The supervisor's withdrawal
- Becomes relatively silent
- Stops calling the meetings that only they ever called
- Reads as: giving room to someone unhappy with my advice
- Is read as: judgement, or abandonment
One structural detail from earlier in the scenario now costs everything. Meetings were arranged usually at times arranged by the supervisor. When the party who initiates stops initiating, nothing else in the relationship generates a meeting. The only remaining forcing function is the scheduled progress review - an institutional checkpoint that would have happened regardless, and that arrives months late as far as this project is concerned.
The three competencies in the response
The following slide answers the scenario with three distinct capabilities. They are not restatements of one another, and the third is the only place in fourteen weeks that the material supplies a form of words to use.
What the response asks you to be able to do
Tell a direction from a suggestion
The material's own examples of non-negotiable directions are university rules and occupational health and safety matters. Everything else may be a suggestion - and its stated reason is the line worth memorising: ultimately the thesis has to be yours. If the status is not obvious, ask.
Expect some suggestions to fail
Research is described as an uncertain enterprise. Supervisors try ideas in their own research that do not work out, so expect that some of their suggestions to you will not work out either. A suggestion that fails is not evidence of bad advice, and it is not evidence about you.
Disagree in a form that can be heard
Talk to them about your concerns and explain why you think the technique is not suitable in this case - and when critiquing an approach, recognise its strengths before explaining why it does not fit. The material supplies both the good and the bad wording.
The second competency is the quiet one and it does more work than it appears to. If you expect every suggestion from an expert to succeed, then a suggestion that fails must mean either that the expert was wrong or that you executed it badly - and in a supervisory relationship most people conclude the second. That conclusion is what produces the student's confusion in the scenario, and it is dissolved simply by holding the correct prior about research.
The script
WHAT EACH VERSION ACTUALLY COMMUNICATES
| The recommended form | The rejected form | |
|---|---|---|
| Evidence of effort | "I've tried the technique" - the attempt is stated first | "I've tried" - present, but swamped |
| Scope of the claim | Bounded: it does not fit my case | Unbounded: it is useless anywhere |
| What it says about the adviser | Their judgement holds in the domains it was formed in | Their judgement was worthless |
| What it leaves open | A conversation about which technique does fit | A defence of the technique |
| What it asks for | A joint decision | Agreement, or an argument |
The comparison is this library's analysis. The source supplies the two forms of words and the instruction to consider how each would feel to receive.
The test attached to the script is the best part of it: think about how you would respond emotionally to both types of feedback on one of your ideas. That converts a rule about phrasing into something you can check yourself against in the moment, without needing to remember the rule.
Note also what the recommended form is not. It is not softening, and it does not withdraw the criticism - the technique is still being rejected, and the rejection is still explained. What it withdraws is the implied verdict on the person who suggested it. That distinction runs through everything at Seeking and Using Feedback, in the other direction.
What the response does not cover
One further silence is worth recording. The scenario has the student in real distress - confused, troubled, increasingly discouraged, and eventually exploding in a formal meeting - and the response addresses none of that directly. It treats a wellbeing trajectory as a communication problem. Avoidance under pressure runs through the week's other worked scenario too, at Overcoming Writer's Block, and in neither place does the material follow it past the practical advice.
Running the relationship so this cannot happen
The controls below follow from the scenario rather than from any instruction in the source, and they are marked as this library's synthesis. Each one targets a specific step in the table above, and each is the kind of omission catalogued at Common Mistakes in Project Management Research.
Six controls, each aimed at a step in the sequence
- Ask the status of any input you are unsure about, in the meeting: is this a direction or something worth trying?
- Record which it was in your own notes, with the date - the same discipline used for decisions on a delivery
- Agree who calls the next meeting, every time, before the current one ends
- When you attempt something suggested, report on the attempt whether or not it worked - a report of a failed attempt is progress
- Never let a criticism travel without its reason attached; the difficulty you encountered is the useful half
- Treat two missed contacts as a trigger to act rather than as a state to endure, in whichever direction the silence runs
The fourth is the one that would most cheaply have broken this scenario. The student attempted the technique, found it unsuitable, and reported a verdict without the attempt. Had the difficulty itself been described, the supervisor would have had something to respond to - and the closing line would have arrived in month one instead of month six. The general preparation habit behind it is at Working With Your Supervisor; the subject's own paired instruction not to let meetings lapse is paraphrased at The Do's and Don'ts of Social Research.
What to carry forward
- The scenario is a failure with no villain: every step is reasonable, and the outcome is months lost.
- It turns on one unmarked utterance - an expert's suggestion, received as an instruction, never labelled by either party.
- A suggestion from a recognised authority in that very technique does not land with the weight the speaker intends, and the speaker cannot feel the difference.
- Criticism without its reason attached is what escalates the failure. The difficulty encountered was the useful half and was never said.
- Both withdrawals are legible as consideration and are read as judgement. Interpreted silence is the load-bearing fault.
- The three competencies: separate directions from suggestions, expect some suggestions to fail, and disagree in a form the other person can hear.
- Ultimately the thesis has to be yours - which is the reason the first competency exists, not a licence to ignore advice.
- The remedy is addressed only to the student, offers no route back from months already lost, and treats a wellbeing trajectory as a communication problem. Record those limits.
Frequently asked questions
Whose fault is the breakdown in the scenario?
Nobody's, which is the point of the item. The supervisor offers an idea, the student tries it in good faith, both withdraw for reasons that make sense from where they stand, and the scheduled progress review is the first thing that forces contact. A scenario with a culprit would teach you to avoid being the culprit; this one teaches you to close the gaps that let two reasonable people diverge.
How do I tell a direction from a suggestion?
Ask, in the meeting, and write the answer down. The material's examples of genuinely non-negotiable directions are university rules and occupational health and safety matters; its stated reason for the distinction is that ultimately the thesis has to be yours. Anything whose status you are inferring is a status you do not have.
How do I disagree with my supervisor without damaging the relationship?
Use the form the material supplies: state that you tried it, acknowledge what it is good for, then explain why it does not work in your case and why. The strengths clause is not politeness - it withdraws the implied verdict on the person while leaving your rejection of the technique fully intact.
What if I have already lost months to this pattern?
The source has no answer, and this page will not invent one - the response is entirely preventive and names no recovery route, no third party and no escalation path. What the scenario does show is that the first real conversation resolved the substance in one sentence, which is an argument for having it now rather than at the next scheduled review.
Is it my job to keep the meetings going?
The material puts the initiative with the student in both directions - it tells you to see your supervisor regularly, and to make arrangements for continued supervision when they are away. The scenario shows why that matters: when the only party who ever called meetings stops calling them, nothing else in the relationship produces one.
Does this transfer to a sponsor or steering group?
The mechanism transfers exactly. An unlabelled suggestion from someone who assesses your work, a criticism delivered without its reason, and a silence that both sides interpret rather than test will produce the same outcome in a delivery relationship. What differs is that a project usually has more scheduled checkpoints than a thesis, which shortens the interval before the divergence surfaces.
References and source attribution
- The supplied teaching source: weekly study notes, slide decks and assessment activities for a master's-level research methods subject in project management. Author, institution and year are not stated in the supplied files.
- The Week 13 slide deck on the challenge of writing up, slide 28, which carries the supervision breakdown scenario quoted in full above, and slide 29, which carries the three-part response including both forms of words.
- The same deck's slides 23 to 27, which supply the roles, expectations, meeting-preparation and feedback material that this scenario is set against.
- The closing checklist of the same subject, reproduced by its final week from a methods text's student-researcher toolkit with a copyright line dated 2012, whose paired supervision items are paraphrased rather than reproduced above.
Suggested questions for Ask KEVOS
- Draft the sentence that asks whether an instruction from my supervisor is a direction or a suggestion.
- Rewrite this criticism of a suggested method using the strengths-first form.
- I have gone quiet on my supervisor for two months. Draft the message that restarts contact.
- Which of my current project decisions came from an unlabelled suggestion by someone senior?
- Turn this scenario into a set of controls for a sponsor relationship rather than a supervisor.
- Help me report an attempt that failed, in a way that reads as progress rather than as a complaint.