I have a system with four objects in it. They are projects, documents, tasks, and people.
A project has children and they are tasks, documents and people which in turn are siblings.
But the problem arises because some use cases mean that sometimes tasks become children of documents. Imagine a big floor plan where there are multiple broken pipes and each broken pipe is a different task.
I have a wireframe that deals with the first use case easily enough ie when tasks, docs, and people are all children of the project and it looks like this:
But how do I adapt my interface so that when use cases dictate that tasks are children of a document it doesn't mess everything up. I'm thinking breaking the implied relationship of the top navigation would be a good start....