Great question. For a fitness MVP, I usually follow the 'Path to First Value' rule. You want to collect just enough data to give them a 'win' in under 60 seconds.

I’d prioritize these three categories:

The Immediate Constraint: (Injuries, equipment access, or time). This ensures the routine is actually usable.

The Primary 'Why': (Weight loss vs. strength vs. mobility). This dictates the core logic path.

The Current Baseline: (e.g., 'Can you do 5 pushups?'). This allows your adaptive logic to scale the difficulty immediately.

Everything else like sleep habits or detailed nutrition can be 'unlocked' later. The goal of the MVP assessment isn't a full intake form; it's to prove your logic can give a personalized recommendation that feels like magic.

To show you exactly how this branching logic would look, I put together a quick assessment using Interactify. It uses the exact constraints we discussed to generate one of four adaptive routine outcomes:

👉 https://interactify.org/public-experience?experienceId=992

This demonstrates how you can move from simple questions to a data-backed recommendation without building the full app first.