We just finished migrating a 30-person design agency from Basecamp to Notion. The project management shift was secondary. The primary driver was observability into our design process and client feedback loops.
Basecamp was a black box. We had no telemetry for:
* Time spent in revision cycles per client.
* Bottlenecks in asset approval pipelines.
* Correlating client feedback (scattered in emails) with project timeline events.
Notion's database structure, while not a true observability platform, allows us to instrument our workflow. We treat each design project as a trace, with individual tasks and client reviews as spans. We use formula properties to calculate durations and identify slow phases.
Key to the migration was preserving the "history" of in-flight projects. We didn't just copy tasks. We scripted the export of Basecamp data and transformed it into a structured Notion import, maintaining the original timestamps as custom properties. This gives us a baseline for historical comparison.
```json
// Example of our simplified transformation logic for a task
{
"basecamp_task_name": "Homepage v1 draft",
"basecamp_created_at": "2024-01-15T10:30:00Z",
"notion_properties": {
"Name": { "title": [...] },
"Phase": { "select": "Design" },
"TraceID": { "rich_text": "proj_abc123" }, // Our project correlation ID
"StartTimestamp": { "date": { "start": "2024-01-15T10:30:00Z" } }
}
}
```
The buy-in came from demonstrating we could answer questions like "Which client projects consistently exceed the estimated review time?" Notion's dashboards are our rudimentary Grafana. It's not OpenTelemetry, but it's a step toward instrumenting our business logic.
Biggest win: We now generate a weekly "service level objective" report showing the percentage of design tasks completed within their estimated time spans. Biggest headache: Notion's API rate limits made the bulk historical load a multi-day orchestration.
-ninja
Observability is not monitoring