> For the complete documentation index, see [llms.txt](https://austin.worldiaday.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://austin.worldiaday.org/people/matthew-eng.md).
# Matthew Eng
Team Lead for IBM Cloud Platform UX Research, IBM Design
Matt is a Research Team Lead for IBM Design. He has worked on projects for companies such as IBM, AT\&T, Ogilvy and Symantec. During these projects, he has conducted numerous research efforts that helped to align and focus stakeholders with diverse needs. His experience as a Team Lead for the IBM, led him to discover new techniques for bringing together multidisciplinary teams and internal stakeholders into the research process for quicker alignment.
When he is not untangling team priorities, he shares his lessons and experiences with other communities such as UX Australia, Nerd Summit, THAT Conference, Big Design, MidWest UX, and TEDx San Antonio.
On the side, he runs experiments with bicycles, old computers, and his dog.
Find him at:
* :link: Link:
* :linkedin: LinkedIn:
* X
---
# 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://austin.worldiaday.org/people/matthew-eng.md?ask=&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.