The Metropolitan Water District of Southern California (MWD) is a cooperative of fourteen cities, eleven municipal water districts, and one county water authority. MWD transports, treats, and delivers water to 19 million consumers in a 5,200-square-mile service area.
To understand this project I viewed many historical documentaries and took a deep dive into their current site. I also requested the client take me and the team through a new hire training course into what it is that MWD does. With that being said, there was a lot riding on these stakeholder interviews.
After listening to stakeholders and auditing the site, I created a sitemap structure based on what was available. I also changed the content within those buckets.
The document repository search allows users to find documents they need without having to dig through the site.
With the help of the client, I was able to lay down a taxonomy to categorize content within a very robust spreadsheet. This spreadsheet was to guide the development team on the dependencies of this search/content filter.
I wanted users to be able to access the repository at any time while on the site, so the document repository was placed within the utility navigation. Clicking on the repository opened a modal takeover with the filtering system.
Users are able to search for specific documents, but because many times the document titles do not match the file name, they do not appear within internal search results. Filtering and sorting functionality was added.
Though it seems highly unlikely that anyone may be accessing these documents on their mobile devices; per client request, I created a mobile version of the document repository.
Sometimes it is hard to keep track of what people say, and especially when there are a lot. Taking notes and recapping were essential before leaving to make sure I was going in the right direction.
With this project it helped best to tell the client why and how we got to the solution we were presenting.
It was difficult to know what the client wanted. My best approach was to create what I believed the client wanted, run it through the team and then, I would present that to the client. Most times, I knew I would get a lot of feedback, but it gave me a better sense of how to handle the direction of that part of the project.