The only person you hurt when you hold back on giving your best effort is you. If the team is not up to your level, you bring them up, otherwise you are letting them down. If your intensity and commitment is different than everyone else’s, you share that with the team so they know where you are coming from. If you see problems that they don’t, bring them up to speed, don’t wait...
We sometimes ask for Feedback, expecting validation in return. “This is perfect” “Great plan” “I like this approach” “No comments” And when we receive feedback we are disgruntled at what we get back. “It’s good but have you tried this?” “What if we incorporated this as well?” “I have some other ideas if you want...
It takes time, it takes patience, it needs a methodical approach to measure what is needed – it cannot be all point and click as fast as you can go and then say – “we’ve tested for performance”. If you’re getting started with implementing a Performance Strategy for the first time there are a few steps you can take before you even start coding that will help set...
Think about the people you are teaching to. Think about the problems they are trying to solve. Plan for what they want to get out of the course. Understand they will not be at the same level that you are. But don’t do it on the First Day of the course. There is nothing that kills a course faster than doing all these things 5 minutes before you go into YOUR plan that has nothing to do with...
I could go on and on about everything going on in this comic book drawn by the incredible Todd McFarlane. Instead just focus on that one line – “Rise above it all.” Share this:Click to share on Facebook (Opens in new window)Click to share on LinkedIn (Opens in new window)Click to print (Opens in new window)Click to share on Twitter (Opens in new window)Click to share on Google+...