Received: from [139.222.1.3] by messenger (ArGoSoft Mail Server Freeware, Version 1.8 (1.8.6.4)); Fri, 4 Feb 2005 16:33:08 +0000 Message-ID: <000a01c50ad7$521f8150$0301de8b@participant2> From: "participant2" To: References: <01c50ad6$Blat.v2.2.2$13a47030@messenger> Subject: Re: Please summarise the last meeting. Date: Fri, 4 Feb 2005 16:33:54 -0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01C50AD7.51328940" 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_0007_01C50AD7.51328940 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: participant2@ami=20 Sent: Friday, February 04, 2005 4:25 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. =20 In this final meeting we presented our three prototypes to the rest = of the group, discussed benefits and drawbacks for each one, and decided = to go with design number 2, the mango. This will be produced in a rubber = cover, with 6 push buttons and an ergonomic shape. It will have a = kinetic battery. We then analysed how closely the final decision matched = our original design and economic goals. we are fairly satisfied that we = fulfilled our dual objectives of simplicity and fashion, and that the = 'mango' will be a successful product with wideranging appeal, and a = considerable profit margin. =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. final design choice - the mango* yellow/black colour combo, also perhaps a few other options for = variety. rubber (spongy) case* to be made for 12.3 euros per piece =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. =20 is it easy enough to learn? what is case shape?* =20 =20 =20 =20 =20 =20 =20 [ACTIONS] Name the next steps that each member will take until the = next meeting. Write fragmented notes. end of meetings and design process! ------=_NextPart_000_0007_01C50AD7.51328940 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: Friday, February 04, 2005 = 4:25=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.

 

 In=20 this final meeting we presented our three prototypes to the rest of = the group,=20 discussed benefits and drawbacks for each one, and decided to go with = design=20 number 2, the mango. This will be produced in a rubber cover, with 6 = push=20 buttons and an ergonomic shape. It will have a kinetic battery. We = then=20 analysed how closely the final decision matched our original design = and=20 economic goals. we are fairly satisfied that we fulfilled our dual = objectives=20 of simplicity and fashion, and that the 'mango' will be a successful = product=20 with wideranging appeal, and a considerable profit = margin.

 

 

 

 

 

 

 

 

[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.

 final=20 design choice - the mango*

yellow/black=20 colour combo, also perhaps a few other options for = variety.

rubber=20 (spongy) case*

to=20 be made for 12.3 euros per piece

 

 

 

 

 

 

 

 

[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.

 

 is=20 it easy enough to learn?

what=20 is case shape?*

 

 

 

 

 

 

 

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

end=20 of meetings and design process!

------=_NextPart_000_0007_01C50AD7.51328940--