Brewing a Better Workplace: Coffee Lessons from Toxic Management

The Bitter Taste of Bad Management

There's a reason so many of us dread Monday mornings. It's not the coffee—it's the workplace. We've all been there: the endless stand-ups, the ever-changing priorities, the feeling that no matter how hard we work, it's never enough. And it's no different in the coffee world. I've seen cafés where the manager runs the place like a tyrant, and the baristas—the heart and soul of the operation—end up burnt out and bitter.

But here's the thing: the problem isn't the tools we use. It's the people wielding them. Just like a perfectly good espresso machine can produce a terrible shot if the barista doesn't know what they're doing, management frameworks like OKRs and agile can turn toxic in the wrong hands.

OKRs: More Than Just a Buzzword

OKRs—Objectives and Key Results—are meant to set ambitious goals that push you to grow. The idea is that you should aim for 70% completion, because that means you're stretching beyond your comfort zone. It's like trying a new brewing method: you might not get it perfect the first time, but you learn a ton in the process.

But some managers treat OKRs like KPIs—Key Performance Indicators—and use them to evaluate your performance. That's like grading a barista on how many latte art hearts they can pour in a minute, instead of whether the coffee tastes good. It misses the point entirely.

When OKRs are tied to bonuses, people start playing it safe. They set goals they know they can hit, not goals that challenge them. The ambitious ones who shoot for the stars and land on the moon are seen as failures. The cautious ones who aim for the ceiling and touch it are rewarded. It's a recipe for mediocrity.

The Agile Approach to Coffee

Agile development is all about short cycles, teamwork, and embracing change. It's like the iterative process of perfecting a coffee blend. You start with a recipe, taste it, adjust, and taste again. You don't expect to get it right the first time. You're constantly learning from feedback—from your own palate, from your customers, from the beans themselves.

But in a toxic workplace, agile is often faked. Managers take a big waterfall plan—a rigid, top-down approach—and chop it into sprints, pretending it's agile. They're just checking boxes on a schedule, not actually responding to feedback. It's like a café that claims to offer single-origin pour-overs but is secretly serving instant coffee.

Embracing Change, the Right Way

True agile is about welcoming change based on real feedback. In coffee, that means listening to your customers. If they say the roast is too dark, you adjust. If they love a new single-origin, you feature it. But you don't change the menu on a whim just because the owner had a bad day.

In Scrum, there's a concept of a sprint—a fixed period, usually two to four weeks, where the work is locked. New ideas go into the backlog, but they don't disrupt the current sprint. This protects the team's focus. It's like a café that has a seasonal menu. You don't swap out the espresso blend mid-shift just because a customer asks for something different. You note it for the next season.

Refactoring Your Coffee Routine

One of the key principles of agile is continuous improvement through refactoring. In code, that means cleaning up the structure to make it easier to add new features. In coffee, it's about constantly tweaking your brew ratio, grind size, or water temperature to get the best cup.

Each batch of beans is different. What worked for one roast might not work for another. You have to be willing to adjust and refine. This is the essence of craftsmanship. And it's what separates a mediocre cup from an exceptional one.

The Human Element

Ultimately, the problem isn't OKRs or agile. It's the toxic culture that misuses them. People are not resources to be squeezed dry. They're humans, with ideas, feelings, and a need for purpose. In a healthy workplace, like a well-run café, everyone has a voice. The barista's feedback on the new blend matters. The server's observation about customer preferences is valued.

When we strip away the jargon, it's about respect. Respect for the process, respect for the people, and respect for the craft. Whether you're brewing coffee or building software, the principles are the same: set clear goals, embrace feedback, and never stop refining.