In partnership with

issue #24 | date: 10/15/2025

Special Event

Editors Note

Many years ago, I was the glue holding everything together.

If a project was slipping, I jumped in. If stakeholders were misaligned, I ran the meeting. If something wasn't documented, I wrote the doc.

My manager called me "the go-to person." I thought that was a compliment.

Then I got passed over for a senior management role. The feedback: "You're too in the weeds. We need someone who can scale the org, not just save projects."

I was furious. Of course I'm in the weeds; someone has to do the work.

But here's what I missed: Great executors get promoted to manager. Great orchestrators get promoted to executive.

The transition from executing to orchestrating is invisible. No one teaches it. No one even tells you it's the bar.

In this issue:

  • The exact moment you need to stop doing and start enabling.

  • How to build systems that run without you.

  • Why "being indispensable" is killing your career.

  • Jobs for people who've mastered orchestration.

  • Automation to auto-triage your tickets.

Let's talk about letting go.

Phedra Arthur Iruke

Editor in Chief

The Future of AI Communication Starts Here

Every day great ideas fade because turning complex thinking into clear communication takes time most people do not have.

Pressmaster.ai changes that. It captures how you think, amplifies it into powerful communication, and shares it in your authentic voice.

This is not about writing faster. It is about thinking louder.

Join us on October 15 at 12 PM ET or 6 PM CET for The Worlds First AI Built for Cognitive Amplification.

Discover how one short conversation becomes thirty days of strategic and market ready content.

Be part of the launch of a new category where AI becomes part of your cognitive architecture.

Featured Job Listings

🏆 Top Picks of the Week (Hand-Picked, High-Impact Roles)

🔹 Sr Director Program Management, 340B
Company: Prime Therapeutics
Location: Remote (US)
Apply: Prime Therapeutics careers


In this remote, full‑time role, you lead Prime’s 340B program strategy and execution. You’ll drive cross‑functional program committees, align long‑term objectives and strategy, provide leadership to the program management team, and serve as the escalation point for program issues. The role manages key vendor relationships and directs the development of program management processes and tools. Requirements include a bachelor’s degree (or equivalent experience), 10+ years’ program management/business analysis experience, and 7+ years of leadership or supervisory experience, plus strong communication and change‑management skills.

🔹 Senior Director, Global Program Management
Company: Takeda
Location: Boston, MA (Cambridge office; full‑time)
Apply: Takeda careers


This senior leader provides matrixed program management and strategic leadership for global cross‑functional teams across Takeda’s portfolio. Responsibilities include translating product/portfolio strategy into executable plans, ensuring functional resources are available, championing AI‑enabled tools to drive productivity, mentoring junior program managers, and fostering transparency and alignment across. Candidates need a bachelor’s degree (advanced degree preferred), 12–14 years of pharma development experience, 10+ years of program‑management experience, and excellent leadership, negotiation, and communication skills

🔹 Director Change Management
Company: RGA (Reinsurance Group of America)
Location: Hybrid – Chesterfield, MO (RGA HQ)
Apply: RGA careers


At this Fortune 500 reinsurer, you’ll design and deliver change‑management plans using Prosci® methodology, partner with business leaders to address the people aspects of significant change, and manage communications, training, and stakeholder engagement across all levels of the organisation. Qualifications include a bachelor’s degree (master’s preferred) in business/HR/organizational psychology, 8+ years’ change‑management experience, certification in change management (Prosci CCMP), and expertise in facilitating major business transformations. Experience in financial services/insurance and strong influence and communication skills are valued

🔹 Director, Product Operations (EverHealth)
Company: EverCommerce
Location: Remote (US) – distributed team across U.S., Canada, UK, Jordan, NZ & Australia
Apply: EverCommerce careers


This role leads product operations across EverHealth (EverCommerce’s healthcare software division). Responsibilities include owning instrumentation across the portfolio, establishing consistent metrics and dashboards, improving data literacy, partnering with product leaders for planning and reviews, and providing tools to enable better discovery and learning. The director focuses on context rather than command‑and‑control and requires 7+ years in product/analytics/enablement roles, proven success implementing product analytics at scale, and strong communication and systems‑thinking skills; the position is fully remote within the U.S. with travel as needed. Target base pay is $170k–$185k plus variable compensation.

🔹 Director‑Enterprise Payments Product Operations
Company: American Express
Location: U.S. (role sits within Global Merchant & Network Services)
Apply: American Express careers


