Using recipes is not easy for a linear thinker. The information is a blob of text, action steps aren’t as logically presented as they could be, and the info is scattered among books and online websites in lots of different formats. I wanted a way to manage my recipes and groceries in the same place, so I created an Excel-based “recipe database”. I’m going to use it to do meal planning, and to create quick shopping lists. It’s not 100% developed, but I wanted to share a nugget from it in the mean time.
In addition to keeping a list of ingredients and cooking steps, I’m cataloging the recipes using these fields: Recipe Title, Servings, “Healthiness”, and “Taste Awesomeness”
For the last two, I’m using a tool from the Quality world called a “Likert Scale“, where a range of values is assigned to on-off data. So instead of saying “Is it healthy?”, I can say “how healthy is it?” – which allows for better organization, planning, and sorting. That way, I can make sure that I have enough recipes of 2’s and 3’s in the mix so I’m equipped to eat healthy
Here are my scales:
How Awesome (0-3)
0 – delete off list; very not-awesome and not worth keeping
1 – Meh
2 – AWESOME – must. eat. often.
3 – MIND BLOWN – deserves a recipe honeymoon (eat for every meal for a while)
How Healthy (0-3)
0 – little to no nutritional value (i.e. desserts)
1 – some nutritional value, but either is high in sodium, fat, or sugar
2 – average nutritional value
3 – has superfoods, low sodium, and low in added bad fat
I’m thinking that zero’s in healthiness are going to be mainly desserts and zero’s in awesomeness are going to be deleted.
If you’re reading this, and would like a copy of the finished recipe database, leave a message in the comments below, and I’ll hook you up once it’s done.