Urgent.News

What's breaking now, across thousands of outlets.

Tech

Your Manager Rewrites Every Document Before It Goes Out

You spent most of the week on the proposal. You sent it to your manager on Thursday, and on Friday the version that went to the directors was almost unrecognisable. New opening, a different order, half your paragraphs gone and two new ones you had not written. It is the third time this has happened. Your name is still at the top, and you are no longer sure why. It is easy to feel that your…

Your manager rewrites every document before it reaches its intended audience. A week's worth of work on a proposal was transformed on Friday, with a new opening, altered order, missing paragraphs, and additional content you did not write. This third occurrence of heavy editing has left you questioning your writing abilities and wondering if your manager lacks trust in your skills.

It's tempting to assume your writing is insufficient or that your manager does not believe in your capabilities. However, these feelings are often unfounded. A manager who edits extensively is typically reacting to their understanding of the audience, working under tight deadlines, and employing an expedient approach to problem-solving.

This method is often faster than thorough explanations, particularly on a Friday. The key takeaway is that every rewrite provides detailed feedback, even if no direct communication occurs. Thus, it's beneficial to view each edit as constructive criticism, regardless of its source. Begin by comparing your original draft with the finalized version, looking for recurring patterns in the changes rather than individual alterations.

Did they shift the recommendation to the top? Did they remove the background information? Were technical terms replaced with more business-oriented language? Were numbers inserted where descriptions previously existed? After three documents, you should begin to recognize the same few modifications repeatedly. Once you've identified these patterns, discuss them with your manager at a calm moment, rather than in the aftermath of the most recent edit.

For example, you might say, "I've noticed you typically move the recommendation to the start and eliminate the historical context. Could you clarify what the directors prioritize? I'd like to better align my initial drafts with their expectations." Most managers will be willing to explain their reasoning, as they would prefer not to undergo the editing process themselves.

Next time, request a different form of assistance, such as comments on your next draft instead of full edits. This will take them a bit more time initially, but it will save them considerable time in the long run. Additionally, it will enable you to understand their reasoning, not just the end result. Before sending your next document, attempt to structure it based on the anticipated format: recommendation first, the necessary decision, followed by only the essential background information required by a busy reader.

Submit it a day earlier than usual, providing ample time for comments rather than a complete rewrite. Monitor the extent of changes with each iteration. If the edits gradually reduce your document from nearly its entirety to just a few lines, you're making progress, and it's worth acknowledging this improvement. However, if the edits never diminish despite your adaptations, it's crucial to have a separate conversation about ownership of the document. Ultimately, a document bearing your name should primarily contain your words.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Your Scripts Assume git init Creates master and Git 3.0 Will Make It main

A new developer joined and ran the tests. Fourteen failed on her laptop and passed in CI. All of them in the same file. The tests built little repositories to try the release tool on.

  • Tests failed on developer's laptop due to missing master branch
  • Git default branch name changed to main in 2020
  • Scripts should explicitly name branches using git init -b

You Saved the Stuck Design Problem for Your Sharpest Hour and It Would Not Move

You know when you are sharpest. For you it is nine to eleven, coffee in, messages off. So that is where you put the hard thing. The design problem you had been stuck on for a week.

  • Individual struggled with design problem for a week during peak hours.
  • Solution emerged at 4:30 PM on Thursday, during off-peak hours.
  • Research suggests tackling insight problems during off-peak hours can be effective.

Ssangyong E&C Secures Potential KRW 3.6 Trillion Dubai Development Pipeline

Ssangyong Engineering & Construction has entered into a strategic partnership with Dubai-based Wasl Group, securing a potential development project pipeline worth approximately KRW 3.6 trillion over…

  • Ssangyong E&C partners with Dubai-based Wasl Group.
  • Potential KRW 3.6 trillion development pipeline over three years.
  • Collaboration includes residential, hotels, and mixed-use projects.

Kolmar Korea’s Targeted Anti-Aging Material Earns NET Certification

Kolmar Korea’s antioxidant material technology, developed jointly with a research team at Jeonbuk National University, has received New Excellent Technology (NET) certification from the Ministry of…

  • Kolmar Korea develops targeted anti-aging material TOT with Jeonbuk National University.
  • TOT selectively releases vitamin E in response to hydrogen peroxide, reducing oxidative stress.
  • NET certification from Ministry of Trade, Industry and Energy validates advanced technology.

More from Thursday 5 November →