Team Meeting Notes 03
September 28-30 Team Meetings
Team Meeting Objectives
You’ve completed the 6 ideas milestone. Now you will prepare for the upcoming sketch model review. For this lab we are still ideating! Your team will work towards identifying four promising concept direction or variations within the team’s assigned subtheme area.
You should also look ahead to team meeting 4 since the sketch model review takes place Thursday evening next week!
What's due
Individuals
- Write down (one line) on at least 20 ideas - often students write (many) more. These ideas should be related to your subtheme which will be sent out on Monday afternoon after 6 ideas.
- 2 of these concepts should be further developed (with research on feasibility, consumer etc) and sketched. The sketches and explanations should be drawn or copied on 2 separate pieces of paper for pinning up in your team meeting.
- A milestone reflection should be written in your design notebook - this is your personal account of how you think the first milestone went and we require it after each milestone.
- Note - your physical design notebook should also contain the research/planning for 6 ideas (any additional work not included in the poster or appendix). The preparation and your milestone will be reviewed by your team instructor during your team meeting this week or next week depending on instructor preference.
Team
Continue to populate the DHF, prepare for Sketch Model Review next week
Preparation Before Team Meeting #3
The system integrators should prepare an agenda for the team meeting and make sure that the name cards are set up on the table before the start of the team meeting.
Make sure that you understand the goals of the sketch model review.
Review the written feedback received from the 6 ideas presentation. You will probably want to further distill this into key points that will allow you to effectively review and discuss issues raised, while being careful to not overlook potentially valuable suggestions. Having the key points highlighted on a page or two and printed for use in the team meeting can help the discussion.
Each team member should write down many (we suggest at least 20 and often students do (many) more. You should further develop at least two concept variations within the team's assigned idea area. While the timing is very tight for the Tuesday teams, it is really important to get the exploration process restarted before your team meeting. Prepare the concept variations on individual sheets of paper so that they can be pinned up, as was done in the first team meeting, but the ideas should be more complete, focused, and researched (at least similar to the 6 ideas posters). Make sure that you have done enough research to be confident that the ideas have a degree of novelty and competitive advantage, and that there is a real, tangible need motivating the concepts.
Teams should organize into appropriate task forces and begin gathering additional information relevant to the sub-theme for your team ASAP. This might include customer needs, market data, and observation. Be prepared to present a short summary to the team at the beginning of your team meeting. Tuesday teams will probably need to do this as part of their team meeting time.
Team Meeting #3 Activities
Begin with a reflection upon your effort in the 6 ideas presentation, its outcome (reviews), and the team's idea area. This should be a brief discussion. Have each 6 idea task force take roughly 5 minutes to summarize their findings.
Pin up the 2 NEW concept variants that each team member developed when you prepared for this team meeting. Discuss each other's ideas. If you feel that the variants from the pinup are not adequate, spend additional time brainstorming as a group.
Establish relevant selection criteria and pick four concept variants for further development, using a method such as a Pugh chart.
Divide your team into task forces to work on the four concept variations in preparation for the sketch model review, which is next week. You will need to further develop the idea, prepare informative sketch models, conduct simple tests, and refine customer needs, benchmarking, and market data. Ideas need to be researched so that you have clear needs connected with real users, and so that you understand what competitive products may exist.
Review the What to Sketch Model? handout to help you decide what to sketch model. You may also want to refer to the sketch modeling demonstrations on designy (cardboard and foamcore, polystyrene foam).
Use the remaining time to work.
See tutorials for next week -
Monday:
7-8pm: Story Officer Training
Tuesday
7:30-8:30pm: Tutorial: Identifying and Understanding Users: Part I
8:30-9:30pm: Taking the bull by the horns: Setting up your team dynamics (yodas, SIs)
Wednesday:
12 noon: Tutorial: Ombuds office - a confidential and independent resource
Thursday:
12 noon: Tutorial RFP (finance officers)
8:30-9:30pm: Yoda Workshop