For Remote Teams

NCT for Remote Teams

When you can't align in the hallway, you need alignment in the system. NCT gives distributed teams a shared strategic context that works across time zones — without more meetings.

Sound familiar?

The problems NCT was built to fix

Problem 1

Alignment requires a meeting — and your team is in 4 time zones

You can't do a quick hallway chat when half the team is asleep. Every alignment moment becomes a calendar event, and the meeting load is crushing the time people have to actually build. Remote teams need async alignment, not more syncs.

Problem 2

Context gets lost between Slack, Notion, and standup updates

The strategy is in a Notion doc. The updates are in Slack. The work is in Linear. Nobody knows which source of truth to trust, and the information is fragmented across three tools and two time zones.

Problem 3

People are doing good work that doesn't connect to anything

Remote work amplifies autonomy — which is great until people are building in isolation. Without visible strategic context, individual contributors make reasonable decisions that don't add up to a coherent direction.

How it works

Three layers — built for remote teams

Every layer of NCT maps directly to how remote teams already think about their work.

N
NarrativeShared strategic context

Narratives are the async alignment layer. Every team member — in any time zone — can read the Narrative and understand what the company is solving and why. No meeting required.

"Our remote team is shipping features but losing coherence. Each pod is optimizing their own area without understanding how it fits into the bigger picture. We need a single source of truth for strategy that's readable in 5 minutes — not a 90-minute all-hands."
C
CommitmentWhat each pod delivers

Commitments make accountability visible across time zones. Every pod knows what they're delivering, when, and how it connects to the Narrative. No more 'I thought the other team was handling that.'

"Ship async daily check-ins that replace standup meetings. Each team member posts progress against their Commitments — readable by any team member in any time zone."
T
TaskVisible daily work

Tasks connected to Commitments mean every contributor's daily work is visible in strategic context. Managers don't need status meetings — the system shows progress.

Design check-in format · Build async update flow · Integrate with Slack notifications · Test across time zones · Write team guide

Real example

A Narrative for remote teams

"Our distributed team spends 12+ hours per week in synchronous meetings — most of which are status updates, not decisions. Engineers in our APAC time zone attend meetings at 10pm. We're losing people to meeting fatigue, not workload. If we move alignment to an async system, we free up time for deep work and make the company accessible to talent in every time zone."

Commitments for this Narrative:

  • 1Replace all status-update meetings with async Narrative and Commitment check-ins
  • 2Ship a weekly async update format that each team lead completes in under 10 minutes
  • 3Reduce total synchronous meeting hours by 40% across the engineering org

Use cases

How remote teams use NCT

Async cycle planning

Run planning as a written process. Narratives are proposed, reviewed, and finalized in documents — not meetings. Comments and decisions are captured in writing, accessible to everyone.

Cross-timezone handoffs

When the EU team ends their day and the US team picks up, the Narratives and Commitments provide the context. No handoff meeting needed — the strategic intent is always visible.

Reducing meeting load

Every meeting that exists only to share context or alignment can be replaced by a Narrative. Reserve synchronous time for decisions, not information sharing.

Remote retrospectives

At the end of a cycle, review health scores against Narratives and Commitments. The data tells the story — the retro focuses on learning, not status updates.

We killed 8 hours of weekly status meetings. The Narratives carry the context now, and the whole team has more time to build.

Head of Remote, Fully distributed team, 35 people across 6 time zones

Ready to run NCT with your remote teams?

Set up your first cycle in minutes. Free forever to start — no credit card, no consultant.

Free forever. No credit card needed.