01 · Purpose and the right starting question
Purpose and the right starting question
Analogy brainstorming generates options by transferring a useful relationship from one setting to another. A warehouse team might study how a restaurant releases meals together, how an airport separates departure gates, or how a hospital identifies patients. The valuable transfer is the mechanism: synchronization, separation, or identity checking. Copying the visible equipment without understanding that mechanism usually produces expensive decoration rather than improvement.
Use this tool when a team repeatedly proposes familiar fixes, such as more staff or more reminders, despite a well-defined problem. It belongs before solution selection. The prerequisite is enough causal understanding to name the function that needs improvement. “Make dispatch faster” is too broad. “Make the carrier assignment visible before cartons enter staging” gives people something concrete to transfer. Analogy brainstorming expands the choice set; it does not validate a cause or establish that an imported practice will work.
02 · Prepare the comparison deliberately
Prepare the comparison deliberately
Fictional Northbank Dispatch ships 1,200 cartons each weekday. A review of 100 late cartons assigns each to one primary observed delay category: 45 unclear carrier assignments, 35 cartons awaiting label reprints, and 20 delayed by late order release. These categories describe the investigation sample, not population probabilities. The team focuses on unclear assignments because the warehouse can change that mechanism locally without changing customer order timing.
The facilitator invites a dispatcher, picker, transport coordinator, systems analyst, and safety representative. Before introducing outside examples, they write the current sequence: print label, stage carton, find carrier, move carton again. They distinguish the fixed constraint—carrier identity must remain accurate—from habits that can change, such as when the carrier is assigned. A list of constraints prevents a creative session from recommending an attractive practice that violates traceability, walking clearances, or the carrier collection agreement.
03 · Move from source mechanism to warehouse concept
Move from source mechanism to warehouse concept
First, describe a source system without proposing the warehouse solution. At an airport, a gate assignment connects a passenger, a departure, a place, and a time; the assignment can change, but changes are communicated explicitly. Second, extract the relationship: make the destination visible before the movement starts. Third, translate that relationship into the warehouse: assign a carrier lane when the dispatch record is created and include the lane in the carton label. Fourth, identify the mismatch: cartons cannot read a departure board, and label changes can leave stale information physically attached.
The mismatch generates another concept: the lane barcode must agree with the carton record before loading is released. The team records each idea with its source mechanism, intended causal link, assumptions, and possible failure. This sequence matters because it separates imaginative association from engineering. A source system may inspire several designs, and those designs may require different controls even though they share an analogy.
04 · Worked example: three transfers, three decisions
Worked example: three transfers, three decisions
The restaurant analogy suggests releasing complete orders rather than sending every carton independently. Northbank considers an order-completion signal. It could reduce partial orders at the dock, but waiting for a missing carton might delay otherwise ready shipments. The team retains it for multi-carton orders and excludes single-carton orders from that design. The airport analogy suggests preassigned carrier lanes and an explicit lane-change signal. The hospital identity analogy suggests a positive identity check immediately before loading, rather than relying on carton appearance.
These become three distinct concepts: order completion release, early lane assignment, and carton-to-lane scan confirmation. The team combines the last two because early assignment prevents searching while scan confirmation catches stale assignments. It keeps the first concept separate because its effect depends on order composition. Combining every creative idea into one large pilot would make it difficult to understand what helped and would create unnecessary operational disruption.
05 · Make the candidate measurable
Make the candidate measurable
For the lane concept, Northbank specifies a proposed change from 90 seconds of average carrier-search time per affected carton to 30 seconds. This is a hypothesis, not an observed benefit. If 180 cartons per day currently require that search, the hypothesized release is 180 × 60 seconds = 10,800 seconds, or three hours of capacity daily. Three hours of capacity does not automatically mean three hours of payroll savings; dispatch staff might instead spend the time clearing the collection queue.
A small comparison will measure search time, wrong-lane placement, label changes, and total order-to-loading time. The team also measures scan interruptions because the new check could add delay. It proposes testing early assignment on one carrier with a similar untreated carrier as context, while recording mix and collection timing. The analogy has now produced an operationally specific candidate whose mechanism and disadvantages can be challenged.
06 · Interpretation, weaknesses, and advanced use
Interpretation, weaknesses, and advanced use
A weak analogy says “airports use screens, so buy screens.” A strong analogy says “airports expose destination and change status before movement; we will test earlier carrier assignment with explicit revision handling.” The distinction is the chain from problem to mechanism to local design. Creative confidence should never replace evidence about software response, label reliability, operator workload, or walking routes.
Advanced teams deliberately use a near analogy and a distant analogy. A parcel hub gives familiar operational constraints; a medication handoff highlights identity failures that familiarity can hide. They compare where each transfer breaks and design controls for the breaks. Separate a prevention concept from a detection concept so the pilot can evaluate both. Record rejected analogies as well as accepted ones, including why they failed. This keeps an evocative story from returning later as an unsupported management mandate.
07 · Operating conditions and evidence
Operating conditions and evidence
The analogy record should also name the conditions needed for transfer. Northbank’s airport-inspired destination signal assumes an assignment exists early enough to be useful, the lane identifier remains legible, and a revision reaches the operator before loading. If transport cannot assign a carrier until late in the day, a better board cannot fix that dependency. The team must change assignment timing or restrict the design to orders whose carrier is known. This conditional logic is the reason to keep the mechanism beside the idea.
A useful advanced review asks what the source system sacrifices. Airports tolerate a passenger waiting at a gate; the warehouse may lack enough lane space for an early-release buffer. Restaurants may hold a completed item to synchronize an order; some warehouse shipments have a strict cutoff that makes holding unacceptable. Examining these sacrifices prevents a superficially successful transfer from moving cost or delay elsewhere. The final concept should explain both the relationship being borrowed and the trade-off being rejected.
08 · Decision record and next step
Decision record and next step
The decision record finishes with the smallest useful test. Northbank does not need to reproduce an airport control center to test earlier destination visibility. It needs a reliable assignment, a clear lane signal, and a response to change. This minimum concept makes the mechanism easier to observe and reduces the chance that an expensive bundle succeeds or fails for reasons the team cannot separate. The team can add presentation features later if evidence shows they are necessary.
Before selecting the test, the facilitator reviews whether every proposed feature has a purpose. A large display may be useful for supervisors but unnecessary for a dispatcher whose label already contains the current lane. A second scan may be necessary at loading but redundant at printing. Removing unnecessary features is not rejecting creativity; it makes the transferred mechanism clearer and the operating burden smaller. The final analogy output is a set of reasoned candidates with boundaries, not a shopping list.
| Transfer condition | Evidence sought | Decision implication |
|---|---|---|
| Carrier known early | Assignment timestamp precedes staging | Test early assignment only where the dependency exists |
| Destination can change | Reassignment alert reaches the loading role | Include revision handling in the concept |
| Positive identity needed | Carton and lane records can be compared | Retain a verification control at the customer exposure point |
Connections
Related methods and phase use
Placed under Improve because of the outcome it supports. Use the method in other phases when its purpose and assumptions fit the work; the phase list is a guide to selection, not a compulsory sequence.
Sources
Professional foundations and further reading
The explanation and fictional teaching examples are written for LeanTrainingLab. Linked primary sources provide professional foundations; example values and local conventions are stated in the guide. The accepted toolset draws on Six Sigma+Lean Toolset, second edition (Lunau, editor; Springer, 2013). No book text or examples are reproduced here.