Rule from personal software projects: If you tell other people of your first release, you won't have a first release, ever. The only thing that works is "hey, i wrote this and it works, have a try!" -- you'll be hatching your creation until that and you might actually get to release it.<p>Note that the first release need not be big and complete, just something that works. But the game changes after that, so the above rule loses its context. Running a public project is a different scenario from the initial phase of development.
My experience is that it depends a great deal on the types of the goals and how they're presented. The article mentions vaguely-defined, general self-improvement goals, like taking up a new hobby. I can see a public commitment being counterproductive there. But I'd bet that it works differently for more quantifiable goals, especially ones with a specific starting time, such as completing Nanowrimo, or telling your boss that you're going find a fix for bug XXX before Monday.<p>Quitting smoking? A hell of a lot easier to change your mind about if you haven't told anyone.<p>Of course, we're just going on the article. I don't have access to the original paper, but just reading the abstract already suggests (big surprise here) that the article is probably not a faithful summary of the study in question.
I got to know this law by Derek Sivers's TED talk[1] and I totally agreed with him especially about personal programming project.
A downside of this approach is that you cannot get a feedback until you unveil first version.<p>[1] Derek Sivers: Keep your goals to yourself
<a href="http://www.ted.com/talks/lang/en/derek_sivers_keep_your_goals_to_yourself.html" rel="nofollow">http://www.ted.com/talks/lang/en/derek_sivers_keep_your_goal...</a>
I find it more likely that the harm done to your goal is not caused by public announcement of that goal, but rather announcing it is evidence that you aren't as committed to the goal as you are to other goals that you're better at sticking to. In other words, if you're having trouble with achieving something in particular, or working towards it, then you are likely to acknowledge that to yourself in the form of "needing to set a goal" and thus "announcing it to the world", thus automatically ensuring that announced goals are less likely to be kept by the very nature of the fact that they needed to be announced in the first place. If you want something badly enough, you are more likely to "just do it", thus foregoing the need to announce it to others.
I found beeminder (<a href="https://www.beeminder.com/" rel="nofollow">https://www.beeminder.com/</a>) to be a surprisingly effective commitment utility. The goal has to be measurable, and you have to trust yourself somewhat enough not to subvert the rules, but since there is a counter-party most people's sense of personal ethics should be sufficient.
<a href="http://four.livejournal.com/963421.html" rel="nofollow">http://four.livejournal.com/963421.html</a><p>I'd say, only talk about your future plans as much as you are comfortable to. Sometimes just talking vaguely about your things with other people helps to keep you interested and motivated.
Well, I'm sorry to say that I believe exactly the opposite. Public committing means a high level of responsibility and scrutiny, and it is the best motivator for any task.<p>In our weelky meetings we write down each task that needs to be done and the name of the person in charge, then send it by email. Even if there is no follow-up the next week, we observed that stopping to send the emails leads to less work done (or, at least, not the work that is expected to be done by the managers)