# Interview Guide

Since process updates can take different shape or forms, it's important to be clear about their purpose and content. Here's a basic set of questions you can ask your interviewee:

#### Process updates

* What is the purpose of the update? What is the desired outcome?
* What could happen if the update is not in place?

#### Functions and workflows

* What's the goal/purpose of the function?
* What are their inputs and what are their outputs?
* What can potentially go wrong when doing the work?
* What are some specific requirements, and constraints?
* What's the exact workflow and process? What are specific tools used during the process?
* What should people read first and what can be hidden away?
* For this function, what is the easiest thing to get started with?
* Is there a clear beginning and end of the project?
* Are there any references you personally use?
* Are there any helpful resources for those who are just beginning?

{% hint style="info" %}
Take into account that you will be entering the transcript into GPT. Keeping the conversation on track by sticking to one question at a time will help when getting GPT to generate content.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.deepwork.studio/teams-departments/operations/roles/documentation-writer/interview-guide.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
