Setting Up a Practice for XR

The first decision is the most important, and it is a decision to *narrow*, not to buy. Before any hardware, name the single use you will start with - and it should almost always be the one with the highest value at the lowest cost: client communication. Letting a client who cannot read drawings stand inside their future space, understand it instantly and commit with confidence is the use most likely to pay for itself, on the cheapest hardware, aimed at the oldest problem in the profession. Everything else waits.

Choosing one proven use does several good things at once. It lets you buy the least hardware that serves it - an affordable standalone headset, or even tablet AR - rather than an expensive general-purpose setup. It gives you a concrete, measurable goal (do clients understand and commit faster?) instead of a vague ambition to "do VR". And it keeps the effort small enough to actually happen: one workflow to learn, one kind of session to run, one skill to build, on one or two real projects.

This is the practical face of the whole course's discipline - make immersion earn its place. You are not adopting spatial computing as an identity; you are testing whether one specific use genuinely beats your current way of communicating design, on real jobs, at a cost you can see. A narrow start makes that test honest and cheap. A broad start - a lab, several devices, many hoped-for uses - makes it expensive and muddy, and is exactly why so many well-meaning "XR initiatives" quietly die.

Resist the pressure to be comprehensive. You do not need to cover VR and AR and MR, review and site and concept, all at once. You need one use that clearly helps, proven on real projects, before you add a second. In a cost-sensitive Indian practice this restraint is not timidity but wisdom: it puts scarce money and time exactly where the return is clearest - client understanding and buy-in - and refuses to spend on capability you have not yet shown you need. Begin with one proven use, and let the rest of this lesson build the workflow and the discipline around it.

With one use chosen, the work is to make it *repeatable*. A single lucky demo is not capability; capability is being able to do it reliably, quickly enough to be worth it, again and again. So build a standard workflow around your chosen use: a clean, repeatable path from your model to the headset (the pipeline from lesson 8.1), a set way to run the session, and a habit of updating the immersive copy when the design changes.

Concretely, that means settling a few things once. Agree how you export from your BIM or 3D tool - the format, units, origin and material handling - so it works the same way every time. Establish a light optimisation routine so a model becomes walkable without a day's fuss. Decide how a session runs: how you seat and brief the client, what navigation you use, what you are trying to learn from their reactions, how you capture their decisions and markup. Write it down. A documented, repeatable routine is what turns "we tried VR once" into "this is how we help clients understand a space".

Building skills matters as much as the workflow. Someone in the practice needs to become genuinely fluent - comfortable preparing a model, confident running a session, calm when the technology misbehaves in front of a client. That fluency comes only from doing it repeatedly on real, low-stakes jobs before it matters on a big one. Give one person ownership, let them practise, and let the routine mature. Better one person who can reliably deliver the chosen use than a whole studio that has each tried a headset once.

Keep the effort proportionate throughout. The point is a reliable, reasonably quick way to deliver one valuable use - not a virtuoso production for every project. If preparing a model for a session is taking a day, your optimisation routine is too heavy for the value; simplify it. The workflow should be as light as it can be while still doing the job well, because the lighter it is, the more often it will actually get used - and a capability that gets used is the only kind worth building.

Once you are putting a headset on other people - clients, colleagues, consultants - the boring logistics become a professional responsibility, and getting them wrong quietly kills adoption. Chief among them is hygiene. A headset presses against the face and is shared between people, so treat it like any shared personal equipment: wipe it down between users, keep hygiene wipes to hand, clean the lenses and straps, and use a wipeable or replaceable face pad. A client offered a visibly clean device relaxes; one handed a grubby, sweaty headset does not, and word spreads.

Shared-headset etiquette matters too, because a single device is usually passed around. Have one person act as host: they set up the device, guide each first-time user through putting it on and adjusting it, stay alongside to reassure and prevent stumbles, and hand over cleanly to the next person. First-time users are often disoriented for the first few seconds - the host's calm presence is what turns nervousness into delight.

Then the comfort and safety logistics the course has stressed throughout. Keep sessions short - a few focused minutes, not a marathon - because no headset is comfortable for long and fatigue sets in fast. Offer a seated review as the default; it is comfortable, safe and perfectly good for most design communication. Clear the physical space of trip hazards, especially for standing use. Give every user an easy, obvious way to stop and take the device off, and never push someone who feels queasy - some people get motion-sick regardless, and pressing them is both unkind and reputationally costly. Follow the manufacturer's guidance on safe use, session length and age.

Finally, the mundane upkeep: keep the device charged, updated and stored safely, so it is ready when a client meeting comes, not flat in a drawer. None of this is glamorous, and none of it appears in the hype, but it is exactly what separates a practice that reliably delivers immersive sessions from one whose headset gathers dust after an awkward first attempt. Professional logistics are how the capability survives contact with real clients - and how it keeps earning the trust that makes it worth having.

Growth should be earned, one step at a time, not planned as a grand rollout. Once your one proven use is genuinely working - clients understand faster, decisions come sooner, expensive late changes drop - you have evidence, not just enthusiasm. Only then consider a next step, and choose it the same disciplined way: name a specific new use, ask whether immersion clearly beats your current approach for it, buy the least additional capability it needs, prove it on real jobs, and keep it only if it keeps paying. Each expansion faces the same test the first one did.

That test naturally paces your growth. Maybe the next step is a second headset so two clients can review together, or adding tablet AR for on-site checks, or investing in richer real-time review for a particular project type - but each is added because a real, repeated need has shown up, not because a roadmap said "scale up". Capability that grows this way is capability that gets used; capability bought ahead of proven need becomes the shelf of idle devices that gives spatial computing its bad name.

Be equally willing to stop. If a use is not earning its keep - the sessions are not changing outcomes, the effort outweighs the value, clients are lukewarm - it is not a failure to set it aside. Making immersion earn its place cuts both ways: you keep what pays and drop what does not, without sentiment about the technology. A practice that prunes honestly stays lean and credible; one that keeps buying and using immersive tools out of identity, not value, wastes money and slowly loses trust.

This is the whole module, and much of the whole course, in one habit. Spatial computing enters a practice well not through a lab or a grand strategy but through disciplined increments: start with one proven, high-value use on the cheapest hardware that serves it; build a light, repeatable workflow and real skills; run it professionally, hygiene and comfort and all; prove it on real jobs; and scale only where, and only as fast as, it keeps earning its place - always remembering that the immersive model is a tool for seeing and communicating, never a source of truth, with binding dimensions, decisions and setting-out kept to the verified model, the specialists and the codes. Start small, make it earn its keep, and let value, not hype, decide every step.