This is the last one.
Seven weeks ago I opened with a meeting you had probably been in, and a metaphor I knew would make some of you uncomfortable. The Titanic in plain sight. I asked you a question I’ve been carrying through every piece since: what would you do differently if you actually believed the people inside these decisions deserved co-authorship? I told you I would call four witnesses, walk you through the framework that holds them together, and ask the question one more time at the end. We have done all of that.
Now I am asking the question.
But before I do, I want to say one thing out loud. The thing that has been running underneath every piece in this series, that I have not yet stated directly, and that is the whole of it.
We are not automating work. We are automating dysfunction.
That is the verdict. That is what the seven weeks have been building toward. Every piece in this series has been a different angle on the same observation. Véliz showed us that we are using probabilistic systems in places where they do not belong, and treating the outputs as facts. The Amodeis showed us what it looks like when stated values actually constrain behavior, and what it looks like when stated values are absent. Brynjolfsson showed us the data on who is being hurt and how, and named the choice no one was naming. The view from inside the room showed us the Five Wounds of Change, alive in the language of the people carrying them, and the unfinished sentence the executive sponsor holding the pen could not complete. The framework showed us the order the work actually requires — Mindset before Heartset before Skillset before Toolset, the 4SET sequence, in the order almost every enterprise gets backwards. And underneath all of it, in every room this series has taken you into: Hands, Heads, Hearts. What we automate. What we augment. What we amplify. Three questions. Every rollout answers them whether anyone asks or not.
All of it points to the same place. We are pouring the most powerful technology of our generation into operating models that were already broken, decision-making structures that were already extractive, and workforce dynamics that were already asymmetric. We are accelerating the dysfunction. We are calling it transformation. And the people on the other side of these decisions — the ones we have not asked, the ones we have not consulted, the ones whose livelihoods and identities are being reshaped by choices they did not make — are absorbing the cost.
This is not a technology problem. It never was. It is a transformation problem with a technology component, and the technology is moving faster than the transformation work the system was built to do.
You don’t have to look far to see this happening in real time. In April, Jack Dorsey and Sequoia’s Roelof Botha published an essay arguing that AI can now replace the coordination work middle managers have done for centuries — five weeks after Block cut roughly 4,000 jobs. Their proposed metric for whether the new model is working: money. “The most honest signal in the world,” they called it. Not the workforce. Not the people whose roles were routed away. The money.
That’s not a hypothetical. That’s the pattern, in public, argued in three thousand words, by two people with the platform to set the terms other companies follow.
I want to bring my parents back into this piece for a paragraph, because I’ve been thinking about them every week of the series.
My mom is a now-retired nurse. My dad was a farmer. In my forthcoming book, I call the chapter about them Soil & Souls, because it’s just the truest way to say it. She tended to souls. He tended to soil. Sacred labor, to both.
Both spent careers developing expertise the new systems are now eroding. My mom learned telehealth mid-career — a screen where a hand used to be, a webcam where her eyes used to meet a patient’s. She adapted. She still doesn’t fully trust a system that can’t feel a pulse change under its palm. My dad watched his instruments shift from the sky and the smell of a field after rain to a sensor that could tell him the moisture level of one patch of ground to the decimal. He would have used every bit of it. He also would have kept walking the field, because that’s where the meaning was, not the dashboard.
Both adapted; both grieved; neither one was asked. Craft or computer was never really the question. Who decides is.
Your workforce is full of my mother and my father. The senior practitioner in your organization, whose tacit knowledge is being codified into a model and deployed to a chatbot. The mid-career professional, whose judgment is being supplanted by a tool that cannot defend its reasoning. The new graduate, whose first job no longer exists because entry level work has been automated. The leader, whose own AI literacy is barely ahead of her workforce’s, and who has not been given the space to learn out loud.
None of these people were asked. Not permission, exactly. Not for a vote or veto. Just for the kind of lived expertise that might have made the decision better, the kind only the people closest to the consequences can give. Instead, they are absorbing a transformation that was decided somewhere above them, on a timeline that did not account for their absorption capacity, with a vocabulary stripped of the words they would need to surface what is happening to them.
That’s the part I cannot let go of. The asymmetry. The decisions being made far from the people who will live with them. The silence the workforce has been carrying because the conditions for speaking were never built.
You are not going to fix this with a better deck. You are going to fix this by interrupting it.
So here is the question I asked you to carry since the start of the series.
What would you do differently if you actually believed the people inside these decisions deserved co-authorship?
I want you to answer this. Out loud or to yourself, but actually answer it. Not in the abstract. About one decision you are making this week. The AI vendor evaluation you are about to sign off on. The pilot scope you are about to approve. The training program you are about to launch. The headcount target someone above you has set without consulting the workforce it will reshape.
Pick one. Hold it in your mind. And ask yourself, honestly: if the people who will live with this decision were in the room when you made it, what would you do differently?
Most readers, I suspect, will arrive at one of three answers.
The first answer is nothing. The decision is fine. The people would have agreed. The process was sound. If this is your honest answer, the decision was probably good. Move on.
The second answer is I would slow down. I would ask whether we have the strategy clear enough to defend. I would ask whether we have done the mindset and heartset work the deployment requires. I would ask whether we have actually named the substitution-versus-augmentation choice or whether we are letting the vendor scope it for us. If this is your honest answer, the decision is not fine. Slow it down. The cost of slowing it down is far smaller than the cost of being wrong.
The third answer is I would not make this decision at all without the people in the room. If this is your honest answer, you have just identified the work. Not the work of redesigning the decision. The work of redesigning the room in which decisions like this get made. That is bigger work. It is also the only work that actually addresses what we have been talking about for seven weeks.
I watched a version of this happen in miniature when my daughter Bailey was 9. She went in for a routine cavity fill, already dreading that alone. Then the plan changed mid-chair — the dentist looked closer, found more than she’d expected, and escalated us to The New Treatment Plan, a root canal, and started walking me through the new estimate. Over Bailey’s head. While she sat small and smaller in the chair, lip quivering, chest heaving under her softball hoodie.
Suddenly, a small voice cut into our big adult ones: “Mom, can I talk to you?”
Everyone stopped dead in their tracks. “Would you like us to leave the room?”
Yes, she nodded slowly.
She didn’t want comfort. She wanted information. Well, both. What is a root canal? Why did the plan change? Is it going to hurt? Do we need to do this? Do you get to stay? With Bailey’s permission, we asked the dentist back into the room, and I asked her to explain it all to Bailey instead of to me. She did, exquisitely — the tools, the steps, what Bailey would feel and when. Bailey listened, and then she told them to turn on the massage chair and go.
Nobody decided anything for her. They decided it with her, the moment she had what she needed to decide for herself. How did she know to do that? I’ve taught her, all three of my daughters, to reclaim her voice the moment she feels it being taken. But knowing how to ask is only half of it. Someone still has to stop and listen.
This time, the room did.
That’s the entire distance between the second answer and the third. My daughter did that work, at nine, in about ninety seconds. Most leadership teams won’t do it in a quarter.
You may have a different answer. The point is not which answer you arrive at. The point is that you arrive at one, honestly, about a specific decision, this week. Most of the time, in most organizations, the question never gets asked. Asking it once is more than most leadership teams will manage all year.
So here’s the Titanic Test. Before a decision earns its place in your roadmap, it needs three yeses.
Does it expand human potential? Does this move the people it touches toward more capability, or just more automation? If it’s the second, that’s not automatically a no, but name it. Don’t let it pass silently as the first.
Does it create measurable business impact? Can you name the metric this decision should move? If you can’t, it’s just motion, not progress.
Does it strengthen the institution you’re building? Were the people who will live with this decision in the room, or did it arrive fully formed, for them to accept? If the decision could be lifted from any company and dropped into yours without accounting for who works there, how work happens, or what people stand to lose, it isn’t transformation. It’s just boilerplate.
Miss any of the three, and that’s not a yellow flag. That’s the iceberg. You saw it. Now what do you do about it.
That’s the test. Here’s what you do with what it shows you.
A few practices to take with you. Not a checklist or framework. Three things that interrupt the pattern at the layer where the pattern lives.
Notice the silences. In every room you are in this week, watch for the question nobody asks. The participant who almost speaks and then doesn’t. The agenda item that gets deferred for the third time. The follow-up that never happens. Silences in enterprise conversations are not empty. They are full of the thing nobody wants to name. Notice them. You do not have to solve them. Noticing them is the first move.
Make one decision visible that you would normally bury. The Hands, Heads, Hearts framework is not abstract. It is the place where you can name, out loud, what AI is doing to a specific role on your team. Pick one role. Pick one project. Pick one workflow. State, explicitly: we are automating this. We are augmenting this. We are amplifying this. Communicate the decision to the people it affects. You do not have to be certain. You have to be transparent. The transparency is what produces trust. The decision being made invisibly or not at all is what kills it.
Slow one thing down. One pilot. One deployment. One training rollout. Identify it, and slow it by a quarter. Use the time for the mindset and heartset work the standard sequence is rushing past. Most enterprise AI failures are not from moving slowly. They are from moving fast in the wrong sequence. Slowing one thing down to do it correctly is the highest-leverage move available to most leaders this year.
Three practices. None require new budget. None require new vendors. All require the willingness to interrupt yourself, in a meeting, in a decision, in a room where the pattern is currently running.
That is the work.
Seven weeks ago I opened this series with the Titanic in plain sight. The metaphor has been doing the work I needed it to do. The ship was built by people who knew the lifeboats were inadequate, the icebergs were known, and the speed records mattered more than the safety margins. None of those decisions felt wrong in the rooms where they were made. All of them were wrong.
What we’re building now is bigger than a ship. And the rooms where we’re building it are smaller. The decisions are being made by people with little downstream line of sight or care. The icebergs are known, and the lifeboats are inadequate. The speed feels necessary. The speed is the problem.
You are not going to stop this from the outside. None of us are.
We are going to stop it from inside the rooms where the decisions are being made. By interrupting. By noticing. By naming what is happening to people and refusing to let the silence stand for consent. By making the substitution-versus-augmentation choice visible. By building the conditions for the workforce to speak. By letting belief actually constrain behavior. By doing the embodiment work the standard sequence rushes past. By asking the question, every quarter, in every room: what would we do differently if we actually believed the people inside this decision deserved to participate in it?
Noticing is the first act of civil disobedience.
The next act is yours.
Thank you for reading, all the way from the Titanic in plain sight, or from wherever you found this. That’s not nothing, in an environment built to spend your attention on things that don’t deserve it.
This series ends here. The work doesn’t.
I’ll see you out there.
— JVB
Jess Von Bank is the co-founder of Now to Next, a transformation firm specializing in the human dimensions of enterprise AI deployment. Her book, Work Like a Mother, will be published in the fall of 2026.
This is the seventh and final piece in the series. Read them all:
Piece 1:
The Titanic in Plain Sight
Piece 2:
When the Prediction Becomes the Verdict
Piece 3:
The Five Wounds of Change
Piece 4:
It’s Not ‘Will AI Take Your Job.’ It’s Which Choice Your Company Already Made.
Piece 5:
The View From Inside the Room
Piece 6:
A Different Sequence
Piece 7:
What You Choose to Interrupt
Seven weeks building toward one sentence: "We are not automating work. We are automating dysfunction." That verdict is worth sitting with.
The 4SET sequence applied backwards — toolset before heartset before mindset — is the pattern I watched in every EdTech rollout I was part of, and now recognize in every AI deployment case that comes through the door. The tool goes in first because that's what's visible and purchasable. The shift in who people believe they are to the organization arrives months later, usually as a problem rather than a design question.
The three practices at the end are the right level. Not a framework. One silence noticed, one decision made visible, one thing slowed down. That's where the work actually starts.
The idea of co-authorship feels important to me for another reason: the people living a system often see dependencies that those designing the transformation cannot see from above.
A decision can make perfect sense at one level and create a completely different consequence somewhere else in the organization. Perhaps co-authorship is not only about making change more acceptable. It may be one of the ways an organization actually understands the system it is trying to change.