Skip to content
Pursue The PassionAbout
Expert Roundups

How Leaders Give Feedback That Builds Ownership

Terkel23 min read25 experts answer

§ How this was made

The perspectives in this article were written by the named contributors and submitted through Connectively. Connectively's automated system selected them and used AI to write the headline, introduction, section headings, summary sections, and illustration, and to make minor edits for clarity. Articles are assembled and published automatically. Report errors to corrections@connectively.us. How we make our content

Illustration generated with AI

How Leaders Give Feedback That Builds Ownership

Strong feedback does more than correct mistakes—it helps people take ownership of their work. Experts in leadership and team management share practical ways to address obstacles, balance workloads, and protect decision-making authority. Learn how clear questions, fair trade-offs, and focused support can build stronger teams.

  • Create Sustainable Action Plans
  • Revise Constraints, Define Success Criteria
  • Remove Process Barriers, Manage Results
  • Document Agreements and Future Steps
  • Ask First, Address Concrete Obstacles
  • Let Staff Choose What to Shed
  • Add Resources, Empower Crew Leads
  • Diagnose Hidden Causes Before Redistribution
  • Distinguish Excess Load From Skill Gaps
  • Simplify Workflows, Defend Customer Stewardship
  • Invite Colleagues to Propose Solutions
  • Use Weekly Micro-Reviews
  • Fix Request Intake, Maintain Core Accountability
  • Request Trade-Off Proposals
  • Let Designers Select Their Relief
  • Match Commitments to Available Capacity
  • Resolve Blocked Decisions Fast
  • Clear Dependencies, Avoid Takeover
  • Rank Priorities, Safeguard Project Autonomy
  • Protect Outcomes, Shift Logistics Assistance
  • Normalize Direct Workload Dialogues
  • Meet Delays With Practical Aid
  • Rebalance Duties Without Demotion
  • Offload Administrative Bottlenecks Together
  • Reassign Routes, Retain Lead Authority

Create Sustainable Action Plans

When a capable employee struggles, the challenge is to provide enough support to help them succeed without taking over their responsibilities. A manager who solves every problem may achieve short-term results but can create dependency and leave underlying issues unresolved.

I would start by discussing the employee's workload, competing priorities, and specific obstacles. Sometimes the issue is capacity, such as too many urgent requests, unclear priorities, or accumulated responsibilities. In other cases, the employee may need more information, coaching, or a clearer decision-making framework.

Once the cause is clear, I would collaborate with the employee to create a manageable plan. For example, we might prioritize key deliverables, defer lower-priority tasks, and set regular check-ins. The employee remains responsible for proposing next steps and communicating risks, while I help remove obstacles and make necessary decisions.

Managers should clearly define what support entails. It does not mean lowering all expectations or monitoring every detail, but ensuring the employee has the resources, authority, and clarity to meet commitments. If the workload is unsustainable, the manager should make adjustments rather than treating every capacity issue as a performance problem.

This approach preserves ownership and reinforces that seeking help is part of responsible work. The employee remains accountable for outcomes, while the manager is accountable for creating conditions that enable good work. This balance supports stronger performance, better judgment, and a sustainable working relationship.

Revise Constraints, Define Success Criteria

When an employee is overloaded, I ask them to identify the earliest point at which a commitment could slip. Then, I can revise a nonessential constraint while they retain control over execution within established procedures.

Acceptance criteria translate the revised expectations into clear, straightforward requirements that must be met by the completed work. In addition, testable criteria allow you to confirm that the desired conditions have been met. Throughout the production process, make sure you maintain the same quality standards.

How feedback is delivered matters - a lot. For instance, generalized feedback is unhelpful and can be confusing. Before giving feedback, managers should evaluate whether the concern directly relates to the employee's performance or whether factors beyond the employee's control contributed. Then, the recipients of the feedback are asked to evaluate their own performance and assess how their actions impact others. As soon as any concerns or issues have been mentioned, follow immediately by discussing how these could be improved or rectified in the future. After all, you can't conduct an effective performance review if the employee leaves the conversation without a plan of action. Finally, schedule future progress checks, offer your help through coaching or training recommendations and thank the staff person for their time.

