Dependencies are things that occur in succession. One thing happens, then another thing can happen. Ideally, on a kanban, the value stream will visualize these transitions. For a value stream like this:Analysis -> Creation -> Refinement -> Launchrefinement is dependent on both analysis and creation.That neatly takes care of dependencies, but in our Personal Kanban we really don't want to have to come up with new value streams for every little project we are doing. So we need to come up with ways to visualize dependencies that will let us maintain a simple value stream.So let's look at a few ways we can do that. As always, these are suggestions and we'd love to see how other people work this out.Task NotationWe can simply notate tasks with where they lie in a stream of pre-requisites. Noting what comes before can help us not prematurely pull a task, letting us know what comes next can help us raise that next task in priority ones it's antecedent task is completed.Scheduled EscalationSometimes tasks become relevant on or around a specific date. What we can do is place tasks that need escalation on a certain date on an actual calendar. When that date comes, take the task off the calendar and place it in backlog. If is has a due date, be sure to note that date on the sticky.Sticky StacksTasks that neatly follow one another can simply stack. When a task is pulled, its next task is seen in the backlog. Sticky stacks can also nicely visualize a project without taking up too much space.--So that's it. Some quick ways to deal with dependencies outside the value stream. Of course, do look in Design Patterns to see if you can find ways to deal more elegantly with specific projects.