Newly created role leading the risk, control, and compliance oversight program for the Enterprise Payments Center of Excellence. Responsibilities include designing and improving Risk & Control Self‑Assessment (RCSA) processes, overseeing regulatory and payment‑scheme compliance (Nacha, SEPA, etc.), creating an audit‑ready repository of product documentation, and partnering across risk, compliance, legal, and operations to ensure cohesive governance. Requires at least 10 years’ experience in non‑card payments within risk or compliance functions, deep knowledge of AML/KYC/OFAC and payment regulations, proven RCSA design/execution, and strong program‑management, analytical, and communication skills; Accredited ACH Professional (AAP) certification is preferred. Salary range is $144k–$256k plus bonus and potential equity


📌 IC & Manager Roles

Role

Company

Location (City, State)

Format

Apply (direct link)

Enterprise Onboarding & Implementation Manager

EvenUp

Remote (US)

Remote

Strategic Project Lead

Crosby

New York City, NY

On‑site

Customer Experience (CX) / Implementations Lead

DualEntry

Austin, TX or New York City, NY

Remote/Hybrid

Project Coordinator

Base Power Company

Austin, TX

On‑site

Intern – IT Project Manager

Labcorp

Remote (USA – Indiana/Eastern Time)

Remote

IT Portfolio & Project Manager

Owens Corning

Columbus, OH (remote)

Remote

Manager IT PMO

Aventiv Technologies

Remote, United States

Remote

Technical Program Manager

WEX

Remote (California or Maine)

Remote

Staff Technical Program Manager, AI

Hims & Hers

Remote (US)

Remote

Technical Program Manager

Rise8

Remote

Remote

Implementation Manager

Verifiable

United States (remote)

Remote

Implementation Manager

Curri

Remote – United States

Remote

Implementation Manager

Coastal (Coastal Community Bank)

Fully Remote, United States

Remote

Sr. Mgr, Change Manager – Finance Product

ServiceNow

North America & Canada (Flexible/Remote)

Flexible/Remote

Change Management Consultant (1099)

Mosaic

East Bay, CA (US – 70–80 % travel)

Contract/Remote with travel

The Gold standard for AI news

AI will eliminate 300 million jobs in the next 5 years.

Yours doesn't have to be one of them.

Here's how to future-proof your career:

  • Join the Superhuman AI newsletter - read by 1M+ professionals

  • Learn AI skills in 3 mins a day

  • Become the AI expert on your team

Bots Take the Wheel

🤖 Auto-Triage Support Tickets by Urgency

The Problem: Support tickets pile up, and by the time you realize something's critical, it's already a P1 incident.

The Fix: Automate ticket triage so urgent issues get routed instantly and nothing slips through the cracks.

Real Use Cases:

  1. Zendesk + Slack: Auto-Escalate High-Priority Tickets

    • Logic: When a support ticket is created with keywords like "outage," "urgent," "production down," automatically tag it as "Critical," assign to on-call engineer, and post alert to #incidents Slack channel

    • How: Zendesk Triggers → Check ticket subject/description for keywords → Set priority = Critical → Assign to on-call rotation → Send webhook to Slack with ticket details

    • Impact: Reduces mean time to response (MTTR) for critical issues by 60%. Teams using this report fewer escalated customer complaints (Zendesk Benchmark Report 2024)

  2. ServiceNow + PagerDuty: Auto-Page On-Call for P1 Incidents

    • Logic: When a P1 incident is created in ServiceNow, automatically trigger a PagerDuty alert to the on-call engineer and create a war room in Slack

    • How: ServiceNow Flow Designer → Incident created with priority = P1 → Trigger PagerDuty incident via API → Create Slack channel named #incident-[ticket-number] → Add on-call engineer + stakeholders

    • Impact: Cuts incident response time by 50% and ensures no P1 goes unnoticed. Organizations report 70% faster resolution (PagerDuty State of Digital Operations 2024)

  3. Jira Service Management + Opsgenie: Smart Routing by Team

    • Logic: Route incoming tickets to the right team automatically based on keywords (e.g., "billing" → Finance, "login" → Engineering, "onboarding" → Success)

    • How: Jira Automation → New issue created → Check issue summary/description for keywords → Assign to corresponding team queue → Notify team lead via Opsgenie

    • Impact: Reduces ticket mis-routing by 80% and speeds up first response time by 40% (Atlassian Jira Service Management data, 2024)

TL;DR: Stop manually triaging tickets. Let automation flag urgent issues, route them to the right people, and create accountability—so you can focus on solving problems, not sorting through noise.

Visionary Voices

📝 Claire Hughes Johnson, Former COO Stripe

Claire Hughes Johnson is the executive who helped Stripe scale from a scrappy startup to a $95B payments giant. As COO for nearly a decade, she built the operational infrastructure—hiring, culture, systems—that allowed Stripe to grow from 160 employees to 7,000+ without losing its soul.

