Database design, database repair, access, paradox

Welcome to TTG Services with Phil Marcus

Call Toll-free 877-934-4766   

 

Major Topics
on This
Site

Home

My Database
Qualifications
and Depth of
Experience

Range of
My Services

Check Out My
Case Studies

My Tell-All
Interview

Database
Basics

Rich Web
Pages

All About Data
Servers

The Synergy
of My
Education

The Value to
You of My
Memberships

A Common
Thread

Why TTG?

Ask Me
Questions;
Get Answers

Links &
Resources

Online Shtick

Home

Start

A Candid Interview with Database 'Medic' Phil Marcus...

In this recent interview I am asked how my clients can ensure that they will get database systems that do what is really needed.
Begin interview...

Navigation Bar

Interviewer: You seem to pride yourself in creating results-oriented database systems. How do you accomplish this?

Phil Marcus: One of the first things I learned when I started out is that every business or organization is different. Therefore, I never assume beforehand that I know what my clients want or need. Instead, I begin by asking straightforward, non-technical questions about how things are going now.

I never assume beforehand that I know what my clients want or need.
Interviewer: How do you put this approach into practice?
Phil Marcus: By carefully ascertaining what is working well and what needs to be improved, I am able to create custom database solutions that fit each of my clients' unique requirements. In this way I have seen, time and again, how a simple, well thought out, well functioning system can give a tremendous boost to production efficiency, employee morale and organizational profitability.
Interviewer: One gets the impression that you run across a lot of companies that have poorly designed systems.

Phil Marcus: One of the biggest problems I see is that of companies being saddled with database systems that are incompatible with their needs. This is because so many software engineers make biased or subjective assumptions and tend to use their favorite solutions over and over. As a result, other features that are critical to success never make it into the system design.

One of the biggest problems I see is that of companies being saddled with databases that are incompatible with their needs.
Interviewer:
Can you give me an example of how your approach might improve efficiency?
Phil Marcus: Yes: One of my non-profit clients is involved in providing emotional counseling to troubled youngsters. When they bill Medical Assistance for these sessions, they get back data on diskettes showing which claims have been paid and which have been denied.

The client had files for thousands of sessions that had been submitted and denied, as well as files for many sessions that apparently had never been submitted but should have been. Collectively, these sessions represented tens of thousands of dollars. By selective content analysis, I was able to show at a glance which billings and services were or were not being properly submitted.

Interviewer:
Couldn't any systems professional have done that?
Phil Marcus:
Not necessarily. Keep in mind, this wasn't just a programming solution. First, I had to understand the principles behind their services and billing. Once the properly submitted or incorrectly unsubmitted claims could be quickly differentiated, the problem was easily remedied. My "low tech" procedural solution saved the client from reviewing thousands of sessions by hand and created an efficient database system that saved a huge amount of labor.
Interviewer: How can organizations make sure they end up with solutions that will maximize their operational potential?
Phil Marcus: My advice to clients trying to improve processes is that they only hire experienced systems professionals who know how to listen. They should avoid working with software engineers who are too quick to offer a "solution." Indeed, I've been doing what I do for a long time since ‘86 actually and I've seen countless examples of systems designed around preconceived notions or antiquated concepts. If programmers are not asking insightful questions, or if they respond in ways that suggest they aren't listening, that should raise a big red flag. If programmers respond in ways that suggest they are not listening, that should raise a red flag.
Interviewer: Is there any one thought that you would like to leave with our readers?
Phil Marcus: : Yes, "bells and whistles" do not make a good system. Careful, probing analysis, combined with an experienced developer does.
Back to Top

Navigation Bar

Be sure to read my "Basics of Databases" article.  It will tell you everything you wanted to know about databases but were afraid to ask.

Navigation Bar

I'll be looking forward to hearing from you!

Interested? You can reach me at:
phil@ttgservices.com

Toll-free phone: 877-934-4766
Fax: 301-498-9454
Location: Columbia, MD, near Washington, D.C.

Use your Discover card!

TTG Services-Helping Clients Since 1989

Member of Independent Computer
Consultants Association
,
and subscriber to its Code of Ethics

Creative solutions for you, designed for excellence. 
Serving North America.

Navigation Bar

Links to other Webs are provided as a convenience only.
No endorsement of or by any link should be inferred.
Access and Paradox product trademarks are the properties
of their respective owners.

Entire Website copyright � 1999-2002 by Philip L. Marcus.  Last updated 11/24/2002

Divider
Divider