How to Get on COO Podcasts

To get on a COO podcast, propose one operating decision you handled directly. Explain the business constraint, your authority, the people or functions involved, and the trade-off the decision forced. Match that case to the show's recent editorial pattern, verify the exact guest route, and clear restricted information before a producer sees it.

Start with a decision you owned

"COO available to discuss scaling" is a biography, not an episode. Producers need a real operating problem. Choose a decision where your responsibility is clear and where the result depended on judgment rather than a slogan.

A usable case may involve redefining authority after a reorganization, changing a planning cadence, fixing an intake process across departments, or deciding when a plant automation project was ready to move. It could cover a commercial handoff after the sale or a dispute between functional targets and a company-wide outcome. The job title matters less than the decision rights attached to the case.

Write the premise in plain language. State what the company needed, what constraint made the choice difficult, which part you owned, and who approved or executed the work. Give credit to the people involved. If a plant manager designed the implementation or a finance leader controlled the budget, do not absorb their work into a first-person success claim.

A good premise also gives the host room to challenge you. Name the option you rejected and the cost attached to the choice you made. Avoid a tidy victory story if the decision created a new dependency or delayed another goal. The same caution applies when it worked only under particular company conditions.

Match the case to the show's operating territory

COO programs do not cover one uniform job. Some focus on the chief executive relationship, while others examine scaling-company role design or enterprise supply chains. Industrial shows care about physical constraints. Cross-functional and commercial operations programs follow different handoffs again.

Use the Convokast podcast directory and business news category to expand a candidate list. Then read the publisher's official description and current feed. A category page can surface a show, but it cannot confirm editorial fit or access.

Read the feed for the questions the show repeats

The Second in Command feed centers on leaders operating behind a chief executive, so a pitch should show the boundary between executive roles and the decision that tested it instead of relying on generic management advice that misses the relationship giving this show its frame.

The Operations Room feed covers operating leaders inside scaling companies. Look for repeated problems around role design, ownership, hiring, systems, and organizational pressure. A proposal works better when it names the stage or structural change that exposed the operating problem.

The McKinsey Talks Operations feed connects boardroom choices with frontline systems. A case confined to personal productivity will be too small for that frame. Show how planning, quality, supply chain, technology, workforce capability, or service delivery crossed organizational boundaries.

The Operations Science Podcast feed draws on plants and project environments. Bring the physical operating conditions into the premise. Equipment and capacity change what a decision means, as do site authority, logistics, and deadlines.

Tonkean's Modern Business Operations page covers workflows across enterprise functions. A strong case identifies where the work entered the organization, which approvals or policies controlled it, and where ownership broke. Operations with Sean Lane is narrower around commercial systems, so cases about partner, customer, post-sale, and go-to-market handoffs belong there.

Verify permission before writing a full pitch

The Second in Command publisher page links an application for prospective guests. Use the fields provided and treat the form as a request for editorial review. It does not establish acceptance or a production schedule.

The Operations Room uses third-person language. Its page asks readers to pitch someone they have in mind and explain why the story matters. That wording supports guest recommendations. A prospective guest who wants to propose themselves should ask whether the team considers self-nominations before sending a detailed submission.

Modern Business Operations publishes a direct invitation to prospective guests. Its page asks people who want to share a story to email the team or make contact through its social profiles. This is an inquiry, with no acceptance promise.

The other reviewed shows establish interview formats without publishing equivalent permission in the inspected sources. Record them as "interviews verified; public access unconfirmed." General LinkedIn invitations and consulting forms keep their stated purposes. So do company contacts and sponsorship pages. A private introduction can open a conversation, but the permission applies to that exchange and should not be presented as a public route.

The guest-access verification guide explains how to record applications, inquiries, suggestions, generic contact, and commercial routes without merging them.

Clear restricted operating information

COO stories often touch information that the company, a client, or a partner has not cleared for release. Financial performance, employee actions, customer terms, and supplier problems may sit inside an otherwise useful story. Board discussions and transaction plans can be restricted too, along with security details, litigation, and internal investigations.

Create a public version before outreach. Mark which company names, counterparties, dates, financial details, and outcomes may be discussed. If the useful mechanism can be explained without identifying a client, check that removing the name does not create a misleading account. Do not combine several events into a cleaner story unless the producer knows it is a composite and the format permits that treatment.

Confirm which person owns the approval. That may include an employer or client, the communications team, the legal team, a board representative, or a transaction counterparty. A former executive may still owe contractual or legal duties, and departure from a role does not release confidential material.

Keep unsupported causation out of the pitch. A better margin or faster cycle may have had several causes. The same applies to a successful launch. Describe the decision and available evidence without claiming sole credit for an outcome the case cannot isolate.

Disclose the position behind the story

A COO may also advise companies, invest in vendors, sit on boards, sell software, coach executives, or speak for an association. Those interests do not erase the operating experience, but they affect how the producer evaluates and frames it.

State the connection in the first proposal when it bears on the topic. Identify client work as client work and confirm that the client cleared any details. If a vendor supplied the product in the case, separate the operator's decision from the vendor's claims. Keep sponsorship discussions apart from editorial outreach unless the publisher expressly combines them.

Send a premise the producer can assess quickly

Open with the operating decision and its fit with the show's current territory. Follow with your role, the constraint, and the trade-off. State which evidence and names are cleared for discussion, then disclose the commercial relationships that affect the case. A few precise paragraphs are easier to assess than a long biography and several attachments.

Use the audience-overlap guide to check whether the listeners own the problem. A plant authority case and a post-sale handoff may both involve a COO, yet they call for different audiences and shows.

If you want to draft a concise message after checking the route and disclosure boundary, build your COO podcast pitch with the free generator.