I’m currently in the middle of migrating our PMO office from a manual setup over to Monday I like the automations, but I’m hitting a bit of a wall with how to structure our columns to handle non-linear project dependencies. Specifically, I’m struggling with how to visualize ‘conditional’ milestones where Task C only starts if Task A and B meet certain criteria."
To help my team visualize the logic before we build out the boards, I’ve been using the Dependency map from https://www.projectmanagertemplate.com/product-page/dependency-map-timeline. It has the exact data architecture we need, but I’m having trouble ‘translating’ that specific layout into a Monday board without it becoming a cluttered mess of 50+ columns.
Has anyone else managed to recreate a high-level dependency map like this in Monday? Should I be looking at using the ‘Mirror’ column feature more aggressively, or is there a specific app in the marketplace that handles this better? I’d love to hear how others have transitioned from structured templates into a more fluid Monday workspace."
Great question, and this is a very common challenge when moving from structured PMO templates into monday.
The key shift is this: instead of trying to translate the entire dependency map into columns on one board, model the logic across connected boards and let automations handle the conditions.
A few suggestions that tend to work well: 1. Separate structure from logic
Keep your main Project Plan board focused on tasks and milestones with standard columns like Status, Timeline, Dependency, Owner. Avoid adding columns for every conditional rule. That’s usually what causes the “50+ column” problem. 2. Use dependency + status-driven automations for conditions
For something like “Task C starts only if Task A and B meet certain criteria,” you can:
Set Task C as dependent on A and B using the Dependency column.
Use automations such as “When Status changes to X and Dependency tasks are done, change Status to Ready” or similar logic.
If criteria are more complex than “Done,” create a specific status like “Approved” and trigger from that instead.
This keeps the logic in automations rather than visual columns. 3. Consider a two-board architecture for high-level mapping
If you want a clean, high-level dependency map:
Use one board for Milestones or Phases.
Connect it to a detailed Task board.
Mirror only high-level statuses or completion percentages back up.
That gives you a structured “map” view without cluttering your task board. 4. Mirror carefully, not aggressively
Mirror columns are helpful for rollups and visibility, but using them heavily to replicate full logic across boards can quickly get messy. I’d use them for summary fields, not for building conditional logic itself. 5. Marketplace apps
If your dependency logic is highly complex or closer to program-level scheduling, you might explore advanced Gantt or portfolio apps in the marketplace. However, many teams find native dependencies plus well-designed automations are enough once the board structure is simplified.
In short, instead of recreating the template’s exact architecture in columns, think in terms of:
Tasks and milestones as items
Relationships via Dependency and Connect Boards
Conditional logic via automations
Visualization via Gantt or Dashboard widgets
If you’d like hands-on help or want us to walk through this live, you can book a 1:1 paid 60-minute strategy session with our team here: Calendly