Remove Process Barriers, Manage Results

Helping a team member overwhelmed with workload involves switching from simply managing their actions to managing their results, thereby granting them authority over how to get out of the tight spot. As soon as a leader comes in and starts calling the shots, they essentially imply that there is a loss of trust regarding the responsibility of the team member for the result. From my experience in leading teams, the best way to assist a peer who is having difficulties is to replace the role of a task performer with that of a barrier remover. The process begins with a review of capacity, where we order the list of the tasks according to their impact and not simply deadlines. By finding obstacles in processes such as waiting for external approvals or being preoccupied with manual documentation, I can step in and remove them without taking away project ownership from the person.

Feedback should be given as a support rather than as a criticism to keep up psychological safety. When the individual achieves high performance but meets difficulties, I focus the discussion on the system, asking what his/her workflow lacks. This allows for recognizing that scaling operations will inevitably lead to hitting ceilings, whereby it is a sign of growth rather than failure. Thus we start looking at outcome-related delegation, where I can assign simple tasks and ask the team member to define the criteria for success of these tasks. Thus, he/she is still in charge of the process even if not in charge of each tiny detail.

The relationship does not suffer because the team member feels supported rather than taken over. It is the task of a leader to preserve the capacity of the team in order that it can perform its valuable tasks effectively. By placing emphasis on ownership rather than speed of tasks performance, you create a culture of readiness to speak about the problems.

Document Agreements and Future Steps

When addressing overload, I ensure the manager sets priorities and protects required work while the employee retains ownership of the plan. I recommend ending the conversation with a short written agreement that covers the top priorities, what is changing, who owns each dependency, and when progress will be reviewed.

Organizations would be well advised to ensure that workload does not exceed individuals' resources (time, competencies, etc.). When priorities are piling up, you need a clear system in place to take you from overwhelmed to under control. It is not a flaw in your character. If you find you don't have full availability, think about how you can stagger the work or bring in extra help.

Recognize that each employee is facing challenges in their own way and that at times they may feel overwhelmed. If an employee is unable to meet their goals or believes new goals are unattainable, discuss the specific reasons why. Be flexible and adjust goals impacted by resource constraints or other circumstances beyond the employee's control. Let the ideas come from the person who is receiving the feedback. To the extent possible, give employees the autonomy to make decisions about their work and encourage employees to share their knowledge and skills. It would be a good idea to create a brief plan of action outlining the next steps. At the end of each performance review, ensure everyone's clear on what they need to do next (before their following review and in the long term). If any process improvements have been agreed, make it clear how and when these will be implemented.

Ask First, Address Concrete Obstacles

I start by asking before I tell. The first question I put to an overloaded or struggling team member is always: "What is getting in your way this week?" Capable people usually already know the real problem and have half a solution in mind. If I jump straight in with my own fix, I take away the ownership I'm trying to protect.

Once I understand the blockers, I give feedback only on the work, never on the person. I use one specific example and one clear expectation. Then we agree together on three things: what they will change, what I will remove from their plate, and a date when we will check in. Keeping that follow-up date matters more than the exact wording, because consistent follow-through is what tells someone the feedback was genuine.

I saw this clearly with a capable team member who was missing three deadlines out of ten. We removed two low-value tasks from their plate and added a short weekly check-in. Within a month, the miss rate dropped to one in ten, and they never felt I had taken over. I stayed available for blockers, but I left the decisions with them. The relationship stayed productive because they could see I was backing their ownership, not auditing it.

Let Staff Choose What to Shed

1. First separate the person from the pile. Someone who is very strong on my sales team at CheapForexVPS may miss the occasional tiny detail. It's not a skills issue. They are just overwhelmed with too many things. So I ask them to walk me through everything on their desk and to tell me which things only they can do. Most people can identify the 'dead weight' items quite quickly. And then I ask them to identify the things that they would hand off, delay or push back on to someone else and I go and get the rest of the team to agree with their decision. The workload actually decreases but they are still making the decisions that a capable person wants to make. It's like a homeowner in the middle of a renovation. You don't take the keys away from them. You help them decide which rooms to focus on next.

