Motivation at work: give autonomy a clear shape

You ask someone to take ownership of a project. They bring the next decision back to you. It is tempting to conclude that they lack motivation. But if every previous independent choice was revised, asking for approval may be a sensible response to the environment.

Autonomy at work is useful when people can make meaningful choices within understandable boundaries. It needs a clear task, access to support and authority that matches the responsibility. “You decide” followed by hidden rules gives none of these.

This guide helps you examine the work before trying to motivate the person. It is intended for team and project leaders, including people introducing new AI workflows. It does not diagnose an individual’s psychological state or promise a universal technique for improving performance.

Distinguish motivation, capability and opportunity

A task that is not progressing may reflect several conditions. The person may not understand its purpose, may lack a necessary skill, may be waiting for access, or may be responding to another priority. These are not interchangeable explanations.

Ask for a recent example. What needed to happen? What did the person try? At which point did progress stop? Which choice could they make without approval? What did they expect would happen if they chose incorrectly?

The conversation should produce a description of the work, not a verdict on attitude. You can discuss interest and effort directly, but do not infer them solely from response speed, visibility in meetings or hours online.

Also check the workload. A person can care about a project and be unable to absorb another responsibility. Asking them to find their purpose will not create capacity. Resolve the trade-off with whoever owns the competing priorities.

Use self-determination theory as a lens

Ryan and Deci’s self-determination theory identifies autonomy, competence and relatedness as important psychological needs. In everyday work, the lens encourages questions about choice, support and connection.

Autonomy concerns experiencing an action as meaningfully one’s own. It does not simply mean working alone. A person can choose to collaborate or seek advice while exercising autonomy.

Competence concerns the ability to act effectively. At work, useful support includes task examples, access to relevant information and feedback that helps the person improve a specific action.

Relatedness concerns connection with others. A team needs ways to collaborate and ask for support that go beyond a friendly social event.

These descriptions are reference points for work design. They do not provide an employee scoring system, and you should not assume that an observed behaviour maps neatly to one unmet need.

Define the result before deciding how much freedom to offer

A vague task invites repeated clarification. “Improve the reporting process” does not tell someone which decisions the report should inform, which sources must be used or what the result needs to make possible.

Define the outcome and acceptance criteria. Explain why the work matters, including who depends on it. Name the constraints that are real: an approved data source, a delivery date, a spending boundary or an access requirement.

Then separate the fixed parts from the choices. The person might choose the report structure and analysis sequence, while data permission remains with the relevant owner. Make those boundaries explicit before the work starts.

The job-design research of Hackman and Oldham is a second useful reference for examining how the task itself is structured. The practical worksheet below is an editorial tool, not a reproduction of their research instrument.

Match support to this task, not a permanent label

An experienced colleague can need close support on an unfamiliar process. A junior colleague can own a task they have practised successfully. “Senior” and “junior” alone are poor descriptions of the support required.

Ask what the person has already done, which part is new and what an acceptable result looks like. Agree where a worked example, a review or access to another specialist would help.

Support should preserve ownership. If someone asks a question, do not immediately take the task back. Clarify the decision, discuss the options and decide whether the person can make the choice with the new information.

If the task carries a serious risk or requires a qualification, respect those boundaries. Autonomy is not permission to bypass competent review. A person should not be made responsible for an outcome they cannot safely authorise.

Make the permission structure visible

Create a short decision agreement. State what the person decides, what they discuss before acting, and what remains outside their authority. Include the route for a case that the agreement does not cover.

This can reduce the need to guess how a manager will react. It also makes your own behaviour easier to review. If you frequently reverse decisions that were inside the agreed boundary, examine whether the criteria were unclear or your preference is overriding the agreement.

Do not quietly add a new constraint after the person has delivered. If circumstances change, explain the new requirement and revise the task. Distinguish the change from a performance issue.

For the practical handover, use delegation and accountability. Clear autonomy becomes more credible when the delegation specifies resources, review points and escalation.

A hypothetical reporting task

Imagine an analyst asked to redesign a weekly commercial report. This is a hypothetical example. The manager wants more initiative, yet requests approval for every new metric and regularly changes the layout after publication.

They review the task together. The analyst can choose the visual structure and explanatory notes. The commercial owner approves metric definitions. The data owner controls access to restricted sources. A draft review happens before the first revised report is distributed.

The manager also supplies examples of decisions the report needs to support. The analyst does not have to guess whether the audience wants a detailed exploration or a short operational summary.

At the agreed review, they examine repeated approval requests, misunderstood definitions and whether readers can make the intended decisions. They also ask whether the new ownership adds too much work. No outcome is asserted: the arrangement may need to change again. The example shows how to make initiative possible, rather than demanding it in the abstract.

Use an autonomy agreement worksheet

Complete this with the person who will do the task. The conversation matters more than the form.

Add the deadline and the capacity the task requires. When you discover a missing resource, assign its resolution rather than leaving it as a test of initiative. The agreement should expose obstacles, not disguise them.

Avoid making recognition another form of control

Recognition is most useful when it names the contribution. “You made the handover understandable for the receiving team” is more informative than “You are a star.” The first describes work the person can understand and build on.

Be careful with rewards tied to a narrow activity count. If you celebrate prompt volume during an AI pilot, people may produce more prompts without improving the task. If you praise being constantly available, you may undermine the boundaries needed for sustainable work.

This does not mean pay, promotion or recognition are irrelevant. It means they belong in a broader and fair organisational arrangement. Do not suggest that meaningful work can compensate for unreasonable conditions or an unresolved compensation issue.

Discuss what competent work looks like and how contributions will be considered. Avoid using praise to push somebody into responsibilities they have not agreed or cannot resource.

Read progress without pretending to measure inner motivation

Look at the quality of decisions within the agreed boundary, repeated requests for clarification, rework and whether support is used effectively. Ask the person whether the arrangement gives them enough clarity and choice.

These signals concern the work. They do not reveal an inner motivation level. A reduction in questions may indicate greater confidence, but could also mean the person has stopped asking after an unhelpful response.

Use the guide to psychological safety to examine that possibility. Use team cognitive load when the task requires too much reconstruction or switching between priorities.

A team-level before-and-after comparison also needs context. Staffing, task complexity and external deadlines can change alongside your intervention. Record those conditions before attributing the difference to autonomy.

Try one clearer agreement this week

Choose a task where approval keeps returning to you. Write the outcome, the choices, the constraints and the support in plain language. Discuss the agreement, then act consistently with it.

At the review, ask what became easier and what remained unclear. Change the arrangement when the evidence warrants it. The broader organisational psychology guide helps connect the task to team structures. The consumer psychology guide makes the same distinction between an observation and its explanation.

If unclear ownership is slowing a digital or AI programme, tell me which decision keeps coming back. We can turn that recurring question into a task agreement the team can use.

Apply this to your project

Tell me the decision you are facing, the constraints and what you have already tried.

Complete all three fields to send your message.

Name

Email

Message

Send message

Keep exploring

Organisational psychology

Organisational culture: look at everyday behaviour

Understand organisational culture through decisions, rewards and everyday responses, then turn stated values into working practices you can review.

October 3, 2026·8 min read

Organisational psychology

Organisational psychology: a practical team guide

A practical guide to organisational psychology for digital teams: understand friction, clarify decisions and improve how people work together.

October 3, 2026·9 min read

Organisational psychology

Psychological safety: help teams speak up

Build psychological safety through everyday team practices: invite concerns, respond to mistakes and keep clear standards for accountability.

October 3, 2026·8 min read