About design vision

[mikegianno]

Again triggered by an article shared by @glezos (don't recall the link) I present you an initial exercise on design vision. Design vision is supposed to help in guiding our work moving forward.

For the exercise I used elements found in this article: https://medium.com/google-design/design-for-a-vision-a4565107e079 along with reviewing our product interfaces.

Generic vision: Be like Batman's Alfred or Ironman's Jarvis, users know that TX is there to answer any questions they have and can offer tons of help without taking over for them.
Our design should be:

• Readable: users should clearly understand what’s going on all over the design, interactions are clear and readable as to what the result will be

• Promote content, don't interfere with the actual information: information is standing out against any visual aid

• Have priority & structure: highlight most important parts, separate noise from value, provide structure on parts

• Feel Cozy & Welcoming: be friendly and promote interaction with designs, don’t look hostile and overwhelming


• Interacting with the user: personalise experience to each user and try to adopt to her changing needs, enhance user’s abilities and help her get better at what she does, always reply to each request

Circles exercise (Why/How/What):
WHY
Let people own their workflow
HOW
By interacting with a assistive interface
WHAT
To perform the tasks they have in mind fast and move forward

Again, this is a starting point for discussion! @dontpanicgr @codegaze @yiotaz (can't find Antonis here...please add)

[mikegianno]

A good article on "Interacting with the user": https://www.invisionapp.com/blog/personalize-design/

we call this designing for situational relevance. What we mean by this is a value proposition meets a need, solves a problem, or fulfills a job to be done at the time it’s actually relevant

Perhaps "personalize" could be dropped from the description.