> For the complete documentation index, see [llms.txt](https://process.mad.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://process.mad.co/project-work/design/key-design-team-roles.md).
# Key Design Team Roles
## Head of UX & Design
This person will know the project since the pitching stage, contractual and scope of work. Their main role is to lead the business requirement, overall experience and define the problems that project want to solve. He will be involved in the design thinking process, design sprint and workshop, once all of those problems solving workshop are done, and client and Mad agreed with the challenge that we want to solve with this project, the head of design will hands off a bit from the project and give the free hand of solutions finding, to the Product designer. Once the project hand over to the product designer, the head of UX & designer will work on deliverable timelines, communicate to his team, oversight the quality of work and outcome from a high level point of view.
## Product Designer
Product Designer will be bring on the project at the Kick off meeting. He main role is to work on the solution findings and lead the whole project not only as a UX/UI designer but also product designer. Work on finding the solution that both will solve the customers experience but also match with the business requirement. He/she will work on building the new proposed Customers journey to improve from the existing experience and solve the paint points. Product Designer act as the Lead of the project. He has the right to take any directions of kind of solution as long as it will match the problems statement that was define by the Head of UX and business requirement.
---
# 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://process.mad.co/project-work/design/key-design-team-roles.md?ask=&goal=
```
`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.