- Colin Barclay
Whether it is for production or print, the most important thing about a recipe is that it works and works the same every time. Developing a recipe for an end-user includes the component of communication. If a phenomenal recipe isn’t transferred properly it will not yield that same phenomenal product.
The process of transferring a recipe from creator to user is an art form. Professional chefs spend years in kitchens trying to learn from their mentors - trying to understand what they understand. With such a large pool of knowledge it can be difficult to know exactly which pieces of information need to be passed on in a short blip like a recipe.
One very important factor to consider is that the user will always need to improvise in one-way shape or form. They will have a different kind of salt than the developer, they will be missing one ingredient and they will have a 30-year-old oven with a crack in the door and so on. This is great news and a golden opportunity for the developer to properly hand the reigns over to the user. If the right bits of information are passed on with the right language then they will be set up for success. While making this recipe the user truly becomes a chef - this is an entirely different experience from simply following instructions; it is empowering and will likely yield a repeat user.
Regardless of why I am creating a recipe, it is written the way a chef is taught to think. This approach is such a huge part of why restaurant food comes out differently then your average home-cooked meal. Following these recipes step by step take the user through a process that mimics the workflow of a professional kitchen.