Latest Articles 

Leaders ask for "good work." They ask for something "done well." They want "quality"; they want people to be "professional." They assume, often without ever examining the assumption, that everyone hearing those words is picturing the same finished result they are. They're not.

People who ask why are trying to do the job well. They're trying to understand the purpose, alignment or mission driving the instruction itself, so that when a judgment call comes up later, they know which way to lean.

This, of course, had pros and cons. If you had a manager that was supportive and willing to listen to your concerns, you felt like you were in a great working environment and were able to bring your best to work. However, if your immediate manager was difficult to work with, wouldn't listen to what you had to say, and was harsh or critical, there was no way for you to find resolution but to leave.

A plant supervisor is training a new team member on a line change. He shows her the sequence once, hands her the checklist, and walks away. Two days later, she's still getting it wrong, and he's frustrated: "I never had anyone tell me twice. I just figured it out."

Generational fluency was the practice ground. Curiosity is the actual skill.

Two people, one relationship, two completely separate stories, and neither of them had said theirs out loud.

Put the two together, though: what you know about generational patterns and what you actually know about this particular person, their history, their role, the stretch they have just been through, and your curiosity gets sharper. It knows where to look.

The real trouble starts when we treat that first guess as a conclusion instead of a starting point, when we stop right there and build a whole response around it without ever checking whether it held up.

"Try that again" lands two different ways depending on who's hearing it. For some, it's relief. A chance to get something right without it counting yet, away from any real consequence. For others, the same five words feel like an accusation. Like proof that they should have already had it. How it's actually taken internally doesn't announce itself. People simply respond to it. That difference is part of what makes psychological safety at work so difficult to read from the out

There are two different things that can happen in a meeting when someone says, "Got it, that makes sense." One is real. Something landed, and what happens next will look different because of it. The other is a performance. Nothing has landed. The nod is happening because asking a clarifying question felt riskier than letting the moment pass. (Not forgetting the spectrum of responses in-between.) From across the table, these look identical. That's the problem. Progress means u

Most organizations don't suffer from a lack of knowledge. People have been trained. They've seen the slides. They can explain the model back to you, almost word for word. Yet behaviour stays stubbornly the same. This gap between knowing and doing is one of the persistent challenges of workplace learning. It usually gets explained away as resistance, low motivation, or a lack of follow-through. There's another layer underneath that's easy to miss, and it has less to do with wi

A leader asks for an update on something still taking shape. For one person, that request feels like exactly the right amount of checking in. For another, it feels like being asked to show an unfinished drawing before the lines have settled. Progress is not only about what is done. It is also about timing, about when sharing happens and why. That timing can play a surprisingly important role in workplace psychological safety. Some people need to work quietly until something i

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