Why A Woman's Struggle In A 1960s Chemistry Lab Actually Teaches You Something Useful About Your Monday Morning
I was debugging a persistent issue in a client's deployment pipeline last month — something that should have been straightforward, but the logs kept pointing in completely unrelated directions. I spent about three hours circling the same problem before I actually stepped away from the screen and thought about how you'd handle this kind of situation if you were in a field that actively didn't want you there. That thought led me back to rewatching Lessons in Chemistry, the show based on Bonnie Garmus's novel, and I realized something I hadn't considered before: the strategies Elizabeth Zott uses to survive and actually make progress in that 1960s Hastings Foundation lab map pretty directly onto how you navigate a modern workplace that's subtly designed to slow you down. The show isn't really a workplace drama in the traditional sense. It's about a woman who has to do her actual job while being told her job doesn't exist, while colleagues steal her ideas, while the entire institutional structure assumes she's a mistake. But if you strip away the period detail and the melodrama, what you're left with is a remarkably practical set of approaches to doing real work in environments that aren't set up for your success. That's what I want to talk about here — the actual tactics, not the inspiration.
Wakely Lessons In Chemistry How A Fictional 1960s Lab Unlocked Real Strategies For Modern Workplaces
Let me start with something specific that most people miss when they talk about this show. Everyone focuses on Elizabeth Zott's brilliance at chemistry. Nobody really talks about the fact that she kept meticulous, dated records of her experiments even when no one asked her to, even when the lab director made it clear her work wouldn't be published under her name. That wasn't just good science practice. It was risk management. She was building a paper trail that survived institutional erasure. I've seen this exact pattern in my own work. A few years back I was leading a project where the project lead changed three times in eight months, and each new lead had a different idea of what we were supposed to be building. The documentation was terrible. I ended up spending weeks reconstructing decisions that had been made in meetings that nobody had written anything down about. The workaround I used was simple but painful to implement: I started maintaining my own project log, separate from whatever official system the company used. It tracked every decision, every change in scope, every email confirmation. When the fourth project lead tried to pivot the entire direction based on a misunderstanding, I had three months of dated evidence showing exactly where we'd agreed to go. It didn't make them change their mind, but it gave me the leverage to negotiate a compromise instead of just being told I was wrong. This is the first lesson from the show that translates directly: documentation as self-preservation. Not because you expect to need it in court — though that happens more often than you'd think — but because it gives you clarity about what has actually been decided versus what someone claimed was decided. In a chemistry lab, if you don't record the concentration and temperature precisely, you can't reproduce your results. In a workplace, if you don't record the agreement precisely, you can't hold anyone accountable to it.
The second lesson is about what Elizabeth Zott does when she realizes she's being excluded from the actual work. She doesn't ask nicely. She doesn't wait to be invited. She starts doing the work anyway, using whatever access she can find, and she does it in a way that makes the results impossible to ignore. This is counterintuitive for most people because workplace advice usually tells you to build relationships first and let the work speak for itself. The problem with that advice is that it assumes the work will be recognized fairly, which it almost never does if you're in a group that the institution already considers secondary. I ran into this head-on during a product launch where the marketing team was handling the external messaging for something I'd helped build from the technical side. I was CC'd on maybe two emails out of thirty throughout the entire campaign. When the launch happened and the messaging was factually wrong about half the features, nobody came to me to correct it because I wasn't in the conversation. The mistake I made was assuming that if I did good work, someone would eventually include me in the relevant discussions. It took me about six months to stop making that assumption and start attending the meetings I wasn't invited to, sitting in the back, taking notes, and sending follow-up emails to the people who were actually there confirming what had been discussed and what the decisions were. The parallel to Elizabeth Zott is almost uncomfortable. She shows up to the male chemists' discussions even when she's not welcome. She asks questions that expose gaps in their reasoning. She doesn't leave until she understands the problem well enough to solve it. The strategy isn't about being aggressive — it's about being present in spaces where decisions are actually made, because absence is where ideas go to die.
Get the Full Details
There's a third lesson that's harder to articulate and easier to mess up. Elizabeth Zott frequently has to teach people who are trying to prove she doesn't understand her own field. She does this by speaking plainly, without jargon, without condescension, and without ever apologizing for taking up space. The common pitfall here is that most people, when put in that position, either over-explain (which sounds defensive) or under-explain (which lets the other person frame the narrative). Zott finds the exact middle ground: she explains just enough to demonstrate competence, then moves on to the next point. I remember a performance review where my manager tried to frame a successful project as "team effort" in a way that completely erased my contribution. The instinctive reaction is to push back hard and insist on being named, which usually makes you look difficult. What I learned from watching how Zott handles similar situations is that you can redirect the narrative without confrontation. Instead of saying "actually I did this part," you say something like "the component architecture I designed is what allowed the team to hit the deadline — here's how it worked." You're not denying the team effort. You're just making sure the record shows where your specific value sat within it. It's a small distinction but it changes the entire outcome of the conversation. Now I should say what doesn't work, because this isn't a magic formula. The Elizabeth Zott approach has real limitations. First, it requires you to be genuinely excellent at your core work. If you're copying her tactics without the substance, you'll just come across as arrogant and get pushed out faster. Second, it doesn't work in environments where the power structure is completely ossified — if the people above you have zero incentive to listen to you and zero fear of consequences for ignoring you, documentation and presence won't save you. You need to assess whether the institution is at least somewhat functional before investing heavily in these strategies. Sometimes the right move is to leave and take your skills somewhere that values them, which is literally what Zott does by the end of the story.
Third, and this is important, these strategies are emotionally expensive. Keeping meticulous records while being systematically undermined. Showing up to meetings where you're not wanted. Explaining your expertise to people who'd rather you not exist. This takes a toll. I've seen people burn out from applying these tactics for too long without any real institutional reward. The show acknowledges this — Zott is exhausted by the end, and she's still young. You have to pace yourself and recognize when the cost of staying and fighting exceeds the cost of leaving. If you want to apply these lessons practically, here's what I'd suggest as a starting point. Pick one area of your work where you feel invisible — maybe it's a project, maybe it's a recurring meeting, maybe it's a client relationship. Start documenting everything about it yourself, in a place you control. Then find one way to insert yourself into the decision-making loop without asking permission, the way Zott does when she starts running experiments that her superiors didn't authorize but can't ignore. Then practice explaining your work plainly to people who might try to diminish it, focusing on demonstrating competence rather than defending your position. The broader takeaway from Lessons in Chemistry isn't really about chemistry at all. It's about what happens when someone refuses to accept that their contributions don't matter, and develops a practical, unglamorous set of tools to make sure they matter whether anyone acknowledges them or not. That's the Wakely Lessons In Chemistry How A Fictional 1960s Lab Unlocked Real Strategies For Modern Workplaces framework, distilled down to its essentials. The rest is just details.
