Skip to content
Convokast

How to Get on Change Management Podcasts

A practical process for matching a change case to a podcast, checking guest permission, and pitching evidence without exposing restricted information.

Research this article with AI

Follow Convokast on Google

Add Convokast to your Preferred Sources.

How to Get on Change Management Podcasts

How to get on change management podcasts starts with one defensible change decision, not a broad claim of expertise. Match that decision to the show's current audience and subjects. Then verify that the producer permits a proposal. Current interviews prove the use of outside voices, while a published route or direct invitation establishes access.

How to get on change management podcasts with a defensible premise

Choose a decision that you owned or advised closely enough to explain under questioning. It could involve an adoption signal that contradicted the project dashboard, a sponsor who would not make a necessary choice, or a communication plan that failed when it reached frontline managers. The useful episode sits in the judgment and evidence, including the trade-off.

Write the premise before writing the biography. Name the listener who faces the problem and the condition that made action necessary. State your role with precise language. Identify what evidence changed the team's view and what remains interpretation. Set the disclosure boundary before promising details to a producer.

A compact one-sheet can hold the finished premise and biography alongside recording details. The podcast one-sheet builder shows how those fields fit together without turning the asset into a list of credentials.

Select shows by the change problem they already examine

Start with the Convokast podcast directory and management podcast category, then inspect each candidate's current first-party material. A shared category does not mean every show serves the same listener.

