All Posts

The team is busy. People are doing the work. And yet… things still aren’t moving. That’s usually when the conversation turns to: “What else do we need to do?” That’s the wrong question. In my experience, execution problems are rarely execution problems. More often, it comes down to a few things: Direction isn’t as clear as people think Expectations aren’t aligned Or there are conversations that just aren’t happening None of that shows up in a project plan. But it shows up eve

You see it all the time. The team is working hard. Everyone is busy. Nothing obvious is broken. And yet… nothing really moves. Deadlines slip. Decisions drag. Progress feels slower than it should. Most people assume it’s an effort problem. It’s usually not. More often, it comes down to a few things: Ownership isn’t as clear as people think Priorities aren’t actually aligned Decisions sit just long enough to slow everything down On their own, none of those seem like a big deal

Have you ever had a boss with an “open door” who was never really available? Or a peer who, when you needed someone to listen, only talked about their own challenges? Most of us have been there. When you’re leading a team, it’s often difficult to spend meaningful one-on-one time with each person. If you’re managing bi-weekly check-ins, that’s great — but in high-stress environments, it’s rarely enough. In complex project settings, people need support that looks different. Qui

One of the hardest parts of execution isn’t getting people to work. It’s getting teams to work together. Most teams aren’t unwilling to collaborate. More often, they haven’t been given the opportunity — or the incentive — to do so. Over time, organizations naturally drift into functional silos. Teams focus on optimizing their own work, often without visibility into how it impacts others upstream or downstream. The result is predictable. Work moves forward within each team, bu

Most stalled initiatives don’t fail because of effort. They fail because no one is clearly accountable for moving the work forward. On the surface, it can look like progress is being made. People are involved. Tasks are moving. Meetings are happening. But when you ask a simple question — “who owns this?” — the answer is often unclear. Or worse, there are multiple answers. This is where execution starts to break down. Ownership, in practice, isn’t just responsibility or accou

One of the fastest ways to stall an initiative is to start without clear direction — or to lose it along the way. At the outset, most leadership teams believe direction is clear. There’s agreement on the goal, alignment around the strategy, and momentum to begin. But over time, especially in longer initiatives, that clarity often starts to drift. Leadership priorities shift. New perspectives enter the room. Teams begin interpreting the goal differently based on what they’re h

I last wrote about something I call the Execution Stack. One of the most common breakdowns inside that stack happens in the Decisions layer. One of the more frustrating patterns I’ve seen is how often good work stalls while everyone waits for a decision. The team isn’t stuck because they lack skill, they’re stuck because the next move depends on someone making a decision. I’ve started thinking about this as the Decision Gap, the space between recognizing that a decision is ne

One pattern I’ve seen repeatedly inside organizations is that work often slows down long before anyone openly acknowledges there’s an execution problem. Everyone looks busy, right? Meetings are happening. Teams are busy and status reports look reasonable. Yet somehow the initiative isn’t really moving. When I step into a struggling initiative, the issue is rarely effort or capability. More often the problem sits somewhere in what I think of as the Execution Stack. For complex

In the old days of photography, you couldn’t get a photo without first developing the negative. Everything was inverted. The light was dark, and the dark was light. In many ways, that phenomenon mirrors professional development. Early in my career, I worked on — or rather was assigned to — projects that, quite honestly, felt like a waste of time. I was young and very much an individual contributor, but despite my lack of experience, something was gnawing at me. I often couldn

You get home from work, greet your family (or dog… or cat), walk into the kitchen, open the refrigerator door, and just stand there. “What do I want to eat?” You know you’re hungry, but nothing really looks good. Ugh. You just can’t decide. We’ve all been there. Research suggests we make over 200 decisions a day about food alone. Add the thousands of other micro-decisions required to get through the day, and it becomes understandable that by the time a leader sits down to rev

I’m a Fractional Leader who specializes in accountability, but I have a confession. It’s much easier to provide accountability than it is to seek it. Even while positioning myself as a partner for organizations—aligning expectations and clearing blockers—I realized something: I need one, too. Lately, I’ve caught myself trying to outsource that "need" to AI. It’s tempting. I use LLMs to: - Pressure-test ideas. - Refine messaging. - Tighten communication. It's powerful,

Leadership isn’t always “Follow me.” Sometimes it’s so subtle people only recognize it in hindsight. In dynamic project environments, leadership often looks like restraint. Not more activity. Not more oversight. Not more noise. Restraint. • Listening longer before deciding • Thinking bigger — starting smaller • Pausing to ask: – Does it need to be said? – Does it need to be said now? – Does it need to be said by me? • Knowing when to lean in • Knowing when to step back

I’ve been thinking about something lately: One of the quiet risks in many careers isn’t failure — it’s competence. When you’re good at doing, you get more work. When you’re good at managing, you get bigger projects. But when you learn to lead, you change trajectories. Early in my career, I believed being the best “doer” would naturally make me a strong leader. But these are very different things and I've seen it in others and myself over my career. Execution creates output. M

Last week I wrote about two key considerations to think about when you’ve become an Accidental Project Manager. This week I’ll add a third. Here’s a quick refresher: First - don’t get stuck on tools or methodology. Even PMI recognizes “[...] the choice of project management approach does not play a critical role in driving project performance rates beyond the average.” To me this means: given what you know about your organization, select a path forward that will allow you

I’ve been touching on this idea of being an “Accidental Project Manager” – someone that is responsible not just for their own work, but also for coordinating the work of others, and typically, without any real authority over the people, the process or work. There is a cost to this approach. There are several actually. There is a personal cost to productivity, to emotional capacity in navigating ambiguity and added risk to your overall performance come your annual review. T

Lately, I’ve been reflecting on the conversation around time as our biggest constraint at work. But as I tried to write about it, I hit a wall—maybe because the topic has been covered so much already, we all have the same number of hours in a day. That got me thinking: what if the real issue isn’t just time, but capacity? Capacity is closely related to time, but it’s not quite the same. Our capacity—what we can realistically accomplish within those hours—is shaped by all the

I’m going to be honest - the term “Fractional Leader” just strikes me as very “buzzword-y”. I don’t particularly like it as I’m not a fan of buzzwords in general. One company I worked for got hooked on the word “synergy” for a while and used it in almost everything. Ugh! 🤢 Corporate buzzwords aside I’d argue that one of the important aspects of Fractional Leadership is this idea of being an Accountability Partner. Some roles - or maybe it comes down to the people in thos

In the last few years, I’ve heard a lot of talk about Curiosity and what it means to be “curious”. But what happens when curiosity isn’t enough? I’ve talked previously about becoming an Accidental Project Manager early in my career. Those were years of Do-ing: documenting requirements (or eliciting requirements from stakeholders), writing code, designing interfaces, creating new processes and testing, testing, testing. Looking back, when taking the opportunity to become the p

Three seemingly simple words. Unpacking the deeper meaning and applying to your own or your team’s role is not always so simple. I like to think of this balance as a triangle similar to the Project Management triple constraint of Scope, Schedule, and Budget, with each side representing one leg of performance. Strength in one area can only be sustained if it’s supported by the other two. ‘ Lead ’ gives us vision and direction: the why behind our work. ‘ Manage ’ gives us stru

A few weeks ago I wrote about the Accidental Project Manager—the high-performing employee who suddenly finds themselves responsible for coordinating a project without any real project leadership experience. Sometimes it works out. But more often, it introduces real risk: to the individual, the team, the work, and ultimately the business. Hidden Costs for the Individual When someone is filling a role they haven’t been trained for, the costs often show up quietly, like: - Tim