JHU Career Architecture: AI Fluency as a Career Stream

What JHU's Career Architecture Actually Is

JHU's Career Architecture is a 2024–2025 Johns Hopkins University initiative that reclassifies approximately 16,000 staff jobs into 18 job families with defined career streams and levels¹. The first phase— covering roughly 1,309 staff in HR and IT— launched in January 2025². Phased rollout continued through July 2025, and the myCareer platform, described internally as JHU's own internal LinkedIn, launched in October 2025³.

The structure is plain enough. Every staff job sits inside a career stream (the kind of work), at a level (the depth of responsibility), within a job family (the discipline)⁴. Subfamilies sharpen the picture inside the larger families. Roughly two thousand individual job titles have collapsed into eighteen¹.

What this is not: it is not a faculty path, not a pay-cut exercise, and not an AI program. It is a public statement that growth at Johns Hopkins is now defined by competencies, not titles⁴. And when competency replaces tenure as the engine of advancement, the question every staff member faces is the same: which competencies actually move me up the stream?

The Holdout Has the Right Data, the Wrong Conclusion

The senior leader who tried Copilot once and quit is statistically defensible. MIT's NANDA initiative found that 95% of enterprise generative AI pilots fail to deliver measurable business impact⁵, and global survey data shows roughly eight in ten workers are bypassing or refusing AI tools their employers have deployed⁷. The verdict is correct. The conclusion— "this is not for me"— is where the analysis breaks down.

Fortune's coverage of MIT's GenAI Divide report locates the 95% failure in enterprise integration practices— not in the model itself⁵. Vendor-purchased tools and partnership deployments succeed about 67% of the time; internal builds clock in at roughly a third of that⁶. Critics like Marketing AI Institute push back on the methodology, but even the conservative read leaves the base rate ugly.

The Copilot-specific picture is no kinder. Workplace conversion sits near 35.8%⁸, and most enterprise rollouts climb for six to eight weeks before stalling between 15% and 25% adoption⁹. Per Petri's analysis, Copilot's accuracy Net Promoter Score slid from -3.5 in July 2025 to -24.1 in September 2025¹⁰. Trust deteriorated faster than tenure.

If 95% of pilots fail, the holdout is right about the base rate and wrong about the conclusion. The 5% that succeed look nothing like a casual first attempt. They look like this:

• A specific task chosen, not a generic demo opened
• Structured onboarding, not a help-tip popup
• A vendor or partnership in the loop, not a solo experiment

The senior leader didn't run that experiment. He ran the one almost everyone runs— and he got the result almost everyone gets.

If the data validates the prior but invalidates the conclusion, the question becomes: why does this particular reader— the senior pattern-matcher— bounce off Copilot harder than anyone else?

The Expertise Paradox — Why Senior Pattern-Matchers Reject AI Fastest

Senior experts reject AI tools faster than junior staff because their pattern recognition catches small errors instantly, and those errors register as a verdict on the whole tool rather than as a workflow-fit problem¹¹. The expertise paradox is structural: the same compressed judgment that makes a thirty-year career valuable is the judgment that closes the Copilot tab in ninety seconds.

Junior staff don't catch the error. They use the output, learn the tool's edges over weeks, and route around the weak spots. The senior catches it in a paragraph and stops. More pattern data, lower noise tolerance, higher opportunity cost per minute— all the things that make the role expensive make the demo expendable.

The 10% of judgment AI cannot do is exactly what senior experts deliver— which means the leverage is not in replacing them, it's in matching the tool to the 90% they shouldn't be doing.

There is a second wrinkle. Effectively supervising AI requires the same expert skills that atrophy when one over-relies on it¹². That is the supervision paradox, and it cuts both ways: the holdout who refuses is preserving the skill but missing the leverage, and the over-reliant user is gaining the leverage but losing the skill. Both are true. Neither is safe alone.

Here is the ninety-second moment in plain view. The VP opens Copilot, asks for a draft of a board memo, reads two paragraphs, sees a hallucinated metric inside a sentence that is otherwise plausible, and closes the tab. The instinct fired. The fluency assessment that should have followed— what is this tool actually for, and is the board memo even the right test— never started. You can't read the label from inside the bottle. The deployment was the variable; the leader assumed the tool was.

Connect that back to the Career Architecture frame. AI fluency, if we name it, is a competency— and competency means knowing where the tool fits, not whether it works. The 90-second verdict tested fit by accident. Fluency tests fit on purpose. See AI fundamentals for the wider competency picture; the leverage point is not the model.

If the rejection is structural, the second attempt has to be structural too. Casual won't fix what casual broke.

What a Structured Second Attempt Looks Like

A structured second attempt matches the tool to tasks where senior judgment is the leverage and AI handles the volume— drafts, summaries, first-pass research, structured comparison work— under a deployment that includes training, governance, and an internal AI Champion. Casual exploration produced the 90-second verdict; structured deployment is what flips the 5% column.

Three scaffolds are missing in the 75–85% of stalled rollouts⁹:

• Structured training tied to specific tasks, not generic demos
• Usage governance that defines what's appropriate input, what's reviewed, what's logged
• Internal AI Champions who hold the social contract for the team's adoption curve

Vendor-purchased and partnered deployments succeed roughly 67% of the time⁶. That is not a software story; it is a delivery-model story. An AI strategy roadmap earns its keep here— not by adding a tool, but by deciding which task gets the tool and which doesn't.

