Strota

A newsroom is a system, not a desk

Our starting point was Khabar Lahariya — a rural, women-led newsroom where Dalit women report on their own communities. Not representation, but ownership of narrative. What stayed with us from Writing With Fire wasn’t journalism, it was persistence: reporting in local languages, covering hyperlocal realities, navigating risk, caste and power.

A story breaks at 7:42 PM. A reporter sends a voice note. It gets forwarded, rewritten, verified, and by morning it is the newspaper in your hands. Every story moves across roles before it becomes public — through people, coordination, decisions and constant pressure. So what does a newsroom actually need to function, especially in the field?

Reporters, editors and bureau staff across The Times of India, Hindustan Times, NDTV, Deshabhimani and regional Marathi desks. We weren’t evaluating tools — we were watching how work happens under pressure.

A story begins as fragments. The challenge is not capturing data, it is making sense of it.

• Role & decision making

  01

  Who do you coordinate with? What can you decide independently?

• Workflow

  02

  Where does work slow down? What depends on informal systems?

• Data flow

  03

  How does information arrive? How much is usable vs fragmented?

• Field reality

  04

  Who knows where you are? What risks are managed individually?

• Systems vs workarounds

  05

  What continues to happen outside official tools?

Five whys

Field reporters resist adopting new newsroom technology, preferring informal but fragmented methods. Existing tools prioritise publishing, control and output management — they assume structured information already exists before it enters the system.

There is no structured layer between field input and publishing. Newsroom coordination depends more on human workarounds than on system intelligence.

Weak in the same five places

The research and the audit landed on the same weaknesses, independently.

• First signal

  No structured capture of what a reporter sees first

• Field to desk

  Coordination support is thin or absent

• Visibility

  Little real-time awareness across roles

• Safety

  Minimal risk-awareness layers

• Memory

  No institutional knowledge integration

Strota means flow

Information does not move in straight lines. It flows, branches and converges — like rivers meeting, multiple streams forming one direction. Strota is the bridge between field and desk, chaos and clarity, people and systems. It doesn’t replace the newsroom; it strengthens how it moves.

Role-based, but connected: each user sees what they need while staying part of the same flow. News doesn’t break in a CMS — it breaks in the field.

What the bureau chief sees

The field surface captures signals. The desk surface is where they become decisions. Four screens carry the bureau chief through a shift — what is happening now, what has just come in, how the desk is holding up, and who is answerable for it.

Each one answers a gap the research named. The intake queue gives a first signal somewhere to land instead of a group chat. The command centre makes the state of the newsroom visible rather than remembered. Roster control puts a name against who acts, and when.

Success is not faster publishing

Strota succeeds when coordination feels lighter, visibility feels clearer, and the newsroom no longer depends entirely on invisible human workarounds.

• Adoption above 70%

  01

  Within pilot teams, and without a mandate

• Signal to visibility

  02

  Measurably less time from first field signal to editorial sight

• Decision routing

  03

  Editors report clearer escalation paths

• Information loss

  04

  Fewer incidents of work lost between tools

• Support, not surveillance

  05

  The system is read as help, not monitoring

A five-person academic team project. Research and synthesis were done collectively; my own contribution was concentrated in interaction design and prototyping. Team: Arnav Chakravarty, Jahnvi Choudhary, Kush Bothra, Melvis Hilton and myself.