Managing Up Summary: Melody Wilding's Conversations at Work

Key Ideas

1. Separate agreement about results from agreement about working style

The alignment and styles conversations solve related but different problems. You can agree that a report matters while disagreeing about whether the manager should see an outline, a rough draft or only the finished document. Wilding's author materials make these expectations discussable instead of treating either person's default as obvious.

In our fictional example, Hannah coordinates product onboarding at a small equipment supplier. Her manager, Leon, keeps changing a customer update after she has finished it. Hannah assumes he distrusts her. Leon assumes an early draft would have made his preferences clear. The immediate question is not which personality is wrong; it is which decisions require his involvement and when that involvement is useful.

Hannah could prepare two lists. One names the results the update needs to support: accurate delivery information, fewer avoidable follow-up calls and a clear next step for customers. The other names working arrangements: an outline on Tuesday, one review window and a deadline after which new suggestions move to the following edition. These lists are our exercise, not a worksheet reproduced from the book.

Ask the manager to correct both lists, then state what you need in return. Perhaps Hannah needs feedback on the proposed structure before polishing individual sentences. Record the arrangement as something to test and revisit, not a permanent diagnosis of Leon's style. Flexing communication should help a message arrive; it should not require hiding an important concern or accepting unlimited interruptions.

2. Turn a capacity problem into a decision about tradeoffs

Wilding's concept of pushback power recognizes that the same refusal can carry different consequences for different employees. Experience, credibility, role, relationships and organizational conditions affect the room someone has to negotiate. The concept is a reason to assess context, not a moral ranking of people who find it easier or harder to object.

Hannah is asked to prepare new launch data while an agreed onboarding repair still needs two days of work. An automatic yes conceals the conflict. An unexplained refusal may leave Leon unaware of the original commitment. The useful information is that both tasks currently draw on the same time and attention.

Her preparation can show the existing outcome, the new request, the capacity estimate and two plausible options. She might finish the repair first and deliver a narrower launch analysis, or pause the repair and record the resulting delay. The point is not to manufacture a false binary: if Leon can change staffing, scope or deadlines, those are real alternatives too.

Wilding's tradeoff approach places the competing priorities in view while leaving the appropriate decision with the person authorized to make it. Hannah should also state a genuine constraint rather than implying that every limit is negotiable. If late-evening availability is not possible, she can discuss a workable schedule without inventing a personal justification. Our application aims for an explicit commitment and recorded consequence, not the illusion that skillful wording always prevents disagreement or retaliation.

3. Propose ownership without absorbing every unresolved problem

The ownership conversation is about useful initiative. In her interviews, Wilding describes finding opportunities that benefit the employee, their manager and the organization, while avoiding unnecessary territorial conflict. This differs from simply volunteering for every task no one else wants. More work is not automatically more valuable work.

For Hannah, the recurring customer-update revisions may indicate a process problem worth addressing. She could propose a small trial: one shared list of approved delivery facts, a named reviewer and an agreed point for handing changes to the next update. That proposal connects initiative to a problem Leon already needs to solve.

Before presenting it, Hannah should identify the people whose work would change. The sales lead may supply customer questions; the operations coordinator may own delivery data. Asking for their input before announcing a new system prevents a helpful proposal from becoming a surprise instruction. This stakeholder check is our suggested application, rather than a claim about a specific book chapter.

The proposal needs boundaries of its own. State what the trial includes, what Hannah can decide, what requires someone else's approval and when the arrangement will be reviewed. If the manager wants a larger project, discuss what will move out of her existing workload. Ownership should increase clarity about contribution and authority, not erase that distinction. A useful result might be a modest reduction in conflicting edits; it should not be inflated into a guaranteed promotion or presented as proof that an employee can repair every organizational failure.

4. Make your contribution visible through results and reasoning

Wilding connects visibility with giving people usable information about your contribution. A manager often needs to explain a team's work to someone else. A long account of effort may not provide what that explanation requires, especially if the significance of the work remains unstated.

Hannah can change her weekly update from a list of emails sent to a short account of a completed milestone, the problem it addressed and the next decision needed. If she has reliable evidence that a change reduced repeated customer questions, she can report it with its limits. If she has only an observation from three colleagues, she should call it an observation rather than invent a performance metric.

The reasoning matters too. Explaining why she tested a shared fact list before requesting new software shows judgment, not only activity. A useful update can also acknowledge collaborators and identify a decision that remains with Leon. These details make the contribution understandable without implying that Hannah worked alone or controls the whole outcome.

Visibility should be proportionate to the task. Agree on a rhythm that gives necessary information without turning every minor action into a broadcast. Wilding also warns against relying on one manager as the only source of advocacy. Relevant relationships elsewhere can give context and continuity, but networking should respect confidentiality and existing responsibilities. Our practical test is whether the recipient can explain the contribution accurately, not whether an update sounds impressive or produces immediate praise.

5. Discuss a desired next step before the decision window closes

Advancement conversations become harder when an employee waits until a formal review to reveal what they want. Wilding's interviews emphasize earlier discussion, concrete expectations and follow-up. The desired change might be a project, broader scope or additional resources, not necessarily a promotion.

Suppose Hannah wants responsibility for onboarding across two product lines. She can describe the work she hopes to take on, explain why it would help the organization and ask what Leon would need to see before supporting the change. That question can reveal skill gaps, competing priorities or another decision maker whose agreement matters.

A useful record distinguishes a development activity from a promise. Being asked to lead a trial may provide evidence, but it does not by itself mean that a new role or compensation has been approved. Hannah can ask when the trial will be evaluated, which criteria will matter and who can authorize the next step. If the scope expands, the effect on her workload also needs discussion.

The money conversation belongs alongside the value and responsibilities involved, rather than being concealed in a general request for recognition. This guide does not calculate salary levels or offer employment-law advice. Its application is a clearer conversation about what is requested, what information supports it and what remains undecided. If the answer is no, ask whether the obstacle is timing, evidence, resources or a firm limit. A more precise refusal can inform choices even when it does not produce the desired result.