A brilliant programme that nobody can describe clearly will lose the grant, miss the policy window, and confuse the community it serves. In development, communication is not a soft add-on — it is how evidence travels, how money moves, and how people are heard.

Across South Asia, development work runs on English — donor proposals, journal articles, MoUs, global conferences. It is the language that connects a field office in Bihar to a funder in Geneva. That gives English real reach — and real power.

The plain-language movement — from the UK's Plain English Campaign (founded 1979) to plain-writing laws in the US and international standards — holds a simple idea: a document works if its intended reader can find what they need, understand it, and use it, the first time.

Complex writing rarely signals a complex mind. It usually signals that the writer has not finished thinking. Clear writing is the final, hardest draft — not the first.

A useful target for professional writing: an average of 15–20 words a sentence. Not every sentence — an average. Mix short punchy lines with the occasional longer one for rhythm.

Passive voice is not a crime. Use it deliberately when the doer is unknown, unimportant, or obvious — or when you want to keep the focus on the thing acted upon.

Every sector grows its own jargon, and development has a famously thick one. Used inside the team, shorthand saves time. Used with a donor, a journalist or a community, it becomes a fog that hides meaning and excludes outsiders.

“The CSO submitted the DPR to the PMU for the WASH intervention under the CSR-funded SHG programme.” A reader outside your office is now completely lost.

Before writing a single line, name your reader. A donor, a village committee, a government officer and a journalist want different things from the same project — and reward completely different writing.

Tone is separate from formality. You can be formal and warm, or informal and cold. Development writing should usually be confident, honest and human — never boastful, never apologetic, never bureaucratic for its own sake.

Assume your reader is overworked and skim-reading on a phone between meetings. Front-load the point. Use headings. Keep paragraphs short. Make it scannable.

‘Disaggregated baseline’ is precise and welcome in a donor report; it is a wall in a village meeting. Audience does not just change your tone — it changes which words are clear and which exclude.

Even plain sentences fail if they arrive in the wrong order. How you sequence information decides whether a busy reader finds the point — or gives up looking for it.

A topic sentence opens each paragraph with its main idea; the rest of the paragraph supports it. A reader skimming only the first line of every paragraph should still follow your argument.

For many reports, the executive summary is the only part a senior reader opens. Write it last, but make it stand alone: the problem, what you did, what you found, what you recommend.

Good structure also links sentences. Each sentence should pick up a thread from the last — old information first, new information at the end. That ‘known → new’ flow is what makes prose feel smooth.

You will write more emails than reports in your career, and your reputation is built on them, one message at a time. A clear, courteous, well-structured email marks you as someone reliable to work with.

Good minutes are not a transcript. Capture decisions, actions and owners — who will do what, by when. Everything else is usually noise.

Short messages can read as curt. A single warm word — ‘Thanks!’, ‘Got it’, ‘Hope you're well’ — costs nothing and keeps a working relationship human, especially across cultures and languages.

Indian English is a legitimate, fully grown variety of English, with its own valid conventions — like American, British or Australian English. ‘Prepone’, ‘do the needful’, ‘kindly revert’ are perfectly correct in their context.

Articles are famously tricky if your first language has none. A quick guide: a/an for one of many (not yet known to the reader); the for a specific one the reader can identify; no article for general plurals and uncountables.

A policy brief is two to four pages aimed at a decision-maker who has minutes, not hours. It states a problem, gives the evidence, and recommends specific, feasible action.

A strong analytical paragraph has a simple engine: a topic sentence stating the point, evidence that supports it, and a takeaway that says why it matters.

Numbers do not speak for themselves; you translate them. The skill is to carry a statistic into a plain sentence that a non-specialist reader can picture — without distorting it.

When you describe a chart in text, do not narrate every number. State the pattern, then the most important point, then the exception if there is one.

Writing ‘47.3% of beneficiaries’ from a sample of 60 people pretends to a precision the data cannot support. The decimal is false precision — it misleads by looking exact.

Good data writing carries its own uncertainty. Qualifiers are not weakness — they are accuracy. They tell the reader how far to trust the number.

Numbers prove scale; stories create understanding. A single, well-told human story lets a reader feel why the work matters — and people act on what they feel. The best communication pairs the two.

Extractive storytelling takes a community's pain, packages it for distant audiences, and gives nothing back. Non-extractive practice shares power: people help shape how they are shown.

Communication is not only on the page. You will pitch to funders, brief officials, present at workshops and answer hard questions live. The same principles apply: know your audience, lead with the point, keep it plain.

An elevator pitch explains who you help, what you do and why it matters — in the time of a short lift ride. Prepare and practise it; the chance comes without warning.