But here's what makes Claire extraordinary: She obsesses over systems, not heroics.

She's famous for her "operating principles" documents—frameworks that codify how Stripe makes decisions, communicates, and executes. Her belief? Great companies don't run on individual brilliance. They run on clarity, repeatability, and shared mental models.

On Orchestration vs. Execution:
Claire talks openly about the hardest transition in her career—moving from "doing the work" to "building the conditions for great work." Early at Stripe, she'd jump into every fire. Eventually, she realized that made her indispensable, but it also made the org fragile.

Her shift: Stop being the hero. Build systems so good that heroics become unnecessary.

On Building Operating Systems:
At Stripe, Claire created frameworks for everything—how to run meetings, how to give feedback, how to make hiring decisions. She documented these and made them public (many are still on Stripe's blog). Why? Because when everyone has the same mental models, the org moves faster and with less friction.

She writes about this extensively in her book Scaling People, which is basically a blueprint for operational excellence at scale.

What You Can Learn From Her:

  1. Document your mental models – If you make good decisions, write down why. Make your thinking portable.

  2. Design for scale, not speed – Shortcuts now = technical debt later. Build systems that work at 10x your current size.

  3. Make yourself replaceable – The mark of great leadership is an org that runs smoothly when you're not there.

Where to Learn More:

Why She Matters to Delivery Professionals:
Claire is proof that delivery excellence scales through systems, not heroics. If you're a TPM, COO, or PMO lead trying to move from "firefighting" to "orchestrating," her work is your roadmap.

She's also a rare example of an operator who made it to the C-suite—and stayed there for a decade—by obsessing over the how, not just the what.

Final Word:
Claire Hughes Johnson built one of the most admired operational cultures in tech by making one simple shift: Stop being indispensable. Start building systems that make great execution inevitable.

That's orchestration.

Gif by nickatnite on Giphy

Weekly Recommendations

Discover the six proven strategies that transform technical program managers from perceived overhead into trusted engineering partners who drive successful program delivery.

This 30-year-old discovered 40 brutal life lessons that most people learn too late (or never).

Meet Tilly Norwood, the AI actress who never ages, never complains, and is making real actors obsolete.

The cultural phenomenon of Mean Girls proves why some movies transcend their genre forever.

You can completely transform your entire life in just 30 days—here's proof it's actually possible.

These 47 brutal questions will expose whether a startup is worth your time before you waste years there.

In partnership with Askalawyeroncall.com

“Your secret weapon for high-stakes delivery work.”

You’re negotiating SOWs, vendor contracts, and NDAs — but don’t have in-house counsel on speed dial.


AskALawyerOnCall.com gives you exactly that.

Flat-fee answers.

No gatekeeping.

No surprises.

Professional Development

📚 The Orchestration Playbook

Let's get uncomfortable:

If your team falls apart when you're on vacation, you're not a leader. You're a bottleneck.

The shift from executing to orchestrating is the hardest transition in any delivery career. Nobody teaches it. Nobody even tells you when to make it.

But here's the reality: You cannot get promoted to an executive level while still being the person who does the work.

Let me show you how to let go without everything falling apart.

1. The Executor's Trap

Here's the pattern I see constantly:

You're promoted because you're great at execution. You ship on time, you solve problems, you're reliable.

So what do you do? More of the same.

You take on bigger projects. You work longer hours. You become the "go-to person" for everything.

Your manager calls you indispensable. You think that's job security.

It's not. It's a ceiling.

Data Point: Research on management effectiveness consistently shows that inability to delegate is one of the most common barriers to executive-level promotion. Leaders who remain too operational struggle to scale their impact."

The Trap:

  • You're rewarded for execution, so you keep executing

  • Your team learns to rely on you, so they stop solving problems themselves

  • You become busier and busier, but your leverage doesn't increase

  • Eventually, leadership sees you as "too in the weeds" to promote

Sound familiar?

2. What Orchestration Actually Means

Orchestration isn't about "delegating more." It's about building systems that produce great outcomes without you in the room.

Think of it like this:

Executors ask: "How do I get this done?"
Orchestrators ask: "How do I build a system where this always gets done well?"

Example:

Executor approach: You personally review every project plan before it goes to leadership. You catch all the mistakes. You ensure quality.

Orchestrator approach: You create a "Project Plan Template + Checklist" that captures your review criteria. You train the team on it. Now they self-review before submitting. Quality stays high, but you're not the bottleneck.

The Shift:

  • From doing → to enabling

  • From solving problems → to building problem-solving frameworks

  • From being in every meeting → to ensuring the right people are in the right meetings

  • From making every decision → to teaching others how to make good decisions

3. The 4 Levels of Delegation (And Where You're Probably Stuck)

Most people think delegation is binary: either you do it or someone else does it.

Wrong.

There are 4 levels:

Level 1: Do it yourself
You own it. You execute it. You're in control.

Level 2: Delegate execution, keep decision-making
Someone else does the work, but you make all the calls. You're still the bottleneck.

Level 3: Delegate execution + decision-making, review outcomes
They do the work and make decisions. You review after the fact and coach.

Level 4: Full ownership
They own the outcome. You're informed, not involved. They come to you for coaching, not permission.

Where most people get stuck: Level 2.

They delegate tasks but not authority. Result? The team still waits on you for every decision. You're "delegating" but you're still in the weeds.

The Fix:

Start moving more work to Level 3 and 4. Here's how:

  • Level 3: "Here's the decision framework. You make the call and let me know what you decided and why. I'll give feedback afterward."

  • Level 4: "You own this. I trust your judgment. Come to me if you hit a blocker or need a strategic gut-check."

Reality Check: If you're nervous about Level 3 or 4, that's a sign you haven't built the right frameworks or hired the right people.

4. How to Build Systems That Scale Without You

Here's the orchestration playbook:

Step 1: Document Your Thinking

Every time you make a decision, ask yourself: "What's the framework I'm using?"

Then write it down.

Examples:

  • How do you prioritize projects? (Your framework: Impact vs. Effort matrix? RICE scoring? OKR alignment?)

  • How do you decide when to escalate? (Your criteria: Timeline risk? Budget risk? Stakeholder impact?)

  • How do you run 1:1s with your team? (Your structure: Wins, blockers, coaching, career growth?)

Claire Hughes Johnson at Stripe made this an art form. She documented everything—how Stripe interviews, how they make decisions, how they run meetings. Then she made it public so everyone had the same mental models.

The Result: Stripe scaled from 160 to 7,000 employees without losing execution quality.

Your Action: Pick one repeatable decision you make weekly. Write down your criteria. Share it with your team. Now they can make that decision without you.

Step 2: Build Templates and Checklists

Don't just document—create tools people can actually use.

Examples:

  • Project kickoff checklist: What needs to happen in week 1 of every project? Stakeholder alignment? Requirements gathering? Risk identification? Make a checklist. Now every PM on your team can run a solid kickoff without you.

  • Status report template: Create a standard format (Wins, Risks, Next Steps). Now your team writes updates you can scan in 2 minutes instead of 20.

  • Decision log template: When big decisions are made, capture: What was decided? Why? Who was involved? What data informed it? Now you have institutional memory.

Data Point: According to Atlassian's 2024 State of Teams report, teams that use standardized templates see 35% faster onboarding for new hires and 28% fewer miscommunications.

Your Action: Identify the top 3 tasks your team does repeatedly. Build templates or checklists for each. Roll them out. Watch your time free up.

Step 3: Create Rituals, Not One-Offs

Orchestrators build rhythms that ensure quality without constant oversight.

Examples:

Bad: You check in on projects whenever you remember or when something feels off.
Good: You have a standing weekly "Delivery Review" where every PM presents their top 3 risks. It's on the calendar. It's expected. Problems surface early.

Bad: You give feedback whenever something goes wrong.
Good: You have a monthly "Retro of Retros" where the team reflects on what's working/not working in your delivery process. Continuous improvement is baked in.

Bad: You hoard knowledge.
Good: You run a bi-weekly "Lunch & Learn" where team members present frameworks, tools, or lessons learned. Knowledge spreads horizontally.

The Pattern: Rituals create predictability and accountability without you micromanaging.

Your Action: Add one recurring ritual to your calendar this month. A weekly risk review. A monthly retro. A quarterly planning session. Make it non-negotiable.

Step 4: Coach the Mindset, Not the Task

When someone comes to you with a problem, resist the urge to solve it.

Instead, ask:

  • "What do you think we should do?"

  • "What options have you considered?"

  • "What would you need to feel confident making this call?"

Example:

Team Member: "The client wants to add 3 new features mid-sprint. What should I do?"

Executor Response: "Okay, here's what we'll do. Push feature X to next sprint, negotiate feature Y down to MVP, and..."
(You solved it. They learned nothing.)

Orchestrator Response: "Good question. Walk me through your options. What's the impact of each on timeline and scope? What's your recommendation?"
(They solve it. You coach them. Next time, they won't need to ask.)

Data Point: According to Google's Project Oxygen research, being a good coach was identified as the single most important quality of effective managers. The study found that higher-scoring managers held frequent 1:1 meetings with their teams and focused on coaching rather than directing. After implementing coaching-focused management training, Google saw statistically significant improvements in 75% of their worst-performing managers.

Your Action: Next time someone asks you to make a call, pause. Ask them what they'd do first. Coach their thinking, don't bypass it.

Step 5: Make Your Team Comfortable Making Decisions Without You

If your team waits for you to be in the room before making decisions, you've trained them to be dependent.

The Fix: Set clear decision rights.

Example Decision Framework:

  • Type 1 Decisions (Reversible, low-impact): Team decides. No need to ask me. Examples: Meeting times, task assignments, tool choices for internal use.

  • Type 2 Decisions (Reversible, medium-impact): Team decides and informs me afterward. Examples: Sprint prioritization, stakeholder communication approach.

  • Type 3 Decisions (Irreversible or high-impact): Team proposes, we discuss, I make final call. Examples: Major architecture decisions, vendor contracts, headcount allocation.

Once you set this framework, hold the line. If someone asks you to make a Type 1 decision, send it back: "This is a Type 1. What's your call?"

Your Action: Define decision rights for your team this week. Share it. Enforce it.

5. How to Know You've Made the Shift

You'll know you're orchestrating (not just executing) when:

Your calendar has whitespace. If you're in back-to-back meetings, you're still doing, not leading.

Your team makes good decisions without you. They don't wait for permission. They come to you for coaching, not approval.

You can take a week off without panic. The system runs smoothly because the system doesn't depend on you.

You're working on the business, not in it. You're identifying new problems to solve, not firefighting old ones.

People outside your team reference your frameworks. Other orgs are adopting what you built. That's leverage.

Warning Sign You're Not There Yet:

If you say things like:

  • "I'm the only one who can do this."

  • "It's faster if I just do it myself."

  • "My team isn't ready to handle this."

...you're still executing. And you're capping your growth.

6. The Uncomfortable Truth About Letting Go

Here's what nobody tells you:

Letting go feels like losing control.

You built your career on being the person who gets things done. Now you're being asked to not do the thing you're best at.

It's terrifying.

But here's the reframe: Control doesn't scale. Systems do.

If you can only deliver great outcomes when you're executing, you'll never lead at scale.

But if you can build a system that delivers great outcomes without you, you've unlocked leverage.

And leverage is what separates managers from executives.

The Mantra:

"My job isn't to be the best player on the field. It's to build a team that wins without me on the field."

7. Your 30-Day Orchestration Sprint

Want to make the shift? Here's your action plan:

Week 1: Audit your time

  • Track everything you do for 1 week

  • Categorize: "Only I can do this" vs. "Someone else could do this"

  • Identify 3 tasks you're doing that someone else should own

Week 2: Document and delegate

  • Pick 1 of those 3 tasks

  • Document your decision-making process (write it like you're teaching it)

  • Delegate it to someone with clear expectations and coaching support

Week 3: Build a framework

  • Identify 1 repeatable decision you make constantly

  • Write down your mental model (criteria, tradeoffs, examples)

  • Share it with your team and have them use it for 1 week

Week 4: Create a ritual

  • Add 1 recurring meeting that creates accountability without you micromanaging

  • Could be: Weekly risk review, bi-weekly retro, monthly 1:1 deep dives

  • Make it non-negotiable and enforce it for a month

At the end of 30 days, ask:

  • Do I have more time to think strategically?

  • Is my team making better decisions without me?

  • Did anything break when I stepped back?

If yes, yes, no—you're orchestrating.

TL;DR: Orchestration isn't about doing less work. It's about doing different work. Stop being the person who saves every project. Start being the person who builds systems so good that projects don't need saving. Document your thinking. Build templates. Create rituals. Coach, don't solve. Make yourself replaceable. That's how you go from manager to executive.

🤝 Support the Community

  • Community: Submit a recommendation by replying to this email!

  • Leaders: Apply to be featured by replying to this email.

  • Recruiters/Hiring Managers: Get your job in front our community. You got it - just hit reply.

If you’re reading this on the web, feel free to send an email to [email protected]

Buy us a coffee so we can keep doing this.

Got something cool? Let’s get it out there.

Was this email forwarded to you?

How I can Help

Wanna chat IRL? Connect with me on LinkedIn and we can set up some time.

The Delivery Career Decoder shows why you’re already qualified for more—and how to prove it.

I love feedback. If you have topics you want to see? Or thoughts or ideas on how to serve the community better, please hit reply or email [email protected].

Until next time,

The Business of Delivery

Quiet moves. Bold Careers.

Login or Subscribe to participate

Keep Reading

No posts found