Listen Up (assuming you want to get better)

There is only one path to getting better at whatever it is you are doing.

And it starts with listening to those around you.

Listen to their suggestions.

Listen to their ideas.

Listen to their feedback.

Listen to their experience.

You don’t need to accept it all, but you need to do more than hear it, you need to listen to it, you need to process it, you need to think about it.

And then you need to put your own twist on it.

You’re not alone but if you can’t take feedback from others, you always will be.

Sniffing Markers: Ep 20 Kanban Can!

And here’s the follow-up to our episode on SCRUM BUMS – the KANBAN CAN – learn how one of the producers has a KANBAN board for their family (not me).

As always, please rank, review and connect with us on Facebook!

Download the latest episode here –

Bad News Message Delivery

There are two ways to convey bad news to someone (whether it be their personally tied to them, i.e., their performance or their team at large).

Option #1

You screwed up, you failed, this isn’t working out, it’s time for you to move on.

Your best (is that what you called it) wasn’t good enough.

Option #2

Here’s what you’re doing well, here’s where we’re going to help you with and here’s what we need from you to help us get there.

The Difference?

Option #1 assigns the problem and throws it at someone’s feet (doesn’t matter if it’s right or wrong).

Option #2 recognizes the problem, acknowledges the person and puts the onus on both the leader and the individual to get better and turn it around.

Or simply put – one reinforces the negative, while the other seeks to learn from it and become better.

Run To

If you don’t know what the answer is, go find someone that does.

If you don’t know what coding language you should be using, choose one.

If you don’t know what the customer wants, schedule a call.

If you don’t know what features are in the task you are working on, identify some and get to work.

If you don’t know what to do on the field, run to the ball.

In any endeavor, the first step can sometimes be the most daunting.  Perhaps we are part of a very complicated project, the customer is hard to talk to, no one really knows what they are doing, or the rules of the game are really complicated.

Whatever the case, Run To, Jump In, Take a Leap, whichever you want to call it.  The goal is to start, to get going and take that first step.

Because once you take that first step, all the other steps that you are worried about – using the right coding language, asking the customer the right questions, knowing what to work on, what to do with the ball when you get there, will all fall into place.

Run To and never stop.