Getting the Most from the Design Crit Session

Getting the Most from the Design Crit Session

My personal way to do Design Crit more effectively and getting the most quality feedback
October 15, 2021

. . .

Originally posted on my Twitter in Indonesian πŸ‘‰πŸ» Link to thread

‍

There is a new habit in my current role, in our design team there are twice times Design Crit session in a week. Once with Global design team, Once with JP design team. After 5 months, I found a good way to get maximum feedback and doing this session more effectively.

🧡 About seeking maximum feedbackπŸ‘‡πŸ»

‍

The most effective Design crit session is usually the session with the global team, with the JP team is usually only when someone wants to share something, if there isn't, we usually use the session to share knowledge, especially about JP users and all related to it.

‍

During my early months, I was nervous every time I got to shared my work in a design crit session. Because every week there are 2x, and in rotation. So maybe in a month, there would be 3 times per person. Always took a nap after the session, Being criticized is exhausting 🀣

‍

In my second month I feel unstructured, every time I got a session, I just threw the screen option and explained a bit. As a result, from the 30 minute slot, about 20 minutes it used for people to ask for context only. Then when I was asked, I discovered that the scope of the crit I was looking was too big. So it's not clear either.

‍

Finally, in the past month, I have tried a new method so that 30 minutes is more effective for feedback than for explaining the context. Try breaking it down one by one, the outline is like this πŸ‘‡πŸ»

‍

1. Background

Make the team understand the background of the project. Why does this project exist? Is this an improvement project or a new project? What is the current state if this is an improvement project? What are the intentions of each stakeholder and user?

‍

It's also important to know the scope we are working on and how far we want to get feedback for this session. Which parts? the flow? Or the layout? Or what? From what I experienced, the more specific the better. The feedback will straight to the point.

‍

2. Play problems/goals

What is the main problem with this project that you want to solve? Isn't there a technical limitation? What is its main purpose?

‍

3. Questions

Show Β the design solution we made and explain why we made it that way. Let's ask again, do you think the solution been able to solve the project's objectives? What can be improved? What's not connected with goals? etc

Those are the 3 main points.

‍

Because the time is only 30 minutes, so explain the 3 points above in a maximum 10 minutes. So what do you do with the remaining 20 minutes? ThisπŸ‘‡πŸ»

Make an MoM doc, we use Notion. Write the name of each person for them to write their feedback. After explaining the context, ask them to write their feedback for 5 minutes in the doc.

‍

After everyone is focused for 5 minutes to write their thoughts and feedback in the doc. The last 15 minutes are used to share the feedback. So here's the main session.

‍

It's will be a discussion session to give feedback, we can also clarify and discuss the written feedback. Or someone else can share another solution that they thinks is better. It's been an open discussion, just in the last 15 minutes.

‍

If the time is running out, the feedback is already written in the doc, so it's good, and you can clarify it to the person concerned in a separate forum or on Slack.

‍

Been a month of using this method, it's even better and the feedback quality that I get is increased in my opinion.

‍

End of Thread. Thank you for reading.

Giving back to the community!

No matter how much you know, there’s always more to learn. I'm humbled to be able to give back to the community through ADPList. It's completely free. Let's learn from each other here.

Book 30 minutes call for free!

Let's talk about portfolio review, brainstorming, career advice, or just casual sharing chat. ✌🏻