What You Can Actually Do When You're Told to "Take Ownership"

• Target audience: Employees who are being told to take more ownership, or to think like an owner
• Prerequisites: None. This is the practical half of a three-part series; the structural diagnosis lives in a companion piece
• Reading time: about 15 minutes

Overview

This one is for anyone who has carried “I’d like you to take more ownership” back to their desk without quite being able to swallow it.

The companion piece, “Take Ownership” Becomes a Different Sentence the Moment You Name the Scope, takes that sentence apart and shows what it breaks. The short version: one phrase covers two opposite operations, a request with the scope named and a request that takes the scope away. In the second version decision rights, information, and stake all stay where they were, and accountability moves alone. So the discomfort you feel comes out of the structure rather than out of some deficit in your attitude.

Structure only gets you halfway, though. The other half is what to do on Monday. You can’t do the work of the person who hands over authority, and this article assumes you never will. What’s left is to name each thing that hasn’t been handed over, ask for it, and, when the asking goes nowhere, write the boundary down yourself.

Three moves make up the spine: identify what hasn’t been handed over, translate it into a concrete request, and record the boundary yourself when the request fails. The third is insurance against a failed negotiation, and it doubles as raw material for establishing after the fact where your responsibility actually ended. Around those three sit a few more checks: when to raise the question of stake (evaluation and pay), whether the person across the table is a viable counterpart at all, and how to decide it’s time to leave.

An honest disclaimer up front. None of this is a general solution. A meta-analysis comparing proactive constructs put the correlation between voice behavior and performance at r = .13 to .34, which is far from a guarantee that speaking up improves how you’re rated¹. That’s why the last part of the article deals with the exit criteria for a place that isn’t going to improve. I’d rather include that than pretend the negotiation always works.

1. Identify what hasn’t been handed over

The first move is neither protest nor endurance. It’s triage.

“You need to take more ownership” is too vague to argue with and too vague to act on. Run it through the four conditions, though, and usually one or two specific things are missing.

• Decision rights. Are you allowed to make this call yourself? Whose approval does it route through?
• Information. Can you see the numbers the judgment requires? Costs, budget, what other departments are doing, the priority order.
• Stake. If the outcome beats expectations, what comes back to you?
• Accountability. When it fails, who absorbs it, and how?

Most of the time accountability has arrived on your side and the other three haven’t. Being able to say which ones are missing turns the next step into something concrete. The reply to “you lack ownership” stops being “I’ll try to be more mindful” and becomes “am I allowed to decide this myself, and can I see the cost breakdown?”

One caution here. Not all four are necessarily missing. Sometimes the information is disclosed and you simply haven’t gone and fetched it. The point of triage is to find the parts you can move, not to build a case against your manager. File something as “not handed over” when it was actually available on request, and you freeze the piece you could have moved.

flowchart TB
    A["Told you lack<br>ownership"] --> B["Which of the<br>four is missing"]
    B --> C["Get it<br>yourself"]
    B --> D["Ask for it"]
    B --> E["Withheld<br>anyway"]
    C --> F["Available"]
    D --> G["Turn into<br>a request"]
    E --> H["Record it"]

2. Translate it into a request

2.1 Convert talk about mindset into talk about objects

An abstract demand can only be answered abstractly. So make it concrete. Think of it as translating the other person’s words into the name of the thing you want handed over.

In practice it looks like this.

• “Be more cost-conscious” becomes “tell me the gross margin on this deal and the ceiling I’m allowed to decide within”
• “Think about what’s best for the whole company” becomes “tell me what we’re prioritizing this quarter and what we’re dropping”
• “Treat it like it’s yours,” “take ownership of this” becomes “how far does my own decision reach on this project, and from where do I need to consult?”

The advantage of the translation is that it moves the conversation forward whenever the phrase was used in good faith. As the companion piece argues, ownership is the right destination, and the version of the request that leaves the scope unnamed is the part that misses. Supply the name of the thing that should be handed over and the handing-over becomes a concrete task, which is often enough for it to actually happen. In effect you are naming the scope on behalf of the side that owed you the work.

2.2 Negotiating individually is not an aberration

You may be thinking this is only available to a privileged few. But individually negotiated employment arrangements have a research literature of their own, under the name i-deals (idiosyncratic deals): non-standard terms arranged between an employee and an employer that are meant to benefit both². A review synthesizing 23 empirical studies (27 samples, 8,110 participants) found flexibility i-deals positively associated with job satisfaction and affective commitment³.

