# Step 1 : Analysis

## Steps ⚡:

1. Gather Requirements
2. Always ask for clarification. Do not assume your assumption is correct
3. A solution designed to solve the problems of a young startup is different from that of an established company with millions of users. Make sure you understand the requirements
4. Ask Questions

## **Examples of asking questions 🔍:**

1\. What specific features are we going to build

2\. This a mobile app? Or a web app?

3\. What are the most important features for the product?

4\. How fast does the company anticipate to scale up?

5\. What are the anticipated scales in 3 months, 6 months, and a year?

6\. What is the company’s technology stack? What existing services you might leverage to simplify the design?

7\. How many users does the product have?

{% hint style="info" %}
Good muck interview to explain how to ask questions to do analysis
{% endhint %}

{% embed url="<https://www.youtube.com/watch?ab_channel=Exponent&v=NtMvNh0WFVM>" %}

### ref:

![](/files/Eyp02KpuUjYZQVBlEwE6)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://abdulrahman-1.gitbook.io/my-digital-garden/level-2-system-design/step-1-analysis.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.