Most to-do lists pretend every task is independent. Real work isn't like that. You can't "send the contract" until legal "reviews the draft." You can't "publish the post" until someone "approves the images." When those tasks sit as a flat list, the blocked ones either clutter your view or get started too early. And when a blocker clears, nobody notices the next step is ready.
Vyneron handles this with task dependencies. You chain tasks so a dependent one stays locked until its blockers are done, and it shows up again on its own once it's free.
TL;DR: On any task, hit + Add blocker and pick the task(s) it's waiting on. The dependent task stays locked until all its blockers are completed (finish-to-start). The Flows view shows what's Waiting and what's Ready now. You can also set dependencies in plain language from web chat or Telegram.
The problem dependencies solve
Without dependencies, a blocked task is in a bad spot either way:
- Leave it in your list → it's noise you keep scrolling past.
- Hide it somewhere → you forget it exists, and when the blocker clears, the next step stalls.
A dependency fixes both: the blocked task stays out of your way while it can't be done, and it comes back the instant it can.
How to set a dependency
In the app (+ Add blocker)
Open the task that has to wait, choose + Add blocker, and pick the task it depends on. Need more than one? Add several. The dependent task stays locked until all of them are complete (a logical AND). That's a finish-to-start dependency: start Y when X (and everything else blocking it) is done.
In plain language (chat or Telegram)
You don't have to click around. Tell Vyneron the relationship in natural language, for example "the launch email depends on the landing page going live", and it links the two existing tasks for you. This works the same from the web chat and the Telegram bot, so you can wire up a workflow from your phone.
See what's waiting, and what just opened up
The Flows view is where dependencies pay off. It has two sections:
- ⏳ Waiting: tasks that are still blocked, with what they're waiting on.
- ✅ Ready now: tasks whose blockers just finished, so they're cleared to start.
When you complete a blocker anywhere (including by dragging it to Done on the Kanban board), its dependents move from Waiting to Ready now on their own. You don't have to keep track by hand or wonder "wait, what was that unblocked?"
Honest limits (so you're not surprised)
- Finish-to-start only. Vyneron models "X must finish before Y starts." It doesn't do start-to-start or partial-overlap scheduling. That's deliberate, to keep it simple and predictable.
- Routines aren't chained. Dependencies are for one-off tasks, not recurring routines.
- No push when it unblocks. A freshly unblocked task shows up in Ready now rather than firing a notification, so it waits where you'll look instead of adding to your alert pile.
A simple example
Say you're shipping a small feature:
- Write the copy → Design the screen → Build it → QA → Announce.
- Make each step depend on the one before it (or add the real blockers: QA might depend on both "Build it" and "Write the copy").
- Work from Ready now. As you finish each step, the next one appears, cleared to start.
You stop juggling the order in your head. The list tells you what's actually doable right now.
FAQ
How do I make one task wait until another is finished?
Open the task that has to wait, choose + Add blocker, and pick the task it depends on. It stays locked until that blocker is complete, which is a finish-to-start dependency.
Can a task have more than one blocker?
Yes. Add several and the dependent task stays locked until all of them are complete, a logical AND.
Do I get a notification when a blocked task is ready to start?
No. A freshly unblocked task moves into Ready now in the Flows view instead of firing a notification.
Dependencies are part of a larger June update. See What's New in Vyneron for the full list, or pair this with the Kanban board to move tasks across stages visually. Try it free.