Workspaces: Team Goals Without Losing Personal Focus

Every team tool makes the same trade-off: you get collaboration, but you lose your personal space. Your private goals, journal entries, and daily reflections become visible to everyone. Or worse, you end up using two separate tools — one for yourself, one for the team — and nothing connects.

Workspaces solve this differently. Rather than splitting your life across two tools — or two containers inside one tool — everything lives in a workspace, and each individual record decides whether the team can see it. Your team's objectives and your private side project sit in the same system. Only one of them is visible to anyone else.

The Problem with Team Tools

Most productivity tools fall into one of two camps:

Team-first tools (Asana, Linear, ClickUp) assume everything is shared by default. Your personal tasks, notes, and goals live alongside team work. There's no private space that's truly yours.

Personal-first tools (Todoist, Sunsama) are great for individual productivity but bolt on sharing as an afterthought. Shared projects feel disconnected from the rest of your system.

The result? Knowledge workers end up with fragmented workflows — personal goals in one tool, team coordination in another, and no connection between them.

How Workspaces Work

Every account starts with a personal workspace, created automatically. It behaves exactly like a team workspace — it just happens to have one member. Invite people and it becomes shared; nothing moves, nothing gets migrated, and you don't switch tools.

The important part is what happens to individual records. Every goal, project and task carries its own visibility: workspace (teammates can see it) or private (only you). So a private project can live inside the shared workspace without leaking.

What's Shared

Inside a workspace, your team can:

• Set shared goals and OKRs — track objectives with key results, see progress across the team
• Manage projects — organize work into projects, link them to OKRs, track completion
• Assign tasks — create, assign, and track tasks with priority, due dates, and status
• View analytics — team velocity, workload distribution, project health, OKR vs BAU focus

What Stays Private

Two different mechanisms are at work here, and it's worth keeping them apart.

Private by choice. Goals, projects, tasks and milestones each carry a visibility setting. Mark one private and only you can see it, even though it lives in the shared workspace. This one is a toggle — a per-record one, not an account-wide mode.

Private always. These are never shared with a workspace, under any setting:

• Journal entries and reflections
• Moods and personal notes
• Personal highlights
• Your connected calendar
• Your personal stats and consistency scores

One deliberate exception worth knowing about: your highlighted focus is visible to your workspace. Teammates can see the single thing you've pinned as your current focus — that's the point of it, and it shows up on the shared dashboard under Team Members Focus. Only you can change it.

Visibility is enforced by row-level security in the database, so a private record is invisible to teammates in the app, in exports, and through the API — not merely hidden in the interface.

Setting Up Your Team's OKR System

Here's a practical example of how a 5-person startup might use a workspace:

Step 1: Create Your Workspace

Open the workspace switcher and choose "Create Workspace". Name it after your team or company, and the setup walks you through inviting teammates and creating your first project. (You already have a personal workspace — create a second one when the work genuinely belongs to a group.)

Step 2: Define Objectives

Create 2-3 top-level objectives for the quarter. Good objectives are qualitative and inspiring:

• "Build the product our customers can't live without"
• "Create a sales engine that scales"
• "Build a team culture that attracts top talent"

Step 3: Add Key Results

Under each objective, add 2-4 measurable key results. Good KRs are:

• Measurable — include a number ("Increase MRR to $50K", not "Grow revenue")
• Outcome-focused — describe the result, not the activity ("Achieve NPS of 50", not "Send surveys")
• Time-bound — set a target date (the quarter end)
• Ambitious — stretch goals drive progress (0.7 = success in OKR methodology)

Step 4: Link Projects to Key Results

Create projects for the work that drives each KR. Link them using "Contributing to Goals" in the project edit dialog. Now you can see:

• Which projects serve which strategic goals
• Which work is OKR-aligned vs Business as Usual (BAU)
• How project completion drives KR progress

Step 5: Assign and Execute

Create tasks within projects and assign them to team members. Assigned tasks appear in that person's Today view and in the Task Backlog tab under Projects & Tasks, so they work on team tasks in their own context while status syncs back to the workspace.

Telling OKR Work from Business as Usual

Not every project serves a key result, and that's fine — someone still has to renew the certificates. What matters is knowing the ratio.

Projects linked to a key result carry a target icon in the projects table. The ones without it are your business as usual: necessary, but not strategic. Scan the list and the balance is immediately visible. If the BAU pile is growing while the linked projects stall, that's your signal to rebalance.

The projects table also groups by status, assignee or focus, filters by owner, and searches — so "show me everything Sam is carrying that isn't linked to an objective" is a few clicks rather than a report.

Team Analytics That Matter

Analytics lives under Review in the main navigation, and gives your team visibility without micromanagement:

Team Velocity — tasks completed per week over the last 4 weeks. Is the team accelerating or slowing down?

Workload Distribution — active tasks per member. Who's overloaded? Who has capacity?

Project Health — each project rated as "On track", "Needs attention", or "At risk" based on blocked tasks, overdue items, and completion rate. Hover for the specific reason.

OKR vs BAU Focus — stacked bar chart showing how much of the team's completed work is OKR-aligned vs business-as-usual. Track strategic focus over time.

Real-World Examples

Example 1: Startup with 5 People

Workspace: "Acme Startup"

Objectives:

1. Launch MVP (Q2) — theme: Product
2. Get first 100 paying customers — theme: Customer
3. Build a sustainable development process — theme: Internal Process

Projects:

• Auth & Onboarding → linked to KR "Ship core auth flow" under Objective 1
• Landing Page Redesign → linked to KR "Achieve 5% signup conversion" under Objective 2
• CI/CD Pipeline → linked to KR "Deploy to production in under 10 minutes" under Objective 3
• Bug Fixes → BAU (not linked to any KR)

Example 2: Department in a Larger Company

Workspace: "Marketing Team"

Objectives:

1. Establish thought leadership in our category — theme: Customer
2. Build a predictable lead generation engine — theme: Revenue

Projects:

• Content Calendar Q2 → linked to KR "Publish 12 blog posts with >1K views each"
• SEO Optimization → linked to KR "Achieve top-3 ranking for 5 target keywords"
• Email Nurture Sequences → linked to KR "Improve email-to-demo conversion to 3%"
• Brand Guidelines Update → BAU
• Event Sponsorship → BAU

Getting Started

1. Create a workspace — or just invite someone into the one you already have
2. Invite your team — by email; they'll see a banner to accept
3. Set 2-3 objectives — start simple, iterate
4. Create projects and link them — build the OKR → project → task chain
5. Let people work in their own views — assigned tasks flow into their Today and Task Backlog automatically

The key insight: your team doesn't need to change how they work individually. They keep their own journal, their own daily planning, and anything they've marked private. The workspace is where coordination happens — without a second tool to maintain.