Focus on what you know. Make sure your team includes at the very least (in no particular order): - Someone who is part of the target audience. They should be a

Focus on what you know. Make sure your team includes at the very least (in no particular order): - Someone who is part of the target audience. They should be able to provide your team with a good idea of the features you absolutely need to get started, and might be a good source of ideas for differentiating features. - Someone great at manual quality assurance - user testing, poking the system through the laughably complex and diverse devices we all use, and ideally translating manual test scripts to automated ones, where possible. Lots of software has massive amounts of features hidden behind a broken UI. - Someone great at UX, in particular related to the type of UI you are building. Web UX is not the same as desktop or API UX. - Someone great at automated quality assurance - TDD, CI/CD, linting, fuzzing, code & user metrics, telemetry, performance and stress testing. They keep your progress from stalling over time. - Someone trusted by the entire team to plan, direct and arbitrate. They avoid double work, keep the team going in the same direction, and keep interactions human rather than textual (which has far too low bandwidth to avoid conflict in the long term). For most features you'll want all of these involved in the planning at the same time (and place, if at all possible), to get the most out of everyone's time. They'll all be able to see how the work fits together and will provide unforeseen insights and questions crucial to building an excellent product.