Most people seems to think OneDrive settles the document storage needs.
They are wrong in a number of ways.
The most obvious problem is a OneDrive is that when you lose a staff, and end their license, all their documents go with them.
What you need is a central place to put key documents and lists that you company needs beyond a single users. These documents you might want version controlled, assigned with metadata, and searchable.
What you want is Sites which is SharePoint in Office 356. Better yet SharePoint with Delve, allowing your users to see the socially most significant documents in circulation.
Planning a proper Sites configuration is not technically hard but it is a lot of work to create a good Information Architecture, that is a plan of sites and subsets.
Here are some simple rules:
- Regardless of what anyone says the hard limit for supported Sites is 200 GB. So if you have a lot of content to store make many sites.
- Don't rely on your company structure to provide the structure for the sites, rather find out what people need or let teams design they own layout.
- Keep it clean and simple, don't worry too much about colours or new layouts. Spend effort on design of layout and making it easy to use over making it look a certain way.
- Use Wikis, they are easy light weight way to store data.
- Keep pushing users to it, if they have a question don't write an answer when a link in a wiki exists, have the search for it in the wiki. Get users to learn the independent way of looking for things, break the ask first habit.
- Have people who have keeping SharePoint up to date and clean as part of their jobs.
- Find energetic people who want to work with Sharepoint.