Received: from [139.222.1.4] by messenger (ArGoSoft Mail Server Freeware, Version 1.8 (1.8.6.4)); Fri, 28 Jan 2005 15:14:12 +0000 Message-ID: <006f01c5054c$319467b0$0401de8b@participant3> From: "participant3" To: References: <01c50549$Blat.v2.2.2$9f9696c8@messenger> Subject: Re: Please summarise the last meeting Date: Fri, 28 Jan 2005 15:15:24 -0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_006C_01C5054C.30B9E630" 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_006C_01C5054C.30B9E630 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: Friday, January 28, 2005 2:57 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 the last meeting we made important decisions about design issues. = We decided which materials we wanted to use, which functionalities to = include, once more spoke about the market trends and what is 'in' at the = moment. As far as interface design issues are concerned, things have = become much clearer. We are going to have buttons for major functions = that enable fast action, and an LCD and a spinning wheel to access more = options. =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. - Buttons for channels - spinning wheel - rubber case + buttons - color: vegetable colour - simple battery - case curved on one side - voice recognition=20 - advanced chip - sample speaker =20 =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. Time pressure - did not have enough time to discuss the appearance as = far as colours are concerned * =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. Marketing manager: Product evaluation Project manager: preparation for the last meeting, and progress = assessment Industrial designer: look-and-feel of the product + prototype User Interface designer: the user-interface design + prototype ------=_NextPart_000_006C_01C5054C.30B9E630 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, January 28, 2005 = 2:57=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 the last meeting we made important decisions about design issues. We = decided=20 which materials we wanted to use, which functionalities to include, = once more=20 spoke about the market trends and what is 'in' at the moment. As far = as=20 interface design issues are concerned, things have become much = clearer. We are=20 going to have buttons for major functions that enable fast action, and = an=20 LCD  and a spinning wheel to access more = options.

 

 

 

 

 

 

 

 

[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 Buttons for channels

-=20 spinning wheel

-=20 rubber case + buttons

-=20 color: vegetable colour

-=20 simple battery

-=20 case curved on one side

-=20 voice recognition

-=20 advanced chip

-=20 sample speaker

 

 

 

 

 

 

 

 

 

[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.
Time=20 pressure - did not have enough time to discuss the appearance as far = as=20 colours are concerned *

 

 

 

 

 

 

 

 

 

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

Marketing=20 manager: Product evaluation

Project = manager:=20 preparation for the last meeting, and progress = assessment

Industrial = designer:=20 look-and-feel of the product + prototype

User = Interface=20 designer: the user-interface design +=20 prototype

------=_NextPart_000_006C_01C5054C.30B9E630--