Take a source system from one field and document its parts, relationships, failure modes, and success metrics. Then translate each element into your target context, noting mismatches and promising echoes. The map reveals transfer candidates quickly while protecting you from naive one-to-one copying or shallow metaphors.
Combine two partially conflicting ideas to generate emergent structures neither offered alone. Write constraints from both sides, then invent hybrids that respect the strictest limits. This disciplined friction often creates surprising design rules, educational exercises, product experiments, or research hypotheses worth testing with small, reversible trials.
Draft provocative prompts like, How would a mycologist debug this network, or What would a choreographer remove from this onboarding? Route those prompts through your notes, collecting responses. The questions route attention through unexpected corridors, stimulating honest novelty grounded in prior reading rather than random novelty alone.
Each day, capture one insight from outside your domain and write why it matters to a current project. Add one intentional link to an existing note. By week’s end, review the chain and select a micro-experiment you can run within two hours.
Each day, capture one insight from outside your domain and write why it matters to a current project. Add one intentional link to an existing note. By week’s end, review the chain and select a micro-experiment you can run within two hours.
Each day, capture one insight from outside your domain and write why it matters to a current project. Add one intentional link to an existing note. By week’s end, review the chain and select a micro-experiment you can run within two hours.