
We received the following feedback about the Design Document:
Concept description:
- Don’t get too technical about it yet
- Everyone, without technical knowledge, should understand this
Moscow method:
- What are these used for?
- Speakers for what kind of sounds?
- How many displays?
- Focus on functionality!
Concept sketches:
- Don’t put old iterations in here.
- We want to give a clear image of what’s being built in the first part of the document.
List of requirements:
Performance:
- Be more specific of the specs of the installation
- In what kind of timeframe are people using this?
Life in service:
- Keep in mind that kids can bash our installation too!
Target product cost:
- Doesn’t say anything
- We should DEFINE “Very low”
Transport:
- Same as “target product cost”
- HOW do we transport this and DEFINE “easy”
Size and weight:
- Put some things in here
- It doesn’t have to be accurate YET
Customer Journey Map:
- It looks complete
- We need more possibilities to find the installation. (flyers, social media, etc.)
- We need more entry points! (currently, it has 2)
- Maybe make it more graphical!?
- What is a success? The endpoint? Measurable success? HOW do we measure that? (coupons? forms?) Define “success”.
Morphological Chart:
- Put images in here
- Don’t limit yourself to the hardware
- ONLY THINK ABOUT THE FUNCTIONALITY FIRST
State diagram:
1st diagram:
- Think about how to turn it on
- (distance sensors?)
- The black dot represents the US turning the thing on. We shouldn’t be touching the thing after that
2nd diagram:
- Attraction Mode
- And play should be somewhere else
- Loop button is not a state
Deployment Diagram:
- Where is the computer?
- This should tell us, where do we use and what
@appleflapjc @izabelatyprowicz @oyvindknustadgmailcom @uselessmarkies @ruhrexp






