Portfolio × monday dev – Hybrid Portfolio for Business & Engineering
Monday.com
Multi-board epic selection: a focused modal that allows users to pull epics from different boards into one Agile project without overwhelming them.
Drag-and-drop status mapping: users match labels from their epics board to the default statuses in the portfolio template.
Overview
Portfolio × monday dev is a hybrid portfolio project I led and designed to bridge the gap between business and engineering teams at scale.
It was the first-ever multi-product collaboration at monday.com, designed to unify Agile and Waterfall projects from monday dev into a single portfolio view within the Work Management platform.
By surfacing development epics directly inside Work Management portfolios, the feature creates a single source of truth where leaders can see how engineering work tracks against go-to-market plans and strategic business goals.
This was a highly strategic, end-to-end project. I led the design process across multiple teams and products, orchestrating collaboration between PMs, developers, and designers from different groups while balancing complex technical constraints with a clear, approachable user experience.
the first-ever multi-product collaboration at monday.com, setting a new pattern for how products are designed across products.
More about the project can be read from desktop
Portfolio × monday dev – Hybrid Portfolio for Business & Engineering
Monday.com
Multi-board epic selection: a focused modal that allows users to pull epics from different boards into one Agile project without overwhelming them.
Drag-and-drop status mapping: users match labels from their epics board to the default statuses in the portfolio template.
Overview
Portfolio × monday dev is a hybrid portfolio project I led and designed to bridge the gap between business and engineering teams at scale.
It was the first-ever multi-product collaboration at monday.com, designed to unify Agile and Waterfall projects from monday dev into a single portfolio view within the Work Management platform.
By surfacing development epics directly inside Work Management portfolios, the feature creates a single source of truth where leaders can see how engineering work tracks against go-to-market plans and strategic business goals.
This was a highly strategic, end-to-end project. I led the design process across multiple teams and products, orchestrating collaboration between PMs, developers, and designers from different groups while balancing complex technical constraints with a clear, approachable user experience.
the first-ever multi-product collaboration at monday.com, setting a new pattern for how products are designed across products.
The Vision
Leaders across Enterprise accounts were forced to “guess” how engineering work mapped to business initiatives. Portfolio and dev lived in separate worlds:
- Business stakeholders tracked initiatives, timelines, and owners in Work Management
- Engineering teams worked in dev boards with their own hierarchy and Agile structures
- There was no easy way to see both sides side-by-side, or to understand progress at a glance
The vision for Portfolio × monday dev was to eliminate that guesswork:
Put business projects and dev epics in the same place, and give leaders a clear “battery status” of progress across the entire organization.
The Solution
In the alpha and beta, I intentionally designed the feature to support epics from a single board. That constraint helped de-risk the first iteration, fit early technical limitations, and validate the core “hybrid portfolio” concept with users.
Based on what I learned from moderated and unmoderated user interviews with Enterprise customers, and in ongoing collaboration with engineering around technical capabilities, I then evolved the design into a more robust system that can:
Handle multiple epic boards per project.
Support templates of complex, cross-team portfolios.
The Collaboration
Because this was the first multi-product collaboration of its kind, the work required:
- Aligning cross-product design teams around a shared mental model of “hybrid portfolio”
- Navigating complex tech constraints between the Portfolio product and monday dev’s Agile structures
- Creating a flow and UI that felt natural to both business users and engineering teams
I drove this collaboration by:
- Running highly organized workflows with developers and designers from multiple groups
- Writing detailed meeting summaries, decisions, and open questions to keep everyone aligned
- Initiating a user interview workshop to sharpen research insights and ground decisions in real Enterprise use cases
Key Design Decisions
Cross-product mental model
I designed the Agile project to live in one product (monday dev) and appear inside a portfolio in another (Work Management), so it feels like a single connected system rather than two separate products.
Two personas, one shared view
The experience needed to work simultaneously for technical users (developers, team leads) and business users (portfolio managers, directors). The UI exposes just enough “dev reality” for business stakeholders to make decisions, while still giving technical users the depth they need, all within the same view.
Design patterns for cross-product flows
Creating an Agile project in monday dev and inserting it into a portfolio introduced complexity around seats, permissions, and data ownership. I designed an experience that translates cleanly between products, so the flow feels predictable and safe. These patterns were later adopted by other teams as a standard for multi-product flows and for scenarios where users need to reconcile different terms and concepts, preserving user trust and learnability.
Information architecture by expertise
I deliberately separated and grouped information based on who needs it and when: structural configuration and board selection are oriented around the dev persona, while high-level status, ownership, and risk are surfaced for portfolio managers. This prevented the UI from becoming a “kitchen sink” and helped each persona quickly find what is relevant to their role.
Scalable interaction patterns
Many of the interaction patterns I introduced here have since been reused by other products and features. Several aspects of this work have been registered as design patents, reinforcing the robustness and reusability of the design.