Planning guide / Singapore

How to Plan a Corporate Experience Centre, Innovation Lab or Visitor Briefing Centre

Someone has told you to build a space where the company shows what it does. Customers will come, partners will come, possibly ministers and delegations. You have a budget, a deadline, a sponsor with a strong opinion, and no obvious way to write the brief.

We build these rooms, in Singapore and abroad, across public security and defence, smart cities and mobility, and cybersecurity. Most of what follows is a mistake we have watched happen, usually more than once.

First principle

Start with the visit, not the room.

The most expensive error in this whole category is designing a room and only afterwards asking what happens inside it.

Before anyone draws anything, answer these.

  • Who actually comes? Not the aspiration, the real list, in order of frequency. Customers, prospects, partners, regulators, ministries, delegations, your own staff.
  • How many at a time? Six people and thirty people are different buildings.
  • How long do they stay? Twenty minutes between meetings is a different space from a half-day workshop.
  • What must they do afterwards? Approve a trial. Shortlist you. Sign something. Go home and describe you accurately to their own boss.
  • Who runs the visit? A dedicated host, a rotating sales team, or an engineer who does this twice a month and hates it. Design for whoever it actually is.

Put the answers on one page and make your sponsor sign it. Every later argument gets settled against that page.

One test is worth doing first: ask each stakeholder to describe a single visit out loud, start to finish. If three people describe three different visits, you do not have a design problem. You have a brief problem, and no drawing will fix it.

Three different animals

Which of these are you actually building?

Experience centre covers at least three different animals. They have different circulation, different content and different cost logic. Many organisations think they want the third and need the first.

01

The technology lab

Small. Built for a handful of high-value visitors. Live systems, real data, engineers in the room. Success is a technical conversation that goes deeper than a slide deck allows.

Circulation barely matters. Sightlines, somewhere to sit and argue, and kit that can be reconfigured without a contractor matter a great deal. This is the territory of innovation hub design in Singapore.

02

The briefing or consultative space

Medium. Built around a structured conversation with a customer or delegation: arrival, framing, demonstration, discussion, close.

This is where most corporate briefs actually land, and the one most often over-built into something grander and less useful. See executive briefing centre work.

03

The gallery

Large. Built for volume and for audiences you cannot pre-qualify: public safety briefings, national visits, mixed delegations, school groups.

Wayfinding, throughput and durability become real engineering problems, and the content has to work without a host, because sometimes there will not be one. See galleries and heritage exhibitions.

We build all three, and we will tell you plainly which one your visit list justifies. A gallery built for a handful of visitors a month is an expensive empty room. A lab asked to host a crowd is a fire safety conversation you did not plan for.

The rule

Consultative, not showcase.

A showcase space performs at visitors. Content plays, visitors watch, someone claps politely, everyone leaves. It photographs well. A consultative space is built around the conversation you need to have. That difference is physical, not philosophical.

  • Can people sit down? Standing keeps a visit short, which is right for a walkthrough and wrong for a decision.
  • Can your own team pull something up? If your engineer cannot get their own file onto the main screen in seconds, the room is fighting you.
  • Where does the group stand? A host at the front with visitors in rows produces a presentation. A screen people gather around produces a discussion.
  • Can it be reordered mid-visit? Real conversations skip. If the sequence only runs one way, you will steer visitors away from what they came to ask. This is what interactive content and interaction design is actually for.
  • Is there somewhere to close? A table, a quiet corner, a place to agree the next step before everyone reaches the lift lobby.

Design consultative spaces, not just showcase spaces.

Then check every drawing against it.

Content

Content is the project, not the decoration.

In technical sectors the content has to be understood before it can be designed. Not summarised. Understood.

The commonest failure in this category is putting content and build in separate hands. It looks sensible on a procurement sheet: the builder builds the room, an agency writes the content, an AV vendor supplies the screens. Then the content arrives late, does not fit the space it was written for, and the room gets furnished with whatever was ready.

Two consequences follow. First, content scope drives build scope: how many stories you tell, how deep each goes and how often each changes are what decide screen sizes, wall lengths and circulation, not the other way round. Second, somebody has to learn your subject. If the people designing the space cannot follow a conversation about your technology, they will design a beautiful container and you will spend the last month fixing what goes inside it.

We keep interior design and build, content development, and interaction planning under one roof for exactly this reason. When a buyer splits those three, they become the project manager by default, unpaid, and usually with the least time for it. The full argument sits on our page comparing design-and-build with design-only.

Constraints

Security and restricted environments.

Some of these spaces carry real constraints. Access control and visitor screening. Rules about what may be shown to whom. Secure and non-secure zones in one footprint. Equipment that cannot leave the room, or cannot be photographed in it.

Our domain experience runs across public security and defence, smart cities and mobility, and cybersecurity, and work in those sectors commonly sits inside confidential corporate and government sites that cannot be shown publicly. Not on this page, not in a pitch deck, not anywhere. Those credentials are presented privately in a qualified consultation.

Raise these constraints in the first conversation. They change the plan more than anything else here, and they are cheap to design for early and painful to retrofit.

