/
Data Warehousing

Data Warehousing

Data warehousing is another make work activity that I would lump in with gap analysis.

It’s the idea that there is value somehow in creating a massive database of information pulled from a bunch of different systems.

Why is this a bad idea?

It comes down to lack of clarity as to what problem is being solved. When there isn’t a clear problem being solved then it’s not likely to generate anything of value, the timeline of the project will be unlimited. See boiling the ocean.

Related content

The 80-20 rule
The 80-20 rule
Read with this
Gap analysis (and why some gaps are a good thing)
Gap analysis (and why some gaps are a good thing)
More like this
Successful solutions make user's lives easier, not harder.
Successful solutions make user's lives easier, not harder.
Read with this
Fixing visibility gaps
Fixing visibility gaps
More like this
Why use simple frameworks for debugging your own code versus generalized third party debuggers?
Why use simple frameworks for debugging your own code versus generalized third party debuggers?
Read with this
Fixing visibility gaps - Using Tyson as an example
Fixing visibility gaps - Using Tyson as an example
More like this