This section is about to how I design products and services. It’s a big one. I created it based on our years of experience, a few screw ups, and never wanting to screw anything up again.
InVision Workflow lets us see how a project is coming along
Assemble the teams
Allocate tasks & reminders
Manage assets & documents
Manage timelines & people
Build style guides
InVision is visually stimulating and easy to use. Better than most project management tools, IMHO.
I review the client’s data and turn it into actionable items
I turn those into sketches
Which I capture on my iPhone
And upload them to InVision for desktop prototypes
Or Marvel for mobile prototypes
Comments like these used to come over email. Not anymore.
InVision allows teams to collaborate in real time. It doesn’t matter where you are, if you have an internet connection we can collaborate instantly. No more GoTo meetings or lengthy email chains.
Teams can comment on documents, tasks and workflows
Prototypes, colour palettes, gestures, and images
And sorts of data can be reviewed & optimized collectively
This is Mary. She’s a day trader we recruited to test a product we designed for desktop.
I love InVision. That’s pretty clear by now. It gets even smarter when it comes to usability testing. At the press of a button (literally, press a button), I launch Lookback, a usability tool that integrates seamlessly with this process. All video, audio and screen gestures are captured. Feedback starts appearing in our Slack feed for the team to see.
It’s one of those apps #Iwishicameupwith
Tree testing provides quantitative data for how people perform tasks. If you like numbers, you’ll love a tree test.
The results tell us how to improve the taxonomy and structure of the information.
InVision Boards allow our designers to organize their thoughts and share with the team.
With InVision our visual designers lay out how the product will look, even as our UX designers are out testing and optimizing. This is a part of agile I love.
My teams work in tandem with round 1 of testing because we have to start somewhere. Things like fonts, colours, buttons, links… every product needs these. My approach uses data to inform the design, giving my teams a head start and allowing everyone to collaborate.
Because it’s the right thing to do.
In round 1 my teams check if the experience is working for the intended audience. In agile circles, this is known as a ‘proof of concept’. It’s kind of like that.
However, when content and visuals are applied things can get weird.
Some product owners feel they’ve learned enough from round 1 of testing but fail to remember that content changes everything. So I test the experience the way people ultimately intend to use it: with real content.
Round 2 is for real. It’s the last chance you have before making any product’s first impression with the real world.