Attendance: Kaja, Manus, Zach, Olivia
Group leader: Olivia
Meeting Notes:
- reconsider features (weather, health info, implications of our actions)
- login and settings page - not functionalities
PROTOTYPE PRESENTATION FEEDBACK
- Overview
- body of text on screen
- give text loads of space
- do not center the text (left align)
- highlight keywords
the idea-> the product (the customer doesn't want to hear the brief over again and again, they want to hear the solution)I or We-> use third person (our product-> the product)- the order of travel options is important (carbon, health, time, money?)
- saving time display options
- saving 1 hour=1 unit of happiness
- money display options
- % of a holiday
- 1 coffee
- careful so it's not just for students
- how many zlotys/czech crowns did you save
- Aims
- has to be measurable (
time/money management) - the rest are the aims of the product
- not just an app to display data -> make it interesting
- gamification
- target audience 17-65
- don't say
I think so - do more testing, more feedback from different age ranges
- Background
existing solutions-> they are not based on the brief- Nike run app
- add 2 more apps
- don't put details on the slides OR spread into 2 slides (2 apps on each slide)
- be clear how you are raising the bar
- Objectives
- that slide is fine
- don't use templates or clipart (if it's easy to find it somebody else is already using it)
- Wearables
- that slide is fine
- User engagement
- make sure everybody knows what's going on on every slide/aspect of the app
- work as a team
- Survey
- too small -> make pictures bigger, one per slide
- make sure you know what you want to show when showing this information
- age/gender - fast slides, don't waste time on those slides
- How long of a walk... - too long -> reword this question
- make sure everybody understands the conclusion of all the data
- carbon question
- why is it an important question?
- make sure to use the data creatively
- how meaningfully implement the data -> what are the actual consequences of people's behaviour?
- how to show that?
- carpool
- did the respondents have cars?
- PROTOTYPES
- Phone screen prototypes - only "prototype"
- have contrast on the pictures, scan them
- keep prototypes simple and consistent
- list all the functions beforehand (primary/secondary) -> makes it easier to design
- also consider how do we get the info
- travel options
- where are you going
- feedback
- consequences
- goals
- navigation
- get more prototypes based on the feedback, test them
- don't focus on settings, log in page
- no maps on a watch (too small) -> symbols...
- on and off button for directions?
- what happens if a user chooses to walk but then jumps in the car?
- you don't have to show the thought process in the presentation - you can show that on the blog
- -> choose and maybe rescribble the main things for the presentation
- use scanner for presentation
- Next step
- key features
- tree - simplified data
- what do you want us to know?
- why a tree?
- pick your own tree
- but some grow faster, some take ages to grow...
- explore the idea more
- you might need to start from scratch
- for the report -> just keep writing, you can always shorten it then
- To do
- have a meeting
- assign tasks
- list all features of the app
- do more prototypes (possibly from scratch)
- test them
- fix presentation based on feedback
Comments
Post a Comment