Database Development:
A Structured Approach

The best consultant is a good listener. We learned that many years ago. You know what you want to accomplish. Our role is to listen to your needs, wants and wishes, to ask relevant questions and then to develop a system you can use to exceed your expectations.

Of course, the in-between steps are most important, for they determine how together we will get to where you want to be.

From the onset we will dialogue, explore purpose and identify a hierarchy of preferences until there is absolute understanding and agreement defining exactly what you hope to accomplish with your Database.

We have developed a carefully orchestrated system to assure your requirements are satisfied. As with any other good system, this process is dynamic. It will be adapted to address your specifics, and as important, to work within your corporate structure.

Every process should incorporate a beginning and an end. We believe the process of developing a Database should begin with a Mission Statement. An example appears below.

Your comments, questions and suggestions are always welcome. Should you wish to contact us about our Database services, send email to Database@crmnetwork.com 

Mission Statement:
Create a single repository (?the Database?) for all data identified as relevant to meet the requirements of the department or business entity you define (?the Business?). Develop and implement user friendly tools, systems and procedures to enable the Business to successfully use the Database to achieve its mission.

The Process:

• Create A Task Force
• Key Staff members who understand and can convey needs/wants
• Must represent
• Each Marketing User Unit within the Business
• Administrative Staff
• Management
• Define Major Marketing Objectives for the Database
• Define Process Methodology
• Segment User Groups
• Function
• Needs
• Identify hardware, software available to achieve tasks
• Perform An Audit
• See data samples from all current sources
• Know data origins
• Know how data is captured and fed into which system
• Confirm whether data fields are populated/with what/are blank
• Determine Data Usage
• Task Force members must provide wish/want list for area represent
• Screens
• Queries
• Reports
• Define/Address inconsistencies/obstacles
• Define
• All files and data needs
• All in-house IT rules
• All data elements required
• All data enhancements required
• Evaluate/Address Gaps
• Develop Specifications
• Standardization Specs
• De-duplication and Aggregation rules
• Roll-up of Orders, tracking and other transactional data
• Data Dictionaries
• Definition
• Data update volume/frequency
• Define
• Input editing procedures
• Data Capture methods
• Output requirements
• Address/Define
• Security
• Privacy
• User Access Levels
• Build A Prototype
• Test Prototype
• Begin Training key users
• Load Data
• Continue Training
• Run concurrent with present system until satisfied
• Discontinue use of present system