To Folder or Not to Folder, That is the Question
Since the introduction of file shares, we have become creatures of habit. We create folders, sub-folders, sub-sub-folders, sub-sub-sub-folders, and store all of our project documents in these folders—meeting notes, requirements documents, test procedures, customer intel—you name it. When someone asks us for a document, we sometimes know where it is, but most times we don't.
Search for it? Yeah, that’s done by hand. Open a folder and look—not there. Open another folder—nope, not there either. So we keep looking…and wasting time…
For many of us, file shares have been replaced by SharePoint. We are told to use SharePoint to help us manage our documents, to collaborate with our teams, to enable sharing of documents regardless of location, and the first thing we do is…you guessed it…create a folder. And so the power of SharePoint becomes limited by our habit, and we complain that SharePoint makes our jobs harder. I’m here to tell you that there is a better way!
SharePoint allows us to create “Views” of documents. Views are not a new feature, but we’re constantly surprised by the number of SharePoint users who don’t know how to use them—or don’t know that they exist.
Need to find project requirements documents? Not a problem. Want to review all meeting minutes? Got that in a second. How is this done? By creating a View that uses metadata, filtering, sorting and grouping. The filtering, sorting, and grouping is easy. We’ve done this all of our lives. The metadata? That requires planning.
In this example, I have documents of several types: requirements, notes, and procedures. I can create a column in my library called Document Type and add these types as the values for this column. When I upload a document to the library, I choose one of the types (the metadata), which categorizes the document.
Now that my documents have been categorized, I can filter, sort, and group them using Views of these documents to meet my needs. I can create an All Requirements view that filters the library so that only documents tagged as requirements are visible. I can create an All Documents view that groups the documents by category (requirements, notes, and procedures) and can choose whether to collapse or expand the group to either hide or show the documents when the View is opened.
The possibilities provided by Views are endless…as are the opportunities to find your documents without digging through multiple levels of folders and wasting valuable time.