This website covers topics on knowledge management, personal effectiveness, theory of constraints, amongst other topics. Opinions expressed here are strictly those of the owner, Jack Vinson, and those of the commenters.

Project disclaimers

Hal Macomber reports an idea from a PM discussion group in Warning: This is NOT an accurate representation of how the project will unfold (quoting Amy Schwab of True North pgs):

Here is an example of a forward looking statement disclaimer I recently ran across in a news release about a company's new product offering. Imagine the slight change required to include this for your project -- and how it would more appropriately communicate the uncertainties included in that project:

Certain statements made by the company in this release may constitute forward-looking statements. In light of the risks and uncertainties inherent in forward-looking statements, many of which are beyond our control, actual results may differ materially from those projected in the forward-looking statements. Forward-looking statements should not be regarded as a representation that anticipated events will occur or that expected objectives will be achieved. These forward-looking statements involve risks and uncertainties including, but not limited to, the following: our ability to successfully market a new product in the current economic environment; changes in the demand for, pricing of, or supply of our products; competitive considerations, including possible actions by competitors and an increase in competition for our products; general economic conditions, including changing interest rates, rates of inflation and the performance of the financial markets; and various other factors. We undertake no obligation to release publicly the results of any future revisions we may make to forward-looking statements to reflect events or circumstances after the date hereof or to reflect the occurrence of unanticipated events.

Not a bad idea to include with any projections. In a previous entry Macomber talks about doing "Back to the Future" activities. He didn't elaborate, but I wonder if this is the heart of the way I have learned to plan projects: Identify the project endpoint and successively work backwards to identify the activities that must be accomplished to reach the goal.

Review of The Future of Knowledge

Powerpoint and gov't work