Sean Conte

Teaching / Teaching with AI / Workshops

Workshops

A series of three meetings for faculty. Each one points curiosity at something different: the tool, our students, and what we could make.

The series doesn’t argue against anyone’s anxiety about AI. It tries to give curiosity more room. Each meeting ends with a small task, and the next meeting starts from it. Times assume a 90-minute meeting.

Meeting 1

Curious about the tool

See what AI can do in your own hands, through an interactive process and not a single prompt.

Before the meeting

Participants bring a current syllabus in a digital format. The facilitator prepares a few short demonstrations: some things they have been curious about, a few from outside of work, and a few teaching applications. An HTML syllabus template is optional.

In the meeting

  1. Framing 5 min

    My goal is not to try to convince you to be less anxious about AI. My goal is to give you things to be curious about. My hope is that curiosity takes up more space.

  2. Teaser 15 min

    Quick flashes of things you have been curious about, then a few teaching applications. Point out that each one came from an interactive process: questioning, figuring out what you wanted, figuring out what was possible, and noticing the assumptions you were making. The point of these flashes is to undermine the notion that AI means a prompt and a bad essay.

  3. Syllabus, part 1: basic revisions 20 min

    Demonstrate turning an old syllabus into a new one: old syllabus + PoT (+ HTML template) = new syllabus. The HTML is optional. Then participants try it with their own. The point is to show how easy it is, and its being quick is part of the point.

  4. Syllabus, part 2: thoughtful revisions 40 min

    Participants raise concerns about their syllabus, open-ended, and work through them with AI iteratively, responding to what comes back. Each person tries to find a new problem, a new structure or strategy, a new resource, and a new experience for students. Pairs compare what they found in the last ten minutes.

  5. Close 10 min

    Introduce the task for Meeting 2.

Facilitator notes

  • When the conversation turns to whether AI is good or bad, redirect to what someone would want to find out.
  • Show your own process, including dead ends and revisions. Seeing the back-and-forth matters more than seeing a polished result.

Before the next meeting

Run one of your own assignments through AI. Note what comes back, what surprised you, and what it missed. Bring those notes.

Meeting 2

Curious about our students

Make decisions about specific uses of AI, and see how those decisions become a course’s AI contract.

Before the meeting

Participants bring their notes from testing an assignment. The facilitator opens the case sorter. If participants send notes ahead of time, add a few of their findings as cases.

In the meeting

  1. Opening round 15 min

    Each person shares one thing their assignment test showed. The facilitator writes down the surprises, which often become cases later in the meeting.

  2. Case sorter 25 min

    Show a case and have everyone commit by raising a hand for helps the learning or replaces the learning before anyone speaks. Tally the hands, then ask what would change people’s answers. Six to eight cases is enough. Move quickly.

  3. Fishbowl 25 min

    Open the summary and take the two most divided cases. Four or five people sit in an inner circle and discuss while everyone else listens, with one open chair that anyone can take to join. The goal for each case is to name the condition that flips the answer.

  4. The AI contract 15 min

    Introduce the five headings and show the Logic and Ethics examples side by side. The conditions named in the fishbowl usually belong under B and C.

  5. Close 10 min

    Introduce the task for Meeting 3, including the three ways to fill out the contract.

Facilitator notes

  • Commit first, discuss second. Deciding before arguing is what keeps the session from becoming a list of complaints.
  • When a complaint comes up, ask for the specific situation behind it and add it to the sorter as a new case.

Before the next meeting

Draft an AI contract for one course, or plan how you’ll write it with your class. Also pick one thing in a course you’d like to change: an assignment, an activity, or a point students reliably get stuck on.

Meeting 3

Curious about what we could make

Build one thing for a course, using the same interactive process from Meeting 1.

Before the meeting

Participants bring their draft contract and the thing they want to change. Everyone needs a laptop.

In the meeting

  1. Contract swap 15 min

    Pairs exchange contracts. Each person reads the other’s sections B and C and asks one question about them.

  2. Build 55 min

    Each person builds one thing for their course: a revised assignment, an in-class activity, a study tool, or a small interactive page. Start by describing the problem to the AI before describing the product. Ask it questions back, notice the assumptions in what it proposes, and revise. Halfway through, take five minutes for everyone to say how the idea has changed since they started.

  3. Show 15 min

    Each person takes a minute to show what they made and one thing they learned about the process.

  4. Close 5 min

    Where to find these materials, and what each person plans to try next term.

Facilitator notes

  • It’s fine if something isn’t finished or doesn’t work yet. The process is what carries over.
  • Circulate during the build. The most useful help is usually a question about what the person actually wants, more than advice about prompts.

Afterward

Collect what people made, with permission, as examples for the next group.