Something worth noticing across recent hiring: the same core job keeps showing up under very different names.

JPMorgan calls it Lead Technical Program Manager. EY calls it Senior Manager, Transformation Architecture and Delivery. Coloplast calls it a Digital, Data & IT Business Partner. The UN calls it a Programme Management Consultant. Strip away the titles and the accountabilities line up closely: manage dependencies, own risk, run governance, keep stakeholders aligned, report status upward.

One detail stood out beyond the title mismatch. JPMorgan's posting explicitly asks program managers to use enterprise-authorized AI to consolidate inputs into RAID logs and executive updates, then validate the output before it goes anywhere near a steering committee. That's one posting, not a pattern yet, but it's an early signal that the craft of program leadership is shifting faster than job titles are catching up to it.

My reading is that title inconsistency isn't just an HR annoyance. It can lead candidates to misjudge scope, hiring teams to screen for the wrong background, and compensation bands to drift away from actual accountability.

A few questions worth sitting with, whether you're job hunting or building a team:

• Are you evaluating a role by its title or by what it actually owns on risk, dependencies, and governance?
• If AI tools start drafting your RAID logs and status decks, who signs off before that content reaches leadership?
• When you write a job description, does the title reflect the accountability, or just whatever the org chart happened to call it last time?

I'd be interested in hearing how others have handled the title-versus-accountability gap, especially as AI starts touching the planning and risk work itself. Where have you seen it handled well, or badly?

Evidence and methodology: https://ai.intelligence.strategichonesty.com/reports/stakeholder-management-postings-moved-down-this