*** Before we get back into my list of development principles for Biotech data teams, I need your help. Or more specifically, I need a name for the principles. Please fill out this form to vote on a name or suggest a better one. If you’re the first to submit a name that I go with, I will thank you on this newsletter (unless you don’t want me to). ***
May I suggest that you are laying the groundwork for the other MVP, the 'mvp'. A search for "Minimally Viable Product" ~ 50K hits. A search for "minimally viable process" less than two hundred.
The initial Requirements Gathering for a product can inadvertently fossilize what should be a living objective. Agile seems easiest and is the perhaps the most dangerous when there is only one degree of freedom, that of the data team . You're right that ongoing "deliberate empathy" is helpful. The wet lab and the data bench might be lacking rapport, they likely do not share nuanced vocabulary. People do tend agree to hazy notions, and need a mechanism to review and refine them. Incrementally.
May I suggest that you are laying the groundwork for the other MVP, the 'mvp'. A search for "Minimally Viable Product" ~ 50K hits. A search for "minimally viable process" less than two hundred.
The initial Requirements Gathering for a product can inadvertently fossilize what should be a living objective. Agile seems easiest and is the perhaps the most dangerous when there is only one degree of freedom, that of the data team . You're right that ongoing "deliberate empathy" is helpful. The wet lab and the data bench might be lacking rapport, they likely do not share nuanced vocabulary. People do tend agree to hazy notions, and need a mechanism to review and refine them. Incrementally.