Welcome to Manner Tools. Our guidance on I'm working on not. Here we go.

Folks, this guidance answers the questions of why are projects and tasks so often delayed and how can you help your directs

meet their deliverables?

Projects and tasks are often delayed because deadlines are vague or distant.

Tasks are too big, too hard to quantify, too easy to put off.

And even if a project has already started, you can actually accelerate its progress by asking

for details about what people are working on precisely, rather than just accepting the old answer of fine and of actually creating deliverables

if in fact clear deliverables haven't been created.

And you can do this whether they're working on a project or not just if they're working on standard work, which is of course almost always a series of tasks.

Here's our outline. When your directs are quote working on something, which I'm sure you've heard

them say before you've got to probe for details. The two questions we need to

learn to start asking are what's your next deliverable and when will you commit to delivering it.

Pretty simple. Okay let's get into the details. When your directs are working on

something we recommend you probe for details. Don't be satisfied with the classic answer of fine, right?

Yeah, because that's what everybody says, right?

It's almost a joke, right? except that it's frustrating for managers.

We know when we ask, Bartir X, hey, you know, give me an update or how are things or how is Project X going?

We know they're going to say that and we'd all admit that very few projects finish on time,

on budget, and to scope.

So how is it that whenever we ask, every project is almost always fine.

Or if your directs are willing to go into some detail, what they'll say is, I'm working on this. I'm working on that. Oh, I'm doing this or I'm doing that.

Right. They're not trying to mislead us, right? They're not giving vague answers because they're trying to hide something.

...