> For the complete documentation index, see [llms.txt](https://handbook.renaissancelabs.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.renaissancelabs.org/programs-management/programs-schema/product-development-team.md).

# Product Development Team

<mark style="color:$danger;">**ROLES AND RESPONSIBILITIES**</mark>

<table><thead><tr><th width="112">Stage</th><th width="279">Responsibilities</th><th>Timeline</th></tr></thead><tbody><tr><td><strong>Planning</strong></td><td>Conceptualize program theme, develop materials (content, products, kits, or demos) aligned with objectives.</td><td>4–5 weeks before event</td></tr><tr><td><strong>Pre-Event</strong></td><td>Finalize product samples, presentations, or demo materials; coordinate with PM and PR teams.</td><td>1–2 weeks before event</td></tr><tr><td><strong>Event</strong></td><td>Showcase product/service, manage experiential engagement (demo booth, testing, presentation).</td><td>During event</td></tr><tr><td><strong>Post-Event</strong></td><td>Gather user feedback, document insights for product improvement, and update repository.</td><td>Within 7 days post-event</td></tr></tbody></table>

<mark style="color:$danger;">**CHECKLIST**</mark>

<table><thead><tr><th width="126">Category</th><th width="389">Task</th><th>Checkbox</th></tr></thead><tbody><tr><td>Concept</td><td>Align theme with event goal</td><td>☑️</td></tr><tr><td>Design</td><td>Create supporting materials (slides, product kits, demos)</td><td>☑️</td></tr><tr><td>Testing</td><td>Review product/experience readiness</td><td>☑️</td></tr><tr><td>Showcase</td><td>Execute demo or presentation</td><td>☑️</td></tr><tr><td>Feedback</td><td>Gather participant insights</td><td>☑️</td></tr><tr><td>Improvement</td><td>Update and iterate on learnings</td><td>☑️</td></tr></tbody></table>


---

# 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://handbook.renaissancelabs.org/programs-management/programs-schema/product-development-team.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.