Diagnose common Day 2 weaknesses and use remediation drills to improve response quality.
Remediation after a Day 2 practice case should identify the specific response weakness and then drill the missing skill. Reading the solution is not enough. A candidate must determine whether the problem was role focus, technical knowledge, evidence selection, analysis depth, recommendation logic, communication, time allocation, or professional judgment.
The most useful remediation is narrow. It fixes the response move that failed.
This lesson focuses on diagnosing weak Day 2 responses and designing targeted remediation drills.
| Weakness category | What it looks like |
|---|---|
| Role drift | The answer discusses issues outside the declared role while underdeveloping role issues. |
| Shallow depth | The response names the issue but does not analyze enough evidence. |
| Fact copying | The answer repeats exhibits without explaining implications. |
| Technical gap | The rule, calculation, procedure, or framework is wrong or incomplete. |
| Weak synthesis | Common facts are ignored or disconnected from the role conclusion. |
| Weak recommendation | The answer ends without action, owner, condition, or follow-up. |
| Poor caveats | Missing facts are ignored or used to avoid deciding. |
| Communication weakness | The answer is vague, wordy, generic, or poorly matched to the reader. |
Start with the weakest issue response, not the whole case. Ask:
The answer identifies the remediation target. If the technical rule was correct but the implication was missing, more technical reading will not fix the problem. If the issue was role drift, rewriting the answer with a role filter is more useful than reviewing all content.
Use short drills that isolate the weak response move.
| Weakness | Drill |
|---|---|
| Role drift | For three case requests, write only the declared role, intended reader, and top role issues. |
| Shallow depth | Rewrite one paragraph using issue, evidence, analysis, implication, recommendation. |
| Fact copying | Convert five copied facts into “fact, therefore, implication” sentences. |
| Technical gap | Write a plain-language rule summary, then apply it to two case variations. |
| Weak synthesis | Add one sentence explaining how a common fact changes the role conclusion. |
| Weak recommendation | Rewrite conclusions as action, reason, condition, and follow-up. |
| Poor caveats | Replace vague “more information needed” language with a specific missing fact and next step. |
| Wordiness | Cut a paragraph by one-third while preserving issue, analysis, implication, and recommendation. |
The drill should be small enough to repeat.
Keep a short remediation log after each full case. The log should track behaviour and next action, not broad self-criticism.
| Field | Example |
|---|---|
| Role issue | Finance recommendation for expansion. |
| Weakness | Calculated NPV but did not address covenant breach. |
| Cause | Missed common financing fact when writing role conclusion. |
| Fix | Add common-fact scan before final recommendation. |
| Drill | Rewrite three conclusions with one linked common fact. |
| Next check | Confirm every major recommendation includes feasibility and covenant review. |
This turns practice into a feedback loop.
A rewrite should be purposeful. Do not rewrite the entire case every time. Rewrite the paragraph or issue response that reveals the weakness.
Use this rewrite sequence:
For example, if the weak response copied facts, the rewrite should not add more facts. It should add interpretation. If the weak response lacked a recommendation, the rewrite should add a direct action and condition.
When the weakness is technical knowledge, study should still be application-based. Read the rule, summarize it in plain language, apply it to a fact pattern, then change one fact and apply it again. The variation is important because Day 2 requires judgment about what changes the conclusion.
Technical remediation should end in writing. If the candidate can explain the rule verbally but cannot write a role-depth paragraph, the gap remains.
If the weakness is time allocation, the drill should focus on issue ranking and stopping rules. Practise identifying the top role issues before writing. Practise stopping when a paragraph has enough evidence, analysis, implication, and recommendation. A complete but proportionate answer is better than an overbuilt first issue and missed later issues.
Use this remediation cycle:
| Pitfall | Correction |
|---|---|
| Reading solutions passively. | Rewrite the weak response and apply the fix. |
| Treating every error as a content gap. | Diagnose role focus, analysis, recommendation, writing, and timing separately. |
| Keeping broad study notes. | Record the cause, fix, drill, and next check. |
| Rewriting entire cases without focus. | Target the failed response move. |
| Repeating the same weakness. | Keep the drill active until the next case shows improvement. |