Scoping Beyond the Brief
- Rebecca Abernathy
- Jun 1
- 4 min read
Updated: Jun 2
How planning a refresh of a portable garden cart at Lake Roland park became a lesson in systems thinking
There’s a particular kind of project that looks simple on the surface but reveals its complexity the moment you stop and look more closely. The Lake Roland Nature Center garden cart was one of those projects.
The original ask was modest: the cart needed a refresh. It would be good if it could be used for programming. It would be nice if it helped feed the reptiles and amphibians in the center’s care.
A straightforward scope. An achievable deliverable. Easy to say yes to and move on.
I didn't move on. I started asking questions.
System-Focused Investment Assessment
Step 1: Understand the task
Before making any planting decisions, I inventoried the system the cart existed within.
Physical constraints first: the cart was 57 inches long, 31 inches wide, and five inches deep — shallower than ideal for many perennial plants, but workable with the right soil composition and a few nested containers for deeper-rooted species. It sat on wheels, which meant it could be re-positioned for sun or shade. It lived on the deck outside the nature center, in a high-foot-traffic area.
Operational constraints next: what programs did the nature center already run? What materials did those programs require? What was the staff capacity for ongoing maintenance? What season were we in, and what would the cart's state be in six months?
What the inventory revealed was a gap — not in the cart itself, but in its relationship to the system around it. A 12-square-foot container in a visible, high-traffic location, with no connection to the programming happening thirty feet away inside the building.
Constraint mapping isn't just about knowing what you can't do. It's about locating where the leverage is.
Step 2: Understand the task cadence
The cart had been replanted annually. That cadence wasn't a deliberate choice; it was a default — the path of least resistance in a resource-constrained organization.
The question I brought to it: what happens to the return on this investment if we change how often we run the cycle…without changing the cost?
The answer was significant. A seasonal rotation— spring ephemerals giving way to summer pollinators giving way to fall dye plants— yields four distinct program contexts from the same planting investment. The plants are perennials that return on their own. The “rotation” is mostly a matter of emphasis, sequencing, and signage.
Same budget. Significantly more programming surface. More seasonal variety for visitors and participants. More flexibility for staff to connect the cart to whatever program they're running in a given quarter.
This question — is the current cadence intentional, or is it just what evolved? — is one I find useful in almost every operational context. The answer is usually revealing.
Step 3: Understand the system the task runs within
The third question addressed a different kind of opportunity.
The cart was an active educational tool when a program was running. Between programs, it was inert. No interpretation. No invitation. No connection to what the nature center offered or how a visitor might get involved.
The question: what if it worked all the time?
That question produced the signage system: three printed signs mounted in weatherproof holders on the cart's exterior. A permanent welcome sign explaining native plants and their ecological role. A seasonal "what's growing now" sign that rotates with the planting. A programs sign with a QR code linking directly to registration.
A passive object became a passive engagement tool. A visitor who happened to walk past on a weekday afternoon could now read, understand, and connect — without a staff member present, without a program scheduled, without any additional operating cost.
The sign that points someone to registration is a step in a conversion funnel. In this context, it's a $20 weatherproof frame and a QR code. The principle scales.
What this produced — and what it's designed to prove
The project deliverables — program guide, educational signage, capstone presentation — were built with a specific constraint in mind: this system has to work without me.
A solution that requires its designer to function isn't a solution. It's a dependency. I will continue working on this project — I need the hours for my master naturalist certification — but everything in this project was documented, templated, and handed off to facilitate support and use by fractional staff and volunteers.
Projected outcomes are quantifiable: visitor engagement with signage (visitor survey), QR-to-registration conversion (analytics), program variety by season (activity log). A measurement baseline will be established when the cart goes live in spring 2027.
The garden cart is a small system. But the approach that produced it is not small — and not domain-specific. Read the constraints. Challenge the cadence. Expand the system's surface area. Build for the people who come after you.
That's the work, whatever the context.
Comments