Elizabeth Chesters 🇪🇺 Profile picture
UX Researcher & Designer in Germany 🇩🇪 | HCI MSc graduate @cityuni_hcid | #CFGOTW

Sep 17, 2020, 11 tweets

Over the last week I have 2 collaborative workshops between design, tech and product - which went well!

Here's what I did! ✏️ [A thread]

#uxdesign

The feature is how we identify duplicated objects, which is complicated for tech and users.

I did explorative research before the workshop, so we had general insights into user expectations and the impact of the feature etc.

The goals of the workshop were:
- reduce the number of meetings
- discuss technical algorithm decisions
- create feasible designs ready for testing

Most people were remote, 1 dev + me were in office!

To prepare for the first workshop I collated a list of user requirements and questions for tech to consider, e.g. supporting accents (é, ü, ue etc.) and working offline.

The questions were sent to the team before the first meeting, so that they could be answered beforehand.

The first 1hr workshop included back-end, front-end, design and product.

The 1st half was discussing the questions sent beforehand so design and tech knew of the technical influences. 2nd half was creating use cases; (affordance, dealing with duplicates, error handling etc.)

We ended with a whiteboard of use cases designs needed to cover and limitations to consider.

Everyone was given homework to come up with *quick* sketches on how they pictured the feature looking.

The sketches were posted on Slack ready for workshop part 2!

Part 2: product, tech and design each presented their sketches and ideas.

I noted down core ideas which had been included (e.g. use a folder, use a banner)

For each design, I said why/why not based on user insights.

In the end, I started at the start of the user flow, drawing on a whiteboard how this would look in the product.

I sketched different versions based on ideas. I did so on a whiteboard while my team watched in the room and online. Constantly asking for clarification and input.

We noted down assumptions and questions for users.

The product gave the yes or no input on decisions. Tech said how feasible each idea was - making the ideating *a lot* quicker!

We took photos of every idea and shared them in Slack.

Finally, I took each idea and built them into a prototype on Axure. I took the questions we noted down to create a discussion guide.

Both the prototype and discussion guide were ready for testing with users the next day!

Originally, we were going to split people into teams to ideate, but technical discussions in part 1 took longer than anticipated.

Learning: Get devs to speak to each other to be on the same page before the meeting!

Share this Scrolly Tale with your friends.

A Scrolly Tale is a new way to read Twitter threads with a more visually immersive experience.
Discover more beautiful Scrolly Tales like this.

Keep scrolling