There is no difference between big and little projects. One might need more people and money, the other might need more agility, but in the end, they are still projects with meetings, people, and processes. But they both need to get done. They still matter to someone. They both hold value. Downgrading one because it isn’t “big enough” is a copout. Cutting corners because one is too small is a surefire way to miss valuable…

If you are spending the first 20 minutes of a one-hour meeting, what is the point of your meeting? You aren’t ready to have that meeting. Not probably, not maybe, not kinda sorta. You’re not ready. Figure out the point of the meeting, explain it clearly, concisely, in under 2 minutes – use the rest of the time to address the point. Not to figure out what the point is.

Your job might not fulfill you. Honest but true. You might have a job that doesn’t fulfill you. The next step is finding what fulfills you and putting time into that to counteract the work that doesn’t fulfill you. But first, you have to identify what actually fulfills you – and that’s the hard part – asking and learning what makes us feel great.

I can’t count how many times I have finished a project, only for a new version, an upgrade, a patch, an extended release, a beta, something, anything to come out that required change. I was once told that if you don’t want your software to change often, build software for hardware. (I’m not sure if this is true, but it has stuck with me). You gotta change, you gotta realize the only constant in life…