Ask Employees How the Work Happens

Employees can expose operational requirements a project team may never see. The challenge is getting useful input without turning workplace planning into a vote.

Originally published December 2011. Updated September 2026 to reflect current owner-side workplace planning and employee engagement considerations.

A workplace project eventually reaches a question that sounds simple:

“Should we ask the employees what they want?”

Yes.

But I would ask them something more useful.

“Tell us how the work actually happens.”

Those aren’t the same question.

Employees may not know the lease constraints, project budget, building systems, schedule or competing requirements affecting the project.

But they often know things the project team doesn’t.

They know which equipment is constantly in use.
Which departments exchange information all day.
Where confidential conversations happen.
Which processes create bottlenecks.
Which storage nobody remembered.
Which workaround has quietly become part of the operation.

That information can materially improve the project.

Employee Input Isn’t a Design Vote

One reason organizations hesitate to involve employees is concern that asking for input creates expectations.

If you ask whether someone wants a private office, larger workstation or particular amenity, the answer can easily become interpreted as a commitment.

That’s not the purpose.

The objective is to understand requirements, not collect votes on solutions.

Instead of asking:

“What kind of workstation do you want?”

Ask:

“What do you need to accomplish at your workstation?”

Instead of:

“How many conference rooms should we have?”

Ask:

“What kinds of meetings occur, with how many people, and how often?”

Good questions uncover the requirement behind the preference.

The design team can then evaluate how best to satisfy it.

That information also becomes an input to space and adjacency planning, where operational relationships have to be translated into the physical layout.

Senior Management Doesn’t See Everything

Leadership understands the organization from one perspective.

Employees working inside individual processes see it from another.

Neither perspective is sufficient by itself.

A department head may know staffing plans and organizational priorities but not realize that two employees routinely share specialized equipment.

A project team may understand the floor plan but not know that a particular workflow requires frequent movement between departments.

An executive may see an inefficient process that should change rather than be accommodated.

All of those perspectives matter.

The purpose of engagement is to expose the information so the organization can make deliberate decisions.

Ask the People Closest to the Work

The most useful input often comes from people who perform the activity being planned.

• If you’re planning reception, talk with the people who manage visitors.
• If you’re planning conference facilities, understand how meetings are actually conducted.
• If you’re planning storage, ask what is stored, who accesses it and how frequently.
• If you’re planning specialized work areas, involve the people who use the equipment.

The question isn’t whose opinion carries the most weight.

It’s who knows something the project needs to know.

Separate Requirements From Preferences

Employee feedback will contain both.

A requirement might be:

“We handle confidential information and need somewhere to discuss it privately.”

A preference might be:

“I’d like my own office.”

Those aren’t equivalent.

The first describes an operational need.

The second proposes one possible solution.

That distinction allows the project team to evaluate alternatives without dismissing the underlying concern.

The owner should make sure requirements are captured even when the requested solution isn’t adopted.

Don’t Ask Questions You Aren’t Prepared to Use

Engagement can backfire when employees spend time providing input and never understand what happened to it.

Not every request can be incorporated.

That’s normal.

But the process should be clear about:

• what input is being requested;
• what decisions have already been made;
• what remains open for consideration; and
• who ultimately makes the decision.

That keeps consultation from being mistaken for approval authority.

It also makes the feedback more useful because employees understand the boundaries within which the project is working.

Communication Continues After Programming

Employee involvement shouldn’t end when the requirements are collected.

As the project develops, people will want to know what is changing and why.

That doesn’t require exposing every project decision to organization-wide debate.

It requires enough communication that employees understand the direction of the project, major changes that affect them and what to expect as occupancy approaches.

That becomes particularly important when the new workplace operates differently from the old one.

The Owner Still Has to Decide

Employee input is one source of project information.

So are the budget, schedule, lease, building conditions, technology requirements, business strategy and operational objectives.

The owner’s job is to bring those inputs together and make the decision that best serves the organization.

Employee engagement doesn’t transfer that responsibility.

It makes the decision better informed.

Leadership takeaway: Ask employees for the knowledge they have, not simply the solution they prefer. Good workplace engagement reveals operational requirements while keeping decision accountability where it belongs.