Before there was a plan, there was a feeling. A customer interaction that didn't quite work and kept coming back to mind. A category that kept showing up in conversations the shop wasn't having. A service friction that seemed small and turned out to be structural. A visit to a completely different kind of business that lodged somewhere and wouldn't leave. These are seeds — potential starting points that, with attention and time, can grow into something the shop actually becomes.
The first thing to understand about seeds is that they don't announce their value. The idea that will eventually change the service department doesn't arrive fully formed as a service department overhaul. It arrives as a small noticing — a moment where something didn't quite fit, a customer whose experience pointed at something worth examining. At the moment of arrival, it's impossible to accurately assess its potential. It requires time and attention before its true shape becomes visible. Evaluating it too early, before it's had the chance to develop, cuts off most of the possibilities it contains.
Most shop owners are very good at evaluating seeds quickly. The idea comes up, the filter runs it through the existing framework, and a judgment arrives fast: this would work in our shop, or this wouldn't. That speed is the problem. The filter that makes the judgment is the same filter that's been producing the current version of the shop. It can only see the seed in terms of what the shop already is — not in terms of what the shop could become if the seed were given the chance to develop into something neither the owner nor the filter could have predicted.
"At the moment of arrival, it's impossible to accurately assess a seed's potential. Evaluating it too early cuts off most of the possibilities it contains."
The right posture in the seed phase is collection, not evaluation. Walk to the water, cast the line, wait. You cannot control what arrives. You can only be present enough to notice it and receptive enough to hold it without immediately deciding what it means. A seed for a shop change could be a common customer complaint that points at something structural. It could be a societal shift that's reaching the shop's community before it's fully visible in the data. It could be a personal interest of the owner that turns out to have broader relevance than they initially imagined. It could be a simple inconvenience that nobody has thought to treat as solvable.
Collecting seeds is best approached with active awareness and boundless curiosity. It cannot be muscled — you can't force the good ideas to arrive on schedule. But it can be willed, in the sense that the owner who stays genuinely curious, who keeps the questions alive, who moves through the world with the explicit intention of gathering material, tends to accumulate more seeds than the one who has closed the question and is now in execution mode only.
The seed that doesn't get watered cannot reveal its ability to bear fruit. Collect many seeds and then, over time, see which ones still resonate. Sometimes we're too close to them at the moment of collection to recognize their true potential.
Having a specific vision of what a seed will become can be useful later. In the early phase, it cuts off more than it opens. The owner who receives the seed of a new service model and immediately starts evaluating it against the existing constraints — the current staffing, the current floor plan, the current customer base — will find reasons the seed can't grow almost immediately. The constraints are real. They're also not fixed. The shop that exists when the seed has fully developed may be different enough from the current shop that the constraints that seemed decisive were actually negotiable. But you don't get to that version if you abort the process at the first evaluation.
One of the less obvious arguments for collecting widely is what it does to the quality of selection. The shop owner working from a single idea doesn't know whether it's a good idea — not because the idea is necessarily weak, but because there's no context to compare it against. The owner who has been collecting seeds for several months, who has accumulated thirty or forty or fifty potential directions and observations and questions, suddenly has a much richer basis for judgment. Some seeds will have dimmed in that time. Others will have grown more interesting. A few will have begun to connect with each other in ways that suggest something larger. The appropriate seed reveals itself over time, in relationship to the others, in a way it never could have if it had been evaluated in isolation the moment it arrived.
This argues for keeping something — a notebook, a voice memo folder, a document somewhere — that holds the seeds without requiring them to be acted on immediately. Not a to-do list. A collection. The distinction matters. A to-do list creates pressure to evaluate and execute. A collection creates space for seeds to develop, connect, and reveal their potential on their own timeline.
Some seeds will take the shop somewhere it didn't intend to go. This is not a malfunction. It's often the most valuable outcome. The shop that followed a seed about beginner experience and ended up restructuring its entire service communication model didn't plan for that outcome. The seed led there, through a process of development that couldn't have been mapped in advance. Sometimes the purpose of a seed is to propel the shop in a direction that looks nothing like where it started. The work reveals itself as you go. Cultivate the conditions, gather what arrives, water with attention, and trust the process to surface what the shop most needs — even when it isn't what was expected.
"Sometimes the purpose of a seed is to propel the shop in a direction that looks nothing like where it started. The work reveals itself as you go."