Open any knowledge worker's Google Calendar and you'll find a color scheme — blue for personal, green for Team Alpha, orange for Project Orion, red for the client calendar. It looks organized. The problem is that the organization doesn't answer any useful question. When everything has a color but nothing has meaning, color is just decoration.
Why Project-Based Color Coding Fails
Projects end. New projects start. Priorities shift. Within six months, your color scheme reflects organizational history more than current reality. More critically, project-based colors don't let you ask any aggregate question that matters. "How many hours was I in client meetings this week?" requires manually counting colored blocks. "What percentage of my time was focused work?" is impossible to answer at a glance.
Account-based color coding has the same problem. "Blue = personal Google, green = work Google" tells you the source of the event, not what the event is. A work lunch, a team standup, and a heads-down coding session all show up the same shade of green. They require completely different kinds of time and energy — but the calendar treats them as one thing.
The Right Axis: Life Domains
Color by what the time IS, not where it came from or which project it belongs to. The question to answer with color: what domain of life does this block of time serve?
A four-category domain system works for most people: Work (professional tasks, meetings, deep work), Personal (family, friends, social, errands), Health (exercise, medical, mental health), and Growth (learning, side projects, reading, courses). These categories are stable across years. A work meeting and a personal appointment are both recognizable as "Work" and "Personal" regardless of which project is involved or which Google account owns the event.
What Domain Colors Enable
- →At a glance, you can see if your week is all one color (imbalance alert)
- →You can ask "what % was Health this week?" — a question with a real answer
- →You can notice if Personal time has gone missing for two weeks in a row
- →You can set targets per domain and measure against them
- →The colors remain meaningful in a year because the domains don't change
Setting Up the Four-Category System
You don't need to re-categorize every event immediately. Start with this week. As you add new events, assign a domain. For existing recurring events, spend 15 minutes assigning them once — they'll inherit the category automatically going forward. The system pays off after two to three weeks when you have enough data to see actual ratios.
Colors Become Analytics
This is the shift: colors stop being a way to distinguish events visually and start being a data input. Once every event has a domain, you can ask week-over-week questions about where your time actually goes. Tempo goes one step further: SIGNAL watches your domain ratios and alerts you when a category you care about — Health, Growth, Personal — drops below a threshold you set. You define what matters. The system tells you when it's slipping.