Test the Workplace Before You Build All of It

A furniture pilot can turn assumptions about layout, furniture and work patterns into something employees and owners can actually evaluate.

Originally published July 2019. Updated September 2026 to reflect current owner-side workplace planning and pilot-program considerations.

A workplace design can look convincing on a drawing.

The furniture fits.

The circulation works.

The meeting rooms are counted.

The standards have been approved.

But none of that answers a more practical question:

“What happens when people actually work in it?”

For a significant workplace change, I would rather learn that answer from a pilot than after hundreds of workstations have been purchased and installed.

A pilot doesn’t need to prove that the design is perfect.

It needs to expose what the team hasn’t understood yet.

A Pilot Is More Than a Furniture Mockup

A mockup can help evaluate dimensions, finishes, furniture and ergonomics.

A workplace pilot can do something broader.

It can allow employees to use a proposed environment under actual or simulated working conditions.

Can people concentrate?
Can teams communicate?
Are there enough places for private conversations?
Does the technology work the way the design assumes?
Are storage and support functions where people need them?
Does the furniture accommodate the work?
Do circulation patterns create conflicts nobody saw on the plan?

Those are difficult questions to answer from drawings alone.

Decide What You’re Testing

A pilot is much less useful if the organization simply builds a sample area and asks:

“Do you like it?”

That produces opinions.

Before the pilot begins, define what the organization needs to learn.

Perhaps the question is whether a new workstation standard provides enough functional space.
Perhaps it’s whether employees can work effectively with fewer assigned seats.
Perhaps the team wants to test acoustic separation, collaboration areas, technology or storage.
Perhaps the proposed workplace changes how departments interact.

Different questions require different pilots.

The owner should know what decision the pilot is intended to inform.

Put Real Work Into the Space

People react differently to a showroom than they do to a workplace.

A workstation can feel perfectly adequate during a ten-minute tour and very different after someone works there for several days.

The same applies to acoustics, lighting, technology, privacy and shared spaces.

Where practical, employees should perform actual work in the pilot environment.

That gives the team an opportunity to observe what people do rather than relying entirely on what they predict they will do.

Sometimes the difference is significant.

Don’t Confuse Preference With Performance

Employee feedback matters, but the questions matter too.

Someone may prefer a particular desk, chair or workspace configuration.

That is useful information.

But the owner also needs to understand whether the proposed environment supports the work.

• Can the employee perform the required tasks?
• What creates friction?
• What requires a workaround?
• What works better than expected?
• What isn’t being used at all?

A pilot should help distinguish between “I don’t prefer this” and “this prevents me from doing the work effectively.”

Both deserve to be heard. They don’t necessarily lead to the same project decision.

Watch for Behavior the Design Didn’t Anticipate

One of the most valuable things about a pilot is what nobody thought to ask.

Employees may move furniture.

They may avoid a collaboration area.

They may take calls somewhere the design team didn’t expect.

They may bring equipment into the space that wasn’t included in programming.

They may create informal storage.

They may consistently choose one type of workspace over another.

Those behaviors are information.

Before correcting them, ask what they are telling you about the design.

Give the Pilot Enough Time

The first reaction to a new environment isn’t necessarily the most useful one.

Novelty can make a space seem better than it is.

Change can also make a workable solution seem worse simply because it is unfamiliar.

If the decision warrants it, allow enough time for people to move beyond their first impression.

Then gather feedback again.

The objective isn’t to make everyone comfortable with change.

It’s to understand which issues persist after people have had a reasonable opportunity to use the environment.

Be Willing to Change the Design

There isn’t much value in running a pilot after the important decisions can no longer change.

If the furniture is already ordered, construction documents are complete and the schedule leaves no opportunity for adjustment, the pilot may become a demonstration rather than a test.

The pilot needs to occur early enough for the findings to matter.

That may mean changing a standard everyone thought was settled.

That’s not a failure.

Finding the problem before full deployment is exactly what the pilot was supposed to accomplish.

Don’t Automatically Scale the Pilot

A successful pilot doesn’t necessarily mean every aspect should be replicated everywhere.

Different departments may perform different work.

Some groups may need more privacy.
Others may rely heavily on collaboration.
Some may use specialized equipment or have different technology requirements.

The pilot establishes evidence.

The owner still has to decide where that evidence applies.

Learn While the Cost of Learning Is Still Small

The value of a workplace pilot isn’t that it makes change more entertaining.

It’s that it creates an opportunity to test assumptions while the organization can still respond to what it learns.

Changing twenty workstations in a pilot is one thing.

Discovering the same problem after installing 500 is another.

Leadership takeaway: Use workplace pilots to test the assumptions that matter before committing them at scale. Define what you need to learn, put real work into the space and leave enough time to change the project based on what you find.