5 ms·
I’d recommend checking out Nick Milo’s ideaverse. The idea is about how to capture in a way that sparks ideas and actions not collects
by kkirsche 8mo ago
I’d recommend checking out Nick Milo’s ideaverse. The idea is about how to capture in a way that sparks ideas and actions not collects
- item007 8mo agoNice reference — Ideaverse is a good reminder that capture should create lift, not just storage. My only nuance is: “sparks ideas” is one slice. A lot of what we stash isn’t inspirational at all — it’s obligations, decisions, constraints, receipts, meeting notes, “I’ll need this later” references. So the goal (for what I’m exploring) isn’t only to spark, but to make the right thing reappear at the right moment: sometimes that’s an idea, sometimes it’s a decision you already made, sometimes it’s the one constraint that prevents rework. Curious: in your own system, what kind of captured info most often pays off later — inspiration/ideas, or concrete reference (decisions, specs, links, context)?