That's the problem that can be witnessed in software development teams too. Analysts are over-represented in our craft so there's a real risk of analysis paraly

That's the problem that can be witnessed in software development teams too. Analysts are over-represented in our craft so there's a real risk of analysis paralysis. A potential remedy is a more impulsive type on the team who prefers to start playing with the problem. You should be careful not to stop him from doing that. If there's no such a person then someone, preferably a leader, should move on to prototyping if the project got stuck. All that applies to individual software development too. If you see no progress because you are constantly analyzing then start prototyping.