> For the complete documentation index, see [llms.txt](https://resources.unizin.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resources.unizin.org/support-and-training/professional-development/structured-conversations-initiative.md). # Structured Conversations initiative
Structured Conversations Logo
**The Structured Conversations initiative** was launched to gather perspectives from classroom practitioners about how they would like to use learning data in support of academic achievement. We use the term Structured Conversations to describe a structured, scripted process for generating, grouping, and prioritizing ideas in response to a question prompt. Sessions are organized and facilitated locally with access to a common script and set of supporting resources. [Visit the Structured Conversations initiative website](https://sites.google.com/unizin.org/structuredconversationsresults/home). ## **Participating institutions** #### Project Managers * **Lauren Marsh**, PhD, Senior Academic Technologist, University of Minnesota * **Emily Oakes**, Principal Unizin IT Consultant, Indiana University ### **Support Resources and Consultation** * **Rebecca George-Burrs**, Sr. Technology Training Consultant, University of Minnesota * **Lauren Marsh**, PhD, Senior Academic Technologist, University of Minnesota * **Emily Oakes**, Principal Unizin IT Consultant, Indiana University * **Nick Rosencrans**, User Experience Analyst, University of Minnesota * **Tony Warner**, User Experience Analyst, University of Minnesota ### **Colorado State University** * **Tonya Buchan**, Instructional Designer, Colorado State University * **Stan Kruse**, Learning Technology and Analytics Program Manager, Colorado State University * **Barb Houser**, Assessment Coordinator, Colorado State University ### **Indiana University** * **Greg Siering**, PhD, Director, Center for Innovative Teaching and Learning ### **University of Florida** * **John Jordi**, Instructional Assessment Coordinator, Center for Teaching Excellence * **Alexandra Bitton-Bailey**, Interim Director, Center for Teaching Excellence * **Heather Maness**, Assistant Director of Learning Analytics and Assessment, University of Florida Information Technology ### **University of Minnesota** #### **Sponsors** * **Keith Brown**, Senior Director for Academic Technology, Office of Information Technology * **Leslie Schiff**, PhD, Associate Dean for the University Curriculum and Director of Undergraduate Studies, Office of Undergraduate Education #### **Support Team** * **Rebecca George-Burrs**, Senior Technology Training Consultant * **Lauren Marsh, PhD**, Senior Academic Technologist, Office of information Technology * **Peter Radcliffe, PhD**, Director of Undergraduate Analytics, Office of Undergraduate Education * **Tony Warner**, User Experience Analyst ### **Rutgers University** * **Christina Bifulco**, Associate Director of Teaching & Learning Analytics, Office of Teaching Evaluation & Assessment Research * **Chris Drue**, Associate Director of Teaching Evaluation, Office of Teaching Evaluation & Assessment Research --- # 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://resources.unizin.org/support-and-training/professional-development/structured-conversations-initiative.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.