Latest Articles 

Someone on your team just spent three hours testing an approach that did not work. It is not nothing. They now know something true that will save the project real time later. But there is no field in the update template for that. So they stare at the blank line, trying to figure out how to describe an afternoon that produced no deliverable but real understanding. Progress is often treated as something you can point to. A finished piece of work. A milestone reached. A number t

Somewhere on your team right now, someone is deciding what to make visible. The work is moving. It is not stuck, not behind, just not settled. They know the update is due by Friday, and they are weighing what to put in it. Enough to show movement. Not so much that someone starts pulling on threads that have not been tied yet. The three sentences they finally write will take almost as much emotional energy as the work itself did. From where you sit, none of that is visible. Yo

Every team has them. Nobody wrote them down. Nobody announced them in an onboarding session or included them in a policy manual. But everyone in the room knows them. They learned them the same way people have always learned the rules that matter most: by watching what happened to someone else. Who got rewarded for speaking up. Who got quietly sidelined for saying the wrong thing at the wrong moment. Who learned to wait. Who learned to push. Who figured out that the meeting wa

Most leaders have been in this moment. A project is further along than it should be before someone finally says the thing that changes everything. A decision gets made, implemented, and then quietly unravels. A team member raises a concern in a one on one that would have been genuinely useful three weeks ago in the room where it mattered. And the question that follows is almost always the same. Why didn't anyone say something sooner? It's a fair question. It's also usually th

By the time someone walks into the room, most people have a sense of where they stand. Not always a firm decision. Sometimes it's more of a posture, a quiet leaning toward speaking or holding back, shaped by everything they've learned about what happens in meetings. Some are already settled. Others are still reading the room, looking for a signal that will tip them one way or the other. That posture wasn't formed here. It was formed a long time ago, in a different room, watch

Most leaders I talk to genuinely want to hear disagreement early. They mean it. They're not performing openness. They've seen what happens when concerns arrive too late, and they don't want that again. So they say it. My door is open. Push back. Tell me if something isn't working. And then they wait. What often comes back is quiet. Or general agreement. Or concerns that surface three weeks after the decision is made. And almost immediately, a story forms. It's easy to read th

There's a manager I worked with who told me, flat out, that his apprentices thought one of the supervisors was unapproachable. He said it like it was a fact about the weather. Not a problem to solve. Just a thing. He wasn't wrong. I'd heard it from the apprentices themselves. They routed around him. When they had questions, they asked each other. When they made mistakes, they hid them. When his name came up on a job assignment, a few of them quietly requested a different site

There was a young man, about 25, who sat across from me a few years ago. He had been let go from an architectural firm where he had worked for three years. Efficient on the technical side, by all accounts. A strong hire on paper. But somewhere in year two, something started to break down, and by the time anyone named it, his manager had already made the decision. When I asked him what happened, he didn't talk about the termination right away. He talked about a workflow. There

A few weeks ago, I was sitting across from a Gen X leader who manages a team of mostly younger employees. She leaned back in her chair, crossed her arms, and said: "I'm just tired of all the hand-holding. I did not have anyone checking in on me every five minutes when I started out. Why can't they just do the work?" I nodded. I understood her frustration. And I also knew she was asking the wrong question. Here is something worth sitting with for a moment. The employees she wa

When someone isn't doing what we expect, there's a conclusion that forms fast. "They seem disengaged." "They don't really care." "They're not invested the way they should be." It happens quickly because leaders are busy. The tyranny of the urgent is often running the show. And when urgency is in the driver's seat, there isn't much room for curiosity. What fills that gap instead is judgment, and it tends to land on the negative side. But what if disengaged is not actually what

It often arrives as a quiet confusion. Something shifted with the team, but you can't point to the moment it happened. There was no blowup. No grievance. No obvious turning point. People are still showing up, still doing the work. But they're harder to reach than they used to be. Conversations are shorter. The questions have stopped coming. And when you check in, the answers are fine, but something in them has gone a little flat. You didn't break anything. As far as you can t

There's a version of this that almost every team member has experienced at least once. The leader has said, clearly and more than once, that they trust their people to make calls. That the goal is to build a team that doesn't need to be micromanaged. That collaboration matters and good ideas can come from anywhere. And then a deadline arrives. Or a client escalates. Or something goes sideways. And within about forty-eight hours, the decisions that had been delegated are quiet

Here's something that doesn't always make it into the debrief after a young worker leaves. The organization didn't break a big promise. There was no dramatic falling out. What happened was smaller, and in some ways harder to address because of it: something shifted, and no one said anything about it. A training initiative got paused. A supervisor who had been mentoring closely got moved to a different site. A program that had been framed as a priority quietly dropped off the

There's a conversation I hear more often than you might think. A supervisor pulls someone aside after a shift and says, "You did good work today." The apprentice nods, says thanks, walks to their truck and texts their buddy: I don't know how long I'm going to stick around here. The supervisor meant every word. The apprentice believed none of it. This is not a communication breakdown in the way we usually describe one. No one said anything wrong. The message was delivered. I

It’s Tuesday. Ten minutes to go before the stakeholder call. A capable team member leans into your doorway with a document open on their screen. “Quick one. Can you just confirm this is okay before I send it?” It’s not a big decision. It’s the kind of call they’ve made a hundred times and yet you can feel the air in the question: I’d rather you hold the risk. So you look. You suggest a tweak. You give the nod. They leave relieved. You stay behind with a familiar, slightly hea

You know the meeting. The debrief ends, the leader asks, “Any questions?” and the room answers with synchronized nodding. Nobody speaks. Everyone leaves with the same polite smile… and completely different assumptions about what happens next. The nod isn’t agreement. It’s self-protection. That quiet debrief moment looks harmless. Even healthy, but it often signals something else: people don’t feel safe enough to name what they’re seeing, or they’ve learned it’s not worth it.

Most leaders don’t override decisions casually. They step in because the stakes feel high or because timing matters. Whatever the reason, the consequences feel real. When they step it, almost always it’s framed as an exception. “I’ll just take this one.” “Given the situation, I’ll decide here.” “This is a special case.” From the leader’s perspective, it’s practical. Responsible, even. The challenge is, decisions don’t just solve the moment they’re made in. They also teach the

Some decisions seem to travel in circles. A leader delegates. A decision is discussed. Agreement is reached. And then the question comes back. “Can I just check…” “Before I move ahead…” “I want to make sure you’re okay with this…” From the leader’s perspective, it can feel puzzling. We talked about this. They know what to do. Why won’t they just decide? But decisions don’t bounce back because people lack capability. They bounce back because of what deciding has meant before.

Silence in a 1–1 is easy to misread. A leader asks a question. The answer is brief. Nothing else is added. The meeting moves on. Some leaders leave thinking, “All good. No issues.” Others leave uneasy, thinking about what didn’t get said. What silence means in that moment depends heavily on what it has meant before . For many people earlier in their careers, silence was a form of safety. You learned to speak when you were confident, certain, and prepared. Saying less red

Not every uncomfortable 1–1 feels tense in the room. Sometimes the meeting is calm. Polite. Even productive. and yet, one person walks out feeling supported, while the other feels watched. This difference often surprises leaders. They think they’re checking in. Making time. Being available, but for some team members, the same conversation quietly raises their guard. Generational experience plays a big role in this. For many leaders who came up in environments with clear hiera