> 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/nisreen-salka.md).

# Nisreen Salka

<img src="https://content.gitbook.com/content/w7KdqMH0cA13S7iLAgFF/blobs/G55ifXdEuGUZcNoQUKL7/Nisreen_Salka.jpg" alt="Nisreen_Salka" height="180" width="180">

Nisreen Salka graduated with a dual degree in business administration and screen arts in May 2016, followed up with a masters in human-computer interaction in May 2018 from the University of Michigan School of Information. As the lead product designer for the Mobility Analytic Products & Services (MAPS) department at Ford Motor Company, she collaborates with end users to design applications that leverage mobility data. She has presented at Ann Arbor World Information Architecture Day on the powers and limits of design systems in 2017, and on dark patterns in 2018. In her free time, Nisreen enjoys digital photography, experimenting with new recipes, and talking continuously for long periods of time.

### As a speaker

[Data Transparency: Revealing the Invisible](https://worldiaday.org/talks/data-transparency-revealing-invisible)

[Dark Patterns](https://worldiaday.org/talks/dark-patterns)


---

# 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/nisreen-salka.md?ask=<question>&goal=<user_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.
