How do we create consistent workplaces across locations?
Define what should be shared across a portfolio and where each location needs room to adapt.
Illustrative study · fictional scenario and sample data. This demonstrates a consulting approach. It is not a completed client engagement or an actual ITO result.
3Hypothetical location profiles
6Recurring spaces and systems
3Layers: purpose, requirements, local choices
01
The brief
Create a workplace family with room to adapt.
A fictional organization develops offices independently. Familiar activities work differently from location to location, meeting technology is inconsistent, and similar room names describe different capabilities. Leadership wants a clearer framework for future projects.
The decision is what should remain consistent and where local teams should have discretion. Copying a single layout would not address different buildings, work patterns, or visitor needs.
The scope of this example
A draft standards framework for three contrasting location profiles. No actual building, procurement agreement, brand standard, employee research, or approved product selection is assumed.
The desired deliverable
A concise design-team brief that connects each space type’s purpose with essential requirements, adaptable attributes, and a process for exceptions.
Executive readout
Standardize purpose and operating logic. Adapt the physical solution.
Use recurring space types to establish a common experience. Let room quantities, configurations, finishes, and placement respond to a validated local brief, with decisions documented so future projects can learn from them.
02
Three contrasting contexts
The same principles meet different conditions.
A
Compact hub
A constrained floor plate with limited room depth. Shared settings need to work hard without losing their purpose.
B
Project workplace
A larger setting organized around sustained team collaboration and visible work in progress.
C
Client-facing office
Regular visitors create a stronger need to distinguish public areas from team work settings.
01 / Purpose
What work does it support?
Define the activity and experience the setting should enable.
02 / Essential requirements
What must remain consistent?
Describe functional, operational, and performance requirements.
03 / Local choices
What should respond to context?
Record the dimensions, configuration, quantity, and expression developed locally.
These are decision layers for the sample framework, not validated technical standards.
03
The standards framework
Make consistency a visible decision.
Illustrative directions. Actual requirements and adaptations need development with facilities, technology, users, and project designers.
Space / system
Shared principle
A / Compact hub
B / Project workplace
C / Client-facing
Focus room
Concentration, privacy, light, ventilation, and acoustic performance.
Compact configuration.
Dispersed near neighborhoods.
Beyond visitor routes.
Hybrid meeting room
Consistent control logic; coordinated camera, display, audio, and seating.
Smaller formats.
Discussion + project formats.
Visitor-accessible format.
Team neighborhood
An identifiable base with access to shared support settings.
Shared storage at edges.
Team information near project rooms.
Separate from public circulation.
Project room
Visible work, group discussion, and clear ownership between sessions.
Bookable shared room.
Longer-duration team use.
Enclosed room for sensitive material.
Arrival + community
Clear orientation and an accessible, welcoming arrival sequence.
Combined welcome area.
Shared gathering space.
Reception + waiting area.
Materials + furniture
Coherent palette; durability, maintenance, comfort, and replacement criteria.
Dimensions suit constraints.
Configurations suit project work.
Local finish expression in visitor areas.
Example space-type brief / HM-01
Hybrid meeting room
Support a discussion in which remote and in-room participants can see, hear, and contribute.
Shared requirements to develop
Consistent naming, booking, and control logic.
Coordinated camera, display, audio, and seating.
Privacy and acoustic performance appropriate to the intended discussions.
Accessible use and an agreed equipment-support model.
Locally adaptable attributes
Room quantity and participant capacity.
Table shape, orientation, and furniture configuration.
Placement relative to visitor routes and team neighborhoods.
Finish selection within shared maintenance and material criteria.
A purpose and requirements brief, not a dimensioned room standard or an equipment specification.
Keep exceptions useful.
A local departure should record the requirement, the site constraint, the proposed response, the decision owner, and the point at which it will be reviewed. The reason matters as much as the visual difference.
For example, a shallow room may require a different table and camera arrangement. The proposed response would need a sightline and audio review before being accepted as a suitable local adaptation.
04
The recommendation
Test the framework on real sites before expanding it.
Illustrative recommendation
Develop a small, usable standards set with a clear review process.
Start with the recurring settings in this study. Agree on their purposes and essential requirements, then develop site-specific applications with the project team. Review one proposed application in each location profile before extending the framework.
Dimensions, technical performance, budgets, product availability, accessibility, and applicable building requirements must be resolved against actual conditions. No cost saving, procurement efficiency, or user improvement has been demonstrated here.
01
Agree on ownership
Workplace leadership + facilities
Define who maintains standards, who approves departures, and how updates reach project teams.
02
Develop the technical requirements
Technology + designers + operations
Translate the purposes into reviewable functional requirements and space-type briefs.
03
Apply the framework locally
Local teams + project designers
Test quantities, layouts, products, and finish choices against a validated site brief.
04
Review and revise
Standards owner + project team
Document accepted exceptions and feed evidence from completed applications into future revisions.
What the engagement could provide
A practical package for the next decision.
Portfolio design principles
Standards and local-adaptation matrix
Space-type purpose and requirements briefs
Furniture and finish selection criteria
Exception log and design-review responsibilities
Your question. Your context.
Put this thinking to work for your team.
Start with the decision you need to make. Michael can help define the right scope, information, and deliverables.