Received: from [139.222.1.2] by messenger (ArGoSoft Mail Server Freeware, Version 1.8 (1.8.6.4)); Fri, 4 Feb 2005 12:58:53 +0000 Message-ID: <007601c50ab9$7c892f40$0201de8b@participant1> From: "participant1" To: References: <01c50ab7$Blat.v2.2.2$c2bc59c6@messenger> Subject: Re: Please summarise the last meeting Date: Fri, 4 Feb 2005 13:00:20 -0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0073_01C50AB9.7BAD2720" 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_0073_01C50AB9.7BAD2720 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: participant1@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. =20 In our first real design meeting, we discussed function design with = three important objectives. The Marketing Expert, Jessie, focused on = the needs and desires of consumers, citing a study that the company = performed. User Interface Designer, Iain, looked at the effects of the = product, suggesting that we create prototypes and have groups try them = out because remote use is 'very subjective.' Industrial Designer, = Alima, who was originally frustrated because she could not find enough = information, presented a very coherent explanation of how the remote = works, and the importance of functioning chips, batteries, etc.=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. -target group is a demographic according to whom can afford it -fashion for younger people, big buttons/functionality for older = people -*functions will be: -something to keep it from getting lost -large buttons for essentials -possibility for extra functions (hidden away) -long-life battery or possible charging station =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. -issues with not having enough information/access to websites -learning to use powerpoint and screen projection -time management=20 =20 =20 [ACTIONS] Name the next steps that each member will take until the = next meeting. Write fragmented notes. -all will share notes/powerpoint in the project documents folder -all will provide summary and fill out questionnaire -PM will type up minutes and send out -each will work on individual tasks, in preparation for second = meeting, keeping in mind the goals and objectives set out during this = meeting ------=_NextPart_000_0073_01C50AB9.7BAD2720 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.

 

 In=20 our first real design meeting, we discussed function design with three = important objectives.  The Marketing Expert, Jessie, focused on = the needs=20 and desires of consumers, citing a study that the company = performed. =20 User Interface Designer, Iain, looked at the effects of the product,=20 suggesting that we create prototypes and have groups try them out = because=20 remote use is 'very subjective.'  Industrial Designer, Alima, who = was=20 originally frustrated because she could not find enough information, = presented=20 a very coherent explanation of how the remote works, and the = importance of=20 functioning chips, batteries, etc. 

  

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

 

-target=20 group is a demographic according to whom can afford = it

-fashion=20 for younger people, big buttons/functionality for older=20 people

-*functions=20 will be:

    -something=20 to keep it from getting lost

   =20 -large buttons for essentials

   =20 -possibility for extra functions (hidden away)

   =20 -long-life battery or possible charging = station  

 

 

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

 -issues=20 with not having enough information/access to = websites

-learning=20 to use powerpoint and screen projection

-time=20 management 

 

 

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

 

-all=20 will share notes/powerpoint in the project documents = folder

-all=20 will provide summary and fill out questionnaire

-PM will=20 type up minutes and send out

-each=20 will work on individual tasks, in preparation for second meeting, = keeping in=20 mind the goals and objectives set out during this=20 meeting

------=_NextPart_000_0073_01C50AB9.7BAD2720--