The previous unit gave you a disciplined method for surfacing the right problems, filtering ruthlessly, and letting early wins generate momentum. But once those pilots start delivering results — and AI begins absorbing routine work — a harder question emerges: what happens to the people, the roles, and the structures around them? The conversation turned directly to this challenge, and the answer wasn't a wholesale org chart overhaul. It was something more practical and more courageous — rethinking how work gets organized around outcomes and employee journeys, mapping people to their adjacent futures, and defending a vision of redeployment over reduction.

You'll recall the conversation acknowledged a tension every people leader feels: rigid hierarchy, job descriptions, and career paths are increasingly mismatched to AI-native work, but "responsibly we can't talk about the complete removal of hierarchy and work charts in all of our companies." The practical move isn't to wait for permission to blow up the org chart — it's to start small. The discussion described pivoting teams toward an outcome and product mindset, putting the employee at the center rather than the function. The concrete example was onboarding: instead of scattering ownership across HR, IT, and the hiring manager's team, you take "the technology, the experience I want to drive, the data and analytics I want to know about that person, the process" and assemble what was called an "outcome squad." The key word is iterate — you build one cross-functional squad around one employee journey, learn from it, and expand. As noted in the talk, "the org chart and hierarchy will eventually [...] deteriorate" — but you don't have to wait for that to start proving the model works. You do need