TEM (Task Command Center) — Multi-Business Task Management

The Problem

Running three concurrent workstreams — a full-time job, a creative agency (Beam Creative), and a digital consultancy (Thompson Digital) — means juggling tasks, deadlines, and time demands across completely separate contexts. Generic task managers don't understand that "high priority" means different things in different businesses, and none of them let you see the total workload across all three at once.

The Approach

Build a personal command center that treats each business as a separate workspace with its own tasks, priorities, and timelines, while providing a unified view across all three. The system enforces the workflow methodology rather than just storing data.

The Tech

The application uses a three-workspace architecture where each workspace (Thompson Digital, Beam Creative, Full-Time) has independent task boards, but the dashboard aggregates everything into a single priority-sorted view.

The deployment follows the same Docker pattern as BCOrderHaus: development uses docker-compose.yml with build: ./backend for hot reload, production uses docker-compose.prod.yml with pre-built images. Docker images are built on the dev machine and shipped via docker save | ssh | load.

The production compose adds health checks that the dev version skips — if the backend doesn't respond to curl http://localhost:3001/health within 30 seconds, Docker marks it unhealthy and can restart it.

The Outcome

All tasks across three businesses are visible in one place. The workspace separation means context switching doesn't create confusion — each business has its own board, its own priorities, and its own view. The unified dashboard surfaces what actually needs attention today, regardless of which business it belongs to.