1 or 10 Things You Should Do When Inheriting a FileMaker System/Database

1. Understand the business and process flows of what the business does.
2. Look at system from the users’ point of view and map out what it does.
3. Conduct an in-depth technical analysis (we call this a System Condition Report) which includes review of security, deployment, referential integrity, error handling and adherence to convention. Note any areas of concern.
4. Begin supporting the system, addressing day-to-day problems, but steer clear of any big developments for now.
5. Compare 1 & 2 and see where the gaps are (i.e. what the system doesn’t do but the business does). Of the things it does do, work out how well it does them! Does the system actually support the business process?
6. Brainstorm what could be done to fill in the gaps or to improve what it does or doesn’t do very well.
7. Cost these projects and the areas of concern noted in step 3.
8. Draw up a project plan, prioritising.
9. Deliver, test and implement one project at a time until finished.
10. Repeat from step 5: continually analysing the system’s fitness for purpose will ensure that it continues to fit perfectly with the evolution of a growing business.

Alternatively:

Contact Decent Group, who are experts in all of the above and are well placed to give your systems – and your business – the productivity boost they deserve.