This document discusses best practices for writing in a team environment. It emphasizes the importance of setting clear expectations, deadlines, and providing an outline so all contributors understand how their section fits into the overall document. Team members should commit to deadlines in writing to avoid missed deadlines. The conclusion recommends keeping conclusions and recommendations brief and tied to the purpose and analyses presented in the report. Proper referencing of data is also important.

1. Writing in the workspace
s1220169
Yoko Ota

2. When You Work with a Team
・Team member need to let to
know the level of detail
required,
the audience, and the deadlines.
・Each provide contributor the
outline of the entire document.
everyone need know how their
section fits into the whole.

3. Deadlines
・ Team members should
commit to them in writing
and deadlines should be clear.
・Do not affect the quality of the
project. So Remember to allow
adequate time.
・cause an avalanche of missed
deadlines by one missed deadline.

4. Summary
・It is important to understand
both the purpose the document
serves and the audience who
will read creating a meaningful
document.
・Required level of detail
becomes clear by
understanding of these two
guiding principles.

5. Your role as a writer
・Requires objective analysis and
clear presentation in technical
Writing.
・It is critical that written
communication is clear and
accurate.
・you usually write for hire, either
for a company or a government
entity.

6. Lists
・Allow them to see specific items,
questions, or directions at a glance.
・Bulleted lists present a series of
like items.
・All items should be phrases if one
is a phrase.
・Sentences should have periods at
the end.

7. Wasted Words and Phrases to Avoid
・You cut without affecting the
meaning.
・Don’t add meaning to a
sentence that Avoid words and
phrases.

8. Correspondence&Memoranda
・Corporations and governmental
organizations have standard.
・Email
・Correspondence
・Meeting agendas and minutes
Memoranda

9. Email
・Email is becoming an important
means of communication.
・Use the email subject line to
succinctly define what the email is
about.
・Write short and readable
communications.

10. Employ Email Etiquette
・Employ basic politeness, standard capitalization and
punctuation, and good grammar.
・It is better to leave some extraneous information than
to err on taking out too much.

11. Reports&Studies
・The contents should be organized
as follows to present information in a
logical flow.
Introduction
Methodology
Data
Analysis
Conclusion
Recommendations
Appendices

12. Conclusions
・Designed to tie together the main
ideas of the document in light of the
document’s objectives.
・The conclusions must be
consistent with that purpose.
・Must draw their conclusions from
the data and analyses presented in
the report.

13. Recommendations
・Suggested actions or policies based
on the conclusions.
・Move a step beyond the conclusion
to recommend a specific choice or
decision.
・Only appear if they are part of the
scope of the document and within the
expertise of the author.

14. Reference Information
・References to data are important in
technical documents.
・You can then refer back to
reinforce a conclusion.
・You first define the information it
supports and explore the topic.

15. concepts in technical writing
When you work in a team, the report
is very important.
Because to create a mail and the
report, it is important to learn how to
write.
Finally, it's important to write a
conclusion.
Sentence is important to briefly
write.