> For the complete documentation index, see [llms.txt](https://spaceship.guides.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spaceship.guides.gov.sg/validate/choosing-how-to-validate.md).

# Choosing how to validate

Your prototype's **Analytics** and **User Interviews** tabs gives you four ways to validate your ideas.

<figure><img src="/files/l5aBMWnL7EOcC74y4aIa" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="307.90234375">Method</th><th>Tells you</th></tr></thead><tbody><tr><td>Analytics - Data &#x26; Events</td><td>What users do, at scale</td></tr><tr><td>Analytics - Surveys</td><td>What users think in the moment</td></tr><tr><td>User Interviews - Simulations</td><td>Whether users can do what they want to do</td></tr><tr><td>User Interviews - Recordings</td><td>Why users do what they do</td></tr></tbody></table>

### **Where to start**

**No users yet?** Start with user interviews. You can run a simulated session with a persona in minutes, before you bother anyone real.

**Just published and getting traffic?** Turn on data & events to see what people do, then add a survey when you have a hypothesis to test.

**End of a round?** Check your prototype report to share what you found with stakeholders.

### **A few things worth knowing**

* Analytics and user interviews answer different questions. You usually want both!&#x20;
* Run a simulated interview before a live one to shake out the obvious issues.