2. Specific, timely, framed as a question about the desired outcome instead of a judgment statement. "Three client renewals slipped last week, what happened?" This way the team member gets to analyze the situation with you instead of having to defend themselves. Additionally, I try to have a short weekly meeting to go over the tasks that they are mostly responsible for. This way, it's early enough to deal with any issues before they become big problems and they're not ambushed with a negative conversation when they least expect it. The trust you have with a team member is similar to the trust you have with a client. Small, consistent deposits of trust make the occasional tough withdrawal OK and leave an even better relationship behind in the end.

Add Resources, Empower Crew Leads

In bridge building, when a structure is overloaded, you add support rather than rebuild. I apply the same principle to managing people. At York Bridge Concepts, if a strong crew lead was overloaded, I did not remove their project, as that can undermine trust. Instead, I would ask, "What's the heaviest load you're carrying right now, and what would take the strain off it?" I then allocated resources where needed, whether by providing extra help, adjusting schedules, or handling permitting issues myself. The crew lead remained responsible for decisions.

For feedback, I use a site walk: we review the work together, I specify what needs improvement and explain its impact. I ask how they would address the issue before offering my input. Focusing feedback on the work, not the person, preserves relationships. When team members solve problems in their own way, they maintain ownership.

Diagnose Hidden Causes Before Redistribution

I'm Pratik Mistry, EVP of Technology Consulting at Radixweb, a custom software engineering partner. In my 20+ years of experience, I can confidently say that this isn't a one-off situation. It happens more often than most teams would like to admit.

And I think the first steps towards remedying this are to understand 'why' it happened. Usually, the issue is external and environmental and not actually about the team member's capabilities.

When a team member who has always been reliable and capable slips up, most well meaning managers and team leads try to give them some time off or take the burden off their plate. But that inadvertently gives the person a signal that they are being considered incapable of handling the situation and thus their authority or ownership is being revoked.

So instead of trying to lighten their burden, my approach is to have a private conversation with them. And in that conversation too, the focus should be on 'what problems are you facing' instead of 'why are you not performing?'

Chances are the problem is much deeper than being overloaded and they might not have the right resources. Or the team dynamics might have shifted. Or maybe even something personal. Once you know what's going wrong, it becomes easier to fix it without just asking the concerned person to drop the project or assigning their work to someone else to free them from the load. I remember, a few years ago, during COVID, a senior developer was working on multiple projects and we could see them struggling. Of course, the first instinct was to let them work on only the priority projects and shift some of their workload to others. But this person had juggled multiple projects before, and we knew that they could do it. A conversation with them revealed that they were struggling to get their inputs across to one of the project managers, which meant they had to spend unnecessary time on one project, which led to issues with their other projects too. So instead of taking them off that one project, we built better communication channels and helped them work through their differences with the project manager and within days, they were back to being productive, even when the number of projects remained the same. So I think instead of just assuming that the amount of work is the problem, understanding the cause and fixing it is important.

Distinguish Excess Load From Skill Gaps

The first thing I sort out is whether someone is overloaded or stuck on a skill. From the outside they look the same, with late work and short answers, but the fixes differ. So I ask them to walk me through their week and tell me what they'd drop if they could. People who own a job usually already know where it's breaking.

Turnover work stacks up fast. Checkout windows are tight, and one crew can end up with several homes between late morning and afternoon. When someone is behind, I take a task or a stop off their pile and leave the decisions about how to run the day with them. They still own the work. They just have less of it that afternoon.

Feedback works best for me when it's the same day and about one specific thing. A photo of a missed baseboard, a short call while the details are fresh. Waiting for a monthly review means nobody remembers the situation. I describe what I saw, ask what got in the way, and let them propose the fix. Most of the time their fix is better than mine because they were standing in the room.

