Choice Architecture at Work

A company says employees should prioritise learning.

The training portal requires seven clicks, manager approval and a separate password.

Expenses, meanwhile, can be submitted in ninety seconds.

Which behaviour has the organisation actually made easier?

Policies tell people what matters. Architecture tells them what happens.

Behaviour follows systems

Choice architecture refers to the way options are organised and presented.

A large meta-analysis of 214 publications found that choice-architecture interventions produced a significant average effect on behaviour across multiple domains.

In organisations, architecture appears everywhere:

What is preselected?

What requires approval?

What is visible first?

How many steps exist?

Which information is mandatory?

What happens if the person does nothing?

Forms are behavioural documents

Consider a sales CRM.

If updating customer data takes six minutes, salespeople will delay it.

If managers then complain about “discipline,” they may be treating a design problem as a character problem.

Or consider an employee-assistance programme hidden five levels deep in the intranet. The company can say well-being matters while the system signals the opposite.

Architecture often reveals the organisation's real priorities more accurately than posters do.

Defaults can encode policy

New employees can be automatically enrolled in learning, mentoring or retirement programmes with a clear opt-out.

Meeting invites can default to 25 minutes instead of 30.

Expense tools can flag rather than block unusual items.

Feedback forms can start with specific behavioural prompts instead of blank text boxes.

Every default makes one path easier.

The ethical responsibility is to ensure the easier path is defensible.

Reduce friction before increasing motivation

Managers frequently respond to low adoption with communication campaigns.

“Please complete the survey.”

“Please update CRM.”

“Please use the wellness benefit.”

Before sending another reminder, count the steps.

Watch one real user attempt the process.

Measure abandonment points.

Ask what information is genuinely necessary.

Better architecture can outperform louder persuasion.

Questions worth sitting with

• Which behaviour does your organisation say it wants but make strangely difficult?
• What employee behaviour are you blaming on motivation without examining system friction?
• Which default currently exists only because nobody has revisited it?

Leave points

• Systems teach behaviour through friction and defaults.
• Low adoption is not automatically a motivation problem.
• Forms, menus and approval chains are behavioural design.
• The easiest path should align with the organisation's genuine priorities.
• Before communicating harder, redesign the path.