Episode

#385 - Why Architects Can't Say No

Podcast
Archispeak
Published
Mar 27, 2026
Duration seconds
2264
Processing state
not_requested
Canonical source
https://archispeakpodcast.com/episodes/385
Audio
https://episodes.captivate.fm/episode/54286f76-72e7-46d9-83df-02b9093ac269.mp3
JSON
/v1/public/podcasts/archispeak-774431/episodes/385-why-architects-can-t-say-no
Markdown
/podcast/archispeak-774431/385-why-architects-can-t-say-no.md

Actions

  • POST https://stenobird.com/v1/public/podcasts/archispeak-774431/episodes/385-why-architects-can-t-say-no/transcription-requests
    Idempotently request low-priority transcript generation for this episode.
  • GET https://stenobird.com/podcast/archispeak-774431/385-why-architects-can-t-say-no.md
    Read the agent-friendly Markdown representation of this episode resource.

Summary

Cormac spent twelve hours trying to send one email. Evan has seventeen apps open at all times. This week they trace the architecture of modern distraction — from "you're on mute" killing the flow of real-time thinking, to AI making it easier to do more of the wrong things faster, to the structural reason architects keep saying yes when they should say no. The profession runs on availability, responsiveness, and service, and those instincts are now at war with the deep, focused work that good architecture actually requires. This episode is especially relevant for architects who recognize the gap between how busy they feel and how much actual work they can point to at the end of the day — and who are starting to wonder whether the answer is less technology, better boundaries, or just learning to say no. ----- Have a question for the hosts? Ask it at AskArchispeak.com Thank you for listening to Archispeak. For more episodes please visit https://archispeakpodcast.com . Support Archispeak by making a donation .