PodcastEditorial fitInterview formatGuest recommendation routeOpen self-application
[Change Management Review Podcast](https://changemanagementreview.com/feed/podcast/)Research and practice, adoption, decision-making, leadership under uncertaintyCurrent named specialist conversationsNone published in the reviewed feedNone published in the reviewed feed
[The Only Constant](https://anchor.fm/s/fd7b421c/podcast/rss)Large-scale transformation, alignment, reporting, adoption, change leadershipCurrent interviews with senior change leadersNone published in the reviewed feedNone published in the reviewed feed
[The Change Management Podcast](https://anchor.fm/s/29448f58/podcast/rss)Organizational change, design thinking, digital transformation, applied service casesExperts and practitioners appear in the university feedNone published in the reviewed feedNone published in the reviewed feed
[Built for Change](https://feeds.simplecast.com/J6oAIHuK)Business reinvention, technology, customer needs, workforce questionsConversations with leaders and specialistsNone published in the reviewed feedNone published; production needs a current check
[Diary of a Change Manager](https://thediaryofachangemanager.buzzsprout.com/)Communication, storytelling, employee experience, practitioner casesNamed practitioner conversations in the archiveNone published on the reviewed pageNone published; visible activity is older

Change Management Review Podcast fits a case that connects research with operating practice. The Only Constant has a leader-level view of major transformation. The university-backed Change Management Podcast gives digital transformation and service design more room. Built for Change places change inside wider business decisions, while Diary of a Change Manager concentrates on communication and the people affected.

Use audience overlap to reject weak matches. Write a sentence that connects your proposed lesson to a problem the show's listeners face. If the same sentence works unchanged for every row, the premise is too broad.

Verify format and access as separate research tasks

Editorial fit, interview format, guest recommendation, and self-application need separate evidence. Combining them creates false access claims.

Editorial fit comes from the official description and current episode premises. Interview format comes from named outside voices or explicit interview wording. A recommendation route exists when the publisher invites someone to suggest a guest. Open self-application exists when the show tells prospective guests how to submit themselves. Direct permission from a producer can also authorize a proposal without creating a public route for everyone else.

The reviewed change management feeds establish editorial fit and interview format. They do not publish recommendation forms or open self-applications. The Only Constant includes host connection details in episode notes, but those details are not labeled as guest submission instructions. The Change Management Podcast links into university business material that serves a different purpose. Neither route should be repurposed.

Follow the guide to checking whether a podcast takes guests before contact. Save the official page, the supporting words, and the date checked. Revisit the source when the pitch is ready because production and access instructions can change.

Research enough episodes to change the pitch

Read the description and several current episode entries. Record the listener role, the problem under discussion, the guest's relationship to that problem, and the degree of operational detail. Look for recurring tensions rather than repeated topic words.

Change Management Review Podcast currently connects research with practical questions such as adoption and decision quality. A proposal for that show should explain what evidence altered a change decision and how the practitioner tested the resulting approach. The Only Constant examines major transformation from the leader's seat, so a narrow communication tip may lack the required organizational consequence.

The Change Management Podcast includes digital-service cases. A suitable premise could show how a team defined a service problem, involved affected people, and revised its assumptions. Built for Change ranges across technology and business reinvention, which calls for an executive-level connection. Diary of a Change Manager can help shape a people-centered communication premise, though its older activity makes it a research archive until current production is confirmed.

Research has done its job when it changes the proposed episode. Narrow the listener, replace a generic framework with a real decision, or remove an angle the show recently covered in the same way. Mentioning an episode title without changing the pitch only demonstrates surface familiarity.

Give the producer a case they can question

Open with the change problem and the lesson available to listeners. Follow with the role that gave you direct knowledge. Explain the constraint, evidence, and trade-off in plain language. A host should be able to imagine the questions and identify where your account can be tested.

A useful proposal contains these parts:

  • the listener and change problem;
  • the decision you owned or influenced;
  • the constraint that blocked an easy answer;
  • the evidence you may discuss;
  • the trade-off, failed attempt, or limit;
  • the reason this premise fits the show's current work.

Keep the biography short and relevant. Change certifications and job titles can support credibility, as can speaking history, but they do not supply an episode. A consultant or software founder should disclose the commercial interest. The conversation must remain useful when a product name and sales link are removed.

Avoid promised certainty that the case cannot support. Adoption may move while training, leadership behavior, product design, and operating conditions also change. Describe what you observed and what you concluded without assigning the whole result to one intervention.

Set authority and confidentiality limits before outreach

Change work often contains employee information, client material, internal performance results, or plans that have not been announced. Decide what you have authority to discuss before seeking an introduction. Removing a company name does not automatically make every detail safe to share.

Separate public support from your recollection and interpretation. Do not imply that you speak for an employer, client, regulator, or former team. If a result cannot be disclosed or supported, remove it from the pitch. The remaining case still needs enough concrete detail for editorial assessment.

Tell the producer about any limit that changes the promised conversation. A case pitched as a detailed operating account should not collapse into general advice after booking. Clear boundaries allow the host to plan useful questions and reject a premise that depends on unavailable evidence.

Seek permission without manufacturing a public route

Where a show publishes no open application, a relevant introduction is the cleanest route. The person making it should know your work and have a real relationship with the producer. Ask whether they are comfortable introducing the premise, and give them an easy way to decline. The introduction permits a conversation; it does not guarantee a booking.

Direct producer outreach can also become appropriate after a producer invites proposals in a private exchange or professional setting. Preserve the scope of that permission. An invitation to send an idea is not permission to add the show to a public list of podcasts that accept guests.

Do not send the same proposal through a host email, university business form, publisher contact page, and personal social account. Repetition across unrelated channels does not improve the case. If the producer declines or does not respond, update the record and move on.

Prepare the interview around evidence and trade-offs

After booking, outline the event sequence and the decisions that changed direction. Identify who owned each choice and who carried its consequences. Bring examples that fit the agreed disclosure boundary, then prepare to explain where the evidence remained incomplete.

Change management conversations become useful when the guest can show how judgment changed under pressure. Explain the original assumption, the signal that challenged it, the options considered, and what you would inspect earlier next time. Leave room for the host to question your interpretation instead of rehearsing a speech.

When the premise and permission are settled, use the podcast pitch generator to draft one concise proposal for that specific change management show.

Common questions

How do you get invited onto a change management podcast?

Build a specific premise from a change decision you handled directly, match it to the show's current editorial territory, and use a route the producer has authorized. If no public application exists, seek a relevant introduction or wait for direct permission.

What should a change management podcast pitch include?

Name the listener's problem, your direct role, the decision made, the constraint that complicated it, the evidence available for discussion, and the confidentiality boundary. Connect the premise to the show's current subjects.

Can a change consultant discuss a client case on a podcast?

Only within the authority and disclosure limits that apply to the work. Remove restricted names and details, avoid unsupported outcome claims, and make sure the remaining case is specific enough for a producer to assess.

Can I use a podcast host's general email for a guest pitch?

Not unless the show identifies that address as a guest route or the producer gives direct permission. An email for professional connection, business services, support, or general correspondence does not establish open self-application.

change managementpodcast outreachpodcast pitching

Work with us

Want to be the guest, not the reader?

We pitch, book, and prep you for the shows your buyers already listen to.

Book a discovery call

Free 20-minute call. If we are not a fit, we will say so.