Screen 4.4: Signals Library
The foundation of your knowledge hierarchy. Signals are discrete observations that, when patterns emerge, become the basis for Principles and Frameworks. Three approaches: grid browse (A), connected graph (B), or manual builder (C).
Your signals library.
Discrete observations that form the foundation of your knowledge. When patterns emerge from signals, they become Principles and Frameworks.
8
Signals
82
Total Uses
The Reduction Test
“If you can remove it and it still works, it wasn't essential.”
The Reduction Test is a design evaluation method where you systematically remove elements from a design until it breaks. What remains after everything non-essential is stripped away is the core of your design.
Simple Isn't Boring
“Simple means you've done the work to find what's essential.”
Simplicity in design is not the absence of complexity — it's the result of ruthless editing. When clients say something is "too simple," what they're really saying is they don't trust it yet. Your job is to help them see the work that went into the simplicity.
The Stamp Test
“Does it work at one inch?”
A logo needs to work at every size, from billboard to business card. The Stamp Test is simple: shrink your logo to one inch. If the essential elements are still recognizable, it passes. If details become muddy or disappear, simplify further.
The Sharpie Method
“Thick markers force commitment.”
Using thick markers like Sharpies on cheap paper forces you to commit to bold strokes. You can't fiddle, you can't be precious. Every mark matters. This constraint breeds creativity and helps you explore ideas quickly without getting lost in details.
The 50-Sketch Method
“Quantity leads to quality.”
Before you start refining, you need options. The 50-Sketch Method forces you to generate 50 rough concepts before evaluating any of them. The first 10 will be obvious. The next 20 will push you. The final 20 is where the magic happens.
Finding the REAL Problem
“Clients think they need a logo. They need a solution.”
When a client says they need a logo, that's rarely the actual problem. The real problem is usually about perception, differentiation, or communication. Your job is to dig past the stated request to understand what they're actually trying to solve.
Field Notes Origin Story
“I didn't have a business plan. I had a question.”
Field Notes started from a simple observation: pocket notebooks looked the same for 100 years. I asked: what would a pocket notebook look like if it was designed by someone who actually uses them? No market research, no business plan — just a designer solving his own problem.
Scope Changes, Rate Doesn't
“I can reduce the scope, not the rate.”
Your rate reflects your value, not the project size. When clients push back on budget, offer to reduce scope — fewer deliverables, simpler solution. But never lower your rate. The moment you do, you've told them your original value was a lie.
Version A Design Notes:
- Grid view with search and type filters
- Card-based browsing of signals
- Detailed view shows full signal structure
- Pros: Visual, easy to scan
- Cons: Less efficient for large libraries
- NEW: Staggered fade animation (v0 pattern)