so lessons learned are documented.
BUT, blogging should not be misunderstood as documentation.
you do not put all your learnings in the public view.. (well, may be in the social web 2.0 view of business, but not in a traditional business).
You create an internal repository of documents (designs/requirements/deals/legal etc.), and go back to them, when the need arises.
You're right that there are internal documents that the business is required to develop. Or ones that are necessary for the business to function. Those may or may not be proprietary.
I was thinking more along the lines of the ethereal thought process of the entrepreneur or maybe providing context for public decisions.
Thanks for making this distinction.
why not?
* Some of the lessons learned are highly specific to your project/team. They may not translate well to other teams/projects. Such things, while valuable, may not make sense on a blog.
* Perfect transparency may be at odds with building brand confidence. Letting your customers see every one of your mistakes (in the guise of lessons learned) may work either way with regards to customer confidence.
Startups need to blog to remember what they did and why they did (and this is the most important part) within the context of what was happening at that point in time.
We think we'll remember all of our brilliant moves and boneheaded mistakes. But we won't. And sometimes it isn't even obvious why we made them, out of context.
But a blog will provide an historical record of what we did when. So we don't repeat the same mistakes next time. And so lessons learned are documented.