YoStella: Build a Better Business - Inspiration for Improving Your Brand, Marketing & People
Each year on Fat Tuesday, New Orleans throws a “Stella and Stanley” party. This annual event honors local boy and world-famous author Tennessee Williams and his masterpiece, A Streetcar Named Desire.
The movie version is notorious for the scene where Stanley, Marlon Brando in a tight white vest, yells “Stella-a-a-a-a-!” up the tenement stairs to his wife. “Stella” might be the most repeated movie line ever and Brando never needed to act again except, he said, for the money. Like a legendary actor, businesses need to cultivate their craft: building an amazing brand, elevating creativity, and growing authentic connections.
At StellaPop, we believe every business has a masterpiece in them.
YoStella: Build a Better Business - Inspiration for Improving Your Brand, Marketing & People
How To Document Employee Issues Without Creating Fear
Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.
Your stomach drops the moment an employee says, “I was never told.” You remember the coaching talks, the warnings, the follow-ups. They remember a casual comment by the coffee machine. That gap between two honest memories is where everyday performance issues can suddenly become HR emergencies, legal risk, and expensive confusion.
We walk through a simple, practical approach to employee documentation that keeps management fair and transparent without turning you into an amateur lawyer. The big shift is learning to write an “instant replay” record: observable facts, dates, witnesses, and business impact, not loaded labels like “toxic” or “unreliable.” We also share why prompt notes beat perfect prose, and how a consistent structure saves time and protects credibility.
Then we get into the traps that surprise even experienced managers: consistency across employees, the optics of last-minute documentation, and the legal landmines around retaliation and protected activity. We talk about NLRA protections for conversations about pay and working conditions even in non-union workplaces, plus how to store sensitive records correctly, avoid “Shadow HR” on personal devices, and keep communication front and center so there are no surprises.
If you manage people, this is a repeatable framework you can use immediately. Subscribe for more practical leadership and HR compliance guidance, share this with a fellow manager, and leave a review with the biggest documentation challenge you want us to tackle next.
The Termination Meeting Nightmare
SPEAKER_00Imagine this scenario for a second. Just picture it. You're a manager, right? And you have this employee who has been, well, they've been struggling for a while.
SPEAKER_01Right. A classic situation. We've all been there.
SPEAKER_00Exactly. And you sat down with this person, you know, face to face multiple times, and you're telling them, hey, you really need to improve your performance.
SPEAKER_01But nothing really changes.
SPEAKER_00Nothing changes. So flash forward, say, three or four months, things haven't gotten any better, and you finally have to make the tough call.
SPEAKER_01The termination meeting.
SPEAKER_00Yeah. You bring them in, you sit them down, and to your absolute shock, this employee looks you dead in the eye and claims they were never, ever told what they needed to change.
SPEAKER_01Oh wow. Yeah. That is that's the moment your stomach just completely drops.
SPEAKER_00It really is. Suddenly the panic sets in. Everyone is scrambling. You're like digging through old emails, frantically scrolling through chat histories on Slack, trying to piece together, you know, calendar invites for meetings you know you had.
SPEAKER_01Just desperately trying to reconstruct the actual truth. Aaron Powell Right.
SPEAKER_00And it is a genuinely terrifying position for any manager to be in. But welcome to our deep dive where we're gonna help you make sure that never happens.
SPEAKER_01That's because reality is that specific nightmare happens every single day in businesses across the world.
SPEAKER_00Aaron Powell It really does. So our mission today is to unpack this really comprehensive guide from Stellipop. We're looking at their research on how everyday, you know, seemingly mundane employee issues secretly morph into these massive business risks.
SPEAKER_01And more importantly, how you can actually stop that mutation right in his tracks.
SPEAKER_00Aaron Powell Exactly. So jumping right into it, what's the core idea
Memory Becomes The Record
SPEAKER_00here?
SPEAKER_01Aaron Powell Well, the central thesis of the Stellipop material provides a really, really crucial framing for this entire discussion. They state very clearly, this is a quote, most employee problems do not begin as legal problems. They become legal problems when memory becomes the record.
SPEAKER_00Aaron Powell Memory becoming the record. I mean, that sounds almost philosophical, right?
SPEAKER_01Aaron Powell It does, but the application is incredibly practical.
SPEAKER_00Aaron Powell Yeah. And I want to set the tone right out of the gate here for you listening. We are not talking about like creating some covert secret HR file on your team.
SPEAKER_01No, definitely not.
SPEAKER_00This isn't some masterclass in scheming to fire someone or you know building a trap. We are just talking about basic, fair, and transparent management.
SPEAKER_01Exactly. When this process is done right, yes, it absolutely protects the company. But primarily, it supports you as a manager, and it gives your employees a genuinely fair chance to actually understand their shortcomings and improve.
SPEAKER_00Right. Because the ultimate goal of documentation isn't just to generate like more defensive paperwork to stuff into some dusty filing cabinet.
SPEAKER_01No, the goal is to create a reliable objective record. And the problem is that memory, as cognitive science continually tells us, is just notoriously unreliable.
SPEAKER_00Oh, completely. It's so flawed.
SPEAKER_01It really is. It's highly malleable, especially when you introduce stress or conflict into the mix. So you, as the manager, you remember warning the employee several times with you know grave seriousness.
SPEAKER_00But they remember it totally differently, right?
SPEAKER_01Yes. They remember one casual passing chat by the coffee machine where you just offered like a piece of friendly advice. And the dangerous part is that you both genuinely believe you're telling the truth.
SPEAKER_00Okay, let's unpack this. If memory is basically the enemy of a reliable record,
Facts Versus Judgments In Notes
SPEAKER_00how do we actually write things down without letting our own biases or, you know, our emotions take the wheel?
SPEAKER_01That's the challenge, right?
SPEAKER_00It is. I was thinking about this, and to me, good documentation should function sort of like an instant replay in sports.
SPEAKER_01Ooh, I like that analogy.
SPEAKER_00Yeah. Think about it. When you watch an instant replay, the camera just shows exactly where the player's foot stepped out of bounds. It just shows the physical reality of the moment.
SPEAKER_01Right. The camera doesn't care about the context of the game.
SPEAKER_00Exactly. It doesn't show whether the referee thinks the player is a jerk or if the player was feeling unmotivated that day. It just shows the bare facts. But I have to push back a little here.
SPEAKER_01Go for it.
SPEAKER_00Realistically, when you are in the middle of a heated conflict with an employee, I mean your blood pressure is up. Isn't it just basic human nature for a frustrated manager to jot down like this employee is being completely unreasonable and has a terrible attitude?
SPEAKER_01Oh, absolutely.
SPEAKER_00So how are you supposed to turn off your human reaction?
SPEAKER_01Well, what's fascinating here is how the source material explicitly addresses that exact tension. It draws a hard definitive line between a conclusion, which is essentially a feeling or a judgment, and a fact.
SPEAKER_00Okay, so conclusion versus fact.
SPEAKER_01Yes. Human nature absolutely relies on cognitive shortcuts. We want to label things so we can process them quickly. We just want to say somewhat is difficult and move on.
SPEAKER_00Because it's easier.
SPEAKER_01Way easier. But in documentation, writing what you feel or the conclusion you've jumped to is the most dangerous trap you can fall into. You cannot write what you assume. You can only write what you observe.
SPEAKER_00Okay, so let's dig into how that actually translates to the page. Because, you know, recognizing a bad attitude is easy.
SPEAKER_01Right.
SPEAKER_00But documenting it without actually using the label, that seems way harder.
SPEAKER_01It requires a bit of a translation, really, a translation from judgment to behavior. Let's take your example of a bad attitude. Writing, Jordan has a bad attitude, is an opinion. It's a subjective conclusion.
SPEAKER_00Yeah, it doesn't really say what happened.
SPEAKER_01Exactly. If an outside party reads that, they have no idea what Jordan actually did. Instead, the factual record, your instant replay, would look like this. During the June 12 team meeting, Jordan interrupted two coworkers, raised their voice after being asked to wait, and left the room before the discussion ended.
SPEAKER_00Oh wow. Yeah, that is a completely different ballgame.
SPEAKER_01It is, isn't it?
SPEAKER_00You aren't accusing Jordan of a character flaw at all. You're just providing the timestamps and the physical actions. You're letting the behavior speak for itself.
SPEAKER_01Precisely. Let's look at another one. Something managers deal with constantly. Someone writes, Taylor is unreliable.
SPEAKER_00Oh, I see that one all the time.
SPEAKER_01Right. But again, that is a vague label. It's a character judgment. The factual record translates that too. Taylor arrived after the scheduled 9 a.m. start time on June 3, June 7, and June 11 without notifying the supervisor.
SPEAKER_00And the beauty of that instant replay camera is that it just sees Taylor walking in past 9 a.m. on three specific dates. It doesn't see the word unreliable. Right. It doesn't try to guess why Taylor was late. It just records the event.
SPEAKER_01Exactly. The key takeaway for you listening as a manager is that you must ruthlessly eliminate vague emotional labels from your vocabulary when you're documenting.
SPEAKER_00So words like what?
SPEAKER_01Words like lazy, toxic, unstable, aggressive, insubordinate, or difficult. Those have absolutely no place in your official record unless the document explicitly details the observable physical behavior that led to that word.
SPEAKER_00That makes a lot of sense.
SPEAKER_01And furthermore, the guide is adamant that you must never, ever speculate about an employee's health, their internal intentions, or, you know, their emotional state. Trevor Burrus, Jr.
SPEAKER_00Because you aren't a doctor and you can't read minds.
SPEAKER_01Exactly. If someone is crying, you don't write they were having a mental breakdown. You write the employee began crying. Facts are specific. They could be reviewed objectively by a third party, like an HR director, a mediator, or a lawyer who was never in the room when the event actually happened.
SPEAKER_00So we know that the gold standard is writing down the facts, stripping out the feelings, and providing that instant replay. But I mean that brings up a massive operational
Prompt Notes Beat Perfect Memos
SPEAKER_00hurdle. Time. Time. We are all incredibly busy. Managers are stretched so thin. If a perfect record is required, how do you document this stuff without spending like four hours playing amateur lawyer every Friday afternoon?
SPEAKER_01Aaron Ross Powell Trying to draft legally binding affidavits.
SPEAKER_00Aaron Powell Yeah, exactly. Nobody has time for that.
SPEAKER_01Well the relief here is that you don't need to write like an attorney to protect yourself and your company. In fact, trying to write illegally usually backfires.
SPEAKER_00Aaron Powell It just makes the document super confusing.
SPEAKER_01Trevor Burrus Yeah, exactly.
SPEAKER_00Trevor Burrus And the source makes a really compelling point about timing in this regard. It insists that promptness actually overrides perfection.
SPEAKER_01100%.
SPEAKER_00Like a quickly scribbled sticky note or a brief email to yourself written on the same afternoon the event occurred, that is vastly superior to a beautifully formatted five-page memo that you try to, you know, reconstruct from memory three months later.
SPEAKER_01It's all about contemporaneous notes.
SPEAKER_00Right. And frankly, think about the optics here. If a manager suddenly produces a giant, pristine pile of complaints right before they decide to fire someone, it looks incredibly suspicious.
SPEAKER_01It does.
SPEAKER_00Even if every single word is true, it looks like a fabricated hit job.
SPEAKER_01It looks entirely retaliatory. In legal or HR proceedings, a sudden avalanche of documentation is just a massive red flag. A consistent series of timely, immediate notes is always more useful and carries so much more credibility.
SPEAKER_00Yeah, that makes sense.
SPEAKER_01But going back to your point about not having the time to play a lawyer, the solution isn't drafting essays. The
The Seven-Question Documentation Framework
SPEAKER_01solution is adopting a consistent structure. The Celepop guide actually breaks this down into seven specific questions that act as a framework.
SPEAKER_00Seven questions, okay.
SPEAKER_01If every record answers these seven questions, you are covered.
SPEAKER_00I looked at this framework, and what struck me is that it acts almost like a, well, a managerial mad libs.
SPEAKER_01That's a good way to put it.
SPEAKER_00It kind of forces you to remove your bias. It asks for the basics, but then it forces you to look at the rule book. Let's actually walk through these seven questions using a hypothetical scenario just so we can see the mechanism in action.
SPEAKER_01Okay, let's do it.
SPEAKER_00Let's say we have an employee, we'll call him Alex, who keeps turning in work late and it's holding up the whole team. Where do we start with the seven questions?
SPEAKER_01Aaron Powell So the first three questions establish the baseline reality. Question one, what happened? Question two, when and where did it happen? And question three, who observed it?
SPEAKER_00Okay. So in our scenario, you wouldn't write Alex is always holding us up. No, definitely not. You would write, Alex submitted the Q3 financial analysis on Thursday at 4 p.m. The deadline was Wednesday at 9 a.m. This was observed by myself and the project lead, Sarah.
SPEAKER_01Perfect. Clean, factual, objective.
SPEAKER_00But here's where it gets really interesting. Question four asks what expectation, policy, or job requirement applies to the situation? Because you can't just write down turning things in late is unacceptable.
SPEAKER_01Right. You can't just state a grievance.
SPEAKER_00You actually have to explain the underlying business impact.
SPEAKER_01And this is perhaps the most critical step. And honestly, it is the one managers miss the most. If you don't connect the behavior to a specific business expectation, the conflict just looks like a personality clash.
SPEAKER_00Just a strict manager getting annoyed at a relaxed employee.
SPEAKER_01Exactly. You have to anchor the conduct to something the employee could reasonably understand, like a written policy, a bullet point in their job description, a stated performance goal, or even a previous coaching conversation.
SPEAKER_00It's like building a firewall between personal annoyance and actual professional standards. So in our scenario with Alex, instead of just saying the report was late and I'm super frustrated, you write the business impact. You write. The Q3 financial analysis was due by Wednesday at 9 a.m. so the executive team could review it before Thursday's board meeting. Because it was submitted Thursday afternoon, the board meeting had to proceed without the financial data.
SPEAKER_01Right. And do you see how that completely changes the narrative?
SPEAKER_00It really does. It removes the manager's ego from the equation entirely.
SPEAKER_01Yes. The problem isn't that Alex offended the manager by missing a deadline. The problem is that the executive team couldn't do their job. It shifts the focus purely from personality to performance.
SPEAKER_00And that makes the actual conversation with the employee so much easier, too. Which brings us to question five. What explanation did the employee provide?
SPEAKER_01Yes.
SPEAKER_00I think this is vital because it implies you are actually required to have a conversation and listen to them. This isn't just some one-sided burn book you're keeping in a locked drawer. You have to record their side of the story.
SPEAKER_01Legally and ethically, that is crucial. If Alex says, Well, I didn't have access to the accounting software for two days because IT locked my account, and you failed to document that.
SPEAKER_00Then your record is just a lie.
SPEAKER_01It's incomplete and it's fundamentally unfair. You have to include their explanation, even if you completely disagree with it.
SPEAKER_00Okay, then we round it out with the final two. Question six, what coaching warning or action was given? And question seven, what must happen next and by when? Right. So you document that you gave a verbal warning and that the next report is due next Wednesday by 5 p.m., no exceptions.
SPEAKER_01Exactly. It creates a complete closed loop. You've established the facts, the business rule, the employee's perspective, the consequence, and the path forward.
SPEAKER_00Okay, so if we are documenting perfectly using these seven questions, it brings up kind of a terrifying thought. Uh-oh, what's that? Does this perfect documentation make a manager bulletproof? Like if I fill out the mad libs correctly, am I completely safe from business risk?
SPEAKER_01Not at all.
Consistency And Retaliation Legal Traps
SPEAKER_00Not at all. Because how you treat this specific employee compared to how you treat other employees in similar situations is where things can get incredibly dangerous. Consistency is the next major trap.
SPEAKER_01Aaron Powell Okay, let me play devil's advocate for a second.
SPEAKER_00Go ahead.
SPEAKER_01Does this mean we have to act like robots handing out standard issue demerits? Like if one person is five minutes late because their car broke down on the highway and another is five minutes late because they just overslept, do they have to get the exact same written warning just to prove we are being consistent?
SPEAKER_00Well, if we connect this to the bigger picture, the law does not require you to be a robot.
SPEAKER_01Okay, good.
SPEAKER_00Outcomes do not have to be strictly identical in every single case, because context absolutely matters. Right. An employee's history with the company, the severity of the specific incident, their tenure, their role, and the overall business impact of their behavior, all of that might differ. However, the golden rule here is that the company must be able to clearly and objectively explain the difference in treatment. So if you give the person with the broken down car a pass, because say they have a flawless five-year record, but you write up the person who overslept because they've been late four times this month, that is fine.
SPEAKER_01That's totally fine.
SPEAKER_00But you need to have a legitimate documented business reason for that discrepancy.
SPEAKER_01Aaron Powell Exactly. Because if you lack that documented business reason, it opens the door wide to accusations of discrimination or retaliation. And the source material highlights some incredibly specific legal landmines that managers routinely step on here.
SPEAKER_00Yeah, you have to be extraordinarily careful if you were disciplining an employee who has recently engaged in protected activities. Right, because the timing of discipline can look retaliatory, even if it actually isn't. If an employee has recently raised a discrimination complaint or, you know, requested a workplace accommodation for a disability or reported a safety concern, or even participated as a witness in an internal HR investigation.
SPEAKER_01They are essentially operating under a legal shield.
SPEAKER_00Exactly.
SPEAKER_01Federal and state laws are highly protective of those activities. If someone reports a safety violation on Tuesday and you suddenly decide to fire them on Thursday for being five minutes late, something you usually completely ignore for other employees. Yeah. The courts will almost certainly view that as illegal retaliation.
SPEAKER_00Aaron Powell And there was one specific protection in the text that I think catches a lot of managers completely off guard.
SPEAKER_01The NLRA.
SPEAKER_00Yes. You have to be very careful if employees have recently discussed workplace conditions or pay with their co-workers. The source explicitly mentions that this is protected by the National Labor Relations Act, the NLRA, even if your workplace doesn't have a union.
SPEAKER_01Even without a union. That is a very widespread misconception.
SPEAKER_00People always think it's just for unions.
SPEAKER_01Countless managers assume the NLRA only applies to unionized environments. It does not. The law protects what is called protected concerted activity. When employees act together to address pay, benefits, or working conditions, they are legally protected.
SPEAKER_00So if an employee is like leading a charge asking for better wages on a Slack channel, and suddenly they are disciplined for a minor dress code violation that literally no one else gets written up for.
SPEAKER_01That company is walking right into an NLRA violation.
SPEAKER_00So the crucial rule here is that having perfect documentation does not magically make a retaliatory decision lawful.
SPEAKER_01No, it doesn't.
SPEAKER_00You can't just fill out the seven questions perfectly as a smokescreen to fire someone who just asked for a raise. The documentation must always reflect a legitimate, supported, and consistent business reason.
SPEAKER_01Aaron Powell The paperwork never shields you if the underlying motive is illegal or inconsistent. It simply provides the factual basis for a legitimate, fair decision.
SPEAKER_00Okay, so let's say you have navigated these legal landmines, you're documenting fairly, objectively, and consistently. In the event of a lawsuit, every single piece of paper, every email becomes potential evidence.
SPEAKER_01Everything.
Where Records Belong And Shadow HR
SPEAKER_00So where is a manager actually supposed to keep all this highly sensitive proof? Do I just keep a folder on my desktop named Do Not Open?
SPEAKER_01Definitely not. Storage is actually a highly regulated, high-risk area. The source is very clear that different types of records have to be treated fundamentally differently.
SPEAKER_00How so?
SPEAKER_01Well, standard performance reviews, your coaching notes answering those seven questions, disciplinary records, and attendance info. Those generally belong in the official personnel file managed by HR.
SPEAKER_00Okay, that makes sense.
SPEAKER_01But anything related to medical information, disability accommodation records, or sensitive investigation materials absolutely requires separate confidential storage. You cannot mix an employee's medical history in with their quarterly performance review.
SPEAKER_00And I want to get a little passionate about this next point because I see managers do this all the time. The source explicitly warns against the creation of an official file.
SPEAKER_01Oh, yes. Shadow HR.
SPEAKER_00Yes, Shadow HR managers keeping notes on their personal cell phones or in those private little notebooks they carry around or just scatter across random text message threads that the actual human resources department can't see or access.
SPEAKER_01Aaron Powell Shadow HR is a nightmare for a company's legal counsel.
SPEAKER_00It's so bad.
SPEAKER_01Because if HR doesn't know the information exists, they can't help you evaluate the risk or guide your management strategy. Furthermore, if there is a lawsuit, those personal devices, those notebooks, and those text threads can suddenly become discoverable evidence.
SPEAKER_00Which means a lawyer's going through them.
SPEAKER_01Exactly. You do not want a court subpoenaing your personal iPhone just because you use the notes app to track an employee's performance.
SPEAKER_00That sounds like a disaster. And the retention rules are strict too. The EEOC requires private employers to keep personnel records for at least one year. Right. And Department of Labor rules regarding wage records can require even longer retention. State laws add even more layers. The overarching point is that record keeping is formal, regulated work, not some casual side
No Surprises And Employee Acknowledgment
SPEAKER_00hobby.
SPEAKER_01This raises an important question, though. If we are building these meticulous, formal files, does the employee actually know about them?
SPEAKER_00Right. Are we just sitting in the dark building a secret case against them?
SPEAKER_01The Stellipop guide is crystal clear on this. And it goes back to our earlier point about fair management. Documentation is meant to support communication. It does not replace it.
SPEAKER_00Okay. Support, not replace.
SPEAKER_01The absolute worst case scenario for a company is an employee reaching the end of the disciplinary process, being handed determination notice, and asking in genuine shocked confusion, why was I never told this was a problem?
SPEAKER_00The no surprises rule.
SPEAKER_01Exactly.
SPEAKER_00If they are surprised at the end, you have fundamentally failed as a manager.
SPEAKER_01Completely. Managers should always be discussing the concern with the employee directly, in real time. You explain the expected change, you document their response, and you clearly confirm what may happen if the issue continues.
SPEAKER_00And the source provides some really actionable advice on how to formalize that communication without making it super adversarial. You might ask the employee to sign the document you've created. Yes. But, and this is a critical distinction, the form needs to make it abundantly clear that their signature just proves they received the document. It does not mean they agree with every single word you wrote, it is just a receipt of communication.
SPEAKER_01And to maintain that fairness, you should always allow the employee to provide a written response and attach that response to the official record.
SPEAKER_00That's a great policy.
SPEAKER_01It guarantees their voice is permanently part of the history. To make this entire process a habit, the guide suggests keeping it as simple as possible.
SPEAKER_00Right, because if it's complicated, managers won't do it.
SPEAKER_01Exactly. A straightforward, one-page form covering those seven questions that managers can fill out easily and consistently is infinitely better than some complicated, overly bureaucratic software system that managers actively avoid using until a situation has already exploded.
SPEAKER_00So what does this all mean? Let's bring this all together for you listening. If we synthesize the core message of this entire deep dive into the Stella Pop guide, it's that good documentation is ultimately a leadership tool.
SPEAKER_01It really is.
SPEAKER_00Yes, it protects the company legally, but its primary function is better management. It takes those vague, simmering, emotional frustrations you feel as a manager and forces you to translate them into clear, objective conversations.
SPEAKER_01And it acts as a firewall.
SPEAKER_00Right. Actively separating personality conflicts from actual business impact and performance issues. And most importantly, it gives your employees specific expectations and a genuinely fair, understandable chance to step up and improve.
SPEAKER_01It's entirely true. I know it might feel like tedious bureaucratic paperwork today when you were already busy with a hundred other tasks.
SPEAKER_00Yeah, if it's a lot.
SPEAKER_01But early, consistent, factual documentation is the only mechanism that prevents difficult workplace situations from ending with nothing but competing unreliable memories. It saves time in the long run, it protects working relationships, and it stops avoidable misunderstandings from mutating into wildly expensive legal battles.
SPEAKER_00Well said. I want to leave you with a provocative
Remote Work Data Versus Real Records
SPEAKER_00thought to chew on, something that builds on everything we've talked about today regarding memory versus the record? Yeah, I'm intrigued. We live in a heavily remote work era now, right? Almost all of our communication happens via Slack, Microsoft Teams, or email. We are constantly passively generating a massive, chaotic digital footprint every second of the workday. That's true. Does this reality make the memory versus record problem easier to solve because technically everything is already typed out and searchable? Or does it actually create a much greater risk?
SPEAKER_01Oh, well, that's interesting.
SPEAKER_00Because managers might mistakenly rely on those scattered, out-of-context chat logs to prove their point, assuming the system is doing the work for them, instead of taking the time to sit down, remove their emotions, and write a clear, objective, and unified document that answers those seven vital questions.
SPEAKER_01It's a fascinating tension for modern businesses. Just because mountains of data exist in a chat server doesn't mean a coherent, fair, or legal record actually exists.
SPEAKER_00Exactly. The instant replay camera is rolling 247 in our chats, but if you don't know where to look, or you only clip the isolated parts you want to see to support your own bias, you're not documenting fairly. You're just cherry picking evidence.
SPEAKER_01And that's a dangerous game.
SPEAKER_00It really is. Thank you so much for joining us on this deep dive. We hope you take these insights and that seven question framework into your next management challenge. Until next time, keep the instant replay focused entirely on the facts.
