An analysis of Mark Hadland's personal dining lens — the reference points, philosophies, and first-hand experiences that ground Dynery's design standards, product principles, and experience architecture. Source material used without direct attribution by request.
What Mark Hadland's personal food blog reveals is not merely a dining perspective — it reveals a founder's authentic theory of dining operating as a lived practice across nearly two decades. Analyzed as a lens for Dynery, it is one of the most practically valuable documents in this project.
The blog's architecture — organized into Dishes, Dining, Travels, Meals, an iteration series, and holiday occasions — is not an arbitrary navigation structure. It is a natural taxonomy of how a person who lives to eat organizes their dining life. Each category maps almost perfectly onto a Dynery product layer: Dishes maps to the Dish Story Archive, Dining maps to the Dining Passport and restaurant identity layer, Travels maps to Dynery Away, Meals maps to the social occasion record, the iteration series maps to the signature dish version history, Holiday maps to the occasion architecture.
The blog is a hand-built version of what Dynery automates. Every post is a Memory Card written manually, uploaded with photographs, organized by category, tagged with names and relationships. The platform Mark is building for himself — with WordPress, personal photography, and years of careful documentation — is exactly what Dynery delivers automatically with every meal, for every guest, at every restaurant in the network.
The pitch to guests is simple: most people who live to eat wish they had what this blog represents. They just don't have the discipline or the time to build it by hand. Dynery builds it with every checkout.
The dining section of the blog is a carefully assembled portfolio of the world's most significant dining experiences. This is not a casual restaurant reviewer's log — it is a deliberate, years-long study of what total experience design looks like at the absolute frontier of the craft.
In the midst of documenting a 5-act, 50-impression, 4–6 hour dining experience at one of the world's most celebrated restaurants, Mark noticed something that most guests would walk past without registering: what the kitchen was using to manage the evening's guest orchestration.
At Alchemist in Copenhagen — a restaurant that delivers up to 50 distinct impressions across five acts and six hours, managing individual guest preferences, dietary requirements, and experiential pacing for every table simultaneously — the operations team uses Trello displayed on a large screen to orchestrate the evening. A basic project management tool. Cards. Lists. The same software used to manage software development sprints and marketing calendars.
This observation is visible in the Alchemist blog post: a photograph of the command center screen shows the Trello board with guest information organized in columns. Most diners would see a kitchen in action. Mark saw the tool running the most ambitious dining experience on earth — and immediately recognized the gap between what the restaurant was trying to do and what it had available to do it with.
This is Dynery's clearest operator pitch, delivered from firsthand observation at the apex of the dining world: if Alchemist is managing 50-impression guest experiences with a project management board, every restaurant in the world is managing their guest experience with tools that were built for something else. Memory. Instinct. OpenTable's reservation fields. A notes app. Toast's table management screen. Trello.
Dynery Ops — the Known Guest Protocol, the pre-arrival intelligence brief, the real-time floor dashboard — is the platform that Alchemist is building with Trello. That's not a marketing claim. It's a firsthand observation from the founder at the world's most operationally complex dining experience.
Pitch application: "The world's most celebrated dining experience — 50 impressions, five acts, six hours — manages its guest orchestration with Trello. If they need what Dynery builds, every restaurant does. The gap between what the best operators want to do for their guests and what they currently have available to do it with is the exact gap Dynery closes."
Dietary preferences, flavor sensitivities, occasion context, group dynamics, beverage preferences, pacing needs, previous visit history — everything required to deliver 50 personalized impressions to a table of four strangers who booked six months ago.
A Trello board on a large screen. Cards organized by table. Lists representing stages of the experience. A project management tool repurposed as a guest intelligence platform by one of the most ambitious kitchens in the world. The gap between the ambition and the tool is visible in a single photograph.
Pre-arrival guest intelligence brief built from the behavioral dining identity — not manually entered preference fields, but a living portrait built from real visits, real dishes, and real occasions. Delivered 48 hours before. Updated with every return visit. The Trello board, built properly.
If Alchemist — with its resources, its reputation, and its obsessive commitment to the guest experience — is using Trello, the average independent restaurant is managing guest intelligence with a combination of memory, habit, and hope. Dynery addresses this gap at every tier of the market.
The HadBurger series — twelve documented iterations of the same dish over four years — is the most revealing single body of work on the blog for understanding how Mark thinks about craft, mastery, and the relationship between a cook and their signature dish.
Twelve versions of the same burger. Each one numbered. Each one documented with photography, notes on what changed, and an implicit judgment about whether the iteration moved toward or away from the ideal. The HadBurger OG through HadBurger XII spans the full arc of a cook's development — not across twelve different dishes, but across twelve attempts at a single dish that refuses to be finished.
This is not a casual interest in hamburgers. This is a philosophical commitment to the idea that a signature dish is a living project — a conversation between the cook and an ideal that recedes as you approach it. Mastery is not the destination; it is the practice.
The exact same philosophy underpins the world's greatest restaurants. Noma's fermentation program was not invented in a season. Alinea's deconstructed dishes evolved across years of iterative experimentation. The kitchen at Alchemist has been developing its 50-impression vocabulary since the restaurant opened in 2015. The difference between the world's best and everyone else is not talent alone — it is the commitment to iteration that the HadBurger series embodies.
The HadBurger principle has a direct and specific implication for how Dynery Academy's Dish Story Archive is designed. A restaurant's signature dish is not a static artifact — it is an evolving practice with a history. The carbonara that has been refined across 20 years carries a richer story than the carbonara executed from a recipe learned last month.
The Archive should accommodate version notation — the ability for an operator to document not just the current expression of a dish but its evolution. How did the recipe change, and why? What did the chef learn between version 3 and version 4? This is the richest possible content for a Heritage Card, and it emerges naturally from how serious cooks already think about their food. The iteration is the story, not just the current state.
The most important thing the blog reveals about Mark Hadland's dining philosophy is not his reference bar or his technique knowledge. It is the relational purpose that underpins the entire project.
The blog's stated purpose — articulated directly in the homepage "about" text — is not to document recipes or review restaurants. It is to create a lasting record for sons Carter and Rhone: a tome of culinary adventures, dishes, people, relationships, places, and experiences that will serve as the legacy of their life together through food, friends, and family. "This is how I love and why I do this."
Carter appears in 41 posts across the blog — the highest-frequency tag on the entire site. The most meaningful entries are not about the food alone. They are about who was at the table. The Alchemist entry includes Carter, Mitch, and Paul. The Villa Crespi entry is for Uncle Sean's 60th birthday. The Sequim entry is a day trip to harvest and cook crab together. The blog's emotional register is always relational — the food is the medium; the relationships are the meaning.
This is Dynery's dining companion architecture and Annual Vintage made deeply personal. The platform is designed to capture exactly what this blog captures — not just what was eaten but who was there, what the occasion meant, and why the memory matters beyond the meal itself. The difference is that Dynery captures it automatically, for every guest, at every restaurant, without requiring the discipline and effort of maintaining a hand-built WordPress site.
One of the most distinctive qualities of the blog is its total absence of hierarchy between registers of dining. The Dungeness crab harvested from Sequim Bay and cooked that afternoon receives the same quality of care and documentation as the Noma Kyoto tasting menu.
World-class restaurants with global reputations, years of intentional experience design, and teams dedicated to the guest experience as a total art form. These experiences set the reference bar for what the pinnacle of the Sphere of Narrative looks like — food, service, environment, and culture operating in complete alignment.
Meals cooked at home, crab harvested from the bay and cooked the same afternoon, a dinner at a friend's kitchen. These experiences are documented with equal reverence — they are not lesser meals. They are the meals that carry the most weight relationally, even if the food is simpler. The Dungeness crab Benedict is listed as a signature dish because it is, genuinely, signature — regardless of where it sits in a restaurant hierarchy.
Seattle restaurants of exceptional quality that occupy neither the apex tier nor the home kitchen tier — beloved neighborhood establishments where the cooking is extraordinary without the trappings of global recognition. These are the restaurants that Dynery is primarily built for, and they receive the same weight in the blog as the Michelin-starred experiences.
Dynery's Sphere of Narrative, Academy curriculum, and Constellation curation must be equally applicable and equally dignifying at every register. A Dungeness crab Benedict served with care and craft at a 20-seat Seattle breakfast spot deserves the same narrative attention as a 50-impression Copenhagen tasting menu. The only criterion is whether intentionality is present. If it is, the story is worth telling.
The dual-register fluency is the clearest guard against Dynery becoming a luxury product. A platform built by someone who holds Noma and a Sequim crab harvest in equal esteem is a platform that can serve every restaurant with genuine respect — not as a concession to market size, but as a reflection of the founder's actual values. The stories worth telling are everywhere. The standard is the same.
There is a completionist, quest-structured dimension to how the dining portfolio is assembled. This is not a passive record of meals eaten — it is an active pursuit with goals, sequences, and the satisfaction of completion.
Completing all three Michelin stars in Copenhagen before leaving the city. Dining at Noma in two countries — the same restaurant's philosophy expressed through two radically different geographic and cultural lenses. The HadBurger in perpetual active development. The Steak au Poivre refined through four numbered versions. These are not random dining choices — they form a practiced dining life with an internal logic of exploration, completion, and return.
Each observation from the founder's dining lens translates directly into a product design principle, a pitch refinement, or a strategic emphasis for Dynery. These are not incremental adjustments — several of them are foundational.
What Cook Cook Eat Eat reveals most clearly is that Dynery is not being built from a theoretical perspective on dining technology. It is being built from a life lived at the table — at the highest levels of culinary ambition globally and at the most humble and personal levels of cooking for family. The platform carries the insights of someone who has eaten at Noma twice and whose most cherished dining memories are of cooking for his sons on Mother's Day.
The Alchemist observation — that the world's most ambitious dining experience runs on Trello — could only come from someone who is simultaneously a deeply engaged diner and a trained experience designer. Nobody else sitting at that table in Copenhagen would have known what they were looking at. Mark knew, because he has spent a decade building the operational intelligence platforms that Alchemist is trying to approximate with a project management board.
The HadBurger principle — that a signature dish is a living project with a version history, not a static recipe — could only come from someone who has been iterating toward their own ideal for four years and counting. The dual-register fluency — treating the Dungeness crab and the Noma tasting menu with equal reverence — could only come from someone who genuinely believes both are worth documenting and worth remembering.
That dual fluency is not a product feature. It is the platform's character. And character is the one thing no competitor can replicate, because character has to be earned — one meal at a time, over years, at tables in Copenhagen and on a shore in Sequim and in a home kitchen on Mother's Day.