This is excellent, Ryan. I and a colleague Erin Taylor (Canela Consulting) are writing an open-access report on building healthy research cultures as one tool to help advocates within their companies. I have noticed how this tension between fast and slow research cultures clash when it comes to the prod. dev. cycle.

1. Is agile/scrum the only thinking and doing framework in teams? Is there space within the agile for research? Or is it a case of the tail wagging the dog situation?

2. Should we then formulate our own "slow" research framework (or something more on-point as slow seems to be akin to no progress!) to complement agile? If there is, how can it fit?

I am currently obsessed with this topic as I've recently talked with a tech lead that shared with me that research should fit agile. We shall be hosting online ethnoborrel meetups in January and February 2021 tackling these very same issues here in NL.