I also tell people early that a problem raised on day one is easier for me than one I find on day five.

Simplify Workflows, Defend Customer Stewardship

As Marketing Director for Smith Automotive Group, I'm often coordinating paid media, CRM, reputation, website, and sales/service follow-up across our Nissan stores. In a dealership, overload shows up fast because a missed handoff can affect a lead, an appointment, or a service customer.

When a strong person is struggling, I don't take the work back; I take friction out of the workflow. I'll look at the actual CRM notes, lead sources, appointment steps, or service communication path and separate decisions they own from admin that can be templated, automated, or handed off.

One example is customer communication: our standard is "no pressure, no runaround" and "no confusion," but that doesn't happen by telling someone to care harder. If a manager or advisor is buried, we protect their ownership of the customer relationship while simplifying scripts, reminders, and next-step tracking.

My feedback approach is evidence-first and role-protective: "Here's where the process is breaking, here's the customer impact, and here's the part I still want you leading." That keeps the conversation about improving the system, not diminishing the person.

Invite Colleagues to Propose Solutions

When someone solid looks overloaded, I pull them aside and ask what's working, what's eating their time, and what they'd change if they could. Tried this with a project lead last month. She handed off two status meetings and her output jumped within a week. The key is letting them propose the fix. People protect what they choose.

Use Weekly Micro-Reviews

When someone on the team is swamped, I skip formal reviews. Instead, I do a quick weekly chat where we cover one bottleneck, one thing that went right, and pick one small tweak for next week. That's it. They keep ownership because they're choosing the tweak, not me. People actually start bringing me problems instead of hiding them, which beats any performance review I've ever sat through.

Fix Request Intake, Maintain Core Accountability

My goal with an overloaded team member is to make the work more manageable without signaling that I have lost confidence in them, as there is no better way to pump the breaks on the effort provided by that employee than to give that notion. I start with specific observations and then ask where they see the biggest constraint. In one situation, a strong employee was struggling because too many people were able to send them "urgent" requests directly. Not an uncommon situation, I think. We changed the intake process, gave them clearer authority to push back on lower-priority work, and kept ownership of the core deliverable with them. Their performance recovered because the environment improved, not because expectations disappeared. The feedback approach that helped was being explicit: "I want you to keep owning this, and I also want to remove the obstacles that are making it harder than it needs to be."

Request Trade-Off Proposals

Ask them to bring you a trade-off proposal. When someone is overloaded, I say, "Here's everything on your plate. Show me what you'd pause, what you'd delay, and what you need from me." My job is to approve it or ask questions, and the plan stays theirs. A marketing lead I worked with came back with a proposal that dropped two low-value reports and pushed one launch by a week, which was better than anything I'd have suggested. Keeping the authorship with the person is how you protect ownership.

Let Designers Select Their Relief

A designer on a team I advised was visibly stretched, missing deadlines she never used to miss. Her manager skipped the instinct to reassign her projects and asked instead: "If you could hand off one thing this month, what would it be?" She named the weekly reporting, which she disliked and which took hours. The manager moved it to someone else, and the designer's creative work improved within a few weeks because she kept control of the projects she cared about. Letting the person choose what comes off their plate keeps the decision with them, and people usually know exactly which task is draining them.

Match Commitments to Available Capacity

When a capable employee is struggling, I'd first look at whether their commitments fit the time available. Feedback about speed or quality won't help if the workload makes good work impossible. I'd ask which work is at risk, what can wait and which decisions the employee wants to keep owning. That would give us a way to change the load without taking away their ownership.

I had a conversation with an employee who showed signs of burnout. We went through the work on their plate and took some assignments off it. I checked in again later; they told me the workload felt manageable and their condition had improved. The change concerned what we'd assigned, rather than a judgment about their capability.

