> For the complete documentation index, see [llms.txt](https://llm.theparley.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://llm.theparley.org/starting-to-use-it/lunch-and-learn-series/week-3.md).
# Week 3
### Parley for Research Discovery + AI Synthesis
#### MONDAY — TURNTABLE TEAM
**Part 1: Parley Navigation Tutorial (0-30 min)**
* Introduction to [Parley:](/what-is-parley.md) what it is and how to search it
* Finding researchers by topic, expertise, or center
* Understanding research profiles and comparing capabilities
* Common search strategies
* Demo: instructor walks through a search example
**Part 2: Strategic Research Matching (30-60 min)**
* **Activity**: Given an external partnership request:
* Participants use Parley to identify 3-5 aligned researchers
* Compare their strengths, overlaps, and gaps
* Use AI to create a one-page strategic recommendation with talking points
* Work individually or in small groups
* Share findings and AI-generated recommendations
* Practice checking AI accuracy against Parley data
* Instructor provides feedback on search strategies and synthesis quality
**Outcome**: Parley + AI becomes a decision-making tool for partnerships.
#### TUESDAY — BOOMBOX CREW
**Part 1: Parley Navigation Tutorial (0-30 min)**
* How to use Parley effectively
* Search techniques for finding the right researchers
* Reading and comparing research profiles
* Tips for accurate searches
* Live demonstration of a typical search workflow
**Part 2: Expertise Mapping & Documentation (30-60 min)**
* **Activity**: Given a research domain:
* Participants use Parley to identify 4-6 researchers working in similar areas
* Build a comparison table (expertise, center, focus areas)
* Use AI to rewrite complex bios into clear internal summaries
* Work on real scenarios individually or in pairs
* Share comparison tables and summaries
* Verify AI summaries against source profiles as a group
* Discuss accuracy checks and quality standards
**Outcome**: Parley + AI clarifies research roles and responsibilities.
#### WEDNESDAY — LIMEWIRE LEGENDS
**Part 1: Parley Navigation Tutorial (0-30 min)**
* Parley overview and search fundamentals
* Matching inquiries to researcher expertise
* Understanding profile information
* Efficient search workflows
* Walkthrough of common use cases
**Part 2: Communication & Routing (30-60 min)**
* **Activity**: Given a research inquiry from a partner or funder:
* Participants use Parley to match inquiry to 2-3 appropriate faculty
* Draft a professional outreach email using AI
* Create a simple summary of each researcher's focus for stakeholders
* Complete the full workflow hands-on
* Share emails and summaries with group
* Group review: tone, accuracy, and clarity checks
* Practice verifying details before sending
**Outcome**: Parley + AI supports fast, accurate communication and routing.
#### THURSDAY — SPOTIFY SQUAD
**Part 1: Parley Navigation Tutorial (0-30 min)**
* Introduction to Parley and why it's useful
* Basic search strategies
* How to interpret researcher profiles
* Finding who handles specific research areas
* Step-by-step demo of typical searches
**Part 2: Orientation & Resource Building (30-60 min)**
* **Activity**: Create onboarding resources:
* Participants use Parley to answer "Who handles X research area?"
* Turn 3-4 researcher profiles into simple FAQs using AI
* Create a "Who to Contact" quick reference guide
* Work individually or in small teams
* Share and test resources with each other
* Verify accuracy and usefulness
* Refine based on peer feedback
**Outcome**: Parley + AI helps newcomers understand the organization quickly.
### FRIDAY - OFFICE HOURS
Answer any questions from the different cohorts. Only one hour? Maybe two?
### KEY TAKEAWAYS?
| Turntable Team | BOOMBOX CREW | LIMEWIRE LEGENDS | SPOTIFY SQUAD |
|---|
| | | |
| | | |
| | | |
---
# 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://llm.theparley.org/starting-to-use-it/lunch-and-learn-series/week-3.md?ask=&goal=
```
`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.