For what it's worth, to play devil's advocate, I absolutely agree that there are times that projects belong in more than one Program and is something I feel is limiting in WF. For example: A large IT organization could be running dozens (or hundreds) of projects that have dependencies with each other. So, let's say you have one Program (run by the Infrastructure team) that is "Infrastructure Cloud Migration" that is tracking multiple projects for migrating servers, applications, etc. to the cloud. However, there is another Program run by the Application Team, "Digital Customer Platform 2.0" made up of several mini-projects running at the same time. Now, let's say one of the individual projects the organization is doing, "Migration to Exchange Online" is clearly part of the Infrastructure Cloud Migration Program but is also a key component to making the mail functionality of the new Digital Customer Platform 2.0 work, then that project probably should be tracked as part of both Programs. As a stakeholder in either program, I will want to see that progress of that project in my Program's dashboard. Now, the concern (and why WF probably doesn't do this) is that you don't want to double count the financials, but realistically that Exchange project is part of both Programs. Now, I fully acknowledge you can handle this with custom forms as a way to flag some projects to appear on dashboards of Programs they aren't native to with a custom report...but it would still be nice if you could dual home projects. Jason Maust McGuireWoods LLP