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 –¬†

Delivering the Bad News

The first thing that entered your mind: You messed up, you made a mistake, I can’t believe you are here, what a waste of time.

The first thing that should come out of your mouth: You did well on X, Y needs some work, here’s what we’re going to do to get you there.

Your first thought gets out all your frustrations, in your head but is not the delivery your team needs.

The person on your team already knows they screwed up, they don’t need to hear it in stereo.

What they need to hear is where do they go from here.

Delivering Bad News is less about what went wrong today and so much more about what can be fixed for tomorrow.

Schedule your Work

If you’re struggling with finding the inspiration to create the next amazing novel, piece of art or anything that will stand the test time.

Pro Tip: It’s not going to come, regardless of the number of scented candles, sunsets and moco choco frapunchinos¬†that you have beforehand.

It’ll come when you sit down and do the work.

The easiest way to sit down and do the work is to schedule into each and every day.

That’s it (seriously there’s nothing else).

The Monthly Reset

Whether it’s the first day of a new month or last day of the previous month you need a reset.

Not a week long vacation in the Turks and Caicos, but a one-hour conversation with yourself where you ask the following questions.

What did I accomplish?

What worked?

What didn’t work?

Where did I go wrong?

Where did I go right?

What do I need to repeat?

What do I need to tweak?

What do I want to achieve next month?

If you’re not asking yourself these questions every month, then you’re not challenging yourself to keep getting better.

When to Get Worried

When trying to solve a complex problem and people want less information on the solution.

When everyone is saying “Yes” to everything you are saying.

When there have been no changes to a problem, but the code starts to work.

When the requirements change, but no one knows.

When people start saying “it should just work”.

Those are the moments when you should start getting worried, not because something could go wrong but because it already has.