I'd pick 'Both simultaneously' - seems like a balanced approach, but how do you prioritize when resources are limited?

I'm curious, what kind of product or service are you planning to launch? That might change the order of importance for MVP vs team.

Validate idea first, in my experience, it saves a lot of time and resources down the line.

I'd pick 'Validate idea first' if it were an option - often a solid concept can guide both MVP and team building, but unsure if that's an oversimplification?

We prioritized a strong MVP and had to rebuild our team from scratch later due to initial mis-hires. Would love to hear about experiences where team came first and worked out well.

I'd pick 'Both simultaneously' - hard to imagine one succeeding without the other, especially in a competitive space. How do you see them reinforcing each other?

I'd love to see 'Iterate with a small team and minimal viable product' as an option - often that's the most resource-efficient way to start.

I'd love to see 'Iterate based on user feedback' as an option - often that's what informs both MVP and team build.

I'd pick 'Both simultaneously' - having a solid team can actually help you build a stronger MVP, and vice versa. What are your thoughts on the order of operations for assembling the team and MVP?