Received: from [139.222.1.5] by messenger (ArGoSoft Mail Server Freeware, Version 1.8 (1.8.6.4)); Wed, 16 Feb 2005 11:42:09 +0000 Message-ID: <000a01c5141d$03399680$0501de8b@participant4> From: "participant4" To: References: <01c5141a$Blat.v2.2.2$27bc4122@messenger> Subject: Re: Please summarise the last meeting Date: Wed, 16 Feb 2005 11:45:27 -0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01C5141D.02515960" 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_01C5141D.02515960 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: Wednesday, February 16, 2005 11:25 AM 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 The meeting sufficiently addressed the beginning stages of design for = the product. We have addressed where we want to go with the product, = i.e. how the item should look/feel. We did not cover what type of = market in which we are going to push the product, however, since a = remote control is universally used by almost all age groups it will be = necessary to keep this in mind while designing the remote and developing = a marketing scheme. Overall, the meeting was productive in establishing = general goals of product development that will be expounded upon in = later meetings. =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. *Buying price: 25 ?, product cost 12.5 Desired profit: 50 million ? Product should be multifunctional (apply to all appliances possible), = have modern design, AA or AAA powered =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. *Group not clear on specific roles, possibly due to lack of previous = experience Slight lack of direction - where are we going exactly? =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. UID: technical aspects of the future remote ID: working design of product MD: find specific specifications required by consumers ------=_NextPart_000_0007_01C5141D.02515960 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 16, = 2005 11:25=20 AM
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.

 

 The=20 meeting sufficiently addressed the beginning stages of design for the=20 product.  We have addressed where we want to go with the product, = i.e.=20 how the item should look/feel.  We did  not cover what type = of=20 market in which we are going to push the product, however, since a = remote=20 control is universally used by almost all age groups it will be = necessary to=20 keep this in mind while designing the remote and developing a = marketing=20 scheme.  Overall, the meeting was productive in establishing = general=20 goals of product development that will be expounded upon in later=20 meetings.

 

 

 

 

 

 

 

 

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

 *Buying=20 price: 25 =80, product cost 12.5

 Desired=20 profit: 50 million =80

 Product=20 should be multifunctional (apply to all appliances possible), have = modern=20 design, AA or AAA powered

 

 

 

 

 

 

 

 

 

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

 *Group=20 not clear on specific roles, possibly due to lack of previous=20 experience

 Slight=20 lack of direction - where are we going exactly?

 

 

 

 

 

 

 

 

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

 

UID:=20 technical aspects of the future remote

ID:=20 working design of product

MD: find=20 specific specifications required by=20 consumers

------=_NextPart_000_0007_01C5141D.02515960--