“People at the center” is easy to say.
It can mean a better interface, more user research, additional training, a change campaign, or a commitment to employee experience. Those things can be valuable, but none of them is sufficient.
Enterprise systems shape work. They define what people can see, what they are allowed to do, when they must ask for approval, which information they need, what gets measured, and how responsibility is assigned.
Putting people at the center should therefore change the architecture of work itself.
People are not an adoption problem
Many technology programs treat people as the final dependency.
The process has been designed. The platform has been configured. Controls have been defined. Then the organization turns to adoption: communicate the change, train the users, collect feedback, and encourage new behavior.
By that point, many of the decisions that determine adoption have already been made.
If a workflow adds unnecessary steps, training will not remove the friction. If the system requires a person to make a decision without enough context, a communication campaign will not make the decision safer. If accountability is split across several roles, interface improvements will not create ownership.
Adoption is not only a change-management outcome. It is a property of the operating model and the system design.
A platform is easier to adopt when it fits the reality of responsibility, reduces unnecessary cognitive load, makes the next action understandable, and helps people see the consequences of their decisions.
Human-centered does not mean frictionless
Not every form of friction is bad.
Some enterprise decisions should require a pause. A high-risk action may need additional evidence. A financial commitment may need explicit approval. A sensitive use of data may require a different path. A responsible AI decision may need human review even when automation would be faster.
The question is whether the friction is intentional.
Bad friction exists because systems are fragmented, roles are unclear, information is missing, or process design reflects internal complexity rather than the work that needs to be done.
Good friction exists because the organization has deliberately chosen to slow, challenge, confirm, or escalate a consequential action.
A people-centered design distinguishes between the two.
It removes the friction created by poor architecture and preserves the friction required for responsible judgment.
People need context, not only tasks
Many workflow systems are good at assigning tasks and weak at supporting decisions.
A user receives an item in a queue with a due date and a button. The system knows the history, policy, risk level, related data, prior decisions, and downstream consequences, but the person sees only a small part of that context.
The workflow has digitized the handoff without improving the judgment.
Human-centered design asks what a person must understand in order to act responsibly. It brings relevant information into the decision moment. It explains why an approval is needed. It distinguishes normal cases from exceptions. It exposes the impact of the choice where appropriate.
This becomes even more important when AI is involved.
An AI recommendation can reduce effort, but it can also make a weak decision appear more confident. A human reviewer cannot be meaningfully accountable if the system gives them neither enough context nor a realistic ability to challenge the recommendation.
Human oversight must be designed, not declared.
The decision moment
The same approval, three ways
What the system knows does not change. What the person is shown does — and with it, whether they can be meaningfully accountable.
What reaches the person
- Approval required
- Due in 2 days
- Approve / Reject
What the system knows but does not show
- Why this needs approval
- Risk level and how it was assessed
- Prior decisions on similar cases
- What happens downstream
The handoff is digitized. The judgment is not supported.
Decision rights are part of user experience
Enterprise technology often inherits organization charts and translates them into access roles.
That is not the same as designing decision rights.
A title may not explain who owns a specific decision. A manager may have formal authority but not the relevant operational context. A committee may approve something while no individual feels accountable for the outcome.
A people-centered system makes authority legible.
It should be clear who can decide, who must be consulted, who is responsible for evidence, who can grant an exception, and who owns the consequence after the workflow ends.
This is simultaneously a human, business, and governance concern. It cannot be solved by interface design alone.
Capability must evolve with the system
When technology changes work, capability requirements change with it.
Automation can remove repetitive tasks while increasing the importance of judgment. Integrated data can make decisions faster while requiring employees to interpret information across domains. AI can make knowledge more accessible while increasing the need to verify, challenge, and contextualize machine-generated output.
Training therefore should not be framed only as “how to use the new system.”
The more important question is often: what does good performance in this redesigned role now require?
That can include new knowledge, new judgment, different escalation behavior, clearer ownership, and a stronger understanding of the controls built into the workflow.
People remain at the center when the enterprise develops those capabilities deliberately rather than assuming the technology will compensate for their absence.
What leaders should ask
- 01Are people being involved only to validate a design, or are their responsibilities shaping the design from the beginning?
- 02Does each critical user understand the decision they own, not only the task they must complete?
- 03Is the system reducing unnecessary cognitive load while preserving necessary control?
- 04Do people receive enough context to exercise meaningful judgment?
- 05Are we measuring adoption as usage, or as the ability to perform the redesigned work effectively?
- 06When AI assists a decision, can the accountable person realistically understand, challenge, and override the recommendation?
The HBT position
People at the center is not a design slogan.
It is an architectural commitment.
Human capability defines what judgment the enterprise can responsibly rely on. Business design defines the purpose, boundaries, and accountability of that judgment. Technology should support it with context, structure, and scale.
A human-centered enterprise system does not ask people to compensate for poor process or fragmented technology.
It designs the work so people can contribute what systems cannot replace: intent, responsibility, interpretation, and accountable judgment.