Episode

AV SuperFriends: On Topic - We won't do anything until that form is filled out

Podcast
AV SuperFriends
Published
Jun 1, 2026
Duration seconds
2632
Processing state
not_requested
Canonical source
https://www.avsuperfriends.com/episodes/on-topic-episode-72-we-wont-do-anything-until-that-form-is-filled-out
Audio
https://traffic.libsyn.com/secure/avsuperfriends/AVSF-On-Topic-72-05152026.mp3?dest-id=2412569
JSON
/v1/public/podcasts/av-superfriends-2789935/episodes/av-superfriends-on-topic-we-won-t-do-anything-until-that-form-is-filled-out
Markdown
/podcast/av-superfriends-2789935/av-superfriends-on-topic-we-won-t-do-anything-until-that-form-is-filled-out.md

Actions

  • POST https://stenobird.com/v1/public/podcasts/av-superfriends-2789935/episodes/av-superfriends-on-topic-we-won-t-do-anything-until-that-form-is-filled-out/transcription-requests
    Idempotently request low-priority transcript generation for this episode.
  • GET https://stenobird.com/podcast/av-superfriends-2789935/av-superfriends-on-topic-we-won-t-do-anything-until-that-form-is-filled-out.md
    Read the agent-friendly Markdown representation of this episode resource.

Summary

Recorded May 15, 2026 This episode of On Topic gets into the glamorous, soul-polishing world of how AV projects actually begin, which is apparently somewhere between a formal intake form, a support ticket that got out of hand, a hallway ambush, and someone discovering the room needs power, asbestos abatement, and lots of opinions. The panel compares how different campuses define and initiate projects, from TeamDynamix and ServiceNow workflows to informal emails, consultation requests, facilities handoffs, and the dreaded "this was supposed to be a simple fix" scenario. A big theme is the messy boundary between support ticket, request, incident, problem, and project, especially when aging systems, construction needs, or money get involved. They also get into the joys and failures of project management platforms, Project, Planner, Smartsheet, TeamDynamix, ServiceNow, and the eternal higher-ed struggle of trying to force real work, real communication, and real accountability into software that was clearly designed by people who have never been asked do any of that. In short: projects should start with clear scope, timelines, goals, funding, stakeholders, and process. In reality, they start with an email that says, "quick question," and end with everyone arguing over whether it was ever a project in the first place. Alternate show titles: Is this directed to me? Wow, that's big! I don't touch tickets What if I email you? Hey, we're going to do this thing We'll have the meeting eventually Facilities doesn't do power Requires a state employee to inspect the electrician We get requests every which way from Sunday We want to drive everybody to a ticket Rapid fire from wherever-the-hell-it-came-from That means it's approved and no one wants to do that sh*t I don't do projects,…