In this short post I describe the phenomenon I call “A Place called Something” This scenario often prevents operations managers from gathering the information they need to populate the system for project workload and projections data. Recognizing the signs of the issue is the first step to solving it.

In my latest blog post I reflected on a realization I had as I gradually step back from the pace of my previous duties. Enrolling in a machine-learning course to enhance my grasp of data analytics allowed me to chart a whole new course - retooling.

Every now and then, I remember why I wanted to learn data analytics - to visualize processes that can be otherwise difficult to see. This article highlights a custom visualization to graph all deadlines in the firm in a filterable format.

Creating budgets is an essential step in setting up performance tracking for design projects. There are (at least) three levels to create effective budgets.

What is the one step to get started creating analytics for your own organization? It’s surprisingly simple: start by making lists. To get your database underway, make a list of projects, or a list of assets, or a list of whatever your data tracks. After that, things will likely take on a life of their own.

In a previous post, I introduced the idea that data is an ecosystem of tools that work in concert. In this article I want to describe in more detail the three major phases of the ecosystem: Input, Storage & Reporting.