Received: from [139.222.1.5] by messenger (ArGoSoft Mail Server Freeware, Version 1.8 (1.8.6.4)); Fri, 4 Feb 2005 12:57:26 +0000 Message-ID: <000801c50ab9$7ea44710$0501de8b@participant4> From: "participant4" To: References: <01c50ab7$Blat.v2.2.2$c30b0760@messenger> Subject: Re: Please summarise the last meeting Date: Fri, 4 Feb 2005 13:00:24 -0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01C50AB9.7DC09DD0" 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_0005_01C50AB9.7DC09DD0 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: participant4@ami=20 Sent: Friday, February 04, 2005 12:48 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 afternoon we went over the user requirements, technical = functions design and working design by listening to three presentations = and some additional moderation and discussion led by the project = manager. The needs and desires that were emphasized were: fashion, = functionality and simplicity. We decided that buttons for controls of = channels and volume should be bigger and that additional buttons should = be availible in a "hidden" pull-out format during the technical segment. = During the working design, we learned about the importance of infrared = and high-quality chips and batteries. We ended by deciding that defining = our target based on demographic might be difficult and that we'd be = better off doing it by what the consumer wants it to look and feel like. =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. *No voice recognition Yes to easy buttons *Yes to pull out option Yes to ergonomical design Yes to high quality battery and chip Focus on simplicity and fashion and usability *Yes to something to keep it from getting lost =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. =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. ------=_NextPart_000_0005_01C50AB9.7DC09DD0 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 = 12:48=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 afternoon we went over the user requirements, technical = functions=20 design and working design by listening to three presentations and some = additional moderation and discussion led by the project manager. The = needs and=20 desires that were emphasized were: fashion, functionality and = simplicity. We=20 decided that buttons for controls of channels and volume should be = bigger and=20 that additional buttons should be availible in a "hidden" pull-out = format=20 during the technical segment. During the working design, we learned = about the=20 importance of infrared and high-quality chips and batteries. We ended = by=20 deciding that defining our target based on demographic might be = difficult and=20 that we'd be better off doing it by what the consumer wants it to look = and=20 feel like.

 

 

 

 

 

 

 

 

[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.*No=20 voice recognition

Yes=20 to easy buttons

*Yes=20 to pull out option

Yes=20 to ergonomical design

Yes=20 to high quality battery and chip

Focus=20 on simplicity and fashion and usability

*Yes=20 to something to keep it from getting lost

 

 

 

 

 

 

 

 

 

 

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

 

 

 

 

 

 

 

 

 

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

------=_NextPart_000_0005_01C50AB9.7DC09DD0--