Fielding Jezreel— a federal grant writing consultant with a decade in the discipline— ran the holdout's exact arc and ended somewhere different. He bought and refunded multiple AI tools through 2024 because the tools "claimed to do things they absolutely could not do." By October 2024 he was telling himself a familiar sentence: I don't get it; this isn't doing what I need. Then he stopped running the casual experiment and started running a structured one— framed around his own domain expertise and the specific tasks AI could actually carry— and ended up building a suite of five custom tools his peers now use.

The first attempt failed because the senior expert was the wrong user for the wrong task on a tool with no scaffolding. The structured second attempt changed all three variables— and it was the same person. Domain expertise plus AI is the magic; domain expertise alone burns the leader out, and AI alone burns the company's budget. This is the pattern senior leaders at large institutions need to see modeled before they'll stop calling themselves holdouts; see how for founders & leaders we frame the first-attempt-second-attempt distinction.

The career framework JHU built makes that second attempt unavoidable. The only question is whether you make it on your terms or on someone else's timeline.

The Career Architecture Reading — AI Fluency Is Now a Career Stream

JHU's Career Architecture does not name AI fluency as a competency, but the framework's logic forces it onto every career stream⁴. When growth is defined by competencies rather than tenure, the leader who refuses to develop AI fluency is not preserving expertise— they are removing themselves from the growth path the framework was built to create.

Career Architecture made the implicit explicit: growth is competency-defined, and the next competency is fluency with the tools the institution is already paying for. The holdout posture made sense in 2024. By 2026, the same posture is a self-imposed career-stream demotion. This is the chasm-crossing moment for AI fluency at large institutions, and JHU is the bellwether peer institutions are watching.

If your firm is at the same fork JHU's leadership made institutional, the leverage is in mapping the structured second attempt before the casual first one happens. The first move is naming the tasks where senior judgment is the leverage and AI carries the volume— drafts, summaries, first-pass research, structured comparison. That is the work an AI implementation services partner can do peer-to-peer with senior leadership, in weeks, before the 95% column claims another rollout. The instinct that closed the tab is still the asset. The deployment around it is what changes.

FAQ

What is JHU Career Architecture?

JHU Career Architecture is a 2024–2025 Johns Hopkins University initiative reclassifying approximately 16,000 staff jobs into 18 job families with defined career streams and levels¹. The first phase, covering 1,309 staff in HR and IT, launched in January 2025², with phased rollout continuing through July 2025 and the myCareer platform launching that October³.

Why does Microsoft Copilot adoption stall?

Most enterprise Copilot rollouts stall at 15–25% adoption six to eight weeks after launch when structured training, usage governance, and internal AI Champions are absent⁹. The technology is rarely the variable that fails; the deployment design is. Conversion across the broader workplace sits near 35.8%⁸, which means roughly two-thirds of licensed users aren't actively using the tool.

What did MIT find about enterprise AI pilots?

MIT's NANDA initiative found that 95% of enterprise generative AI pilots fail to deliver measurable P&L impact, with the failure rooted in enterprise integration practices rather than model quality⁵. Vendor-purchased tools and partnership-based deployments outperform internal builds roughly three to one— about 67% success versus a third of that⁶.

Why do experienced senior leaders reject AI tools faster than junior staff?

Compressed pattern recognition lets senior experts spot AI errors instantly, and those errors register as a verdict on the whole tool rather than as a workflow-fit problem¹¹. The same instinct that makes a long career valuable is the instinct that closes the Copilot tab in ninety seconds. Effective AI supervision also requires the very expert skills that atrophy under over-reliance, which is why structured deployment matters more for seniors than juniors¹².

References

1. Johns Hopkins University, "JHU announces Career Architecture Project" (2024) — https://hub.jhu.edu/at-work/2024/05/03/career-architecture-project/
2. Johns Hopkins University, "Career Architecture's work has started" (2025) — https://hub.jhu.edu/at-work/2025/03/03/career-architecture-foundation-work-has-started/
3. Johns Hopkins University, "A new experience creating career pathways" (2025) — https://hub.jhu.edu/at-work/2025/10/17/new-experience-creating-career-pathways/
4. Johns Hopkins University HR, "Career Architecture" (2025) — https://hr.jhu.edu/learn-grow/career-architecture/
5. Fortune (citing MIT NANDA), "MIT report: 95% of generative AI pilots at companies are failing" (2025) — https://fortune.com/2025/08/18/mit-report-95-percent-generative-ai-pilots-at-companies-failing-cfo/
6. Fortune (citing MIT NANDA), "MIT report: 95% of generative AI pilots at companies are failing" (2025) — https://fortune.com/2025/08/18/mit-report-95-percent-generative-ai-pilots-at-companies-failing-cfo/
7. Fortune, "Most of you are rejecting AI. The data shows you're running out of time" (2026) — https://fortune.com/2026/04/16/ai-resistance-running-out-of-time-rebellion-quiet-quitting-trust/
8. Stackmatix, "Microsoft Copilot Enterprise Adoption in 2026: What the Data Shows" (2026) — https://www.stackmatix.com/blog/microsoft-copilot-enterprise-adoption-2026
9. The Human Co., "Why Microsoft Copilot Rollouts Stall at 20% Adoption" (2025) — https://www.thehumanco.org/blog/why-microsoft-copilot-adoption-fails
10. Petri, "Why Microsoft Copilot Adoption Is Lagging: The ROI Dilemma" (2025) — https://petri.com/microsoft-copilot-adoption-roi/
11. Knowledge Architecture, "The AI and Expertise Paradox" (2024) — https://www.knowledge-architecture.com/blog/the-ai-and-expertise-paradox
12. Facing Disruption, "The Expertise Paradox: Why AI's Greatest Promise May Be Its Biggest Risk" (2024) — https://www.facingdisruption.com/p/the-expertise-paradox-why-ais-greatest