BACK TO Milestone 1

Milestone 1

Feedback Summary

We received varied feedback on Milestone One. Some people liked our theoretical approach to the project and noted that we did a good job explaining the existing problems with meetings. Most people also liked our website, but others indicated that we need to do more work on the visual aspects and try to avoid overflowing the page with text. Overall, we still have a lot of space for improvement. One of the major problems we had was that we failed to propose a clear solution and direction, which made our project scope appear vague and unrefined. Another problem was that some people questioned the need of such meeting software and asked if it will be able to compete with existing products. A few people also commented on our presentation skills. Students thought that some team members stood too far away from the main speaker and felt that holding things during the presentation was not necessary. The notes from each critique submitted our listed at the bottom of this email.

Notes

Here’s what I liked about your milestone

  1. CSCW & Organizational Psychology
  2. Thought about holding a meeting outside the meeting
  3. Good explanation about existing constraints
  4. Liked the theoretical focus to the project

Here’s where I felt there’s room for improvement

    Not a clear solution
  1. No need to talk about contextual inquiry
  2. Need a specific direction
  3. Should consider meeting without technical hardware(Meeting without a laptop?)
  4. The superiority comparing with existing meeting software
  5. (about presentation) distribute better around screen so no team members look marginalized, don’t bring a folder unless you need it
  6. (about presentation) Stand more forward, only the speaker was prominent
  7. Should explain without Techsmith’s ideas
  8. Should focus on a certain type of meeting
  9. Problems of meetings should be supported by user research
  10. Didn’t need to tell about the communication covenant in the short presentation
  11. Should address the strength of the project solution and why it will be better than other existing tools
  12. Should focus more on the meeting scenario but not too much into the technology
  13. Project scope should be more refined
  14. Should focus more on the specific subject matter of the project (meeting matters) rather than the process
  15. Very broad solution
  16. Name catches attention
  17. Could solution fit in with other more general software?

Here are my comments about your website

  1. Plain but functional website
  2. Move logo
  3. A bit text heavy
  4. Visuals didn’t seem to relate to the project

Milestones

Initial Meeting with Techsmith