When a model is built, it tends to be an iterative process. The ideal model building process starts with constructing a top-level model (that works) and then digging deeper into the sections that need more details. A good model tends to have a long life and be both adapted and updated. A perfectly transparent first model (in whatever platform or programming language it might be) therefore tends to get increasingly convoluted. Yet, it still needs to be submitted and reviewed since it will likely be used as support to facilitate possibly multi-million Euro decisions. So, any modelling method should be able to accept substantial changes and updates of the model without compromising (any hopefully existing) transparency. One method that is gaining traction has its heritage in one of the oldest types of structured algorithms we have-the cooking recipe. Regardless of whether you are looking at a recipe for Swedish meatballs or a recipe to prepare the poisonous Fugu fish, the structure of the recipe is the same. It begins with a list of ingredients with the cooking steps to follow. Combining the 'recipe' idea with a common software like Excel (which tends to be available on most computers), and the need to 'cook' all kinds of different model types (Markov, micro-simulation, discrete-event simulation, partitioned survival), leads to the DICE method (Caro in Pharmacoeconomics 34(7):655-672, 2016). It starts by listing the initial take on the ingredients needed for the model (in DICE called 'conditions'). Just like writing a recipe, it is easy to add ingredients to this list later as needed. Then the actual 'cooking' is specified as a list of the events needed to fully represent the disease and interventions that will take place, followed by the instructions for each event. Using this approach, it becomes as easy to look at different models as it is to look at different recipes. The simplicity, flexibility and standardized structure, but especially its transparency, are the main features of DICE.