Dear User,
The primary way that I have grown as a writer throughout this course is evident in my first artifact, my team's Technical Proposal that we collaboratively authored, which shows how my teamwork skills have become stronger. My two teammates and I were in constant contact throughout the entire course and particularly when developing the final Project Proposal because it was a culmination of all our individual work and coordination. My second artifact of the Google Docs Version History technical instructions highlights an area where I can still grow. While working on a group project I am open to criticism and edits, but I found myself struggling to make major changes to my individual technical instruction sets, which is reflected in the draft version and final version being practically identical. This is a flaw that many writers struggle with because even our technical work is still an expression of our creativity and can be difficult to edit down or change significantly. There were peer review comments suggesting that I change the structure of my instructions to include subheadings and that I rearrange my introduction paragraph, and while I did edit both of those sections for comprehension and correctness I chose not to make those edits. However, I did make the edits of changing the screenshot annotations to match with my written numbered steps which improved usability. In the future I hope to work in a field where I can use my writing and editing skills within a collaborative team-- I am currently considering working in literary marketing. To continue improving myself and my writing style I will more actively seek out constructive critique in the future so that I overcome my personal struggles with accepting edits.
Sincerely,
K. Chandler
Technical Proposal (co-authored with classmates Jordana Albanese and Zaria Smiley)
Technical Instructions for Navigating Google Docs Version History
Memo Detailing Results of User Testing for Technical Instructions