Hey, hey, hey! Welcome to this session of the Compass Definition project where I am illustrating the ideal state of Cryptiquest with a focus on defining measurable and objective meanings for the terms within the compass statements (vision, mission, and values). In the previous session, I identified the objectives for this project. In this session, I will pin down all the deliverables.
Before I begin, I want to explain something I recently learned. The difference between the terms “future state” and “ideal state”. “Future state” refers to any future version of the process while “ideal state” refers to the absolute perfect version (if resources, physics, or any other logistics were not an issue). I was using “future state” in the goal/objectives in the last session where “ideal state” is more accurate.
With that cleared up, I’ll start by pulling in the goal and objectives:
Goal: To define the ideal state of Cryptiquest based on concrete and measurable terms from the compass statements.
Objective 1: The definition will illustrate the ideal state of Cryptiquest.
Objective 2: The definition will explain each term from the compass statements (vision, mission, values) in concrete and measurable terms.
Objective 3: This definition will be presented as its own thing on a separate page under “Strategy” on the company website.
I think the deliverables are fairly straight forward for this project:
- Identify all the compass statement terms that need to be defined.
- Create objective and measurable definitions for the terms based on the ideal state.
- Define the ideal state of Cryptiquest.
- Draft the copy for the strategy page.
- Send the draft out for confidant feedback.
- Send the draft out for general feedback.
- Implement the page.
- Publicize the page.
I think that’s it. I feel like I’m missing something but I can’t think of what that could be at the moment. Assuming I don’t remember some sort of missing step, I’ll start production next session, focusing on identifying all the compass statement terms that need to be defined. See you there!
- Keep an eye out for project evolution (not scope-creep) with an attempt to identify when it happens (if it happens) and if there is an opportunity to incorporate a step for that in project management documentation.