After launch

Keeping it alive after launch.

The real failure mode is not a bad opening. It is a centre that is beautiful at launch and stale a year and a half later. Decide these before you build.

01

Who owns updates?

Name a person and put it in their objectives. Saying that marketing will handle it is not naming an owner.

02

What changes and what does not?

Your company story changes slowly; product detail changes fast. Build the slow things once and properly, and build the fast things so your own team can swap them in an afternoon without a contractor.

03

What is the refresh rhythm?

Put the first two review dates in the diary before the space opens.

04

Will the technology still be supported?

Choose for a supportable life, not for the launch photograph. Anything exotic becomes somebody's problem later.

Stakeholders

The sponsor who changes their mind.

Your sponsor will change their mind late. This is not bad behaviour. It is usually the first time they have seen the thing at real size, and their instinct is often right.

  • Get the sponsor into physical decisions early, with a mock-up, a walkthrough at scale or a sample wall. Opinions arrive when things become real, so make them real sooner.
  • Keep the signed visit brief in the room during reviews.
  • Say out loud which decisions are still reversible. Late changes to content are normal; late changes to services, power or structure are not.
  • Landlord approvals, fire and building submissions, and IT and security sign-off all take longer than anyone plans. Start them before the design feels finished.

Sequence

A realistic sequence, and what gets worse if you start late.

  1. Visit brief. Started late, everything downstream is guesswork.
  2. Content plan — stories, depth, sources, owners. Started late, this is the most reliable cause of a compromised opening.
  3. Spatial concept and zoning. Started late, content gets cut to fit a room sized before anyone knew what went in it.
  4. Technology and interaction design. Started late, screens become furniture and interactivity becomes a video.
  5. Detail design, approvals and procurement. Started late, this is where a fixed opening date starts eating quality.
  6. Build and installation.
  7. Content load, rehearsal and host training. Almost always squeezed. Protect it, because a room nobody has rehearsed in performs badly on day one.
  8. Opening, then the first scheduled review.

Cost drivers

What drives the cost.

We do not publish numbers, because a number without your brief is a guess that misleads you. What moves the figure:

  • Scale and audience volume, which drive circulation, services and durability
  • How much content is new rather than adapted from material you already own
  • How many things move, light up or respond, and how many of those are bespoke
  • Security and access requirements
  • Site conditions, landlord reinstatement obligations and approval routes, which sit alongside any commercial interior design and fit-out works
  • How compressed the programme is

Why take this from us

We have built these rooms at both ends of the scale.

Some briefs are about making a fixed budget go as far as it can, such as modernising a tired staff canteen for a younger workforce. Others are about changing what a space is: a technology lab for a handful of high-value visitors, a consultative briefing space, a full gallery for briefing on modern technology and public safety. Same team, same discipline. The same thinking runs through our exhibition and pavilion work.

It is not the scope of the project. It is the grit.

If you are holding one of these briefs and are not yet sure which animal it is, that is the conversation to have first. See everything we do under one roof, or read how the same content thinking applies to interactive content on an exhibition booth.

Frequently asked questions

Planning an experience centre: common questions.

What is the difference between an experience centre, an innovation lab and a briefing centre?

Mostly the visit, not the fit-out. A lab is built for a small number of high-value visitors having a technical conversation. A briefing centre is built around a structured conversation with a customer or delegation. A gallery or experience centre is built for volume and for audiences you cannot pre-qualify. Sizing the visit first tells you which one you need, and many organisations ask for the gallery when the lab is what their visitor list justifies.

What should we decide before we brief a designer?

Who actually visits, how many at a time, how long they stay, and what you need them to do or decide afterwards. Put it on one page and have your executive sponsor sign it. That page settles most of the arguments that arrive later.

Should the content and the build be handled by the same team?

In technical sectors, yes. The content has to be understood before it can be designed, and content scope is what determines build scope. When the two are split, content typically arrives late and does not fit the space it was written for. Studio Mojo runs interior design and build, content development, and interaction planning together for that reason.

How do we stop the space going stale?

Decide before you build what changes and what does not. Build the slow-changing company story once and properly. Build the fast-changing product detail so your own team can swap it in an afternoon without a contractor. Name one person who owns updates, and diarise the first two reviews before opening.

Can you work on sites with security and access restrictions?

Yes. Our domain experience runs across public security and defence, smart cities and mobility, and cybersecurity, where access control, secure and non-secure zones in one footprint, and restrictions on what may be shown to whom are normal. Much of that work sits inside confidential corporate and government sites and cannot be shown publicly, so those credentials are presented privately in a qualified consultation.

How long does an experience centre take?

It depends on content volume and approvals more than on build time. The stages that get compressed are content development at the start and rehearsal at the end, and both are the ones worth protecting.

Do you work outside Singapore?

Yes. Our work runs from Singapore to China to Oslo, including multi-company national pavilions.

Holding one of these briefs?

Start with the visit, and we will help you size the room.

Tell us who comes, how many at a time and what they need to decide afterwards, and we will come back with a practical first response.