[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"article-raise-us-ai-jobs-push-retraining-playbook-en":3,"article-related-raise-us-ai-jobs-push-retraining-playbook-en":30,"series-industry-043c2044-b1aa-49b9-9735-b74485f5148e":73},{"id":4,"slug":5,"title":6,"content":7,"summary":8,"source":9,"source_url":10,"author":11,"image_url":12,"cover_image":12,"category":13,"language":14,"translated_content":11,"related_article_id":15,"keywords":16,"key_takeaways":22,"views":26,"created_at":27,"published_at":28,"topic_cluster_id":29},"043c2044-b1aa-49b9-9735-b74485f5148e","raise-us-ai-jobs-push-retraining-playbook-en","RAISE US turns AI anxiety into retraining","\u003Cp data-speakable=\"summary\">A copy-ready playbook for turning AI layoffs into retraining programs.\u003C\u002Fp>\u003Cp>I've been watching the AI jobs conversation turn into a weird kind of corporate theater. Every company says it cares about workers. Every policy pitch says it wants to protect jobs. And then the actual plan usually boils down to a glossy PDF, a panel, and a promise that “reskilling” will happen someday. That’s been off for me from day one.\u003C\u002Fp>\u003Cp>What I keep running into is this: leaders want the optics of helping workers without the mess of building a real system. They want to say AI will create opportunity, but they don’t want to fund the plumbing that makes that opportunity usable. So when I saw a new effort with actual corporate money and actual employer names behind it, I stopped rolling my eyes for a second. Not because I think this solves the problem. It doesn’t. But because it finally looks like someone is trying to turn the vague “AI transition” talk into a repeatable operating model instead of another slogan.\u003C\u002Fp>\u003Cp>This write-up is me unpacking that model the way I’d explain it to a team that needs to build something similar without copying the fluff.\u003C\u002Fp>\u003Cp>I’m working from POLITICO’s report on the launch of \u003Ca href=\"https:\u002F\u002Fwww.politico.com\u002Fnews\u002F2026\u002F06\u002F25\u002F500-million-ai-jobs-push-launches-with-bipartisan-backing-00975439\">RAISE US\u003C\u002Fa>, a nonprofit backed by corporate donors including \u003Ca href=\"\u002Ftag\u002Fanthropic\">Anthropic\u003C\u002Fa>, \u003Ca href=\"\u002Ftag\u002Fopenai\">OpenAI\u003C\u002Fa>, Amazon, \u003Ca href=\"\u002Ftag\u002Fmicrosoft\">Microsoft\u003C\u002Fa>, Bank of America, General Motors, and Eli Lilly. The pitch is simple enough: fund retraining programs so workers can move into new roles instead of getting tossed out when AI changes the workflow. I’m not going to pretend the article gives me every operational detail, because it doesn’t. What it does give me is the shape of the bet, and that’s enough to break down the playbook.\u003C\u002Fp>\u003Ch2>Stop treating retraining like an HR side quest\u003C\u002Fh2>\u003Cblockquote>“Named RAISE US, the nonprofit will work with corporate donors including Anthropic, OpenAI, Amazon, Microsoft, Bank of America, General Motors and pharmaceutical giant Eli Lilly to design and implement programs to retrain workers for new roles, as a way to deter layoffs.”\u003C\u002Fblockquote>\u003Cp>What this actually means is that retraining is being framed as infrastructure, not a perk. That matters. Most companies treat learning as a benefit page somewhere between the commuter stipend and the meditation app. Nice to have. Easy to cut. Hard to measure. This model flips that. It says if AI is going to change job tasks at scale, then worker transition has to be part of the business response, not a cleanup activity after the layoffs hit.\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1782440303660-nhza.png\" alt=\"RAISE US turns AI anxiety into retraining\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>I’ve seen the opposite happen plenty of times. A team automates a workflow, productivity goes up, and then six months later the company acts surprised that the people doing that work need a new path. That’s not a talent problem. That’s a planning failure. If you know a role is being compressed, you should also know which adjacent roles can absorb that person, what \u003Ca href=\"\u002Ftag\u002Fskills\">skills\u003C\u002Fa> are missing, and how long the bridge takes.\u003C\u002Fp>\u003Cp>How to apply it: if you’re building a company or policy program around AI transition, stop starting with “training content.” Start with role mapping. List the jobs being reduced, the jobs being created, and the tasks that connect them. Then fund the bridge, not the brochure. If you can’t name the destination roles, your retraining program is just a motivational poster with a budget.\u003C\u002Fp>\u003Cul>\u003Cli>Map current roles to likely next roles before you buy any training vendor.\u003C\u002Fli>\u003Cli>Define the skills gap in tasks, not abstract competencies.\u003C\u002Fli>\u003Cli>Make the transition budget visible, not buried inside HR overhead.\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>Don’t let donors hide behind generic good intentions\u003C\u002Fh2>\u003Cp>The donor list is doing a lot of work here. Anthropic, OpenAI, Amazon, Microsoft, Bank of America, General Motors, and Eli Lilly are not random names tossed into a philanthropy bucket. They represent different pressure points in the labor market: software, cloud, finance, manufacturing, and pharma. That mix matters because AI disruption won’t hit one sector cleanly. It will move through white-collar support work, operations, compliance, customer service, logistics, and technical roles all at once.\u003C\u002Fp>\u003Cp>What I take from that is this: a useful retraining initiative needs employers who can actually name the jobs they expect to change. Donors should not just write checks and disappear. They should help define the skills, the timelines, and the internal mobility paths. Otherwise the nonprofit becomes an expensive conference machine.\u003C\u002Fp>\u003Cp>I’ve sat in enough “future of work” meetings to know how this usually goes. Everyone agrees on the principle. Nobody wants to commit to the hard parts: which roles are shrinking, which teams will host apprenticeships, and who gets measured on placement outcomes. That’s where these programs die. Not in the announcement. In the handoff.\u003C\u002Fp>\u003Cp>How to apply it: if you’re running a coalition, make each donor sponsor one concrete piece of the pipeline. One company helps define job families. Another funds assessment tools. Another opens apprenticeship slots. Another publishes internal mobility data. If every donor is only there for brand safety, you’ve already lost.\u003C\u002Fp>\u003Cul>\u003Cli>Assign each partner a specific operational responsibility.\u003C\u002Fli>\u003Cli>Require job-family mapping from employers, not just funding.\u003C\u002Fli>\u003Cli>Track placement, retention, and wage movement, not attendance.\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>Make the program boring enough to scale\u003C\u002Fh2>\u003Cp>The article says RAISE US will “design and implement programs” to retrain workers. That wording sounds plain, but I think it’s the right kind of plain. The minute these efforts become too visionary, they become unusable. People start talking about ecosystems, pathways, and transformation journeys, and suddenly nobody can tell me how many workers actually completed a module and moved into a new role.\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1782440302110-kffj.png\" alt=\"RAISE US turns AI anxiety into retraining\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>What this actually means is the program has to be boring in the best possible way. Standardized intake. Clear skill assessments. Modular training. Employer-aligned credentials. Scheduled placement windows. No heroics. No custom one-off miracle curriculum for every company. If you want scale, you need repeatable mechanics.\u003C\u002Fp>\u003Cp>I ran into this while helping teams design internal upskilling programs. The temptation is always to over-customize. “Our workforce is unique.” Sure. Everyone says that right before they build a training system nobody can maintain. The better move is to standardize 80 percent and customize the last 20 percent where the job really differs.\u003C\u002Fp>\u003Cp>How to apply it: define a core workflow for every retraining program. Intake, assessment, learning plan, practice, placement, follow-up. Then decide which parts can be shared across employers and which parts need sector-specific content. If your process can’t be explained in five steps, it’s too complicated to survive contact with real workers.\u003C\u002Fp>\u003Cul>\u003Cli>Use one intake form across all participating employers.\u003C\u002Fli>\u003Cli>Keep assessments short and tied to actual job tasks.\u003C\u002Fli>\u003Cli>Build a shared curriculum spine, then add sector modules.\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>Measure layoffs avoided, not just courses completed\u003C\u002Fh2>\u003Cp>The POLITICO framing is interesting because it ties retraining to deterring layoffs. That’s a much stronger claim than “we offered training.” It changes the metric. Completion rates are nice, but they don’t tell me whether the program actually kept people employed. If the goal is to reduce displacement, then the scoreboard has to include retention, redeployment, and wage stability.\u003C\u002Fp>\u003Cp>This is where a lot of workforce programs get lazy. They report how many people enrolled. Great. Did anyone land somewhere useful? Did they keep working three months later? Six months later? Did they move into a role that paid enough to matter? If you don’t measure that, the program can look successful while doing almost nothing.\u003C\u002Fp>\u003Cp>I’d also push for employer-side metrics. If a company says it’s using AI to reduce headcount, then it should also be able to show how many workers were redeployed into adjacent roles. That’s the real test. Not whether the company bought training credits. Whether it changed the labor outcome.\u003C\u002Fp>\u003Cp>How to apply it: build a dashboard that tracks workers from intake to placement to retention. Add one more line for displacement avoided if you can define the baseline. If you can’t define the baseline, at least track internal transfers and post-training wage movement. Those are harder to fake than course completions.\u003C\u002Fp>\u003Cul>\u003Cli>Track completion, placement, retention, and wage change.\u003C\u002Fli>\u003Cli>Separate “trained” from “redeployed.” They are not the same thing.\u003C\u002Fli>\u003Cli>Publish outcomes by employer and job family so nobody can hide averages.\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>Use bipartisan support as a delivery tool, not a slogan\u003C\u002Fh2>\u003Cp>The headline emphasizes bipartisan backing, and honestly, that part is more useful than it sounds. In the U.S., workforce policy usually gets stuck when it becomes a culture war prop. One side hears regulation. The other side hears corporate cover. Then nothing ships. If this coalition can keep the conversation focused on jobs, transition, and placement, it has a better chance of surviving the usual political mud fight.\u003C\u002Fp>\u003Cp>But bipartisan support only matters if it changes delivery. It should make it easier to coordinate federal, state, employer, and nonprofit action. It should help standardize funding rules. It should reduce the chance that each state invents its own half-broken version of the same retraining program. Otherwise it’s just a press-release adjective.\u003C\u002Fp>\u003Cp>I’ve worked around enough policy-adjacent projects to know that politics can either unblock implementation or bury it in ceremony. The trick is to use broad support to simplify the system, not to make everyone feel good in the room. If the result is more meetings, that’s failure with nicer branding.\u003C\u002Fp>\u003Cp>How to apply it: if you’re in government or a coalition, identify the one or two policy bottlenecks that bipartisan support can actually remove. Funding rules. Credential recognition. Apprenticeship approval. Data sharing. Pick the thing that slows delivery and fix that first.\u003C\u002Fp>\u003Ch2>Build the coalition around jobs, not AI worship\u003C\u002Fh2>\u003Cp>The strongest part of this whole setup is that it’s not pretending AI itself is the mission. The mission is worker transition. That sounds subtle, but it’s the difference between a useful program and a vanity project. If AI is the headline, the conversation drifts into model capability, vendor rivalry, and abstract productivity gains. If jobs are the headline, you have to answer harder questions about who moves, where they move, and what support they need.\u003C\u002Fp>\u003Cp>That’s the framing I’d keep if I were building a similar effort. Don’t center the tools. Center the labor outcome. The tools are only relevant insofar as they change the work. That’s also why the donor mix matters. These companies are not just AI vendors; they’re employers, buyers, and economic actors with real exposure to labor shifts.\u003C\u002Fp>\u003Cp>How to apply it: write your mission statement around worker movement. Not “prepare people for the age of AI.” That’s mush. Try “move workers from shrinking tasks into growing roles with employer-backed training and placement.” It’s less glamorous, which is exactly why it’s better.\u003C\u002Fp>\u003Cp>If you need a simple test, ask this: can a worker read your program description and know what happens to them next? If the answer is no, the program is still too abstract.\u003C\u002Fp>\u003Ch2>The template you can copy\u003C\u002Fh2>\u003Cpre>\u003Ccode># AI Transition Retraining Program Template\n\n## Mission\nMove workers from shrinking tasks into growing roles with employer-backed training, placement, and follow-up.\n\n## Who this is for\n- Employees in roles affected by automation or AI-assisted workflow changes\n- Employers that want to reduce avoidable layoffs\n- Public, nonprofit, or coalition partners funding workforce transition\n\n## Program structure\n1. Identify at-risk roles\n2. Map adjacent roles with hiring demand\n3. Assess current skills against target roles\n4. Build a short, modular training plan\n5. Place workers into internships, apprenticeships, internal transfers, or open roles\n6. Track retention and wage movement for 3, 6, and 12 months\n\n## Partner responsibilities\n### Employers\n- Publish the roles most likely to change\n- Provide job-family maps and skill requirements\n- Offer transfer slots, apprenticeships, or interview priority\n- Share outcome data on placement and retention\n\n### Training partners\n- Create a shared curriculum spine\n- Keep assessments tied to real job tasks\n- Use short modules that workers can finish while employed\n- Report completion and readiness by role family\n\n### Funders\n- Pay for assessment, training, and placement support\n- Require outcome reporting, not just enrollment counts\n- Tie renewal funding to retention and wage outcomes\n\n### Program operator\n- Manage intake and eligibility\n- Match workers to target roles\n- Coordinate employers and training partners\n- Publish a monthly outcomes dashboard\n\n## Core metrics\n- Workers assessed\n- Workers enrolled\n- Workers completed training\n- Workers placed into new roles\n- 90-day retention rate\n- 180-day retention rate\n- Wage change after placement\n- Internal transfer rate\n- Layoffs avoided, if baseline data exists\n\n## Minimum reporting template\n- Company \u002F partner name\n- Role family affected\n- Target role family\n- Number of workers served\n- Number completed\n- Number placed\n- Median wage change\n- Retention at 90 \u002F 180 \u002F 365 days\n- Notes on barriers and fixes\n\n## Copy-ready program language\n\"This program exists to move workers from roles affected by AI-driven workflow changes into adjacent roles through employer-backed assessment, training, placement, and retention support. Success is measured by redeployment, retention, and wage stability, not by course completion alone.\"\n\n## First 30 days\n- Choose 3 at-risk role families\n- Choose 3 target role families\n- Recruit 2 employers, 1 training partner, and 1 funding partner\n- Build one intake form and one assessment rubric\n- Launch a pilot with a small cohort\n- Publish the first dashboard after 30 days\n\u003C\u002Fcode>\u003C\u002Fpre>\u003Cp>That’s the version I’d actually use. It’s plain, measurable, and annoying in the right ways. It forces everyone to talk about the same thing: where workers start, where they go, and whether the move held up.\u003C\u002Fp>\u003Cp>If you want to make it better, add sector-specific modules, local labor market data, and a tighter employer commitment on placement. But don’t lose the spine. The spine is what keeps this from turning into another well-meaning training initiative that nobody can audit.\u003C\u002Fp>\u003Cp>My honest read is that RAISE US is interesting because it treats worker retraining like something that needs coalition design, not just curriculum design. That’s the part worth copying. Not the branding. Not the donor list. The operating logic.\u003C\u002Fp>\u003Cp>Source attribution: I’m breaking down POLITICO’s report on RAISE US from \u003Ca href=\"https:\u002F\u002Fwww.politico.com\u002Fnews\u002F2026\u002F06\u002F25\u002F500-million-ai-jobs-push-launches-with-bipartisan-backing-00975439\">https:\u002F\u002Fwww.politico.com\u002Fnews\u002F2026\u002F06\u002F25\u002F500-million-ai-jobs-push-launches-with-bipartisan-backing-00975439\u003C\u002Fa>. The template above is my own derivative framework built from that reporting, not a reproduction of the article.\u003C\u002Fp>","I break down RAISE US and turn its retraining pitch into a copy-ready playbook for AI-era workforce programs.","www.politico.com","https:\u002F\u002Fwww.politico.com\u002Fnews\u002F2026\u002F06\u002F25\u002F500-million-ai-jobs-push-launches-with-bipartisan-backing-00975439",null,"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1782440303660-nhza.png","industry","en","aead5b75-715f-4754-b9f9-45e46f60fa6d",[17,18,19,20,21],"AI jobs","retraining","workforce transition","RAISE US","layoffs",[23,24,25],"Retraining has to be treated as infrastructure, not an HR perk.","Employer coalitions need concrete responsibilities, not generic goodwill.","Measure placement and retention, not just course completion.",0,"2026-06-26T02:17:56.674034+00:00","2026-06-26T02:17:56.657+00:00","d19fc184-5852-4c4d-9ec0-db0c4841ac17",{"tags":31,"relatedLang":32,"relatedPosts":36},[],{"id":15,"slug":33,"title":34,"language":35},"raise-us-ai-jobs-push-retraining-playbook-zh","RAISE US 把焦慮變成再訓練","zh",[37,43,49,55,61,67],{"id":38,"slug":39,"title":40,"cover_image":41,"image_url":41,"created_at":42,"category":13},"385638be-f2b8-4512-adaa-84829c12b769","product-hunt-best-prompt-engineering-tools-2026-en","Product Hunt’s best prompt tools now split by job","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1782507772133-wbrr.png","2026-06-26T21:02:19.575752+00:00",{"id":44,"slug":45,"title":46,"cover_image":47,"image_url":47,"created_at":48,"category":13},"35207994-7ae5-49b2-b4e6-a981557ca423","xcode-266-gemini-ai-coding-stack-en","Xcode 26.6 Adds Gemini to Apple’s AI Coding Stack","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1782497870381-0m3t.png","2026-06-26T18:17:25.6244+00:00",{"id":50,"slug":51,"title":52,"cover_image":53,"image_url":53,"created_at":54,"category":13},"ead2ce1d-fa17-413f-804e-6c51cdbd1ef5","openai-anthropic-must-sell-efficiency-not-excess-en","OpenAI and Anthropic must sell efficiency, not excess","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1782496964720-x5vl.png","2026-06-26T18:02:20.072557+00:00",{"id":56,"slug":57,"title":58,"cover_image":59,"image_url":59,"created_at":60,"category":13},"19a1449e-0b36-419b-a3b1-39782d7aba3f","ai-code-review-tools-catch-issues-earlier-en","10 AI code review tools that catch issues earlier","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1782491580641-ogdx.png","2026-06-26T16:32:32.260156+00:00",{"id":62,"slug":63,"title":64,"cover_image":65,"image_url":65,"created_at":66,"category":13},"02c78a22-caba-4979-bedd-df83717c1092","openai-ipo-delay-turns-hype-into-caution-en","OpenAI's IPO delay turns hype into caution","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1782489796090-411x.png","2026-06-26T16:02:51.495841+00:00",{"id":68,"slug":69,"title":70,"cover_image":71,"image_url":71,"created_at":72,"category":13},"267496b1-1d65-40d0-a517-ab2f00668464","suno-launches-spark-indie-artists-en","Suno Launches Spark to Court Indie Artists","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1782486179017-3smg.png","2026-06-26T15:02:32.282726+00:00",[74,79,84,89,94,99,104,109,114,119],{"id":75,"slug":76,"title":77,"created_at":78},"d35a1bd9-e709-412e-a2df-392df1dc572a","ai-impact-2026-developments-market-en","AI's Impact in 2026: Key Developments and Market Shifts","2026-03-25T16:20:33.205823+00:00",{"id":80,"slug":81,"title":82,"created_at":83},"5ed27921-5fd6-492e-8c59-78393bf37710","trumps-ai-legislative-framework-en","Trump's AI Legislative Framework: What's Inside?","2026-03-25T16:22:20.005325+00:00",{"id":85,"slug":86,"title":87,"created_at":88},"e454a642-f03c-4794-b185-5f651aebbaca","nvidia-gtc-2026-key-highlights-innovations-en","NVIDIA GTC 2026: Key Highlights and Innovations","2026-03-25T16:22:47.882615+00:00",{"id":90,"slug":91,"title":92,"created_at":93},"0ebb5b16-774a-4922-945d-5f2ce1df5a6d","claude-usage-diversifies-learning-curves-en","Claude Usage Diversifies, Learning Curves Emerge","2026-03-25T16:25:50.770376+00:00",{"id":95,"slug":96,"title":97,"created_at":98},"69934e86-2fc5-4280-8223-7b917a48ace8","openclaw-ai-commoditization-concerns-en","OpenClaw's Rise Raises Concerns of AI Model Commoditization","2026-03-25T16:26:30.582047+00:00",{"id":100,"slug":101,"title":102,"created_at":103},"b4b2575b-2ac8-46b2-b90e-ab1d7c060797","google-gemini-ai-rollout-2026-en","Google's Gemini AI Rollout Extended to 2026","2026-03-25T16:28:14.808842+00:00",{"id":105,"slug":106,"title":107,"created_at":108},"6e18bc65-42ae-4ad0-b564-67d7f66b979e","meta-llama4-fabricated-results-scandal-en","Meta's Llama 4 Scandal: Fabricated AI Test Results Unveiled","2026-03-25T16:29:15.482836+00:00",{"id":110,"slug":111,"title":112,"created_at":113},"bf888e9d-08be-4f47-996c-7b24b5ab3500","accenture-mistral-ai-deployment-en","Accenture and Mistral AI Team Up for AI Deployment","2026-03-25T16:31:01.894655+00:00",{"id":115,"slug":116,"title":117,"created_at":118},"5382b536-fad2-49c6-ac85-9eb2bae49f35","mistral-ai-high-stakes-2026-en","Mistral AI: Facing High Stakes in 2026","2026-03-25T16:31:39.941974+00:00",{"id":120,"slug":121,"title":122,"created_at":123},"9da3d2d6-b669-4971-ba1d-17fdb3548ed5","cursors-meteoric-rise-pressures-en","Cursor's Meteoric Rise Faces Industry Pressures","2026-03-25T16:32:21.899217+00:00"]