Notification wireframe review
👋 The background
We're planning to update the experience for notifications and to-dos within the product over the coming year.
Jeff and Thaina did some great problem validation research and we now have a pretty good idea of the "problem areas" with the current experience (video summary | research summary deck).
From talking to people inside and outside of the company, we heard the following:
- Opinionated to-do system design pushes users out of GitLab in favor of email inboxes.
- Users want to receive more notifications within GitLab – and to have more control over them.
In addition, we heard that:
- Users miss replies when only using to-dos.
- Team leads are afraid of missing important updates.
- Developers want to eliminate noise.
- Users triage notifications to create to-dos.
📝 The wireframes
We've put together a few wireframe sketches to start the process of trying to figure out how to address the problems with the current experience in the product. Here is a clickable walkthrough of the ideas so far. You can also see all of the wires in Figma.
📣 The ask
This is still very early stage ideation, and there are many details we'll still need to figure out. Also, none of this is set-in-stone! But, we wanted to share our early thoughts to get feedback on the following:
- Is there anything important that you wanted to see in these wireframes, that isn't currently present?
- Are any of these improvements more exciting/necessary to you than others?
- Is there anything that seems especially problematic or worrying about what's described?
- Are there things you worry we haven't thought about, that we should?
We're hoping to get feedback over the next couple of weeks. If you're able to provide feedback, please leave thoughts by May 31st.
Thank you!