$100 Website Offer
Get your personal website + domain for just $100.
Limited Time Offer!
Claim Your Website NowAsking Why Five Times: The Habit Legal News Analysts Need
Every news desk that follows the courts eventually runs a correction. The date of a hearing was off by a week, or an order was described as final when it was interim. The usual reaction is to fix the sentence and move on. The analysts who get promoted do something else: they ask why the error happened, and then why again, until they land on a habit of the desk that can be changed. This post treats that questioning habit as a career skill for anyone working in legal services and current affairs coverage in India, and it is written as an analytical exercise, not as legal guidance.
The symptom is never the cause
Suppose a daily digest lists a matter as “listed for hearing on Monday” and the actual listing was Thursday. The first answer to “what went wrong?” is that the writer typed the wrong day. That answer feels complete, and it is the one most teams stop at. It also guarantees a repeat, because the next writer can type the wrong day too.
The exercise only works if each answer is treated as a claim to be tested. Does the first answer explain why the error survived review? Does it explain why it appeared in this digest and not in last week’s? When the answer does not explain those things, it is a symptom wearing a cause’s clothes.
Walking the chain, one question at a time
Here is how the chain might look for the wrong-day correction, written the way an analyst would note it in a review.
- Why was the wrong day published? The writer copied it from a secondary summary rather than from the cause list itself.
- Why was a secondary summary used? It was open in another tab and the original listing needed a login that had timed out.
- Why did a timed-out login decide the source? Nothing in the digest routine says which document a date must come from, so convenience filled the gap.
- Why does the routine say nothing about sources? The intake template was built for headlines and has no field for the primary document.
- Why has nobody added the field? The template has no owner; everyone edits it, so nobody reviews it.
Notice where the chain ends. The fifth answer is not about the writer, the login, or the summary. It is about a shared template that nobody is responsible for. That is a fix you can schedule: name an owner, add a “primary document” field, and make the reviewer tick it. The first answer would only have produced a reminder to be careful.
Why this reads as a career skill
Hiring managers on legal-news and compliance-content teams rarely test for this directly, but they notice it in the first review you write. A junior who reports “the date was wrong” has described an event. A junior who reports “the date was wrong because our intake template has no source field, here is a one-line change” has described a system. The second report is cheaper for the editor to act on, and editors remember who made their work easier.
There are three habits worth building around the technique.
- Write each answer as a full sentence. “Human error” is a label; “the writer copied from a summary because the primary page needed a login” is a sentence you can challenge.
- Stop when the answer is a process, not a person. If your chain ends in somebody’s carelessness, you probably stopped one question early or two questions late.
- Attach one change to the last answer. A chain with no action is a diary entry.
A second example, closer to analysis than reporting
The same method works on analytical pieces. Imagine an explainer on a procedural change that drew reader complaints because it conflated two different stages of a case. The first answer is that the headline was too compressed. Why was it compressed? The desk templates cap headline length. Why does the cap exist? It was set for mobile cards years ago. Why has it never been revisited? Analytics for headline length are not part of any review. Why not? Because the dashboard only reports clicks, not corrections or reader complaints.
That chain ends at measurement, a very different place from the one the first answer pointed to, and it shows why people in this field are well served by curiosity about their own workflow. If you are building a portfolio, a short write-up of one such chain from your own coverage, with the identifying details removed, shows more about your judgment than a list of topics you have covered. For a feel of the material a legal-news desk handles, the daily roundup from one day’s list of notable Indian legal developments is a good case: each line there can only be as reliable as the intake step behind it.
Where a directory-style site fits into the picture
Teams sometimes use outside reference sites to orient themselves when a story brushes against another sector. For instance, a medical-tourism style directory covering hospitals and doctors, with blog, forum and procedure sections shows how a site can organise a very large subject into browsable categories. For a legal desk the takeaway is structural, not substantive: a clear category scheme makes it easier to see which document a statement belongs to.
Common ways the exercise goes wrong
Beginners with this technique often trip over the same few snags, and spotting them early spares everyone some tedious review sessions.
- Blame hiding in the grammar. “Why did the writer not check?” is a person question dressed up as a process question. Rephrase as “why did the routine not require a check?”
- Branching too early. Real incidents have several contributing causes. Pick the branch you can evidence, finish it, and then return to the others in a separate pass.
- Forcing five. The number is a guideline only. One chain may bottom out after three answers and another may run to seven, so judge it by whether the final answer names something your team can actually alter.
- Skipping the test at the end. After you propose the fix, ask whether it would have prevented the original error. If it would not, the chain has a wrong link.
Turning it into a repeatable review
You do not need a meeting for this. A shared note with four headings is enough: what we saw, the chain of answers, the single change, and the date we will check whether the change held. The last heading matters most, because corrections tend to drop off in the weeks after a fix, and a dated check is the cheapest guard against that. Keep each note to one page so that it actually gets read, and file them where new joiners will find them, since the archive of past chains doubles as onboarding material.
Over a year, a desk that keeps these notes builds a picture of where its weak spots cluster: templates, handoffs, login-dependent sources. That picture is the real prize, and it belongs to whoever kept asking why. In a field where credibility is the product, that is a skill worth practising on the next small correction rather than waiting for a large one.