Greenfield Thinking in a Brownfield World
I call it greenfield thinking. And it’s worth understanding the difference between that and what most of us do every day.
Greenfield vs. Brownfield — What the Terms Actually Mean
In facility development, greenfield means you’re building on undeveloped land. No existing structure to work around. No constraints inherited from the last decision.
Brownfield means you’re working within what already exists. You’re redesigning a kitchen that has to keep running while you fix it. You’re improving a production line that can’t stop. You’re solving a problem while living inside it. I call it open heart surgery if systems or major production areas are impacted.
Most operational improvement work is brownfield by default — because the floor is running, the orders are coming in, and the only thinking available is reactive. That’s necessary. But it is not sufficient.
What Greenfield Thinking Actually Does
A few years ago I was working through a throughput challenge in a just-in-time, wave-based deli operation — where each production wave was tied to a specific truck dispatch time. A delay in one wave didn’t just slow output. It hit a truck. The conventional approach would have been to look at the current setup and ask: what can we improve here?
Instead, I ran a greenfield exercise. The question: if we were designing this operation from scratch — no existing layout, no inherited equipment, no shift structure to protect — what would it actually look like?
Two things happened inside that exercise. First, I landed on a design concept that was genuinely better than anything we’d have reached by tweaking the existing system. Second, buried inside that ideal design were four specific changes we could test, review, and move on immediately — no renovation required. A shelf life study on key SKUs. An evaluation of value-added packaging options. A station redesign. And a conveyor-assisted, package-by-wave consolidation flow. Each one surfaced from the greenfield thinking, not from staring at the existing setup.
That’s the counterintuitive truth: greenfield thinking often produces the most immediately actionable insight. Because when you remove the constraints, you stop defending the current state — and start seeing it clearly.
The Process — How to Actually Run It
This isn’t a brainstorming session. It’s structured thinking with a specific sequence.
Step 1 — Create the space You cannot greenfield-think in five minutes between meetings. Block 60 to 90 minutes of uninterrupted time. Write the question before you start — not “how do we fix the deli,” but “if we were designing the ideal deli operation for our volume and product mix, what would it look like?” The specificity of the question determines the quality of the output.
Step 2 — Think before you look Before you walk the floor, think. Sketch, write, map — whatever your process is. Get the ideas out of your head and onto paper while you are not standing in front of the existing constraints. This is where greenfield lives. The moment you walk into the operation, brownfield thinking pulls you back. Protect this phase. Use sticky notes on a whiteboard or a large window. As 65% of the population are visual learners — and in operations I believe it’s closer to 80% — this kind of exercise will really drive it home for you.
Step 3 — Walk the floor and run the Who / What / When / How / Why After thinking, walk the floor — but differently than you normally would. You’re not watching what’s happening. You’re looking at the gap between what you just designed in your head and what you’re seeing. That gap is your opportunity list. There’s a specific cognitive effect that happens here: the constraints that felt immovable before look different after time spent imagining a world without them. For each gap you identify, work through this sequence: Who is involved in this step? What are they actually doing? When in the sequence does it happen? How are they doing it — specifically? Why are they doing it that way? That last question is where the real work begins. Don’t stop at the first answer.
Applied by Operation Type
The framework is the same. The question and the focus areas shift.
Fresh food manufacturer Greenfield question: If we were designing this production flow specifically for our current — plus the anticipated growth — SKU mix and volume, with no legacy decisions, what would intake to dispatch actually look like? Focus on product flow from receiving to finished goods, staging logic and wave sequencing, labor movement through the space, cold chain touchpoints and dwell times, and equipment placement relative to actual demand — not the original floor plan. Count how many times product changes hands before it reaches its next destination. Every unnecessary touch is a greenfield finding.
Commissary or central kitchen Greenfield question: If we were building this prep kitchen specifically for our actual menu and actual production schedule — what would batch sequencing, station layout, and equipment positioning look like? Focus on batch logic. Would smaller consecutive batches help downstream production steps instead of prepping all volume in step one before passing it to the next station? How much of the current layout serves the equipment rather than the product? That inversion is the most common commissary problem and the hardest one to see from inside it.
Restaurant kitchen or culinary team lead Greenfield question: If we were setting up for this specific service — this menu, this volume, this team — where does everything go and in what order does it move? Focus on mise en place relative to station flow during peak, plating sequence, and pass management. The bottleneck during service is almost never where you think it is when you’re standing still. Just observe what happens when a sous chef jumps on a station that’s in the weeds. What do they do? They clean it, reset it, restore the working flow. Years of experience give them that edge instantly. Help yourself by going through the kind of visualization athletes use before a race or a run. It helped me survive my services as a green 17-year-old apprentice in a Michelin kitchen.
What to Do With What You Find
Sort findings into three buckets. Don’t let the third kill the first.
Implement now: Changes that require no capital, no renovation, no system change. Rearranging flow, adjusting sequence, retraining one step. Greenfield almost always surfaces at least three of these — because most current-state problems are habits, not constraints.
Plan for next cycle: Changes that require a budget decision or a scheduled improvement window. These go on the roadmap with a timeline and an owner. The greenfield gives them the justification and the design direction.
Inform the next build: Changes not feasible in the current facility but essential for any future design, renovation, or expansion. Document them now while the thinking is fresh. This list becomes your specification when the time comes — operators who have it walk into architect conversations as informed clients, not passengers.
The best outcome of a greenfield exercise isn’t the perfect facility that doesn’t exist yet. It’s the five things you can do on Monday that you couldn’t see before you gave yourself the space to imagine a world without the current constraints.
What’s the constraint in your operation that feels most fixed right now? Sometimes the most useful thing you can do is imagine — just for 90 minutes — that the limitation doesn’t exist and work from there.
Drop your comments and questions below. Every response gets read — and may become a future post. If this is useful, share it with someone in your network who’s navigating the same terrain and follow to get future posts directly.
Michael Stark Mistalink Consulting Corp. — For operators, by operators mistalink.com
Subscribe for free at www.mistalink.substack.com to receive new posts and support my work.

