Scaling a product organization often feels like a trade-off between speed and control. As teams grow and portfolios expand, the "noise" of fragmented data and complex dependencies can quickly obscure your strategic vision.
At the enterprise level, the challenge isn’t just making the right decisions, it’s ensuring those decisions are built on a foundation of accurate, real-time data that is visible to every stakeholder.
But we’re committed to providing the governance and flexibility that large-scale organizations need to manage this complexity without losing agility.
"Enterprise product management isn't just about building more features, it’s about managing the massive cognitive load of complex dependencies and data governance," says Spencer Cowley, Product Manager at airfocus by Lucid. "With these updates, we’re removing the manual overhead that plagues large teams. We want to give product leaders a clear, automated view of their strategy while ensuring the data driving those insights is ironclad."
Our latest product updates are designed to bring a new level of integrity, connectivity, and clarity to your product strategy.
can support your team.
Book a demo
Required fields give data integrity at scale
Clean roadmaps depend on clean data, but for large organizations, missing information – like "Strategic Pillar" or "Effort" – often leads to manual follow-ups and skewed reporting. Our new Required fields feature addresses this by helping teams maintain data consistency and integrity across their workspaces.
Enforced governance: When a field is marked as required, users must provide a value before a new item can be created.
Preventing data loss: Once a value is set for a required field, it cannot be removed or cleared, only replaced with another valid value.
Workspace & team-level control: Admins can set fields as required at the workspace level or use team fields to ensure consistency universally across multiple workspaces.
Visual indicators: Required fields are clearly marked with an asterisk (*), and any existing items missing values will trigger a warning banner to alert users.
This level of governance ensures that as you move toward advanced portfolio management, your data is always "boardroom ready" without the need for constant manual cleanup.
2. Milestones revamped
Milestones have historically been a critical coordination mechanism, but they often felt disconnected from the actual work. Milestones are now a first-class field type, combining the flexibility of a select field with the time awareness of a date.
Linking work to delivery: Unlike old milestones that were purely decorative, you can now link items directly to milestones, ensuring your timeline reflects real execution.
Customizable & differentiated: Each milestone is an option that can include a title, description, date, color, and icon . This allows teams to visually distinguish between company-level milestones, beta releases, or internal checkpoints .
Portfolio-level roll-ups: Milestone fields can be converted into team fields, allowing one set of milestones to be reused across multiple workspaces. Updates flow automatically, eliminating manual duplication and providing leadership with a reliable source of truth.
Jira fix version sync: Milestones can now sync bidirectionally with Jira Fix Versions, keeping your high-level strategy and delivery systems in lockstep.
3. Two-way dependency mapping for Jira
For many enterprise teams, Jira is the engine room of execution. To bridge the gap between "what we're building" and "how we're building it," we’ve launched bidirectional dependency sync for Jira.
Single source of truth: You can now map item links (like "blocks" or "relates to") between Jira and airfocus so that blockers and relationships are visible in both tools simultaneously.
Flexible configuration: You can map multiple Jira link types to a single airfocus link type and choose whether the sync should be one-way or two-way to fit your specific workflow.
Reduced manual effort: This eliminates the need for teams to manually recreate dependency relationships across tools, reducing the risk of critical blockers being missed on roadmaps.
4. Coming soon: Custom dependency types
No two organizations manage relationships exactly the same way. While standard dependencies like "Blocks" are helpful, enterprise teams often have unique relationship structures that require more nuance.
Adapt to your process: Instead of a preset list, airfocus now supports custom dependency types. This allows you to create and manage relationship types that match your organization’s unique terminology and needs.
Future-proofing: As we continue to build out more advanced integrations, these custom types will ensure airfocus adapts to your existing workflows, not the other way around.
What this means for enterprise product teams
“We’re committed to serving larger, more complex product teams, and we recognize that at the enterprise level, the challenges are different: you aren't just managing a product, you're managing a complex web of dependencies, fragmented data, and diverse stakeholders,” says Spencer Cowley, Product Manager, airfocus by Lucid.
These features are more than just incremental updates – they are the building blocks of an enterprise-grade command center. For product leaders, they provide a reliable roll-up of work without forcing a rigid process. For product ops, they offer standardization through field-based governance.
What’s next?
We are continuing to double down on these capabilities. On our immediate roadmap:
Enforcing required fields via our developer API.
Expanding 2-way hierarchy sync (Parent/Child) for Jira so your structures mirror each other perfectly.
Enhanced integration syncing for Azure DevOps.
Ready to bring more clarity to your enterprise team?
Log in to your airfocus workspace to set up your first Required Field.
Emma-Lily Pendleton
Read also
Experience the new way of doing product management
Experience the new way of doing product management