Comment by MomsAVoxell
6 hours ago
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...
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.)