Showing posts with label Tony Sherman. Show all posts
Showing posts with label Tony Sherman. Show all posts

Monday, December 1, 2014

It's not DONE yet!




Hi, this is Tony Sherman the Implementation Rabbi and Impact Teams hoping that as we hit the holiday season, there is nothing broken and nothing missing in your life.

I've had some interesting interactions about some of the prior blog posts, but the one that seems to have caught a lot of people off-guard is my idea that if you haven't finished the task at the end of the day, break it down into at least three subtasks. Apparently, my brevity in that post did not lead to clarity.


So, let me break it down a bit more to show you how I use it. When I teach this as a component of my SPIDER program, my students quickly come to realise that the reason why something is not done, typically falls into one of two categories:
  1. You've bitten off more than you can chew that day, and the task may have been better living on your backlog list rather than your daily integrity list.
  2. It's a task that you really would rather not do, so there is some psychic resistance to doing the task. The classic example of this for me is travel expenses. Quite often, I would find myself moving the item of travel expenses from one day’s to-do list to the next for way too many days than I care to admit.

However, once I created the system where if I did not complete a task or even worse didn't even start the task, I could not carry it forward without decomposing that task, life changed dramatically from better.

I found one of two things would happen to me as I decompose the tasks. I found that I either just put one of the tasks onto my next day’s list, and the other subtasks went on to my backlog. Or as typically happened with travel expenses when I put the three small steps (which were almost embarrassingly small) onto the next days to-do list found that once I started one small task, and completed that to standard, that I naturally just completed the others because I was in the flow and they were really trivial anyway. In the second case, decomposing a psychological barrier into a few small trivial tasks allowed me to overcome my mental inertia.


I hope this bring some clarity into the idea of decomposing a task and using it to maintain your momentum and sense of professional pride as someone who is a can-do person, who doesn't just start tasks, but completes them to standard on time, every time.
Merry Christmas


Until next year, this is Tony Sherman the Implementation Rabbi at Impact Teams wishing you a productive and high-momentum month with nothing broken nothing missing in your work and personal life, Merry Christmas to all.

Wednesday, November 12, 2014

Defining DONE!



A few weeks ago, I mentioned that one of the steps to driving tasks to “DONE” was to define what done is. So I wanted to grab a few moments  to take a deeper dive into what sounded like a simple activity.

When we're doing something, it is almost always for someone else, let's call them the client. When I'm doing something by myself, I ask the client is this what you mean by done? And then I ask

‘if I do it this way is that a good standard for you’?

I always ask this, even for simple tasks. If I'm having a conversation with somebody and I agree to do something very simple, I will still say at the end of the conversation:

"let me please just reflect back to you what I think my action items are for you - you want X done by this date, and if it's done like this then you will find that satisfactory. Is that correct?"

You'd be amazed at how much clarity comes out of something simple like that.

The other situation is when I'm doing something for the client, and I'm working with a team, here I do exactly the same thing. First, I confirm with the client what DONE is, and what an acceptable standard is. Second, I tell the team what we are doing, what done is, and what the acceptable standard is. Thirdly, I apportion the work that I want them to do, and  also tell them how it contributes to DONE. Finally, I asked them at the end of the conversation to reflect back to me what they are going to do for me, what DONE is, and what the acceptable standard is.

When I first started this practice, I was very nervous that it would make me appear unprofessional or a micromanager. In fact, I have had nothing but positive feedback from both customers and teammates. They enjoy the clarity. The clarity of knowing I know what they want, and what an acceptable level is; and also knowing when it needs to be done.

This is truly a WIN-WIN-WIN situation. Not only do you very rapidly get a reputation for being someone who delivers to a high standard of reliably, but you'll find that your teammates enjoy working with you because you exude a level of confident professionalism in your conversations.

So the next time you think about getting something done, make sure that you define DONE fully; you'll find it a lot easier to do (and by that I don't mean to start doing, but drive through to finished and DONE!).




Until next month, this is Tony Sherman the Implementation Rabbi and Impact Teams, hoping that in your work life there is nothing broken or missing.