2 ms·

I agree, but I think the constraints are doing all the work in your statement. I've just been in the position many times in my own career where product managers

I agree, but I think the constraints are doing all the work in your statement. I've just been in the position many times in my own career where product managers are pushing to get something, anything out there so they can get "real user feedback" And the V in MVP goes right out the window. I was responding in particular to "a quick prototype in front of real users gives you far better information than any amount of internal brainstorming." Maybe it's just a semantic difference but to me "quick prototype" doesn't imply look great, work great and handle all edge cases. Perhaps you meant quick prototype that looks great, works great and handles all edge cases but I think that implication is often lost on product people. They want something deployed and don't care if all of the engineering team's fussy edge cases are handled.

tchaffee 6y ago
> I agree, but I think the constraints are doing all the work in your statement Yep. > I've just been in the position many times in my own career where product managers are pushing to get something, anything out there so they can get "real user feedback" Me too. There are a lot of bad product managers and even companies out there. But I have worked with great ones occasionally, so it's worth describing the ideal so we know what we are aiming for. > I was responding in particular to "a quick prototype... You're right that I need to qualify that because it more often means what you rightly assumed based on your experience. I guess I'm just so in the habit of demanding that we reduce scope that I too easily forget that "quick" more often means the compromise was quality.