Dear Sir,
here is the summary you requested.
 
Regards,
Iain.
(User Interface Design)
----- Original Message ----- 
From: HeadOfDept@ami 
To: participant3@ami 
Sent: Friday, February 04, 2005 11:33 AM
Subject: Please summarise the last meeting

Dear Colleague,

Would you be so kind to report to me on the past meeting? Please hit the reply button and fill in the questions below, then click send. Please keep in mind that your notes are part of the project documentation ? among other things, they will be used by myself and other staff to stay informed about the state of the project. It is therefore essential that your notes ? though kept short - are of high quality. In particular:

* Do not use any abbreviations. 
* Write notes that are understandable for somebody who was not present during the meeting 

The head of your department


[ABSTRACT]   Write one paragraph of coherent text to summarize the meeting as a whole from your role?s perspective.
 
A 'kick off' meeting was held at 11 a.m. on 4th February 2005. The meeting aimed to start a new project with the aim of designing a new television remote control. After some introductions, an outline of the new project and the design process involved was given by the project manager. General ideas were discussed, including the problems often encountered with existing remote controls.
 
 
[DECISIONS]   Name all decisions that were made during the meeting. Mark those decisions that you consider of high importance for your role with a *. Write fragmented notes.

No firm decisions made as this was more a brainstorming session. We have suggested that we will try to address some of the problems with existing TV remotes to improve on their design.



[PROBLEMS/ISSUES] Name the problems or difficulties that occurred during the meeting. Mark those that you consider of high importance for your role with a *. Write fragmented notes.

No specific problems.








[ACTIONS]  Name the next steps that each member will take until the next meeting. Write fragmented notes.
 
Rose (Project Manager):
Alima (Industrial Design): working design.
Iain (User interface): technical functions design.
Jesse (Marketing): User requirements.