The Broken Promise of Today’s Playbooks
Everywhere I go, I meet organizations that have invested in tools and playbooks to strengthen their workplace experience.
Bought the books.
Sat through the workshops.
Handed their team laminated cards with the steps to follow.
The playbooks promised simplicity. They promised that if you just followed the steps, you’d get the outcome. And to be fair, sometimes they do help.
A framework can give us language where before we had none. It can get us started. But too often, organizations stop there. They start treating the tool as the solution instead of as one of the many doorways in. When that happens, people end up checking boxes while carrying the weight of the disconnect.
The broken promise of today’s playbooks isn’t that they exist—it’s how we’ve asked them to do work they were never designed to do. Tools can guide us, but they can’t replace judgment.
They can remind us of structure, but they can’t provide courage. When we mistake tools for transformation, disappointment follows; not because people failed, but because the expectation was misplaced.
The future of work will belong to organizations that stop waiting for the perfect playbook and start learning how to evolve the ones they already have.
The tools aren’t the problem. It’s our relationship to them that must change.
The Limits of Yesterday’s Tools
When I say “tools,” I’m not talking about software or technology. I mean the frameworks, models, and practices we’ve been taught to use to shape culture and performance. These tools are everywhere in management training and leadership development. They’re meant to make culture simpler and more repeatable. And they do help—sometimes.
But too often, they stop at the surface.
Take one example many of us may have introduced to: the feedback sandwich. It has been around for decades and is often the first framework new managers are taught: Start with something positive, share the critique, and close with another positive.
In theory, it strikes a balance between honesty and kindness. In practice, it leaves people questioning what’s real.
I’ve seen managers leave those conversations feeling proud—they believe they’ve been clear and compassionate. But I’ve seen employees leave the same conversations feeling whiplash. They hear the praise and think they’re doing well. Then they hear the critique and wonder if the praise was fake. Then they hear more praise and don’t know which part to trust. Instead of leaving with clarity, they leave with anxiety.
The sandwich isn’t useless, but it’s incomplete. It assumes that the order of words is what creates safety, when in reality, safety comes from the relationship. It assumes balance is the goal, when clarity is the goal. And it ignores the variables that shape how feedback lands: timing, history, identity, and power. A compliment can’t erase those.
When organizations rely too heavily on formulas, they shift the burden onto their people. Employees are left to sort out what mattered most, what was real, and how to interpret it.
But there’s another way:
Instead of relying on packaging, organizations can anchor feedback in purpose. Imagine saying: “I want to talk about this project handoff because I see you stepping into more leadership, and this is part of that journey.”
That one sentence reframes the conversation. It tells someone the feedback is about growth, not judgment. From there, you can be specific about what happened, why it mattered, and what you’ll both try next. That’s clarity. That’s care.
This is the deeper truth: many of yesterday’s tools are useful beginnings, but they stop too soon. They give us technique without discernment. Leadership and organizational practice are not about technique. It’s about judgment. The sandwich can remind you to be kind. But it can’t teach you how to pair honesty with humanity. That’s the real work.
How We Got Here (A Brief History of Tools)
Most of the tools we still use today were created in a different era. They were born in organizations that looked and operated nothing like ours. The management models of the 1980s and 90s were built for stability and control. The goal was efficiency. People were treated as interchangeable parts. The tools reflected that.
We then standardized leadership trainings. Scripts and frameworks spread widely. They brought consistency, but they still didn’t account for the complexity of identity, equity, or belonging. They assumed that everyone could be treated the same and get the same result. They didn’t yet have language for power, inequity, or the invisible weight people carry into work.
To be fair, those tools worked in their time. They gave organizations ways to organize themselves. They created clarity in environments where markets were slower, teams were co-located, and cultural conversations stayed outside the office. But that time has passed. We live in a different reality now: hybrid work, global teams, blurred boundaries, urgent conversations about equity, and a pace of change that leaves little room for static formulas.
The mistake isn’t that those tools were created. The mistake is treating them as timeless—as if they could stretch to fit any era. In truth, they were written for the problems of their day. If their creators were here now, I believe most would say: this needs a part two. The foundation is still useful, but it’s not enough for the reality we face today.
When we recognize that history, we stop treating tools like commandments. We start treating them like drafts. And once we see them as drafts, we free ourselves to pick up the pen and continue writing.
The Complexity We Pretend Doesn’t Exist
Picture this: it’s Friday afternoon, and a manager sends a calendar invite titled “Quick feedback?” She’s trying to be timely, to check the box before the week ends. But for the person on the receiving end, that invite is a stress signal. He spends the rest of the day spiraling, wondering what’s wrong. By the time the meeting starts, his body is already in fight-or-flight. She can say all the right words, but he won’t hear them clearly.
This is the part most frameworks leave out. They teach us to “be timely” but not to ask, “timely for who?” They teach us to “be specific” but not to ask, “does this person have the bandwidth to hear me right now?” Timing, context, nervous systems—all shape whether feedback lands. Ignore them, and you may follow the model but miss the moment.
Identity adds another layer. For some, the phrase “I want to give you feedback” carries years of coded history. Maybe they’ve been told in past jobs they were “too aggressive” when they spoke up. Maybe they’ve been passed over without explanation. So when they hear those words now, they don’t just hear today—they hear their whole history. If you don’t account for that, feedback won’t feel like investment. It will feel like risk.
But when organizations design with complexity in mind, everything shifts. Instead of dropping a last-minute invite, you might send a note ahead: “I want to talk about two handoffs from this sprint so we can tighten the play. Nothing urgent, but I want to set us up for the next one.” That framing lowers the temperature. It tells the person the purpose, the stakes, and that they’re not in danger. Now you’ve created the conditions for the feedback to land.
The difference wasn’t in the content—it was in the design. Same feedback. Different timing. Different framing. Different outcome. That’s what most tools can’t capture: the invisible layers of trust, timing, and history that shape every interaction.
The future of organizations isn’t about ignoring those complexities. It’s about embracing them. Pretending people are predictable doesn’t make work easier. It makes culture brittle. And brittle cultures break under pressure. Organizations that learn to design for complexity will build the ones that last.
We Don’t Need All New Tools—We Need a Different Approach
It’s tempting to believe the solution is always something new. A brand-new framework. A new model with fresh language. But that belief keeps us stuck in the cycle of rollout, reinvention, and churn. The truth is, we don’t need to throw everything out. We need to reinterpret what we already have.
We need to see frameworks and tools for what they are: a reminder to pair care with critique. Useful, but incomplete. Once we see that clearly, we can evolve it. We can keep the reminder, but we add what’s missing—purpose, timing, trust, and context.
That’s not a new tool. That’s a tool that’s evolved.
This shift requires organizations to hold tools differently. Not as silver bullets, but as starting points. Not as “the answer,” but as “an answer.” A framework can give you a place to begin, but it can’t carry all the weight. Judgment has to carry the rest. And when organizations hold tools this way, they stop force-fitting every situation into a formula. They start asking better questions.
The best tools aren’t abandoned. They’re adapted. They’re treated as drafts—ready for revision, ready for the nuance of real work. That’s what people need: not another brand-new thing, but leaders and organizations willing to evolve what already exists into something that truly fits today.
What Future-Oriented Tools Can Look Like
So what does this evolution look like? Future-oriented tools share a few qualities:
They are context-aware. They’re designed for a world that is hybrid, fast, and layered with identity. They don’t assume all conversations happen face-to-face in an office. They adapt to Slack, to video calls, to distributed schedules. They account for nervous systems, cultural dynamics, and power differences. They don’t ignore complexity—they build with it in mind.
Future-oriented tools are generative, not just protective. They don’t exist only to help avoid mistakes. They exist to build capacity. A feedback practice isn’t just about delivering critique without harm—it’s about creating moments of growth. A decision-making tool isn’t just about preventing confusion—it’s about spreading judgment across more people. The best tools create opportunities, not just guardrails.
They also embed belonging directly into workflow. Not as a quarterly reminder, but as muscle memory—in how meetings are run, in who speaks first, in how credit is shared. Belonging isn’t an extra. It’s woven into the everyday. Future-oriented tools make inclusion ordinary, not special.
And finally, future-oriented tools are designed with adoption in mind. They ask: where will this live? What does it replace? Who will model it first? What friction will people face, and how will we clear it? They don’t stop at launch. They plan for life. That’s the difference between a tool that exists in theory and one that transforms how people work.
The point isn’t that we need a completely new set of tools. The point is that we need tools that fit the reality we’re in now—tools that are humble, human, and built to last. When organizations start looking for those qualities, they stop searching for magic formulas and start building practices that truly serve their people.
How to Transform the Tools You Already Have
When I talk with CEOs and leadership teams about tools, someone always asks, “Okay, but how do we actually change them? We can’t just throw everything out — we’ve invested too much. So how do we make the tools work for the organization we are now, not the one we were ten years ago?”
Here’s the truth: evolving a tool isn’t about rewriting a textbook.
It’s about moving from, “Does this tool still work?” to “How do we make this tool serve our people?”
I use five simple but powerful questions to guide that process:
- What was this tool originally designed to do?
Every tool has a purpose. The feedback sandwich, for example, wasn’t created to confuse people. It was meant to remind leaders to balance critique with care. Naming the original intent helps you decide what’s still valuable and what can be let go. - What are people actually experiencing when we use it?
Don’t stop at theory. Ask your managers, ask your staff: when we use this model, how does it land? Do you leave clearer or more confused? Do you feel supported, or just managed? This is where you move from assumption into reality. - Whose experience does it serve — and whose does it leave out?
A model might work fine for someone who feels safe and supported at work, but what about the person who’s been told their whole career they’re “too aggressive” or “not leadership material”? Does the tool reinforce bias? Does it unintentionally privilege one group’s comfort over another’s clarity? - What would make this feel more human and more usable in real time?
Tools often fail because they’re too abstract. Ask: what would make this easier in the hallway after a tense meeting, or on a Zoom call when emotions are high? Maybe it needs simpler language. Maybe it needs a clear purpose statement. Maybe it needs a script people can actually use in the moment. Design for the real world, not the slide deck. - How will we test and refine this together?
Don’t redesign tools in isolation. Put the new version into play, then ask, “Did this help? Did it make things clearer? What still needs to shift?” Treat the tool as a living draft. The minute you stop revising, it starts to fall behind.
When you run a tool through these five questions, what comes out the other side is something more people-centered, more context-aware, and more credible. And here’s the best part: you don’t need to scrap everything and start from scratch. You can begin with what you already have and layer in what’s missing.
That’s how tools transform from check-the-box exercises into real practices. That’s how your people stop rolling their eyes and start trusting the process. Not because the tool was perfect, but because you showed them it could grow — and that you were willing to grow it with them.
These are small shifts, but they change the feel entirely. The tool is no longer something people endure. It becomes something people trust. And that’s the point — not to have the slickest model, but to have one your people actually believe in and can use every day.
The Cost of Staying with Yesterday’s Tools
Here’s something I want you to think about:
Some leaders assume that sticking with the old tools is finel. You know, they’ve been around, they’re familiar, they’re easy to teach. They worked in the past, so maybe they’ll hold us a little longer. I get that instinct. It feels safe. But the truth is, while it is fine, there is always a cost.
Your teams are navigating tools that don’t quite fit. They’re adjusting to systems that don’t meet the reality of their work. They’re carrying the burden of practices that may have been useful once but no longer match the world we’re in.
You don’t need to wait for permission to adapt. You don’t need to wait for the new playbook to drop. The most credible thing you can do as a leader is to show your people that you’re willing to wrestle with the messy parts, that you’re willing to adapt the tools you already have, and that you’re serious about making them fit your reality.
The organizations that thrive in the next decade won’t be the ones who bought the most toolkits. They’ll be the ones who picked up the pen and revised the draft. They’ll be the ones who held tools lightly, stayed curious, and made the practices their own. The ones who stop asking, “What’s the next big tool?” and start asking, “How do we evolve what we already have to serve our people better?”
The ones who stop waiting for edition three and start writing their own.
That’s what builds credibility. That’s what builds trust. That’s what creates momentum that actually lasts. Not the rollout of a new tool, but the lived experience of leaders and staff seeing that what you say is what you do, and that what you do actually matches what your people need.
The future of work won’t be built by tools. It will be built by organizations willing to adapt, willing to listen, and willing to make tools fit the reality of today. Tools are useful. But they’re not destiny.
What your people will remember — and what they will stay for — is how it felt to work with you.