Data Warehouse

The data centralization project I worked on at BCT Limited was designed to bring all of the company’s scattered data sources into one system. Before this, teams were storing and tracking information in different places — spreadsheets, emails, and separate tools — which made reporting slow and sometimes inaccurate.

The centralized system acted as a data warehouse where all operational and business data could be collected, organized, and accessed from one place. It was built to support things like:

1. Finance and accounting data – so reporting and audits were easier.
2. HR and employee records – tied in with existing systems like the HR ERP.
3. Operations data – tracking day-to-day activities across teams.
4. Client and project data – making it easier to monitor performance and deliverables.

My role was to design an interface that made this complexity simple for the end users. I focused on clear navigation, easy search and filtering, and dashboards that gave managers quick insights instead of raw data dumps.

The result was faster reporting, less duplication, and better decision-making since everyone was working from a single source of truth.

I led product design and strategy for the data warehouse interface, defined how people find and read data, and ran user acceptance testing with the teams who rely on it.

Every team had its own version of the truth. Finance numbers sat in one spreadsheet, HR data in another system, and project figures in someone's inbox. Producing a single report meant collecting files from several people and reconciling them by hand, and nobody was sure which copy was current.

A warehouse holds a lot of data, but most people only need a small slice of it. I interviewed people from finance, HR and operations about the questions they ask every week, and designed around those questions rather than around the database.

1. Answers before tables – dashboards lead with the figures managers ask for most.
2. Search and filters first – anything should be reachable in a few keystrokes.
3. Consistent across domains – finance, HR, operations and projects share one layout and one set of patterns.
4. Trustworthy – every figure shows where it came from and when it was last updated.

Reporting is faster, duplicated data is shrinking, and decisions now start from the same numbers across teams. The project is ongoing.