I chose this report because it is one of the strongest examples of how I think as both an engineering student and a technical communicator. It asks a broad engineering question and then works through the evidence methodically instead of treating the topic as a simple yes-or-no claim.
The topic also reflects my interests well. Space-based solar power sits at the intersection of space systems, infrastructure, and sustainability, so the report had to connect technical detail with larger systems-level implications.
What made the assignment especially meaningful was the need for balance. The report argues that the concept is technically plausible while also being honest about economic, logistical, and regulatory constraints.
This report shows growth in document architecture and evidence-driven writing. I organized the piece so the reader moves from the global energy challenge into technical explanation and then into a measured feasibility discussion.
It also demonstrates stronger use of quantitative evidence and visual support. Tables, figures, and sectioned explanations helped me make a complex concept readable without oversimplifying it.
A major sign of growth came from revision. Peer and instructor feedback pushed me to move important evidence into the main body and clarify the transitions between technical sections, which made the argument much stronger.
This report pushed me outside my comfort zone because it required breadth as well as depth. I had to write across orbital systems, power conversion, wireless transfer, economics, and policy without letting the document feel fragmented.
The hardest part was resisting the temptation to oversell an exciting technology. Clear communication here meant being disciplined enough to show both promise and limitation at the same time.
That challenge strengthened my sense of what professional engineering writing should do: not impress the reader with enthusiasm, but equip them to make a better judgment.
This is one of my strongest pieces in terms of scope, structure, and technical maturity. It combines report writing, evidence synthesis, visual support, and balanced reasoning in a way that feels close to professional engineering communication.
If I revised it further, I would simplify a few dense passages and make the strongest quantitative findings even more immediately interpretable for a broader engineering audience.
It belongs in the final portfolio because it demonstrates sustained written reasoning, revision discipline, and the ability to explain a technically ambitious concept responsibly.