[Personal growth] The problem with goals is...

Well, there are actually at least four problems with goal setting:

Winners and losers have the same goals

some make it, some fail miserably. Why?

Achieving a goal is a momentary change

once you achieve your goal, you stop from continuing your transformation

Goals restrict your happiness

when you don't reach your goal, you fail to see the progress and only see the failure

Goals are at odds with long term progress

you can choose to win one game, or continue through the championship. Goals will only achieve the game.

What James Clear nicely says: "You do not rise to the level of your goals. You fall to the level of your systems." really hit home for me.

And as John C. Maxwell highlights: "By actively pursuing development, we can achieve our goals more effectively." it's pretty much saying the same thing: focus on your development, in whatever way you want to pursue it, and the results will follow.

So, as we move from goal setting to creating our systems, there is one more important thing to keep in mind: you need to be clear about who you want to become, and why.

When your identity is clear, the processes will support and the outcomes will follow.

Trying to change the wrong layer is going to lead to failure.

Outcomes are about what you get.

Processes are about what you do.

Identity is about what you become.

If the direction of change is not the right one, the change does not happen.

So it's time to reflect and see how you want to implement your change:

Or... you go the simple but not easy route:

Comments

[Goal driven] A technique that has (almost) nothing to do with tomatoes

I know a lot of theory about time management, techniques, ways of organizing yourself and so. And I am sharing my knowledge with others as well. But the most rewarding part comes from actually applying these techniques myself. For example – using the Pomodoro technique has given me the joy of achieving significant progress in just a small amount of time. Imagine a bright red, glossy tomato-shaped kitchen timer sitting on a clean wooden desk. Its rounded surface gleams under soft daylight, with a small green stem on top, mimicking the look of a real pomodoro. Around its circumference, bold white numbers mark the minutes, with a simple arrow indicator showing the current countdown. The timer’s dial is currently set to 25 minutes, signifying the start of a focused work interval. Nearby, a notebook and pen suggest readiness for productivity, while the timer’s classic wind-up mechanism adds a tactile, satisfying element to the scene – a perfect embodiment of the Pomodoro technique in ...

Getting PMP certified

I've got a lot of friends asking me about how to get certified. Each time, I had to remember how many hours of experience one had to have, and how many hours of learning, and then which where the links that were most useful for me, as well as all the books and software I have ever used. In terms of specific requirements for getting certified, the best resource will always be pmi.org, with a direct link to the requirements: PMI site - Obtaining the Credential . The site lists a credential overview, and then there (currently) 5 handbooks for the 5 available certifications. There is also a page with how to prepare for the exam, from an administrative point of view. If you are new to project management, then you will have to go with the CAPM certification. Then, the rest of certifications are for more and more experienced PMs. I only know well about the PMP certification, as it's the one I've got. First step is to ensure that you meet the elgibility requirements. At the t...

[Management lessons] When the Best Plans Fail: Lessons from a troubled launch

A few months ago, my team was gearing up to launch a new automation tool for case assignment - a project that is key for the future, and also were we spent so much energy into. We spent weeks identifying scenarios, testing in a dev environment, and reflecting on potential issues. We wrote crystal-clear documentation and worked with a rockstar team of developers, testers, and communicators. We thought we had every base covered. But when launch day arrived, chaos ensued. The tool hit snags that never showed up in testing - edge cases we hadn’t anticipated. Worse, some team members seemed blindsided by the changes, despite our efforts to keep everyone in the loop. It was a classic “complex failure,” as Amy C. Edmondson describes in her book Right Kind of Wrong: The Science of Failing Well . Complex failures, Edmondson explains, aren’t the result of one person’s mistake or a single oversight. They happen in intricate systems where multiple factors - technology, human behavior, and unexpe...

Management, Coaching, Consulting, Project services

Search This Blog