Talk:Technical decision making/Technical Decision-Making Process Retrospective and Consultation plan

Why "retro"?
Ironically, if the goal is to bring in as many contributors as possible, etc., use of jargon like "retro" might be a mistake. I know it's short for "retrospective", but beyond that I had never heard of this term being used in a business/management context. I looked it up, and apparently it's an Agile management term, used to refer to discussions about just-completed tasks - like a "post-mortem" but shorter-term, maybe. I'm not even sure if that concept applies here - obviously, discussions about what worked and didn't work in the past are relevant, but that's not the only thing that's relevant. Why not just call it a "discussion", or something along those lines? Yaron Koren (talk) 18:31, 31 March 2023 (UTC)


 * I changed the one instance of "retro" on that page to "retrospective". We could probably come up with a couple sentences explaining what "retrospective" refers to, for people who are not familiar with the term. KHarlan (WMF) (talk) 18:38, 31 March 2023 (UTC)

It would also help to reduce the use of corporate jargon and style, starting from the off-putting Title Case, which makes this look like a non-inclusive space and process. Nemo 18:21, 3 April 2023 (UTC)

Roles
There are two separate lists of roles, both naming someone with "executive ownership", but with a different description of the role and a different name. Are the two things compatible?

It's not clear to me who's responsible for digging up the reasons and objectives the current process was set up for, in order to assess whether they were achieved and whether there was an improvement compared to the status quo ante (i.e. the Requests for comment process and the ArchCom/TechCom as we knew it in 2014/2017/2020). Nemo 18:19, 3 April 2023 (UTC)


 * Thanks for pointing out the inconsistency, I have corrected it.
 * The intention of the retrospective is to understand the pain points and the areas to improve the current process. As part of that process people will be able to make suggestions that may be from previous processes. The core team is responsible for collecting the information and analyzing it. KChapman (WMF) (talk) 11:58, 4 April 2023 (UTC)
 * Thanks. I understand where you're coming from but I would hope for the retrospective to have sufficient resources for an assessment of at least the more recent changes. If that's not possible, the process should take into account the risk of survivorship bias, recency bias and selection bias in the information collected. Nemo 15:43, 5 April 2023 (UTC)
 * We will be asking for feedback on the questions that are asked in the retrospective. There will be an opportunity to suggest specific ways to get input so that we can improve how technical decisions are made regardless of what iteration of decision making the improvements come from. KChapman (WMF) (talk) 15:23, 12 April 2023 (UTC)

Timeline
So its been two weeks. While I appreciate that these things take time, and that this is also annual plan season, it'd be nice if a rough proposed timeline of when various steps in this process will happen could be posted (With the understanding of course that the timeline may very well change depending on how things go). Bawolff (talk) 00:42, 14 April 2023 (UTC)