Define the Problem, Write the Programme

The myth says designers are struck by inspiration and the rest is just drawing it up. The reality is duller and far more powerful: design is an orderly, looping process you can name, learn and repeat. You define the real problem, then formulate a written programme, then develop a concept, then explore and assess several alternatives, then make a reasoned decision, then develop and refine it, then implement it on site, and finally re-evaluate the finished space - and where it falls short, you loop back.

Notice that the loop matters as much as the order. You might be halfway through developing a concept for a 2BHK in Pune when you discover the puja niche your client assumed can't share a wall with the toilet, and you swing back to redefine part of the problem. That isn't failure; it's the process working. The figure shows this arc as an ordered sequence with arrows that fold back - early stages feed the later ones, and late discoveries feed the early ones.

The value of naming the stages is that it stops you skipping the unglamorous front end. Most disasters on Indian sites - the wardrobe that blocks a window, the kitchen counter a 5-foot mother can't reach - trace back to a problem that was never properly defined.

A brief is what the client tells you they want. It is almost always vague, emotional and self-contradictory: "royal but minimal," "open kitchen but no cooking smells in the living room," "a guest room we'll rarely use but it must have a king bed." Briefs are wishes, and wishes don't dimension a drawing.

A programme is the disciplined document you write from that brief. It translates every wish into something testable: which activities happen here, who performs them, what furniture and storage each needs, how the spaces relate, the budget in ₹, the timeline, the site's real dimensions, and the codes and vastu rules that bind you. The figure shows the brief on one side - loose phrases and feelings - becoming the programme on the other - a structured list a builder and a quantity surveyor can both read.

The brief is the client's voice. The programme is the same content, disciplined into a form you can design against and, crucially, be held to. When the client later says "this doesn't feel royal," you return to the programme: what did we agree royal meant - in materials, in budget, in the entrance experience?

You don't receive a programme; you extract it by asking. With a joint family this is half the job. "Who actually cooks, and at what times?" reveals whether you need a second prep zone for the daughter-in-law's tiffins at 7 a.m. and the grandmother's slow lunch at 11. "Where do the children study, and who supervises?" tells you whether the dining table doubles as a homework desk. "How many people sleep here at Diwali?" sizes your living room for floor mattresses you'd never have planned for otherwise.

Good questions chase activities, not objects. A client says "I want a big sofa"; you ask what they do on it - watch TV as a family of six, nap, host relatives - and discover they actually need flexible seating for eight, not one large piece nobody can clean behind. You also chase the non-negotiables: the mother-in-law's puja must face east, the existing Godrej almirah is staying whatever you think of it, the budget genuinely stops at ₹8 lakh.

This interrogation is needs analysis - separating stated wants from real underlying needs. The royal-but-cheap client usually needs a sense of arrival and generosity, which you can deliver with one well-lit feature wall and honest materials, not gold leaf they can't afford.

Before you fall in love with any idea, the programme has to pass a feasibility test: does it fit the budget, the flat, and the rules? A double-height living room is a beautiful brief and an impossible programme in a standard apartment with a fixed slab above. An island kitchen needs roughly 1 metre of clearance on all sides - lovely in a villa, fantasy in a 900-square-foot 2BHK. Feasibility is where wishes meet plaster, and it's kinder to say no on paper than to demolish on site.

The cleanest way to hold all this is a programme matrix: every room or zone down the side, and its requirements across the top - activities, occupants, furniture, storage, services, and required area. The figure shows exactly this grid. Reading across the "kitchen" row, you see cooking and prep for two cooks, needing counter, hob, sink, tall unit, storage for provisions plus 20 steel vessels, services water, gas, exhaust, power, and an area of roughly 8 square metres.

Filled honestly, the matrix is a feasibility machine. Sum the required areas and compare them to your carpet area; if they don't fit, you negotiate now - combine the puja into a niche, make the study a fold-down desk - rather than discovering the shortfall when the furniture arrives.

Once the programme is agreed, you carve out the scope of work - the explicit boundary of what you will and won't do. This is what separates a professional from a friend with taste. "Full interiors for four rooms including civil, false ceiling, wardrobes, loose furniture and curtains; excluding the kitchen chimney and the modular fittings, which the client procures directly." Vague scope is how relationships and budgets both collapse.

The programme and scope together become your yardstick. Every later decision - this tile or that, one wardrobe or two, walnut veneer or laminate - is tested against them: does it serve a listed activity, stay inside the budget, respect the vastu line, fit the agreed scope? Decisions that pass are easy to defend; decisions that don't are how projects bloat by 40% and finish six months late.

This is why the unglamorous document is the most creative one you'll write. A clear programme doesn't cage your imagination - it tells you exactly which walls your imagination is allowed to push against, and gives you the confidence to push hard.