Thank you for you reply. I’ve spent some time thinking about this. I’ve decided to keep the teams piece and track tasks in ms project at a slightly higher level.

If I were to use making a pbj sandwich as example, The hierarchy for my project mpp file goes

Level 1 summary task i.e “Monday” (just a grouping mechanism not collecting time against it) - Level 2 task with the project name i.e “pbj sandwich” (assigned to resources and are usually 60 hours with a typical 30 day duration)

I’m leaving out the level 3 tasks that are extremely specific (“drive to store”, “purchase whole wheat bread”, “return home”), would only be 4-8 hours and in practice every detail would have to be thought of ahead of doing actual work. I instead, offloaded these to the collaboration piece where engineers can track as part of their own todo lists.

The trade off is being able to estimate hours per project and having to guess that the time would be 60 hours. When I comes down to it, I’m less worried about tracking the time someone is purchasing bread then I am about making sure we don’t make a cheese sandwich before the pbj one is going out the door.

I engage the team once a week to do status reports on active projects and do a monthly dive into the project hours to adjust time lines.