Received: from [139.222.1.4] by messenger (ArGoSoft Mail Server Freeware, Version 1.8 (1.8.6.4)); Wed, 2 Feb 2005 15:12:58 +0000 Message-ID: <005201c50939$dd477200$0401de8b@participant3> From: "participant3" To: References: <01c50938$Blat.v2.2.2$6df4b760@messenger> Subject: Re: Please summarise the last meeting Date: Wed, 2 Feb 2005 15:14:16 -0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_004F_01C50939.DC6CF080" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 This is a multi-part message in MIME format. ------=_NextPart_000_004F_01C50939.DC6CF080 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable For the documentation of the design project, you and all of your = colleages are asked to fill out a short questionnaire after e ----- Original Message -----=20 From: HeadOfDept@ami=20 To: participant3@ami=20 Sent: Wednesday, February 02, 2005 3:04 PM Subject: Please summarise the last meeting Dear Colleague, =20 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: =20 a.. Do not use any abbreviations.=20 b.. Write notes that are understandable for somebody who was not = present during the meeting=20 =20 The head of your department =20 =20 [ABSTRACT] Write one paragraph of coherent text to summarize the = meeting as a whole from your role's perspective. This was where our design ideas began to take a more specific shape. = We discussed energy source options, case material options, ergonomic = options, innovative interfaces, and current design trends. From the = perspective of my role, the meeting was important for determining = whether we were going to create a niche remote or a more general, = elegant remote.=20 =20 =20 =20 =20 =20 =20 =20 =20 =20 [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. * Decided to use battery and dynamo for power. * Decided to use rubber for case and button materials. * Decided the remote would be double-curved for ergonomic reasons. We might incorporate fruit and vegetables. =20 =20 =20 =20 =20 =20 =20 =20 [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. * Reissa really wants something like blue-tooth but the others aren't = interested. * We originally wanted a more general remote and all agreed on that, = but it is now becoming a sort of gimmicky remote.=20 =20 =20 =20 =20 =20 =20 =20 =20 [ACTIONS] Name the next steps that each member will take until the = next meeting. Write fragmented notes. Rik is talking to the bosses and responding to mails. Reissa is doing market research. Catherine and I are playing with play-dough. ------=_NextPart_000_004F_01C50939.DC6CF080 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable For the = documentation of the design project, you and all of your colleages are = asked to fill out a short questionnaire after e
 
----- Original Message -----
From:=20 HeadOfDept@ami
Sent: Wednesday, February 02, = 2005 3:04=20 PM
Subject: Please summarise the = last=20 meeting

Dear=20 Colleague,

 

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

 

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

 

The head of your=20 department

 

 

[ABSTRACT]   Write one paragraph = of=20 coherent text to summarize the meeting as a whole from your = role=92s=20 perspective.

 This=20 was where our design ideas began to take a more specific shape. We = discussed=20 energy source options, case material options, ergonomic options, = innovative=20 interfaces, and current design trends. From the perspective of my = role, the=20 meeting was important for determining whether we were going to create = a niche=20 remote or a more general, elegant remote.

 

 

 

 

 

 

 

 

 

[DECISIONS]   Name all decisions = that were=20 made during the meeting. Mark those decisions that you consider of = high=20 importance for your role with a *. Write fragmented notes.

*=20 Decided to use battery and dynamo for power.

*=20 Decided to use rubber for case and button=20 materials.

*=20 Decided the remote would be double-curved for ergonomic=20 reasons.

We=20 might incorporate fruit and vegetables.

 

 

 

 

 

 

 

 

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

 *=20 Reissa really wants something like blue-tooth but the others aren't=20 interested.

*=20 We originally wanted a more general remote and all agreed on that, but = it is=20 now becoming a sort of gimmicky remote.

 

 

 

 

 

 

 

 

[ACTIONS]  Name the next steps that = each=20 member will take until the next meeting. Write fragmented=20 notes.

Rik is=20 talking to the bosses and responding to mails.

Reissa=20 is doing market research.

Catherine=20 and I are playing with = play-dough.

------=_NextPart_000_004F_01C50939.DC6CF080--