> For the complete documentation index, see [llms.txt](https://annarbor.worldiaday.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://annarbor.worldiaday.org/people/james-kalbach.md).
# James Kalbach
Jim Kalbach is a noted author, speaker, and instructor in user experience design, information architecture, and strategy. He is currently Head of Customer Success at MURAL, the leading online whiteboard. Jim has worked with large companies, such as eBay, Audi, SONY, Elsevier Science, Lexis Nexis, and Citrix. In 2007 Jim published his first full-length book, *Designing Web Navigation* (O’Reilly, 2007). His second book, *Mapping Experiences* (O’Reilly, 2016), focuses on the role of visualizations in strategy and innovation. He blogs at experiencinginformation.com and tweets under @jimkalbach.
---
# 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://annarbor.worldiaday.org/people/james-kalbach.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.