Professional Documents
Culture Documents
5-Kelly Project 5b
5-Kelly Project 5b
would allow us) to form a group to work on this semesters projects. With the addition of
Michelle, we quickly emailed each other to set up an initial Skype meeting. During this meeting,
we made an initial timeline for all of the projects this semester, formed our two teams, and
decided who would do what. We also scheduled another Skype meeting the following week as
well as each week (except for holidays) for the remainder of the project. We also decided that
each email about any aspect of the projects, no matter how small, was replied to in such a way
that every group member received a copy. In this way, even small changes to the website or
newsletter could be approved or vetoed by the other group members, so that a massive list of
changes and suggestions wouldnt need to be recorded at the weekly Skype session.
Since Brittany and Jessie were working on a live website, they were able to see what the other
had done to the website instantaneously. While there are programs such as GoogleDocs that
allow documents meant to be printed (such as newsletters) to be live updated, Michelle had
indicated unfamiliarity with such programs. Therefore, Michelle and I used email extensively to
show any and all updates to the newsletter. Due to their close proximity, Brittany and Jessie
occasionally met in person to work on the website. Michelle and I, on the other hand, live much
too far away for meeting in person. So we used Skype, email, and telephone to discuss much of
our work on the newsletter.
Style Guide
The most difficult portion of our project was actually compiling the style guide. Even so, this
process was only difficult due to several last minute color and font changes to the newsletter and
website. Our group had decided that Brittany and I would take the helm in writing the style
guide, so a person from both teams (website and newsletter) would be able to add their teams
changes to the style guide. These changes were, as all other changes to the website and
newsletter themselves, shown in emails sent to every member of our group for their approval. I
did find that while I wanted to be rather exhaustive when deciding what to include in the style
guide; this suggestion was vetoed by the other group members in favor of a more streamlined
style guide that would be appropriate for someone who was always in charge of writing the IPA
newsletter.
Aspects that Needed Improvement
I am very happy with my team and our work on the IPA website and newsletter. However, I do
still have a few things that, in my mind at least, needed improvement. I would have liked to
make each one of the tabs on the website clickable, and have each tab taken the visitor to a page
with something about the IPA written on it. While I know that this would have been next-toimpossible with the allotted time: I still think it would have made for a more polished look to the
website as well as a better presentation for the group as a whole. I would have liked to write a
few more articles about the IPA for the newsletter, in order to put more of a group stamp on the
document. Nevertheless, due to time constraints (and other classes projects due dates
approaching) this was not accomplished. Another aspect that I think needed improvement was
the style guide. I think an exhaustive style guide (along the lines of those created for university
webpages) that defined every font used, when it was used, and where it was used would have
been more helpful to the IPA. With this exhaustive style guide, a person completely unfamiliar
with the conventions of the IPA, or even newsletters in general, would be able to compose a new
issue of the newsletter without anyone knowing that the editor had changed. This exhaustive
style guide would also have allowed for the concept of rotating newsletter editors within the IPA,
thus relieving one person of the sole responsibility of writing the quarterly newsletter. Rotating
newsletter editors armed with an exhaustive style guide would also allow for shorter (though
more frequent) electronic newsletters that would be able to give more timely information.
Conclusions
I really enjoyed this series of projects. I had a great team and we all worked really well together.
Though I like to think that I often work better by myself, I have found (and continue to find) that
if your group all pitch in and contribute; a lot of the burden and responsibility of creating and
writing a piece of documentation evaporates. I have also found that my science background has
affected my writing style a lot more than I previously thought. In science, (especially the
qualitative, computational-chemistry I was performing in my other graduate degree) the writing
is often organized so that first you exhaustively explain one thing (and its corresponding jargon)
and then you explain the next thing (and its jargon). Often my group members would spot this
and point it out in my work on the newsletter and style guide, hence, my preference on the
exhaustive style guide. I hope that in my next group project I am in a group of such talented and
competent writers and designers. If you have any questions, comments, or concerns, about this or
any other paper or project, please contact me as soon as possible. I can be reached via mobile at
910-619-1433 or email at kellycha12@ecu.edu.
Cc. Charles Brian Kelly