How to Design XML Documents
Aug 27 2:51:29
Back online!
Jul 30 16:17:53
Response to "Knowledge Management 2.0"
Jul 18 2:45:52
Drupal Apps
Jun 3 7:17:00
Google Sites and the AJAX universe
May 21 1:18:39
Strategy documents need to outline two key things -- the objectives of the strategy, and the goals which are necessary to achieve these objectives.
Bob Lewis explained the difference between objectives and goals to me this way:
[An] objective [is] the point of it all, described from the perspective of business benefit. So if what's being proposed is a so-called CRM system (customer relationship management) the objective might be to increase revenue and decrease the cost of sales.
["Goals" are the] changes that will occur that will result in the benefits described as the objective. For the CRM effort, the goals might include designing a new sales process, selecting, configuring and implementing software that will support the process, developing and delivering a sales training program, and so on.
It's the difference between describing what will actually happen (goals) and what the business will achieve as a result (objective).
To help the manager evaluate the objectives and goals, most strategy documents are structured under seven sections:
NB: Objectives are sometimes referred to as the purpose of the strategy; Goals can also be known as [key] deliverables.
Documents can be structured in a variety of ways, for example:
or