Activity-based working changes a familiar promise: the desk is no longer a permanent possession. That can be a better workplace when the settings are useful and the rules are fair. It becomes a source of anxiety when the organisation cuts seats before it explains the operating model.
For a Pune or Mumbai project, the useful question is not whether a design looks current. It is whether the brief, building, services, procurement and operating rules agree. The following framework is written for decision-makers who need a workplace that can be priced, built, occupied and maintained.
Explain the reason in plain language
Employees need to know what is changing, why it is changing and what will be available on day one. 'Modern workplace' is not an explanation. Say whether the driver is growth, consolidation, hybrid attendance, collaboration, cost, a new operating model or a combination. Leaders should use the same words throughout.
Do not promise that everyone will love the change. Promise a process for listening, testing and correcting. Credibility is built when difficult trade-offs are acknowledged rather than hidden behind a launch slogan.
Use data without pretending it is perfect
Measure attendance, peak occupancy, meeting demand, team patterns and storage needs where possible. State the period, method and limitations. A two-week observation can inform a decision, but it is not a universal truth about every season or team.
Share the findings in a way people can understand. Show the choices they influence: number of settings, neighbourhood size, lockers, meeting rooms and buffer. Evidence does not remove disagreement, but it gives disagreement something more useful than rumour.
Design neighbourhoods people recognise
People may not own a desk, but teams still need identity, proximity and a place to start the day. Create home neighbourhoods with nearby shared workpoints, project areas, lockers and support spaces. Let teams understand how visitors, new joiners and cross-functional work fit into the plan.
Avoid turning neighbourhoods into hidden assigned desks. The operating rule should be clear. A person can belong to a team area and still choose the setting that suits the work. That is the distinction between a usable ABW model and an unlabelled desk shortage.
Write the rules before move-in
Cover booking, clean desk, lockers, personal equipment, quiet areas, calls, food, visitors, accessibility, managers' spaces and exceptions. Use examples. A rule that says 'be considerate' is a good value and a poor operating instruction.
Give people one place to find the rules and one route to ask questions. Test the rules with representative users. If a rule depends on a technology function that is not reliable, fix the technology or change the rule before launch.
Pilot with a real team
Choose a pilot that reflects the complexity of the rollout. Give it enough time to reveal busy days, room shortages, storage problems and behaviour changes. Track what happened and what people did, not only what they said in a launch survey.
Make changes after the pilot visible. People are more willing to participate when they can see that feedback altered lockers, room settings, signage or booking rules. A pilot is not a public-relations event. It is a controlled learning period.
Keep the workplace alive after launch
The first week is not the finish line. Review utilisation, room bookings, support tickets, complaints, accessibility feedback and team experience after the move. Look for patterns rather than reacting to the loudest single comment.
Connect the review to the physical project. Vektor Spaces' workplace strategy articles and process show why design and operation belong together. If a setting fails its purpose, adjust the space, the rule or the support model rather than blaming the user.
Before approval, ask three plain questions. What is known from the site or the client? What is still an assumption? What will prove the decision worked after installation? Put the answers beside the relevant drawing, schedule or source. This keeps the conversation honest when the project moves from strategy to design, from design to procurement and from procurement to handover.
A decision checklist for the project meeting
Use this checklist to turn the article into a controlled next step. It is intentionally practical: each item should have a named owner, a source or drawing, a decision date and a test that another person can verify. If an item is still an assumption, label it as one. That is not a weakness. It is a warning before the assumption reaches procurement or site work.
- Explain the reason in plain language: define the owner, evidence, decision date and acceptance test before the drawing or order is released.
- Use data without pretending it is perfect: define the owner, evidence, decision date and acceptance test before the drawing or order is released.
- Design neighbourhoods people recognise: define the owner, evidence, decision date and acceptance test before the drawing or order is released.
- Write the rules before move-in: define the owner, evidence, decision date and acceptance test before the drawing or order is released.
- Pilot with a real team: define the owner, evidence, decision date and acceptance test before the drawing or order is released.
- Keep the workplace alive after launch: define the owner, evidence, decision date and acceptance test before the drawing or order is released.
For a live project, carry the open questions into the brief, cost plan, programme and handover record. The team should be able to tell what is confirmed, what is provisional, what is excluded and what will be checked after installation. That discipline is more valuable than adding another adjective to the design description.
Decision matrix for this project
This guide is most useful when it becomes a project control. Use the table below to assign an owner, retain the evidence and define what will count as done. It keeps a design conversation connected to procurement, site work and handover.
| Decision area | Question to answer | Evidence to retain |
|---|---|---|
| Reason | Why is the operating model changing? | Plain-language case from leadership |
| Evidence | What attendance and work patterns inform the settings? | Measurement period, method and limitations |
| Neighbourhoods | How will teams retain identity without owned desks? | Home zones, lockers and settings plan |
| Launch | How will the pilot expose and fix friction? | User feedback, support data and change log |
Implementation checklist
Before releasing the next drawing, order or site instruction, check each of these items. A useful checklist does not replace judgement. It makes the judgement visible to the people who must approve, build and operate the workplace.
- Reason: record the decision owner, evidence source, decision date and acceptance test.
- Evidence: record the decision owner, evidence source, decision date and acceptance test.
- Neighbourhoods: record the decision owner, evidence source, decision date and acceptance test.
- Launch: record the decision owner, evidence source, decision date and acceptance test.
Questions decision-makers ask
The central decision is introducing activity-based working with evidence, neighbourhoods, clear rules, a pilot and a review after move-in. Keep that decision visible in the brief so layout, procurement and delivery choices can be tested against it.
Confirm the evidence listed in the decision matrix: the scope, responsible owner, relevant drawings or records, and the date when the decision will be accepted. Mark assumptions instead of treating them as facts.
Coordinate it before procurement and before ceilings, partitions or services are closed. Late coordination usually turns a design question into a variation, rework or an operational compromise.
Share the evidence and proposed settings with a representative pilot group before finalising desk ratios, lockers or booking rules. The useful next step is a controlled review with a named owner, an agreed evidence source and a simple acceptance test.
Sources and scope note
This article uses the official and professional reference pages below for the limited points they publish. Recommendations about layout, procurement and delivery are Vektor Spaces' practical project guidance, not a claim that a rating, code approval or performance outcome has been achieved. Confirm the current requirements with the appointed consultants, landlord and authorities for the actual project.
- IGBC Green New Buildings rating system. Official IGBC page describing its Green New Buildings rating system and the wider family of green-building programmes.
- GRIHA rating. Official GRIHA page describing the national green-building rating approach and project evaluation.
- CIBSE Knowledge Portal. Professional engineering guidance portal used as a reference point for building-services design and operational questions.