Nirmana
"nirmana" means creation.
Design is the deliberate synthesis of form and function to satisfy human needs and desires. At the level of Nirmana, that definition is necessary but not sufficient. Here, design is also the disclosure of a way of being in the world, the moment when an object, a space, or a system stops being merely useful and becomes a clearing through which relationships, values, and contradictions are made visible. It is the act that refuses to pretend the shaping of things is separate from the shaping of the people who make them.
Nirmana, researching the art and science of design.
The assignment asks for a tangible response to a real human problem. That framing is designed to sound simple. Observe a pain point. Identify a user. Map a system. Prototype an intervention. Present a result. Document the journey.
The first instinct followed that route with some sincerity. Campus services, wayfinding, administrative communication, local friction points, all the obvious candidates appeared on the post-it wall. They could have become competent projects. They would also have remained interchangeable with a hundred other well behaved design school submissions, careful, tidy, and finally without consequences.
The break came early and kept deepening. Every time the inquiry tried to settle on a surface problem, on a confusing sign or an awkward service flow, the conversation underneath it slid toward the people producing those designed things. Designers would begin talking, and within three sentences, the subject was no longer the poster or the product. It was the studio. The billable hour. The identity erosion. The exhaustion dressed up as commitment.
The real human problem kept rerouting itself to the people who were meant to be solving everyone else's problems.
That was the crack. Nirmana is what happened when the project decided to go through it rather than paper over it with something more photogenic.
The first answer to the central question begins here. What must become true for early career designers to sustain craft, agency, and sanity inside the systems we have inherited? First, the problem must be named correctly. The problem is not simply burnout. The problem is that the operating conditions of design practice were never deliberately designed. They were inherited, and then mistaken for nature.
From a distance, the precarity of the creative industries looks like a policy issue, something you put in a white paper with charts and call structural. From inside the room, it is granular, repetitive, and humiliatingly ordinary.
These are not decorative complaints inserted to make a case study feel human. They are evidence. They reveal a profession that speaks publicly in the language of empathy, innovation, and positive human impact while quietly organising itself around opacity, extraction, and the quiet consumption of the people inside it.
The ghost in the room is not overwork in isolation. It is misrecognition. Designers are trained to diagnose friction everywhere except in the economic and institutional conditions of their own labour. They can critique the interface, the exhibition graphic, the service blueprint, the chair, the packaging, and the algorithm. They cannot always name the billable hour as a design decision, or the absence of role clarity as a system failure, or the shared drive full of documents titled final final1 final FINAL use this one.docx as evidence that version control was never taught because chaos was never identified as a problem worth solving.
The second answer follows directly. For designers to sustain craft and agency, their operational pain must stop being treated as personal weakness or professional immaturity. It must be treated as design evidence, pointing to a system that no one designed and everyone inherited.
This project calls that condition the ghost space.
The ghost space is the gap between how design practice describes itself and how it actually runs. Outwardly, the field speaks about human centeredness, imagination, systems thinking, aesthetics, and transformative impact. Internally, it often runs on inherited consulting logic, opaque financial structures, positional hierarchy dressed as creative hierarchy, heroic overwork romanticised as passion, and a strange moral attachment to disorganisation as evidence of authenticity.
The contradiction is precise. A studio can produce a beautiful and rigorous identity system for a client and still have no clear model for how knowledge is transferred between its own members. A school can teach design thinking as a universal method for solving complex problems and still graduate students who do not understand how a studio earns money, scopes labour, preserves craft across personnel changes, or avoids cannibalising itself on the next pitch. A team can speak about radical collaboration while remaining structurally dependent on the exhaustion of its most committed people.
The ghost space is therefore not a poetic image deployed after the fact. It is the root cause diagnosis, arrived at through observation and not through theory alone. The underlying system failure is precise, and it is this, design studios and design schools do not design their own operations with the same rigor they apply to client work. They copy pedagogical models from Bauhaus and Ulm. They copy economic models from legal and management consulting. They copy operational mythology from startups. None of it was designed as a coherent system. It accreted. Then it calcified. Then it was named culture.
The third answer is this. For early career designers to sustain sanity, the ghost space must become visible enough to be redesigned, which means it must first become nameable.
Criticism that stops at naming the problem without explaining its origin is indistinguishable from complaint. A serious critique has to explain not only that the current models are bad, but why they became dominant, why they looked efficient when they were adopted, and why they now feel simultaneously powerful and exhausted. That requires engaging with entropy and atrophication as structural phenomena, not only as metaphors.
Every system that becomes highly efficient around one set of constraints eventually begins to atrophy under another. What first appears as rigor becomes ritual. What begins as productive clarity hardens into doctrine. What once reduced friction starts producing new kinds of friction because the system keeps solving its original problem with increasing discipline while the surrounding conditions have already moved on.
The billable hour was not adopted because everyone in the creative industries was naive. It spread because it solved a real problem. It translated invisible creative labour into units legible to clients, accountants, lawyers, and project managers. It made uncertainty manageable. It created a commercial language between the designer who thinks in atmospheres and the client who thinks in deliverables. The consultation model did not win by being wrong. It won because it created administrative confidence at a moment when the creative sector needed institutional credibility to survive.
The problem is not that the model was wrong when adopted. The problem is that administrative legibility and creative truthfulness are not the same thing, and optimising relentlessly for the first eventually destroys the second.
The same logic applies to design schools. They did not become formal, staged, and increasingly addicted to process diagrams out of pure cowardice or bureaucratic instinct. They did so because institutions need to grade, compare, scale, and justify. Once design entered the academy, the invisible judgment at its core had to be translated into visible criteria. The result was pedagogy that often rewards the performance of process over the presence of operational literacy, and that trains students to design for critique rooms rather than for the real conditions they will encounter on the other side of graduation.
So the project does not merely attack efficiency. It asks the harder and more dangerous question. When does a system's management of entropy become the new source of atrophication, and when does the mechanism designed to preserve life become the primary cause of its slow consumption?
The fourth answer is that for early career designers to sustain craft, they must understand not only that the current system hurts, but why it once looked rational. Without that, every attempt at reform repeats the original mistake at one level of abstraction higher.
One of the most revealing fault lines in contemporary design education is the field's unresolved and mostly undiscussed relationship with art.
Design narrates itself as practical, purposeful, user focused, and analytically grounded. Art is cast as expressive, interpretive, subjective, and culturally unbounded. The distinction is professionally useful and philosophically thin.
The deeper reality is more uncomfortable. Many of the world's leading design schools still award art degrees. The Royal College of Art. Central Saint Martins. Rhode Island School of Design. California Institute of the Arts. This is not a bureaucratic leftover waiting to be corrected. It is a clue about what the field actually knows about itself.
Modern design professionalised itself by distancing itself from art. Bauhaus, Ulm, Swiss modernism, and later the corporate design cultures of Braun, IBM, and Apple all needed to argue that design was not bohemian expression but a disciplined mediator between human needs and industrial life. That move brought legitimacy, scale, and commercial power. It also required a sustained fiction, that design had evacuated subjectivity and installed objectivity in its place.
But the degree title remained an art degree in many places because the field could never fully sever its dependence on aesthetic judgment, historical literacy, cultural positioning, and the kind of interpretive thinking that cannot be reduced to engineering or process alone. Design may solve problems, but it solves them through acts of judgment that require a long and cultivated relationship with meaning, taste, and consequence.
This matters not as institutional gossip but as epistemological evidence. The reason design schools lean into structure and rationalism is that they needed credibility with industry. The reason they retained the language and degree structure of art is that they could not actually do without the deeper domain of judgment, sensibility, and meaning that art school culture preserves, often poorly but always stubbornly.
To critique the present models honestly, you have to study the reasons they became persuasive. The art degree is embarrassing to design's rationalist self-image because it tells the truth that rationalism could not afford to say out loud. The field depends on forms of knowledge that cannot be fully methodologised.
The same contradiction lives inside every design student. A designer is taught to serve communication but also to cultivate sensibility. To solve but also to see. To function but also to signify. Nirmana does not resolve this by choosing one side over the other. It uses the tension. Design is not lesser art and not disguised engineering. It is the field where intention, consequence, and meaning are forced into coexistence, and where the failure to hold all three at once produces the ghost space described above.
The fifth answer is that for early career designers to sustain agency, historical and philosophical literacy must be treated as survival equipment, not as cultural decoration appended after the real training is done.
There is a Derridean thread running underneath the entire project. It is not name dropping. It is operating logic.
Derrida's concept of the trace argues that every system stabilises itself by suppressing alternatives it still depends upon. The coherent structure is never fully coherent. It contains, at its foundations, the very instabilities it was designed to exclude, and those instabilities remain present as suppressed traces that shape the system from underneath.
Design practice is saturated with these suppressed traces. The polished deck suppresses the twenty failed iterations that preceded it. The smooth final deliverable suppresses the version confusion, the invisible unpaid overtime, the panic that was resolved by one person absorbing more than their share of the crisis. The agency homepage suppresses the economic structure that determines which clients get taken, which designers get promoted, and which work never gets made because no one could figure out how to bill for it.
The trace is not recoverable through nostalgia. It is visible through attention to what the official story cannot account for, the remainders, the excesses, the places where the clean narrative breaks down under pressure.
Entropy enters here not as mere physical decline but as philosophical leakage. Systems do not only decay because materials wear out or energy disperses. They decay because the contradictions they contain become increasingly difficult to manage as the gap between the official description and the actual operation widens. At a certain point, maintaining the fiction costs more than abandoning it would.
Design as entropy means this. All designed orders are temporary victories over disorder. Every victory generates new residues. A system begins by reducing chaos and in doing so creates new forms of rigidity that eventually become the next generation's chaos. The Double Diamond was once a liberating observation about how designers actually work. By the time it became a mandatory submission format it had completed its transformation from description into doctrine.
That is precisely why Nirmana cannot present itself as a final answer. The moment a model believes it has escaped history it begins to calcify. The moment a toolkit assumes permanence it begins to lie. The designed obsolescence is not a rhetorical gesture. It is the minimum intellectual honesty the project can afford.
The project did not arrive at its current form by moving cleanly through phases. It moved through wrong directions that left residues worth preserving.
The first branch obeyed the assignment. Fix a local service. Improve a communication system. Redesign a campus touchpoint. These concepts were plausible, well behaved, and finally inert. They solved symptoms while leaving the conditions that produced those symptoms entirely intact. They would have satisfied the rubric and left the ghost space undisturbed.
They were abandoned.
The second branch turned meta. Design thinking as the subject of design thinking. The Double Diamond as the object of its own methodology. IDEO, Stanford, the whole process industry applied to itself. The critique sharpened. A methodology obsessed with user-centredness had never seriously user-tested itself. It was designed by a specific group, largely Western, educated, professionally design-literate, for a specific commercial context, innovation consulting and corporate transformation, and then sold as a universal grammar for human problem solving.
The aporia that emerged was real. Design thinking claims universal applicability. It has never applied itself to the conditions of design practice. Applying it reveals that the methodology calcifies anything it touches, including itself. The alternatives offered, rhizomatic thinking, Japanese Metabolism, Eastern apprenticeship, Deleuzian logic, are themselves arborescent at root. The rebellion was shaped by the structure it was rebelling against. You cannot escape the tree by growing a new branch.
But the critique alone was still insufficient. An argument without an operational answer is just another elegantly articulated ghost space.
The third branch, the one that held, came through a more brutal question. If a small design studio had to be designed as a system from scratch, not branded, not positioned, but actually designed, what would need to exist so that burnout became structurally harder and craft preservation structurally easier? What would the building do? What would the economic model do? What would the first week protocol do?
That question changed the project from theoretical analysis into operational design. And with it came the word gharana, not as a brand, but as a structural concept.
The synthesis between domains cannot be hand wavy. If it is, it proves the very accusation design is trying to escape, that it borrows freely from other fields without the rigor to earn the loan. The three operational models below are specific, examined, and argued on their own terms.
Hospitality is not a metaphor for warmth or a stand-in for human-centred thinking. It is a service sector that evolved under conditions of extreme variability, time pressure, and coordinated specialisation, and it solved operational problems that design has mostly refused to confront.
The brigade system developed in the professional kitchen is the relevant structure. It emerged not from philosophy but from necessity. When Escoffier formalised it in the late nineteenth century, the problem was real, how to coordinate multiple specialists producing differentiated outputs under extreme time pressure, in a space where a single breakdown in sequencing collapses the entire system. The solution was role clarity, preparation before service, visible sequencing, and quality control embedded in the process rather than applied at the end.
Mise en place, the discipline of preparation before action, is the heart of it. Work is staged before it is performed. The kitchen operates on prepared conditions, not improvised ones. Creativity within the service moment is made possible precisely because the conditions for it were designed in advance.
The consultation model in design does almost the opposite. It celebrates strategic ambiguity during the process, hides labour behind polished narratives after the fact, and often treats operational disorder as evidence of creative seriousness. Hospitality evolved toward consistent service through disciplined preparation. The consultation model often evolved toward persuasive presentation through legible billing, leaving the conditions of actual work permanently under-designed.
The lesson is precise. Preparation is not the enemy of creativity. It is the condition that makes creativity reproducible.
Computer science and systems architecture offer a second operational model, one that is even closer to home given design's self-identification as systems thinking.
In software engineering, a well-designed system is not treated as the frozen genius of its creator. It is documented for understandability, built for iteration, controlled through versioning, and structured to reduce redundancy. The assumption is not that perfect code will be written once and preserved. The assumption is that systems will need to change, and therefore the process of change must itself be designed. Infrastructure as code, version control, documented architecture decisions, reproducible environments, these are not bureaucratic overhead. They are the conditions under which complex systems can remain alive rather than becoming monuments.
The contrast with design education is almost comical in its clarity. Design students work in a culture of final final1 final FINAL use this one.psd. The naming convention is a joke because it is accurate. There is no operational language in most studio pedagogy for version control, because versioning was never framed as a design problem. The final artifact is treated as the only thing worth caring about, while the process architecture remains fragile, private, undocumented, and impossible to hand off.
If design wants to claim the language of systems thinking, its own practice must become legible, versioned, and reproducible without destroying authorship. Systems architecture already knows how to do this. Design has largely declined to learn from it.
The third model is apprenticeship, but not in the form in which design discourse has most often borrowed it, as an aestheticised reference to Japanese craft culture deployed to justify slowness, restraint, and the romance of mastery.
Craft apprenticeship across Japan, Korea, Southeast Asia, and India is structurally important, not atmospherically important. In Japan, the shokunin model involves years of observation before independent production, transmission of tacit knowledge through proximity rather than instruction, and a relationship between master and apprentice defined by duration, trust, and the understanding that certain kinds of knowing cannot be transferred through documentation alone. In Korea, the idol training system, whatever its industrial pathologies, preserves the underlying logic of staged mastery, disciplined repetition, and role formation through sustained practice rather than credentialled certification. Across Southeast Asia, traditional craft systems in textiles, ceramics, metalwork, and performance arts have sustained transmission through lineage rather than curriculum.
In India, the traditional craftsman and apprentice relationship operates along similar principles. In Jaipur, craft workshops in block printing, gem cutting, miniature painting, and stone carving transmitted knowledge through proximity, correction, and the graduated assignment of responsibility rather than through formal instruction. The Nirmana project draws from this directly. Not as nostalgia. As evidence that a different epistemology of design knowledge exists and has always existed, one where learning is embodied, relational, and intergenerational.
The gharana, the concept that finally named this project, belongs to Hindustani classical music, but the underlying logic is the same. A gharana is not a building or a curriculum. It is a lineage that survives through living contact. It is defined not by what it teaches but by how knowledge travels between bodies, across generations, under pressure. Jaipur gharana. Gwalior gharana. Not schools. Living systems of transmission.
Nirmana is the attempt to ask what this structure makes possible for design practice, and whether it can be built without calcifying into another orthodoxy.
This project does not emerge from a generalised London design school context. It emerges from Hult International Business School, a practically focused, internationally constituted, triple crown accredited business school, and from the deliberate declaration of design as a major within that environment.
That institutional specificity matters and should not be softened.
Nirmana is in part a statement piece. It argues that design inside a practically focused business school does not need to shrink itself into soft innovation language, service design frameworks, or the performance of creativity on behalf of corporate strategy. It can become a serious, intellectually rigorous, materially aware design essay and project ecology that speaks in the same register as work produced at RCA, RISD, or UAL, while coming from a context shaped by international commercial reality rather than fine art lineage.
The tension this creates is generative rather than embarrassing. A business school demands viability, feasibility, stakeholder clarity, and evidence of systemic thinking. Design demands form, judgment, atmosphere, consequence, and the kind of meaning that does not reduce to market logic. Nirmana is strongest when it refuses the false choice between those demands and insists that a serious design proposition must satisfy both, not by compromising between them but by holding them in productive contradiction.
This project is also the declaration. To study design at Hult, as a major, with this as the statement piece, is to argue that the field is serious enough to belong in a business school without becoming a servant to business school orthodoxies.
The eighth answer is this. For early career designers to sustain agency, institutions must allow design to be both intellectually rigorous and operationally serious, rather than compelling it to choose between the language of creativity and the language of commercial value.
The response Nirmana proposes is not a single designed object. It is a triptych of entangled artefacts that approach the same operational question from different registers and at different scales.
The microsite is the outward facing threshold. This is where the quality of the argument must be legible before the argument is read. A stranger who lands there should be asking who made this within forty-five seconds, not as a reaction to visual novelty but as a recognition of sustained intelligence. The microsite functions across three planes. Practice, as the diagnostic toolkit where designers map their own conditions. Space, as the window into the spatial prototype where architecture becomes an operational variable. School, as the gharana, the living lineage, open source and forkable.
Toolkit depth and card system, extended section to be inserted from master archive.
The spatial prototype translates the logic of the microsite into built form. Using Snaptrude, the project develops a specific studio building where thresholds enforce deliberate transition, where mise en practice zones precede creative production zones, where an archive spine and trace walls give the studio institutional memory independent of any individual, and where gharana rooms create spatial conditions for the kind of conversation that cannot be scheduled but must be possible. This is not architecture as metaphor. It is an argument that space is an operational variable, and that any serious attempt to redesign practice conditions must eventually become architectural.
Architectural documentation and Snaptrude material, extended section to be inserted from master archive.
The school of thought is the close-off. It is the least photogenic and most durable element. For Nirmana to function as a gharana rather than a project, it needs a question it refuses to stop asking, a diagnostic language that others can use, falsifiable principles that can be tested in practice, a visible lineage, and a built-in admission that it too will calcify. All five are present. The question is whether the operational conditions of design practice can be designed to make burnout structurally harder and craft structurally more survivable. The diagnostic language is the toolkit. The falsifiable principles include claims such as operational literacy increases tolerance for creative ambiguity, prepared conditions make deep work more likely than romantic chaos, and economic clarity reduces burnout risk. The lineage runs from Jaipur craft through Bauhaus and Ulm, through Rams and Norman, through Deleuze and Guattari, through Yanagi and Korean and Japanese and Indian apprenticeship traditions, through DevOps and infrastructure as code. The admission of obsolescence is built into the founding document.
The project began with one line that had to be earned rather than asserted.
What must become true for early career designers to sustain craft, agency, and sanity inside the systems we have inherited?
The answer is now available and can be stated precisely.
Early career designers sustain craft only when craft is protected by structures of preparation, transmission, and time that are external to individual willpower. Craft cannot survive on the strength of personal commitment alone inside systems that were designed to extract that commitment without replenishing it. The preparation protocols of the brigade system, the transmission logic of the apprenticeship tradition, the version control discipline of systems architecture, all point toward the same structural requirement. Conditions must be designed before creative work begins, not improvised during it.
Early career designers sustain agency only when the systems surrounding them become legible enough to question, document, and redesign. Money, roles, time, authorship, expectations, and power relations cannot remain hidden inside charisma, hierarchy, and the studied informality of studio culture. Operational literacy is not administrative tedium. It is the minimum condition for having any genuine agency over the work and the life that produces it.
Early career designers sustain sanity only when institutions stop framing exhaustion as the admission price of seriousness, and start treating the operational design of work as part of the work itself. Burnout is not individual failure. It is an epistemological failure, the failure to apply design thinking to the act of designing.
In practical terms, six specific conditions must become true.
Design schools must teach operational literacy as craft, not as administrative supplement.
Studios must document how they function with the same seriousness they apply to client deliverables.
The billable hour must be recognised as one model among many, not as neutral infrastructure, with its trade-offs made explicit rather than inherited without examination.
Apprenticeship, lineage, and intergenerational transmission must be rebuilt in forms appropriate to contemporary practice, which means learning from hospitality, systems architecture, and craft traditions outside the Western design mainstream.
The spaces where design work happens must be designed as instruments of attention, preparation, and transmission, not as neutral containers filled with laptops and aspirational posters.
Every model, including Nirmana, must admit entropy in advance and remain open to revision, forking, and the honest possibility that the next generation will critique it as harshly as it critiques what came before.
Those are not aspirations. They are the minimum structural conditions for a different kind of practice. Nirmana is the designed attempt to make at least some of them more real.
Underneath all the operational language sits an older motive. People do not enter design because they read a market opportunity report. They enter because they are pulled toward truth, toward goodness, toward beauty, and because design is one of the few fields that demands all three be held simultaneously, in tension, and in public.
Truth is seeing clearly what is actually happening. Not what institutions say is happening, not what the brand narrative describes, but what is visible when the polished surface is treated as a trace rather than a conclusion. For Nirmana, truth means naming ghost spaces as designed absences, being honest about economics and power as design variables, and refusing to let systemic problems be diagnosed as personal failures.
Goodness is designing conditions that reduce harm and increase dignity. Treating designer sustainability not as an afterthought to the real work but as integral to what serious design actually means. Recognising that a field cannot produce work that serves human flourishing while consuming the humans inside it without eventually collapsing into bad faith.
Beauty is insisting that the artefacts about practice are themselves carefully made. The microsite, the film, the cards, the architectural proposal, all of it must be held to the same standard as any client work, not because aesthetics are decorative but because form is an argument. Careless form says the content is not serious. Careful form says the content is serious enough to be embodied.
Design education has a persistent tendency to translate these motives into more manageable names. Value. Outcome. Delivery. Efficiency. The translation is not dishonest, but it is incomplete, and the incompleteness accumulates over a career until the original motive is no longer recognisable in the daily work.
Nirmana returns the transcendentals to operational life. Not as philosophical decoration. As the only honest reason to redesign the conditions of design practice in the first place.
Nirmana is specific on purpose.
It emerges from Jaipur craft and hospitality culture, where service, space, and survival were already being designed together without using that vocabulary. It emerges from Hult International Business School, where the declaration of design as a major required a statement piece serious enough to make the declaration unavoidable. It emerges from self-taught graphic and interaction work accumulated alongside rather than inside formal studio training, which means it carries the outsider's position not as a limitation but as a methodology.
It does not pretend to be a universal model. That would repeat the exact mistake it critiques.
Gharanas do not scale. They transmit. Nirmana is one gharana among many that could exist, a small lineage of people who believe design is not finished when the object ships or the service launches or the brief is signed off, but when the people who made it can keep making without burning out, selling out, or gradually becoming unrecognisable to themselves.
A thing is what it is, and also what it is not yet.
Nirmana, creation, is not a finished system. It is an attempt to design the conditions under which better attempts can keep appearing. The reader who arrives here and finds something worth arguing with has already made the gharana real.