So negotiating your own terms is an established object of study rather than a loophole in the system. The scope of your discretion, the content of your assignments, and your access to information can all be on the table.

Two reservations. There’s no figure for how widespread the practice is, so I can’t tell you it’s common. And the consequences differ by type of i-deal (flexibility, development, task content), so don’t assume they all work the same way.

The same literature flags a side effect. When arrangements look unfair from outside, coworkers react badly². If you’re going to negotiate, then, there’s less friction in getting it through as a definition of the role rather than as a personal exception. “Anyone making this call needs the numbers” travels further than “I’d like to see the numbers,” and it survives longer after it lands.

2.3 Preparing for a no matters more than technique for getting a yes

This isn’t a negotiation-tactics article. What actually matters in practice is less the request itself than leaving a trace that the request happened.

Ask verbally, get deflected verbally, and nothing occurred. Put the same content into meeting minutes, a ticket, a chat thread, or an email, and at minimum you have a record that you asked and that no answer came back. Which leads into the next section.

3. When the request fails, record the boundary yourself

3.1 Speaking up is not reliably rewarded

Set expectations first. Organizations tend to be intolerant of dissent, and employees hold back from naming problems, as the literature on organizational silence lays out⁴. And the correlation between voice behavior and performance sits at r = .13 to .34 in meta-analysis¹. Within the same body of work, constructs like taking charge show stronger correlations, but nothing there supports “speak up and you’ll be rewarded.”

Growing Your Own Context — Three Practices for Individual Engineers covered this terrain in detail: how an individual assembles the raw material for judgment when the organization doesn’t supply it. This article picks up where that one leaves off, at the question of how to establish the limits of your responsibility.

3.2 A record can stand in for a boundary

If the side with the authority won’t draw the line, then preserve the fact that no line was drawn. That’s the most reliable move available to someone without authority.

Three kinds of records are worth keeping.

Decisions. Who decided what. Whether you made the call or routed it through approval. “I proceeded after consulting” and “I proceeded on my own judgment” look nothing alike in hindsight. For design decisions there’s already a format for separating what was decided from what wasn’t, and the practices in How to Use ADRs in DDD: Trade-offs and a Situation-by-Situation Playbook transfer directly.

Requests and responses. What you asked for and what came back. The absence of a response is itself part of the record. This isn’t ammunition against anyone; it’s material for reconstructing later why a given judgment was made.

Time and load. When responsibility alone increases, the first place it shows up is hours. Where contribution beyond your role has become a de facto obligation, job stress and turnover intentions rise even after role overload and hours worked are statistically controlled for⁵. Track how much time went into which project and when your caseload changed, and you can put the load in numbers instead of adjectives. “Things have been rough lately” invites disagreement. “My caseload went from three to seven, and four of them involve calls I can’t get approved” is harder to wave off.

These three are negotiating material, not the groundwork for a complaint. You use them in the next review or the next round of assignments, to point at the specific things that haven’t been handed over.

Note the contrast with the records in Growing Your Own Context, which are written as raw material for your own future judgment and deliberately not circulated. These ones earn their keep by being shareable. Same act of writing, different purpose.

4. Don’t postpone the question of stake

When responsibility grows, the piece most likely to get deferred is the stake. “Here’s how much I took on this time” never gets connected to “and here’s what came back,” and then the next period starts.

Three questions cover it.

• Will this increase in responsibility be reflected in my grade or in the definition of my role?
• If so, when, and at which evaluation point?
• If the results beat expectations, what comes back to me, in money or in scope?

When no answers arrive, the stake has effectively not been handed over. Owners and employees also carry structurally different risk to begin with. One side has no ceiling on its share of the upside; the other has a salary cap and loses the job on the downside. Asking both to feel identically invested is asking for something the contract doesn’t support.

This isn’t about being fixated on money. When responsibility keeps accumulating with no stake attached, you eventually lose the ability to explain why you’re this tired. And what you can’t explain, you can’t negotiate over.

5. The counterpart this approach doesn’t work on

Everything so far rests on an assumption: that the other person means well.

As the companion piece argues, “take ownership” usually comes from good intentions, and naming the thing that should be handed over gives the conversation somewhere to go. But there are also people who move the burden deliberately and keep the stake. Awkwardly, both types use the same sentence.

Some signals for telling them apart. This isn’t a clean binary, and in my reading the far more common case is a manager with no malice and no slack whose behavior looks similar. One item hitting means you’re probably still on the ground covered by the earlier sections.

