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

# 1 DEFINE PROBLEM & VALUE PROPOSITION

![](/files/-LHd173QYc5Kf1uT-B7e)

Begin to frame the goals of your design by learning about your users and other stakeholders, the available technology, and the current practices to reach similar goals. Practice using the technology, in order to better understand its possibilities and constraints for design purposes. Consider various problems to solve. Evaluate and refine your ideas for a problem to solve through internal review and stakeholder feedback, in order to select a specific concept to target. Define the specific stakeholders, technology, and goals for a potential solution to your targeted problem.

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 IoT Product Research​](/project-internet-of-things/project-instructions/1-discover-and-define-problem/1.1-iot-product-research.md)     | 5 hours        | ​ | ​  |
| [​1.2 IoT Code Tutorials](/project-internet-of-things/project-instructions/1-discover-and-define-problem/1.2-iot-code-tutorial.md)​          | 10-15 hours    | ​ | ​  |
| [1.3 Project Ideas](/project-internet-of-things/project-instructions/1-discover-and-define-problem/1.3-project-ideas.md)                     | 3 hours        |   |    |
| [1.4 Competitive Analysis](/project-internet-of-things/project-instructions/1-discover-and-define-problem/1.4-competitive-analysis.md)       | 3 hours        |   |    |
| [1.5 User Research](/project-internet-of-things/project-instructions/1-discover-and-define-problem/1.5-user-research.md)                     | 4 hours        |   |    |
| [1.6 Value Proposition](/project-internet-of-things/project-instructions/1-discover-and-define-problem/1.6-value-proposition.md)             | 1 hour         |   |    |
| [1.7 Design Requirements](/project-internet-of-things/project-instructions/1-discover-and-define-problem/1.7-design-requirements.md)         | 2 hours        |   |    |
| [1.8 Interaction Storyboard](/project-internet-of-things/project-instructions/1-discover-and-define-problem/1.7-design-requirements.md)      | 3 hours        |   |    |
| [**1.9 Proposal Presentation**](/project-internet-of-things/project-instructions/1-discover-and-define-problem/1.9-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 dynamically by asking a question.

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

```
GET https://docs.idew.org/project-internet-of-things/project-instructions/1-discover-and-define-problem.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.