Ask HN: Do you also "hoard" notes/links but struggle to turn them into actions?

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

I don't really use "second brain" style notes and links for taking action. I use them to record something I think I might find interesting later, like a bookmark. I tag it and move on and later when enough time has passed, I search the notes by particular tag to see what things I recorded. Usually in that scenario, I actually will be in some mode where I'm trying take action. I'll often be looking for inspiration (say interesting UX design) and will have a ton of saved links and ideas to draw on. But I wouldn't say I'm writing these notes for particular action items.

On the other hand, for work that I do day to day, I do take notes and those are a different type. Those are tied to actions I'm taking and I'll sprinkle them with actual to-do lists that I check off in the notes. I'll link ideas that are related and document things, but for my own projects, I don't try to make it too formal or strict. The notes aren't the goal, they're sort of a scratchpad for day to day operations.

I work on a plugin/platform that makes Obsidian collaborative (relay.md).

Working with other people gives you good habits against hording because you have a sense of the audience and what might be useful to them.

We also support the kanban plugin so that works well to track and share what we're working on.

The only thing that's ever worked is a piece of paper and a pen. Never really look back more than a week.

Not sophisticated, but it moves me forward.

Workflow is key. Things do not just immediately get done - there is a process. Over-generalization is the devil - precise description of targets and goals is key to execution, and soon enough, delivery.

The ability to describe a workflow - or a production pipeline, or whatever you want to call it - but lets say, workflow, is very important in these kinds of automation systems.

You could generalise workflows such that the user is prompted to define and enforce their own flows of work, as a matter of UI/UX interaction, and see if you don't start collecting a lot of successfully executed projects...