Hi Albert, I ran into this for a long time as well. I never found a clean answer to it but I have noticed overtime things have gotten better. To my understanding our system team and WF administrators moved us to different servers for our instance of the application. There has been a large cleanup of old or bad data in the system that seems to have helped (I found a program that had several projects under it with almost 15K in tasks that had no activity on them so that went away). Overall though, it has been my experience with larger projects with lots of data that I've had slow down. The ways I've gotten around that have included: - Check your filters, views, and groupings for ways to see less data on the screen (this isn't a bad idea anyway even without slowness to focus work for resources on a project, maybe a 2-3 week view or by who's assigned to what.. that kind of deal) - In that same vein of filtering and finding ways to see less, I do a lot of parent / child tasks so that I can quickly roll things up on my projects. I'll go into the parent task and then look at the Subtasks tab / link so that I can see just the specific items related to the parent - If you have a lot of completed tasks, I've had to do things like archiving them into an "archive project" just to get the data out. Part of me isn't a fan of this as historical data on the project isn't there but speed being the key I had to consider something (at the end of the project I move it back to the main project so that all the data is one place). I've only done that though for projects that were in the 1000's of tasks and usually when 2/3's of the tasks remain open. One can argue this into phases of a project to "clear the decks" so that phase 1 was everything that is already done and then phase 2 is what's left if people have a hard time with having to create a new project physically in your organization. - As you mentioned, probably the best path along with really utilizing views / filters / groupings like crazy is to chunk out the work into smaller projects. For my opinion, this goes more so into the philosophy of WF anyway of agile concepts where you are doing smaller projects that build to produce something towards a program of effort. You can work with smaller teams and smaller amounts of work at a time. It's less overwhelming and you can build momentum to where you are stealing victory from the clutches of defeat instead of the other way around. You could also build custom reports to get snapshots of project work but the project module with views / filters / groupings is doing this anyway. You can also build out dashboards if you're going the report route and put filtering which can be nice and I do on projects to show what's late, what's starting, what's due, and what got done (it may be an outdated dashboard on my end as there is better agile views now too that I'm going to try out this year on my projects). The new experience of WF overall is faster (as far as I can tell anyway) for larger projects. Check with your WF admins to see if this is something you have access to. Our organization along with others has been testing it so I was able to give it a PM view of things to see how it runs and overall I like it better. I'm definitely interested to see what things you try so that I can use them as well :) Tim Greek IEHP
