In this article I talked about my 6 D’s of projects, objectives, goals, sales, designs, etc. For this short article I’ll do a little follow-up to explain another aspect of the same methodology.
There are only 2 buckets that any sale or project ever falls into:
Business Need – They want something they don’t have.
Business Solution – They have something they don’t want.
Based on whichever you are presented with, my 6 D’s will produce something different. Let’s look at each:
- Describe (Requirements) communicates Desires
- Define (Specifications) communicates Capabilities
- Design (Solution) communicates the Proposition
- Deliver (Implementation) communicates the Integration
- Debrief (Requirements Comparison) is the Proof of Performance
So in the above, we’ve fixed a problem. So now we’ll see how different this same methodology is when applied to a case where they have what they don’t want:
- Describe (Requirements) communicates the Issues
- Define (Specifications) communicates any Limitations
- Design (Solution) communicates the Reparations
- Deliver (Implementation) communicates the Restitution
- Debrief (Requirements Comparison) is the Quality Assurance
Now in more general terms, my methodology can yield certain documentation necessary for large projects where consensus is necessary. Here we’ll take a look at each of the 5 major components (or “Ds”):
- Functional Requirements
- Operational Requirements
- Financial Requirements
- Maintenance Requirements
- Training Requirements
- Functional Specifications
- Operational Specifications
- Financial Specifications
- Maintenance Specifications
- Training Specifications
- Functional Design
- Operational Design
- Financial Design
- Maintenance Design
- Training Design
- Implementation Plan
- Integration Plan
- Legacy Obsolescence Strategy
- Time Line, Goals, Milestones
- Does it perform as advertised?
- Does it meet the requirements laid out in the first (Describe/Requirements) phase?
This is only a high level discussion of the methodology, as there are many more details to each component, each of which based on what the actual objective is.
I can tell you from years of direct experience that you will get the sale, project, or prospect/customer’s confidence if you have a solid methodology behind you. You will win out over those without one (depending solely on an individual’s skills) even though they may appear cheaper or quicker.