> For the complete documentation index, see [llms.txt](https://wiki.elsewhere.team/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.elsewhere.team/the-people/project-experts/rikke-koblauch.md).

# Rikke Koblauch

Rikke is a freelance UX designer and researcher with almost 10 years of experience in building digital products and services. She's a Hyper Island alumni and has been working with big global brands and small startups within mobility, retail, healthcare, the public sector etc in Copenhagen, Amsterdam and London. She's been running my own tech startup and been travelling the world to teach and talk about user centered design.

We talk to Rikke if we need

User research - Getting to know the needs, pains and expectations from end-users

Synthesis and analysis - Identifying patterns, insights and opportunities from the research

Workshop and ideation facilitation - Turning opportunity into ideas

Prototype and experiments - Turning ideas into measurable prototypes

User testing - Putting prototypes and products in the hands of users to validate

Interface design UX & UI - Delivering designs and working closely with developers to ensure the best user experience

[See her on LinkedIn](https://www.linkedin.com/in/rikkekoblauch/)


---

# 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://wiki.elsewhere.team/the-people/project-experts/rikke-koblauch.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.
