About Aaron

Aaron is a multi-disciplinary designer with a focus on product design. With over 15+ years in the field, he’s had the opportunity to work with agencies, consultancies, in-house and non-profits but currently prefers helping out smaller start-up teams. Some previous experiences include IDEO, Google, R/GA, Frog, Verizon, Citi, GE, Betaworks and Instapaper.

At the moment he resides in California with his wife Tina and two parrots, Taco and Burrito.

aaronkapor@gmail.com
209.604.7702

About This Site

This site is an evolving work-in-progress with selected samples from current and past projects. Equal parts process and final deliverables, it’s meant to showcase thought patterns that are unique for each project in order to create a true variety of work. It was coded and compiled with Jekyll.

Sans-Serif: Atlas Grotesk
Monospace: Atlas Typewriter

Other Locations:

Inventory

Matter / Workspace Create

The corresponding projects – Creating a Workspace and the Member Invitee flows – marked a new approach to user onboarding at Matter. The emphasis being the team instead of the individual. 
Matter is a service that allows professionals to send and receive quick feedback from their peers and collegues. Members are able to choose from an assortment of skills and set-up recurring feedback on a cadence of their choosing. Designing the feedback process was a fun challenge but this was one the few places where I was helping improve an existing design system, instead of owning it myself.
create flow
With that in mind, the social connection part of the process (connecting to Slack) needed to be reinforced in order for the creator, as well as the team, to get the most out of the experience.
create flow
As seen here, we made a point to reinforce the third/final step of the process which focused on sending (nearly requiring) invites via Slack or email.
create flow
From a UX/UI perspective, there was basically two appropriate solutions for how to handle the design. First was to use the flow-cards that were grandfathered into the code. The second was an inline option that worked with the side navigation.
create flow
The first option was preferred by the team mainly because it was already being used for our general sign-up flow which meant less drop-off risk – since it would be familiar to returning users – and less work for us being able to reuse code + assets.
On the other hand, I was partial to the second option for a variety of reasons.
  • The flow-card sequence sort of lives outside of the UX within the app and most users already associate it with signing-up.
  • The user POV was of a signed-in user – for them to click a CTA within the navigation and have them lead to a flow-card, would’ve of been confusing if not awkward.
  • The inline option keeps the context of the app while limiting page refreshes – which would happen with every step during a flow-card sequence.
  • From a usability perspective, the inline option is reassuring since it’s easier to opt out via the navigation.
In the end I was out-voted but with good reason. To be fair, when there is so many changes being made at the same time, it’s nice to take a more familiar (if not safer) direction when available.
Sketches: Round 1
create flow
create flow
Sketches: Round 2
create flow
create flow
For the Slack integration we tested two options for the default channel: “Create New” and “Choose Existing”.
create flow
Because of timeline and bandwidth, we decided on the second option for MVP – with an updated slack integration phased in later on.
create flow
Prev: Collection_1
Next: Workspace