Reflection

I entered ENG2003 thinking communication was something that naturally followed from technical understanding. If I knew the material well enough, I assumed I would be able to explain it well enough. The course challenged that assumption quickly. What I learned is that technical accuracy and communication clarity are related, but they are not the same skill.

The first major shift came when I realized how often I wrote to prove that I understood a topic instead of writing to help a specific reader understand it. That distinction changed how I approached every assignment. Instead of asking, "How much do I know about this?" I started asking, "What does this audience need first, and what can I leave out?"

ENG2003 gave me a practical framework for audience-centered communication. In the cover letter, that meant selecting only the experiences that mattered to an employer. In the presentation, it meant structuring slides so the audience could follow a group argument in real time. In the technical report, it meant organizing complex evidence so the document built a case progressively instead of overwhelming the reader.

Those assignments were valuable because they isolated different communication problems. The cover letter was about compression and professional tone. The presentation was about pacing, transitions, and visual support. The report was about structure, evidence, and balance. Together, they made communication feel less like a vague soft skill and more like a set of concrete engineering decisions.

The most useful feedback I received in ENG2003 was not about grammar. It was about emphasis. Peer and instructor comments often showed me where I was trying to say too much, where I had hidden the main point too late in the document, or where my explanation made sense only because I already knew the context. That kind of feedback helped me see communication as a design problem rather than a proofreading problem.

Peer review was especially useful because it made audience response visible. When I reviewed other students' work, I could immediately see how structure and phrasing affected clarity. The same habits I could detect in their writing often existed in my own. Reviewing and being reviewed made revision feel less personal and more analytical, which is a mindset I want to keep using in future engineering work.

My growth as a communicator is tied closely to my growth as an engineering student. Early on, I tended to equate technical density with seriousness. If a paragraph contained more detail, more terminology, or more explanation, I assumed it was stronger. Over time, I have learned that strong communication is often the result of restraint and structure rather than volume.

One of the hardest lessons to accept is that being technically correct does not guarantee being useful. In team settings, research discussions, and coursework, I have seen how easily technically strong ideas can lose impact when they are not framed in a way others can use. That realization matters because engineering is collaborative by nature. If the reasoning cannot travel clearly, the value of the work is limited.

The research poster made that lesson especially concrete. I could not include everything from the project, so I had to decide what evidence would do the most work visually and conceptually. That experience reinforced what ENG2003 had already started to teach me: communication quality depends on hierarchy, not just completeness.

Communication also changes when the context shifts from solo work to team environments. Presentations, design projects, and research all require coordination as much as explanation. Good communication in those settings means creating shared understanding, aligning expectations, and making sure the next person can act on what you have said or written.

That is one reason I wanted the portfolio to include both ENG2003 work and a research poster. Together they show communication across multiple contexts: professional application writing, team presentation, formal technical analysis, and visual research summary. The common thread is the same in each case. My goal is to make technically rigorous work clearer, more usable, and more persuasive for the people who need it.

I am a more deliberate communicator than I was before ENG2003. I notice structure earlier, think about audience sooner, and revise with a clearer purpose. At the same time, I still have habits I am working on, especially the tendency to over-explain when I care deeply about a topic. The next step in my growth is becoming even more efficient without sacrificing nuance.

Looking ahead, I want to become the kind of engineer who can move comfortably between technical depth and public clarity: someone who can write for professors, explain to teammates, present to non-specialists, and communicate carefully in professional settings. That is the impression I want this portfolio to leave, and it is the direction I want my communication practice to keep moving.