This is a transcript dump from a conversation with Monday's AI. Perhaps this has been requested, but I couldn't find a search. I feel like this whole process needs to be better implemented, but I digress.
Many project types are deadline-driven rather than start-driven:
- Tradeshows & Events — Everything must be ready by the event date
- Product Launches — Work backward from launch date
- Regulatory Deadlines — Compliance tasks must finish before filing deadline
- Campaign Launches — Marketing materials ready before go-live date
- Construction Projects — Completion date drives the schedule
Currently, monday.com's dependency system only supports forward scheduling (Task A → Task B → Task C). Users need reverse scheduling (Target Date ← Task C ← Task B ← Task A).
## Current Workaround (Complex & Unintuitive)
To achieve reverse scheduling today, users must:
1. Create a target date task (e.g., "Event Date")
2. Use FF (Finish-to-Finish) dependencies with negative lag values
3. Manually set lag values for each task (e.g., -7, -30, -90 days)
4. Understand that "lag" means "days before target" (not intuitive)
5. Manage a separate "Task Duration" column to control timeline spans
6. Click "Update lag" prompts when changing duration values
Problems with this approach:
- Not discoverable — users don't know FF + negative lag achieves this
- Confusing terminology — "Finish-to-Finish" and "lag" aren't intuitive
- Error-prone — easy to use wrong dependency type (FS instead of FF)
- Hard to explain to team members
- Difficult to set up and maintain
## Proposed Solution
### Option 1: "Work Backward From" Dependency Type
Add a new, intuitive dependency type: "Work Backward From" or "Must Finish Before"
How it works:
1. User selects a target date task (e.g., "Event Date")
2. User sets dependency type: "Work Backward From"
3. User enters: "Finish X days before target"
4. System automatically calculates the task's finish date
5. Task duration determines the timeline span
Example:
- Event Date: September 15
- Shipping Date: "Work Backward From" Event Date, finish 7 days before
- Task Duration: 2 days
- Result: Timeline = September 6-8 (finishes Sept 8, 7 days before event)
### Option 2: "Reverse Dependency" Mode
Add a toggle to existing dependencies:
- Forward Mode (current behavior): Task A → Task B
- Reverse Mode (new): Task B ← Task A (work backward from Task A)
When Reverse Mode is enabled:
- Lag values are interpreted as "days before" (no negative numbers needed)
- Timeline calculations work backward from the target
- UI shows clear "← depends on" visual indicator
### Option 3: "Target Date" Column Type
Create a new column type specifically for deadline-driven projects where users set a target date and other tasks reference it with "X days before" offsets.
## User Experience Improvements
Clear Terminology:
- "Must finish before [Task]"
- "X days before [Target Date]"
- "Work backward from [Deadline]"
Visual Indicators:
- Show reverse dependencies with left-pointing arrows (←)
- Highlight the "target date" task that drives the schedule
- Display "X days before [Target]" instead of technical lag values
Simplified Setup:
- One-click "Set as Target Date" button
- Drag-and-drop to create "X days before" relationships
- Auto-suggest common offsets (7, 14, 30, 60, 90 days)
## Benefits
For Users:
✅ Intuitive — Matches how people think about deadline-driven work
✅ Faster setup — No need to understand FF dependencies and negative lag
✅ Fewer errors — Clear terminology reduces misconfiguration
✅ Easier collaboration — Team members understand the schedule at a glance
✅ More flexible — Easy to adjust offsets and see impact immediately
For monday.com:
✅ Competitive advantage — Many PM tools lack native reverse scheduling
✅ Broader use cases — Unlocks event planning, launch management, compliance workflows
✅ Reduced support burden — Users won't need workarounds or support tickets
✅ Template opportunities — Pre-built templates for events, launches, campaigns
## Real-World Use Case
Tradeshow Planning Template
Current setup (complex):
- Event Date task with single date
- 10+ tasks with FF dependencies, negative lag values (-7, -14, -30, -60, -90)
- Separate "Task Duration" column
- Manual "Update lag" prompts
Proposed setup (simple):
- Event Date marked as "Target Date"
- Tasks set to "Finish X days before Event Date"
- Task durations built into timeline
- Everything updates automatically when Event Date changes
Time saved: 15-20 minutes per template setup
Error reduction: 80% fewer misconfigured dependencies
Team adoption: 3x faster onboarding
## Technical Considerations
Backward Compatibility:
- Existing FF + negative lag dependencies continue to work
- No breaking changes to current functionality
- Optional feature — users can continue using forward dependencies
Implementation Approach:
1. UI sugar over existing FF + negative lag (fastest)
2. New dependency type in the backend (most flexible)
3. New column type with built-in reverse logic (most powerful)
Edge Cases to Handle:
- Circular dependencies (A ← B ← A)
- Multiple target dates in one board
- Mixed forward and reverse dependencies
- Timeline conflicts (task calculated before project start)
## Competitive Analysis
Tools with native reverse scheduling:
- Microsoft Project (Finish-to-Start with lead time)
- Smartsheet ("Predecessor" with negative lag, but clearer UI)
- Asana (limited support via custom fields)
monday.com opportunity: Be the first to make reverse scheduling truly intuitive and visual.
## Priority & Impact
Priority: Medium-High
User Impact: High (affects event planners, launch managers, compliance teams)
Frequency: Common use case, currently requires complex workaround
Effort: Medium (UI changes + dependency logic updates)New