During planning, we review commitments and available time. Our Planning list in ClickUp and filtered workload chart in Metabase show when too many tasks land with one person. We then revisit priorities and redistribute work. The chart can't tell us how demanding an assignment feels, so I'd ask the employee what the list misses. In a feedback conversation, I'd agree with them on realistic commitments and return to those after adjusting the load. Following up matters because a shorter list on screen doesn't necessarily mean the work feels manageable.

I'd make the capacity decision with the employee and set a check-in to hear whether the adjusted load works while they retain ownership of the agreed priorities.

Resolve Blocked Decisions Fast

With 12 years of managing people, my instinct when someone struggles is to help in the most unhelpful way possible: doing part of it myself.

It solves the week and costs you the person. They learn that when something gets hard, someone takes it, so next time they hide it longer.

So now I ask what decision they're stuck on, rather than what work they're behind on. Usually there's one. They're waiting on something, two options look equally bad, or they think they need permission they don't have.

Removing a decision isn't removing ownership. It's often the only thing actually blocking them, and it takes ten minutes.

Sometimes the honest answer is that there's too much work and no clever conversation fixes that. Then I take something and say that's what I'm doing, rather than pretending it's coaching.

Clear Dependencies, Avoid Takeover

Stepping in when someone is overloaded feels like good management. It usually isn't. Capable people don't need you to take things from them. They need you to remove whatever is slowing them down.

Those are completely different responses, and most leaders default to the first one without asking which problem they're actually solving.

The question I've landed on is this. Before any conversation about workload or performance, I ask "what's getting in the way that I could remove?" Not what I can take over. What I can clear. That framing keeps their ownership where it belongs and focuses the conversation on the system instead of the person.

If the conversation needs to go deeper, I follow with a second question: "If you could change one thing about how this work moves through the team, what would it be?" That question almost always surfaces a structural fix the person has already thought through but hasn't said out loud because nobody asked.

At Chronicle that question once pointed directly back at me. A team member was slower than expected and it turned out an approval step required my sign-off before they could move forward, and I wasn't getting to it fast enough. I removed that dependency entirely. Output recovered within the week, and nothing about their role changed except that I stopped being in the way.

Rank Priorities, Safeguard Project Autonomy

Change what they are carrying, not who is carrying it.

The instinct when somebody capable is drowning is to step in and take a piece off their plate. It fixes this week and damages the next six, because you have told them, and everyone watching, that struggling means losing the work.

At Eprezto we run on a cadence that makes this easier to handle. Whoever proposes an experiment owns it end to end and presents the results the following week. That ownership is the whole point of the system, so I am not going to quietly reassign somebody's project because they had a bad week.

What the weekly presentation does give me is a natural place for the conversation. The question I ask is not how they are doing, which gets a polite answer. It is what they would drop if they could only finish one thing by Friday. People will answer that honestly, and the answer is usually that three things are half done because none of them was ever explicitly ranked. Then I rank them, out loud, and say the other two move to the next cycle. The work still belongs to them. What changed is that somebody else took responsibility for the priority.

The other half is being willing to let something run late rather than inserting myself. If I take it over, I learn nothing about whether the workload was wrong in the first place.

So separate the load problem from the performance problem, and fix the load first.

Protect Outcomes, Shift Logistics Assistance

As a co-owner at Plumbing Tech, I deal with this in a very practical setting: emergency calls, sewer issues, water heaters, gas lines, and customers who need clear answers fast. A strong team member can struggle simply because the load is badly sequenced, not because they lack skill.

I try not to take the job away from them; I protect their ownership of the result while removing friction around it. For example, if a tech is buried on a sewer inspection or water-heater call, we may keep them as the lead but shift dispatch updates, parts coordination, or a second set of hands to someone else.

My feedback is usually built around observable constraints, not personality. I'll say, "The diagnosis is solid, but the handoff and timing are getting squeezed; let's fix the process around you before it affects the customer."

That keeps the conversation productive because the person still owns the standard of work. You are not rescuing them from responsibility; you are making sure the system around them does not quietly set them up to fail.

Normalize Direct Workload Dialogues

