The Spectrum of Professionalism: Why Your Supervisor Is Pushing Back
Imagine Marcus, a junior engineering student working as a research assistant on a pilot study regarding urban water filtration. He spent three weeks meticulously documenting the flow rates and chemical reactions observed in the lab. When he submitted his draft, he felt confident; he had used clear, active verbs and avoided the clunky, passive voice he had been taught to avoid in his freshman composition class. His supervisor, a veteran lead researcher, returned the document with a sea of red ink. The most frequent comment in the margins was simply, "Too conversational." Marcus felt frustrated, thinking, "I just wanted to make the data readable."
When a supervisor flags your writing as "too conversational," they are rarely attacking your intelligence or your ability to communicate clearly. Instead, they are usually reacting to a mismatch in "register." In linguistics, register refers to the level of formality and the specific vocabulary choices appropriate for a given social or professional context. Your supervisor likely views the technical report as a document of record—something that needs to stand up to scrutiny in a legal or high-stakes academic environment. When you write, "We noticed that the filter clogged after ten minutes," you are telling a story. When your supervisor changes it to, "It was observed that the filtration system experienced a significant reduction in throughput after a ten-minute interval," they are attempting to distance the human element from the data.
The core mental model you should adopt here is the "Professional Distance Framework." This framework posits that technical writing is not merely about conveying information; it is about establishing an objective persona that exists independently of the writer. Your supervisor wants the text to feel like a scientific fact that exists in a vacuum, rather than a report of your personal experiences in the lab.
Takeaway: Your supervisor isn't asking for more complexity for the sake of it; they are asking for the linguistic markers of objectivity and institutional authority.
Mapping the Professional Distance Framework
To bridge the gap between your natural voice and the expectations of your supervisor, you need to understand how to shift your tone without sacrificing clarity. Most students fall into the trap of thinking that "professional" means "wordy." It does not. Professionalism in technical writing is about precision, consistency, and the removal of the subjective "I" or "we" where possible.
The following table maps common student writing tendencies against the expectations of a high-level technical editor.
| Student Tendency (Conversational) |
Professional Shift (Technical) |
Why the Shift Matters |
| Using "I" or "we" to describe actions. |
Focusing on the object or the process. |
Removes the researcher from the data. |
| Using contractions (don't, it's). |
Using full, formal verb phrases. |
Signals a commitment to formal standards. |
| Using casual transitions (So, Anyway). |
Using logical connectors (Consequently, Furthermore). |
Creates a rigid, predictable logical flow. |
| Describing feelings or observations. |
Describing measurable outcomes. |
Prioritizes empirical evidence over opinion. |
| Using simple, punchy sentence structures. |
Using compound-complex sentences. |
Allows for the inclusion of conditions and caveats. |
When you look at this table, notice that the "Professional Shift" column isn't necessarily better English—it is just a different dialect. If you are writing a blog post, the "Student Tendency" column is actually superior. But in a pilot study report, your supervisor is looking for the "Professional Shift" to ensure that the document feels like it was written by an institution rather than an individual.
Takeaway: Use the table above as a checklist to audit your next draft before you hit send.
Variations for Different Student Profiles
The way you adapt your writing depends heavily on your background. A first-generation college student might feel that overly formal language is a barrier to entry, while a transfer student might be struggling to reconcile the writing style of their previous institution with the new demands of their current department.
The First-Gen Perspective
Sarah, a first-gen biology major, often felt that academic jargon was a gatekeeping mechanism. She wanted her writing to be accessible to her community. However, her internship supervisor at a pharmaceutical firm kept pushing back on her "direct and punchy" style. Sarah realized that by softening her tone and using more precise, technical terminology, she wasn't being "fake"—she was learning the dialect of her field. She started viewing these revisions as learning a second language rather than changing her personality.
The Transfer Student Perspective
Leo transferred from a community college where his professors emphasized brevity and clarity above all else. When he started working on a civil engineering report, his supervisor criticized his writing for being "too informal." Leo had to learn that "clarity" in a community college essay is different from "precision" in a structural engineering report. He began keeping a "glossary of formal alternatives" to translate his natural, clear sentences into the more rigid, technical language his supervisor preferred.
The Non-Traditional Student Perspective
Maria, a returning student with ten years of experience in retail management, was used to writing reports that were meant to be read quickly by busy people. When she returned to finish her degree in environmental science, she struggled to write in the "slow, deliberate" style her professors demanded. She had to learn that in an academic or high-level technical setting, the goal is not to be read quickly, but to be read accurately. She started using a "buffer period"—writing the draft in her natural voice, then spending an hour "formalizing" the language before submitting it.
Takeaway: Your personal background influences your writing style, but your professional context must dictate your final output.
Why Complexity Feels Like Quality to Supervisors
It is easy to feel insulted when a supervisor adds words that don't seem to add meaning. You might be thinking, "Why use 'utilize' when 'use' is perfectly fine?" or "Why say 'in the event that' instead of 'if'?" The truth is that in many technical and academic circles, these longer, more complex phrases act as a signal. They signal that the writer is part of the "in-group" that understands the norms of the field.
"When I first started editing, I thought my supervisor was just being pretentious. Then I realized that the word 'utilize' signaled to the board of directors that we were being precise about the application of a tool, not just the general act of using it. It was a code, and once I learned the code, the feedback stopped." — Elena, Senior Research Fellow
This is a hard pill to swallow, especially if you value direct, minimalist writing. However, you have to remember that your supervisor is likely reporting to people who expect a certain level of formality. If they pass your "conversational" report up the chain, they might be criticized for not ensuring the work meets the expected standard. By asking you to change your writing, they are protecting their own reputation as much as they are trying to improve the document.
You don't have to abandon your voice entirely. You can keep your core logic and your clear structure, but you need to wrap it in the formal language of your discipline. Think of it like wearing a suit to an interview; you are still you underneath the suit, but the suit tells the interviewer that you understand the expectations of the environment.
Takeaway: View complex phrasing as a professional "cost of doing business" rather than an attack on your writing style.
The Art of the "Formal Pivot"
If you are struggling to make these changes, try the "Formal Pivot" technique. This involves writing your draft exactly how you want it to sound, and then going through a second pass where you specifically target the "conversational" markers.
Start by looking for every instance of "I" or "we." Can you rephrase the sentence to focus on the equipment, the data, or the process? Instead of "We measured the temperature every hour," try "The temperature was recorded at one-hour intervals." This simple shift immediately makes the sentence sound more objective and less like a narrative.
Next, look for your transitions. If you have a sentence that starts with "So," replace it with "Consequently," "Therefore," or "As a result." If you have a sentence that starts with "But," replace it with "However," "Conversely," or "Nonetheless." These words carry a different weight; they signal to the reader that you are engaging in a formal, logical argument rather than having a casual conversation.
Finally, look at your verbs. Conversational writing often relies on weak verbs like "get," "do," or "make." Technical writing thrives on precise verbs like "execute," "implement," "facilitate," "demonstrate," or "correlate." Replacing a weak verb with a precise one often eliminates the need for extra adjectives and adverbs, which actually makes your writing stronger and more professional without making it bloated.
Takeaway: You can achieve a professional tone without losing your clarity if you focus on replacing weak verbs and subjective pronouns.
Understanding the "Academic" vs. "Technical" Divide
It is also worth noting that your supervisor might be confusing "academic" writing with "technical" writing. Academic writing, like a literature review or a sociology paper, often leans toward high-level vocabulary and complex, nested sentences. Technical writing, like a pilot study report or a field manual, should ideally be as clear as possible. If your supervisor is pushing for complexity that makes the report hard to understand, you are in a difficult position.
If you find that the changes your supervisor is asking for are actually making the report
less clear, you have a professional responsibility to address it. Don't frame it as "your changes are bad." Instead, frame it as a question about the intended audience. You might say, "I noticed that these revisions increase the complexity of the sentence structure. I want to make sure that the end-users of this report can still easily follow the methodology. Do you think we should prioritize the formal tone, or should we aim for a balance between the formal tone and readability for the stakeholders?"
This approach shows that you are thinking about the goal of the document, not just your own ego. It also gives your supervisor a chance to explain their reasoning. They might say, "The stakeholders are technical experts, so they expect this level of formality," which gives you the green light to continue. Or, they might realize that they have gone overboard and give you permission to simplify things.
Takeaway: Always anchor your defense of clarity in the needs of the reader, not your personal preference.
How to Negotiate Your Writing Style
If you feel like you are losing your voice in the process, remember that writing is a collaborative act in a professional setting. You aren't writing an essay for a grade where you have total control; you are contributing to a team effort. The "conversational" label is a signal that you and your supervisor need to align on the project's "house style."
Ask your supervisor for a few examples of reports they consider to be "well-written." Don't just ask for advice; ask for models. Read these reports and look for the patterns. How do they handle the passive voice? How do they structure their results? What kind of vocabulary do they use? When you have a concrete model to follow, you stop guessing what "professional" means and start imitating the standard.
You will find that once you have read three or four of these "gold standard" reports, your own writing will naturally start to shift. You will begin to internalize the rhythm and the vocabulary of your field. This is how you grow as a professional writer. You aren't abandoning your style; you are expanding your repertoire. You are learning when to be conversational and when to be formal, and that is a skill that will serve you for the rest of your career.
Takeaway: Seek out examples of successful writing within your specific team to understand the local standard of professionalism.
Try This Tonight
Take the last two paragraphs you wrote for your report and perform a "de-personalization" audit. Highlight every instance of "I," "we," "my," or "our." Rewrite those sentences to focus exclusively on the process or the data—for example, change "We observed a spike in the data" to "A spike in the data was observed." Then, look for any contractions or casual transition words and swap them for their formal counterparts. Once you’ve done this, read the paragraph aloud; if it sounds like a neutral, objective record of events rather than a personal story, you have successfully bridged the gap between conversational and professional.