• After you make the request concrete, the problem becomes the fact that you asked rather than what you asked for (“I didn’t think you were the type to say things like that”)
• You get reprimanded for keeping records, or instructions switch to forms that leave none (verbal only, disappearing chat)
• Trying to confirm the limits of your responsibility brings hints about your rating or your next assignment
• People who said the same thing before you were treated badly for it
• In areas covered by statute (working hours, breaks, overtime premiums), even asking the question is refused

If several of these fit, the internal negotiation needs to run differently. Piling on more requests will only get converted into a label like “malcontent,” because the person you were treating as a negotiating counterpart isn’t one.

To be clear, you keep recording. If anything it matters more now. What changes is whether you put the records on the internal negotiating table. Show them internally and you invite wariness, and instructions may shift to channels that leave no trace at all.

What you need at that point is an external channel rather than better negotiating instincts. In Japan the public entry point is the sōgō rōdō sōdan kōnā (総合労働相談コーナー, “comprehensive labour consultation corners”), run by the Ministry of Health, Labour and Welfare and located inside prefectural Labour Bureaus (rōdōkyoku, 労働局) and Labour Standards Inspection Offices (rōdō kijun kantokusho, 労働基準監督署). They take consultations on dismissal, non-renewal of contracts, transfers, pay cuts, and harassment, and route people toward advice, administrative guidance, or mediation⁶. Other routes include Hō-terasu (法テラス, the Japan Legal Support Center, which provides free legal information and referrals) and unions outside your company, including gōdō rōso / “unions” (合同労組・ユニオン, general unions an individual can join alone regardless of employer). Readers elsewhere will have different institutions to look up, but the shape of the move is the same: the counterpart changes from your manager to someone outside the company.

How to preserve evidence and how to file are questions of law and labour administration, past the organizational scope of this article. Assume you’ll be talking to a professional.

The line worth drawing here is that these two situations don’t belong on the same board. Going through an external channel against someone acting in good faith only wrecks the relationship, and continuing to negotiate with someone acting in bad faith raises both the wear and the risk. Working out which one you’re in comes first.

6. Deciding when to leave

Even where section 5 doesn’t apply, meaning the person across the table isn’t acting in bad faith, some workplaces simply won’t move. So it’s worth holding an exit criterion too.

When people are dissatisfied with an organization, they have broadly two options: speak up and try to change it from inside (voice), or leave (exit). Hirschman set out the relationship between the two and the loyalty that acts on them, arguing that loyalty postpones exit and thereby makes voice more effective⁷.

Here I’m giving my own reading: that mechanism works where the organization improves, and where it doesn’t, all that remains is a postponed exit. The more loyal you are, the longer the attrition runs.

The practical signals look roughly like this. Exit criteria seen from the information side sit in Growing Your Own Context, so I’ll keep this to authority and stake.

• You have multiple recorded instances of making a concrete request, and none of them got an answer
• Of the four conditions, not one of the missing ones has moved over six months to a year
• Responsibility keeps growing with no indication it will be reflected in your grade or role definition
• Someone before you burned out inside the same structure

If more than one of these fits, the odds of changing the place are low. What matters is not treating the decision to leave as a personal defeat. Drawing the boundary was the job of the side holding the authority. Where that job goes undone, there’s a limit to how much the side without authority can draw it in their place.

7. Things not to do

Three cautions in the other direction.

Don’t try to change the organization single-handedly. Handing over the four conditions is organizational design work, past what individual enthusiasm can cover. Pour everything into it and you’ll wear down with nothing to show.

Don’t brandish your records. They exist so you can reconstruct your own judgments and your own load later. Deploy them as a threat from the start and the relationship hardens, which stops even the things that were about to be handed over. Use them when you need them.

Don’t internalize “you lack ownership” as a verdict on you. Read the sentence as a signal that the work the other side owes hasn’t been done yet. Take it as an assessment of your character and your appetite for finding the movable parts runs out first.

Summary

What’s available to the person told to take ownership isn’t a change of mindset. It’s the following work.

Identify what hasn’t been handed over by running it through the four conditions: decision rights, information, stake, accountability. Go and get whatever is available for the taking, and translate whatever isn’t into a concrete request. Replace “I’ll be more mindful” with “am I allowed to decide this, and can I see the numbers?”

Requests travel further as definitions of the role, with less friction and better staying power. Framed as a personal exception, they invite a reaction from everyone around you. And whether the request lands or not, preserve the fact that you made it.

When it doesn’t land, record the boundary yourself: decisions, requests and responses, time and load. This is material for pointing at specific missing pieces in the next review or the next assignment round, rather than preparation for a complaint.

