> For the complete documentation index, see [llms.txt](https://hugs-solutions.gitbook.io/hugs-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hugs-solutions.gitbook.io/hugs-platform/introduction/the-problem.md).

# The Problem

The expectations of Millennials and Gen Z workers results in significant challenges for business leaders. The main problem is **the lack of strategy and tools to support this new approach towards task execution**.

*"93% of CEOs say they need to change their talent strategy, 61% don't have a plan for it"*

### **Businesses still have several obstacles to overcome**

* Limited access to pools of supply and demand
* Lack of easy-to-join and easy-to-use platforms
* Lack of trustworthy reputation systems
* Need for better sourcing and matching infrastructure
* Need for data quality assurance

Without the right infrastructure and algorithms in place, businesses will continue to struggle to keep up with the changing demands of the workforce.


---

# 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://hugs-solutions.gitbook.io/hugs-platform/introduction/the-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.
