Strongly agree. I think the biggest leverage is forcing explicit targets + a small, user-defined workflow, otherwise automation becomes vague and noisy.

One direction I’m exploring is a constrained “active projects” list (only a few at a time) plus lightweight workflow templates, so the system can map incoming info to a specific stage/next-step rather than spraying suggestions.

If you had to pick, what’s the minimum workflow schema that’s still useful: stages (e.g. research/draft/review), clear Definition of Done, or explicit next-action ownership? (If helpful, I wrote up the idea in my HN profile/bio.)