Currently, I create a survey builder where the user is able to preview all pre-defined questions within the database and based on this user chooses what type of survey would like to create. Based on the research this functionality is really important to the user to help him understand what type of survey wants to create and what questions wants to include.
Therefore, while entering the survey builder all questions should be visible (based on user research + project manager requirement). BUT to start creating a survey user has to choose the survey type (Questions within survey types can't be mixed up therefore it's crucial to fill in this information before survey creation).
I have created a filter bar where the survey type dropdown is equal to other filters. Additionally, I added a communicate to the user in the bar to highlight that the survey type has to be chosen.
However, this is not the best UX. I'm struggling a lot with it and would love to hear your input on how to structure data with mentioned above dependencies...
Maybe I should highlight the Survey type filter more? I can't though force user to choose the survey type before entering the survey because than he won't see all the questions...
Here is initial prototype: