www.Leazott.com

Faster Research Methods - A Boone Or Bust?      Published Monthly
Lesson 048...                                                                                                            2019 10 01

Defining The Problem...
We all want to record as much family tree information as we can, and in as little time as is possible.
The issue is in finding the fastest method that can still collect all required data for your project.

Sometimes we get so caught up in adding more names, that we fail to get any real data for them.
While there are reasons for that type of family tree, it takes twice as long to add the info later.

It's very common to discover that there are better methods than what we've been "doing all along".
We then have to struggle over whether to change our ways, or to continue with old methods.

The urge to continue "because it takes too long to try other things" can block us from even trying.
Using a familiar practice is comfortable, but can often mislead us to thinking it's the best way.
Conversely, if we quit a new technique too soon, we've also stopped before mastering it.

Regardless of how or why we became "stuck in our ways", we must be openminded to other methods.
If a researcher doesn't verify the data collected, the genealogy shown may be incorrect.
The same is true when we form an opinion using one sided information.


How Did That Happen?...
We're new at this! Without guidance, we simply tried this or that, and adjusted things along the way.
Eventually we gained some expierience and became better at the process we "invented".
The downfall was when we became as drones and stopped advancing.

This was likely because things were running smoothly, and it was the best system we'd seen so far!
So it became "the norm", and as with any system, the better you know it, the faster you go!
This is absolutely fine, and is as things should ever be... Until a better way is found!

Many are not interested in forming a large family tree, which renders some methods unnecessary.
For small trees, the time factor involved with data retrieval for multipersons is minimal.
Though it's crucial for those building a genealogy-database of over 10,000.

There's also the possibility that having tried a new avenue, something went wrong and sent us back!
A close call with a total loss can be enough to freeze you in your tracks for a very long time!
Eventually though, we have to loosen up again and try some more new things.


What Can We Do To Fix This?...
First we need to understand that evolving is necessary in order to maintain even minimal functionality.
Becoming stagnant whether by choice or avoidance leaves us behind while our resources advance.

Adapt as necessary... Keep trying various new methods that are optional.
Even resource changes leave us with option to try other places.
Our "in-house" methods are always open to choice.

Don't destroy what you already have just to make a change.
If it's a software or membership change, try using both for a month.
Move slowly, and never initiate a complete or radical change as all at once.

Even if you're far along, you should still incorporate as many new methods as possible.
Try working a data type that's lacking in many persons to make them equal to the others first.
When all persons in the database have equal data, continue adding new people with all info included.

Additionally, we must be able to recognise not only when a change is necessary, but also if beneficial.
The adjustments that we do to the work has a direct impact on the speed that we do our work.
Constant minor changes that improve productivity is the main message intent here.


How Do We Find New Methods?...
It's important to remember to change only one item at a time...
This gives a more accurate reading of its value and/or issues, and also its "learning curve".
Pick a section or type of information that's obviously lacking or most bothersome to you to start with.

Data blankspots in some persons but not in others may happen if we started adding that data later.
This problem should be considered "sectional". Hopefully your software sorts by that data type.
If it does, then you can quickly add the missing data without having to look at every file.

Be sure to give each method change a fair chance.
Don't expect it to be as fast as items you've been working with for months.
What you're looking for is a "natural feel" or flow. Something that blends well to the order of the rest.

Move slowly, and never initiate a complete and radical change all at once.
If it's a software or membership change, keep both for a trial month.
Don't destroy what you already have, just to make changes.


What Did We Learn From This?...
Regardless of our own desires, research centers will continue to evolve even without our participation.
If the project is to be an ongoing or longterm endeavor, it must adapt in order to survive.

Changes made by outside repositories are beyond our control, and force a choice about continuing.
Each researcher must decide for themselves whether these changes are tolerable or not.
Try to test other places during the interim before any final descision dates.

Within our control are choices that can help constantly guide our family tree database project forward.
Whether they're quantity or quality related, try to maintain only singular changes until mastered.
Changes that are too many or too drastic can overload and make finding issues difficult.

Give each idea for attempting a change the appropriate time that its due in order to prove itself.
Be certain your'e not discarding it simply because it's different or requires adaptation.
Weigh each effort for productivity increase against their time-cost-effort.

Many of the changes that we attempt may be poor choices and not work as planned.
Because of this, we cannot risk chaos due to an extreme change in direction.
The basis of this hobby is always verification. Even for our methods.


The Basic Rules...
First...
Be open to any new suggestions.
Whether or not to implement the change is an entirely different matter.

Second...
Make only singular/non-drastic changes to avoid overload.
Dealing with too many changes at once may be difficult even for advanced genealogists.

Third...
Don't commit fully to any changes until you're certain of its productivity.
Similarly, don't be afraid to make changes simply because of uncertainty. You can always go back.



As always...
What you'll choose to do with this information is up to you.
It will at least serve as a stepping stone for further knowledge.
You should be applauded for your willingness to educate yourself.

These are only basic guidelines, and can always be adjusted to suit your personal needs or budget.
Hopefully the knowledge gained here will help you to be better positioned as a family historian!

      Happy searches!!

        Massachusetts

Our family. Our website.
Leazott.com