I've led teams through some of the most high-pressure environments imaginable--building Amazon's Loss Prevention program from the ground up, training law enforcement across the globe, and running a certification institute serving every branch of the U.S. military. When capable people buckle under load, I've learned the problem is almost never ability--it's clarity.

The move I've made that actually works: I sit down and name exactly what I'm seeing, behaviorally and specifically. Not "you seem overwhelmed"--that's vague and it stings. Instead: "I noticed the last two deliverables came in late and the quality dipped. Walk me through what your week actually looks like right now." That question opens the door without kicking it down. They keep ownership of the diagnosis.

What I saw inside police agencies and inside my own team at McAfee Institute is that high performers struggling under load will grind themselves into the ground before they ask for help--because asking feels like failure. So I don't wait for them to ask. I make the conversation routine, not a red flag. That reframe alone keeps the relationship from getting transactional the moment performance dips.

The hardest part is separating the person from the problem in real time. When I was building out Amazon's LP program, I had to hold people to standards while making it crystal clear that my belief in them was not contingent on a perfect quarter. That distinction--standards are non-negotiable, my confidence in you is unconditional--is what keeps a capable person performing instead of protecting themselves.

Meet Delays With Practical Aid

Managing over $1 billion in healthcare construction projects over 25 years taught me that supporting an overloaded team member begins with how you respond to struggle. In our morning huddles, the rule is to meet admissions of delay with "What do you need?" rather than interrogating why they fell behind.

Early in my career, a project engineer got buried in submittals after handling a field crisis, and my director showed me how to rally the team to take specific tasks off his plate without taking away his authority. You act as a janitor clearing individual obstacles, while keeping that team member in the driver's seat of the actual outcome.

For feedback, I rely on a private closed-door rhythm I call the sacred space, where hard truths are discussed strictly as an investment in their growth. We walk through how to navigate the pressure differently next time and reaffirm my belief in their leadership, keeping the relationship productive and their ownership intact.

Rebalance Duties Without Demotion

As COO at DFW Movers & Erectors, I've had to manage overload in a business where mistakes can hurt people or shut down a plant. When we improved profitability by 215% in my first year and later worked through COVID, the answer was not taking ownership away from strong people.

I tell the person plainly: "You still own the outcome, but we're going to rebalance the load around you." Then we separate ownership from tasks, decisions, and communication so they are not personally carrying all three.

On complex rigging jobs, we do this through planning: one main point of contact, clear crew roles, safety briefings, and hazard reviews before work starts. That same model works with people; add support without making it look like a demotion.

The feedback that works best is specific and private: "Your judgment is trusted, but the current pace is creating risk. What do you need removed, delegated, or clarified so you can lead this well?" It keeps accountability intact while making success realistic.

Offload Administrative Bottlenecks Together

Over my 14 years managing property operations and renovation projects across hundreds of units, I've learned that supporting an overloaded team member shouldn't mean taking the wheel. I address it by stepping in as a resource rather than a replacement, asking them directly where the operational friction is happening.

We use our integrated real-time portals to look at active maintenance requests and contractor timelines together. Reviewing the workflow collaboratively lets us offload specific administrative bottlenecks while keeping the lead person in full control of project decisions.

Framing feedback around system adjustments rather than personal capability keeps the relationship productive and positive. It reinforces that their leadership is valued while providing the structural backup needed to get them back on track.

Reassign Routes, Retain Lead Authority

When a capable person is overloaded, I keep ownership with them and change the workload, not the title. At my telecom company I had a strong crew lead who started missing quality checks because he was covering two routes. I did not take the role away. I sat down with the progress numbers and said the work of two people was landing on one desk, then asked him to pick the three tasks only he should own and name what we would reassign that week.

The feedback stayed productive because it was about capacity and standards, not character. We moved the secondary route to another tech within five days, and his defect rate dropped back to the team average within about two weeks. Capable people usually know they are drowning. What they need is a manager who names the overload out loud, protects the work that matters most, and refuses to pretend heroics are a plan.

Pursue The Passion · Career Education & Inspiration

Back on the road

Keep driving