Analogy
The Garden: Growth Is a System, Not a Heroic Watering
A garden makes delayed, interacting causes visible.
- Drive clears obstacles, commits to the harvest, and acts when delay threatens the outcome.
- Connect attracts participation, shares possibility, and helps people care about the result.
- Sustain tends recurring work through unglamorous days and changing seasons.
- Verify studies soil, light, water, pests, timing, and evidence of what is working.
No amount of one contribution compensates forever for a missing system. Urgent watering cannot repair months of poor soil. Enthusiasm cannot create sunlight. Consistency can preserve the wrong planting. Measurement can document decline without changing it.
The owner lesson
Business outcomes also have conditions, lead times, constraints, and maintenance. Owners often see visible effort and miss the system beneath it.
Ask:
- What outcome are we growing?
- What inputs and conditions does it require?
- Which work is recurring maintenance?
- What early signal predicts trouble?
- Which intervention has a delayed result?
- Who owns each condition?
- What should be pruned or stopped?
Business example
An owner wants more recurring revenue. The system may require customer-fit criteria, reliable delivery, renewal ownership, usage/adoption signals, billing, support capacity, and a feedback loop. Pressuring sales alone may grow commitments faster than roots.
Try this
Draw one outcome as a plant:
- Fruit: customer/business result
- Stem: repeatable operation
- Roots: people, capability, authority, information, technology, budget, vendors
- Water/light: capacity and recurring attention
- Fence: controls and security
- Seeds: experiments and intelligence
- Season plan: continuity and timing
Circle the condition currently supplied by one person only.
BOS links: all seven systems.
Misuse warning: Sustain is not “the gardener,” and Drive is not “the owner.” The analogy maps contributions, not job assignments.