> For the complete documentation index, see [llms.txt](https://docs.launchboard.app/cxd/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.launchboard.app/cxd/project-robotics/project-instructions/1-discover-and-define-problem.md).

# 1 DEFINE PROBLEM & VALUE PROPOSITION

![](https://4071112868-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LDgX-RpDDd3FfQb3yBa%2F-LSGMOxJdQ_bZOxlcydZ%2F-LSGMZbk172DT_5doctl%2Fphase-1-process.png?alt=media\&token=17647689-e7bb-4078-ad26-383e118655fc)

Conduct research to better understand robotics technology and its potential uses. Practice using your team's robotics kit, in order to better understand its possibilities and constraints for design purposes. Generate ideas for possible problems to solve with a robot, and then evaluate and refine the ideas, in order to select a specific concept to target. Research and analyze existing solutions for similar problems, in order to identify opportunities to design an innovative solution. Interview potential users and stakeholders to better understand their needs and expectations for a possible robotics solution. Define the value of your potential solution, and develop task scenarios to illustrate what your robot solution could do. Present your team's robot proposal to the class for constructive critique.

This phase of the project will require about 6-7 weeks to complete. Your teacher will identify the specific deadline(s) for the task assignments.

| Task                                                                                                                                   | Estimated Time | ✓ | ✓+ |
| -------------------------------------------------------------------------------------------------------------------------------------- | -------------- | - | -- |
| [1.1 Robotics Research](/cxd/project-robotics/project-instructions/1-discover-and-define-problem/1.1-robotics-research.md)             | 5 hours        |   |    |
| [1.2 Robotics Code Tutorials](/cxd/project-robotics/project-instructions/1-discover-and-define-problem/1.2-robotics-code-tutorials.md) | 10-15 hours    |   |    |
| [1.3 Project Ideas](/cxd/project-robotics/project-instructions/1-discover-and-define-problem/1.3-project-ideas.md)                     | 3 hours        |   |    |
| [1.4 Competitive Analysis](/cxd/project-robotics/project-instructions/1-discover-and-define-problem/1.4-competitive-analysis.md)       | 2 hours        |   |    |
| [1.5 User Research](/cxd/project-robotics/project-instructions/1-discover-and-define-problem/1.5-user-research.md)                     | 4 hours        |   |    |
| [1.6 Value Proposition](/cxd/project-robotics/project-instructions/1-discover-and-define-problem/1.6-value-proposition.md)             | 1 hour         |   |    |
| [1.7 Robot Task Scenarios](/cxd/project-robotics/project-instructions/1-discover-and-define-problem/1.7-robot-task-scenarios.md)       | 2 hours        |   |    |
| [**1.8 Proposal Presentation**](/cxd/project-robotics/project-instructions/1-discover-and-define-problem/1.8-proposal-presentation.md) | 3 hours        |   |    |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.launchboard.app/cxd/project-robotics/project-instructions/1-discover-and-define-problem.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.