What Pattern Weaving means
The operating mode I keep returning to.
Pattern Weaver is not a job title. It is a description of what actually happens when I work: finding the same structural problem across unrelated domains and building the bridge between them.
This piece is the clearest explanation I have written of how I think.
Part 3 of 5 in the Declared First series, with Retrieval-First AI (/journal/retrieval-first-ai), Declare Your Frame (/journal/declare-your-frame), Àṣà (/atelier/asa), and What I-O Psychology knows about human data that ML doesn't (/journal/io-psychology-and-human-data).
How Tobi actually thinks
This piece explains the cognitive mode behind every case study on this site. If you want to understand how I approach ambiguous problems, this is the place to start.
- Cross-domain pattern recognition
- How structural thinking shows up in product work
- Why this makes me faster on new problem spaces
Structural thinking across domains
The same constraint that appears in consent verification appears in compassion journaling appears in AI retrieval. Pattern Weaving is the practice of noticing that and using it.
- Cross-domain structural mapping
- How to transfer solutions across problem spaces
Finding the same shape in different places
Some people solve problems one at a time. This is about what happens when you notice the same problem keeps showing up with different clothes on.
What drew you here?
This one is personal and intellectual at the same time. Tell me what you are looking for.