do you think the opt-in UX degradation here is outweighed by the requirement? We could create a follow-up issue to design something better but, realistically, it may take us a long time to get to it.

@thiagocsf Can you help me understand what the risk is if we had this setting enabled by default? I don't fully understand the risk here (feel free to make a confidential thread if needed).

Hey @brendan777! Those are great resources to bring up, but out of scope for this design exercise specifically. I think we actually will be able to transfer many of the insights that come out of this (specific to how we can integrate AI into the MR review flow) to reviewing spec-driven development as well, but since that is an ongoing topic in it's earlier stages at GitLab, we will focus on the current MR review flow, where we know the bottlenecks and the areas of opportunity 🙇.

cc: @binduupadhyay @mvanremmerden

@alyssatrinh @leducmills @bonnie-tsang @brendan777 @munthank @mle 👋 Hey everyone!! Thank you for participating in this exercise. I'm super excited to have design, research, and technical writing counterparts all together. Feel free to poke around into the FigJam or other resources if you'd like, but we will officially kick this off starting 2026-03-23. You may have seen me assign you to child items... each have a date of when it will start and a "due" date, as some are async and some are sync events. I will ping you on each on the day it kicks off to remind you.

Questions, comments, concerns? Tag me and leave them in this thread please 👇 🙏 :

@binduupadhyay That would be amazing. I created child items for each step so it's easier to communicate async to the team, that includes one for synthesizing the workshop outcomes, which I assigned to you as well.

Any questions out of left field will probably be handled by the group or deferred

@mle Yes, anything outside of UX MR Reviews will need to wait until you return, or can be answered in the group's slack channel by someone. You can add me as secondary backup as well.

Hey @binduupadhyay! If you don't mind giving the FigJam one more review, then I can make any final edits to the issue + board and share this with the group who is participating, hopefully during the week of 2026-03-16. We will not run this until 2026-03-23.

Hey @mle! All of our Create and Package team will be out around this same time, so I ventured outside our teams for coverage. @clavimoniere very nicely volunteered to cover UX MR Reviews for Source Code during this time. Thank you, Chad!

cc: @alyssatrinh

@amandarueda We have one additional MCP to add, which is Office 365, for the same use case. Based on some market research, we determined both Google Calendar and Office 365 cover 96% of the users who are documenting their availability. Is it possible to add that into the list as well 🙏?

Another question outside listing of MCPs, will we be able to track how much usage each MCP gets?

@derekferguson please add more information if needed.

Talked with @mle about this, so my question was answered!

Auto is the safe layout setting -- this is the new default for any new user. Idea would be that we would remove the whole layout with that setting completely.

Interested to hear your thoughts @paintedbicycle-gitlab