Decoding Leadership

The episode contains concrete methodology (experience mapping using Notion Gantt charts, departmental discovery interviews, categorizing functional/experiential/learning data) and practical insights about cross-functional coordination, but substantial portions are spent on personal background, abstract philosophy about storytelling, and high-level frameworks that could apply anywhere. The guest moves between specific examples and vague aspirational statements, reducing density.

“We weren't necessarily thinking of it from the student's perspective that everybody was berating, and that one of the reasons that students were not showing up on day one was because of too much contact”

“ask a question once, make sure that we are communicating competency by getting it to where it needs to go”

Experience mapping and service design are established practices; the guest acknowledges this explicitly ('experience design is not a, is. It's been around for a second'). While the application to education and the specific Gantt chart implementation show some domain-specific adaptation, the core frameworks (service strategy, business model canvas, journey mapping) are well-known. The recurring metaphor of storytelling and narrative is familiar in organizational development.

“experience design is not a, is. It's been around for a second”

“this grew out of, um, a model, a template that I took and made my own over the, over years”

Damon has relevant practitioner experience in hospitality, education, and consulting, and was brought into Campus to solve a real organizational problem. However, he is not a CEO, founder, or executive who built a company from scratch. He's a specialized consultant/operator hired for a specific function. His background is more in design and culture than in scaling a business or managing P&L.

“I had an amazing career doing that, um, in leadership and in consulting and working with some great brands”

“I had a chance to work with some really great companies both from, uh, you know, event design, um, innovation programming”

The episode includes some specifics: Notion Gantt charts, the scope (application through six weeks of enrollment), OpenTable's guest/restaurant notes distinction, and reference to a 'well-known firm' dealing with project management. However, many claims lack data: no metrics on student show-up improvement post-mapping, no quantified impact from the Campus project, no budget figures, timelines are vague ('about 2016'), and the 'other organizations' mentioned are unnamed. Advice relies on abstract principles rather than concrete case data.

“the scope of the project was from application through the first six weeks of enrollment”

“We're sending out the email from student success, um, to talk about career aspirations”

The host asks reasonable follow-up questions ('What was hard about it? What did that feel like?') and does probe the failure/limitations ('what impact you felt like it had, what were missed opportunities'). However, follow-ups are often gentle and surface-level. When the guest makes abstract claims (e.g., 'how an organization navigates failure'), the host doesn't push back or ask for evidence. The conversation flows pleasantly but rarely sharpens or challenges the guest's thinking.

“Um, so as the representative of engineering at the time, I found this totally interesting because engineering was also doing the same thing”

“And I guess my experience has been with this type of cross functional work, it's often really hard to fully land it”