Raise the question of stake early. Will the added responsibility be reflected in your grade or role, and when? No answer means the stake hasn’t been handed over.

And some places won’t change. If you have several recorded requests and nothing has moved, leaving is a reasonable call. Drawing the boundary was always the job of the side with the authority. Where that hasn’t happened, there’s a limit to what the side without it can do.

For those doing the asking, or the designing This article covered the practical side for the person on the receiving end. Where to draw the boundary, which numbers to disclose, and how to write down the scope of delegation and the rules for splitting results are covered in the companion piece What to Design Before You Say “Take Ownership”.

For those who want the diagnosis first The anatomy of why the sentence is hazardous is in “Take Ownership” Becomes a Different Sentence the Moment You Name the Scope.

Related Posts

• “Take Ownership” Becomes a Different Sentence the Moment You Name the Scope — The structural diagnosis this article builds on
• Growing Your Own Context — Three Practices for Individual Engineers — Individual strategy in an organization that doesn’t supply information
• How Instruction-Waiting Workers Can Survive the AI Era: The Thought-Delegation Trap and Escape Routes — Passivity as a product of the environment
• What to Design Before You Say “Take Ownership” — Companion piece: the design work on the other side
• Why Japan’s Engineering Managers Burn Out: Three Separations You Must Make in the AI Era — The structure the managers doing the asking are stuck in

References

Footnote numbers correspond to the in-text citations, in order.

1. Employee proactivity in organizations: A comparative meta-analysis of emergent proactive constructs — Thomas, J. P., Whitman, D. S., & Viswesvaran, C. (2010). Journal of Occupational and Organizational Psychology, 83(2), 275-300. DOI: 10.1348/096317910X502359. A meta-analysis of 103 samples comparing four proactive constructs (proactive personality, personal initiative, voice, taking charge) against performance and attitudinal outcomes. The correlation between voice and performance sits at r = .13 to .34, while taking charge shows higher values. [Reliability: High] ↩︎ ↩︎²

2. I-Deals: Idiosyncratic Terms in Employment Relationships — Rousseau, D. M., Ho, V. T., & Greenberg, J. (2006). Academy of Management Review, 31(4), 977-994. DOI: 10.5465/amr.2006.22527470. Theoretical treatment of non-standard employment terms negotiated between an individual and an employer (i-deals), including the negative reactions that follow when coworkers perceive them as unfair. [Reliability: High] ↩︎ ↩︎²

3. Idiosyncratic deals in contemporary organizations: A qualitative and meta-analytical review — Liao, C., Wayne, S. J., & Rousseau, D. M. (2016). Journal of Organizational Behavior, 37(S1), S9-S29. DOI: 10.1002/job.1959. A review combining qualitative synthesis with a supplementary meta-analysis of 23 empirical studies (27 samples, 8,110 participants). The meta-analysis primarily tests sociocultural moderation, and the consequences of i-deals differ by type (flexibility, development, task content). [Reliability: High] ↩︎

4. Organizational Silence: A Barrier to Change and Development in a Pluralistic World — Morrison, E. W., & Milliken, F. J. (2000). Academy of Management Review, 25(4), 706-725. DOI: 10.5465/amr.2000.3707697. Sets out how organizations become intolerant of dissent and employees withhold concerns. [Reliability: High] ↩︎

5. Citizenship under pressure: What’s a “good soldier” to do? — Bolino, M. C., Turnley, W. H., Gilstrap, J. B., & Suazo, M. M. (2010). Journal of Organizational Behavior, 31(6), 835-855. DOI: 10.1002/job.635. N = 245. Pressure to perform extra-role behavior was associated with job stress and turnover intentions even after controlling for role overload and hours worked. [Reliability: High] ↩︎

6. Guide to the comprehensive labour consultation corners (Japanese) — Ministry of Health, Labour and Welfare. Established under the Act on Promoting the Resolution of Individual Labour Disputes at roughly 380 locations nationwide, including inside prefectural Labour Bureaus and Labour Standards Inspection Offices. They accept consultations on dismissal, non-renewal, transfers, pay cuts, bullying and harassment, and route people toward advice, administrative guidance, or mediation. Related: Consultation contacts for labour standards administration (Japanese) — Ministry of Health, Labour and Welfare. [Reliability: High (official government source)] ↩︎

7. Exit, Voice, and Loyalty: Responses to Decline in Firms, Organizations, and States — Hirschman, A. O. (1970). Harvard University Press. The classic framework organizing responses to organizational decline into exit, voice, and loyalty. [Reliability: High (classic work)] ↩︎