You might have heard about the ETL technique as it is widely used in most current Business Intelligence projects. Having said that, I am usually surprised how often experienced consultants avoid approaching projects in a systematic way and instead use one application to do absolutely everything, from extracting data from a database to data cleansing to creating visualizations. 

An ETL approach helps you have an understandable and easy-to-manage project. Think of it as a chest of drawers. You put your T-shirts in one drawer, your underwear in another drawer, and your accessories in a different one. It will be a lot easier for you to know if something is missing by splitting your clothes into compartments and it is exactly the same in a Qlik Sense project.

Always think of your project as a global one. If you do everything in one place, there will be no room for someone else to help you. Instead, having your project part separated will allow more than one developer work on a given project.

The approach we will describe here is one that we have been using for a while now and it works. However, you may want to add your touch to the structure or naming conventions. This is only a guide for you to have an idea of what a real project looks like.