Tasks: Where Strategy Meets Execution

The strategy problem isn’t strategy. It’s the gap between strategy and execution.

Teams spend hours on OKRs, roadmaps, and planning docs. They write goals that everyone nods at in the all-hands. Then two weeks later, the sprint board is full of tickets that connect back to exactly none of it. The work happens. The strategy sits. They never touch.

This is a solved problem in theory. In practice, it persists because the tools that hold your strategy are different from the tools that hold your tasks — and nobody has the time or the discipline to keep them synchronized by hand.

Today, we’re shipping Momental Tasks.

What Tasks Actually Are

In Momental, a task isn’t a line item in a spreadsheet. It’s a node in your organizational graph — with full context about why it exists, what strategy it serves, and what has to be true for it to be done.

Every task sits in a tree: Objective → Key Result → Opportunity → Solution → Epic → Task. When you look at a task, you can see the chain that explains exactly why someone decided to build it. When you mark it done, that completion flows up the tree — you can see your solution moving from planned to in progress, your epics closing, your key results filling out.

This sounds like overhead. It isn’t. The tree gets built automatically as you plan. Tasks inherit context from their parents. Agents and humans alike navigate the same structure — so there’s never a question of whether the work happening today connects to the goals you set last quarter.

Assignment That Works for Both Humans and Agents

Momental Tasks works for any assignee — human or AI.

For a human team member, a task shows up in their queue with the full strategic context behind it. Not just “implement user onboarding flow” but the opportunity that surfaces it, the decision history behind the approach, the acceptance criteria that define what done looks like.

For an agent, a task is how work actually gets initiated. The agent picks up the task, locks it so no duplicate work happens, reads the context, and starts. When it hits something it can’t resolve alone, it pauses and asks. When it’s done, it writes its findings back to the graph — so the next task in the sequence starts smarter.

This matters more than it sounds. Most work coordination tools are built for humans managing humans. They assume a person will read context, fill in the gaps, and use judgment. Agents can’t make those assumptions gracefully — they need the context to be explicit. Momental Tasks makes it explicit by design.

Acceptance Criteria as a First-Class Concept

One of the things we spent the most time on was acceptance criteria — the definition of what it means for a task to be complete.

This sounds obvious. In practice, most task systems either don’t have AC at all (the task is “done” when someone says it is) or treat AC as a freeform text field that nobody reads. Neither works when you’re running agents.

In Momental Tasks, acceptance criteria are structured and linked to the task. When an agent takes a task, the AC is part of the context it operates from — not a note it might or might not notice. When work completes, the AC is what gets checked. If something’s not met, the task goes to review rather than getting silently closed.

The result is that “done” means the same thing to everyone — human or agent — every time.

The Todos View

We also shipped a new view we call Todos.

Todos shows you all the tasks across your active solutions, organized by what they’re actually working toward. On the left: your solutions, with real-time status — which ones are in progress, which ones are planned, which are done. On the right: the tasks within whichever solution you’re looking at.

You can assign tasks to team members or agents directly from this view. You can drag to reorder priorities. You can search across everything when you need to find something specific. And you can see at a glance where the work is actually happening — not where you hoped it would be.

It sounds like a task manager. The difference is that everything on screen is connected to something real in the organizational graph. The solutions have outcomes attached to them. The tasks have context. Nothing is floating in a vacuum.

Why We Built It This Way

There’s a version of Tasks we could have shipped that was simpler. A task list. A status column. Maybe assignees. Plenty of products already do that.

We didn’t build that version because we don’t think that version solves the problem.

The gap between strategy and execution persists because most tooling treats them as separate concerns. You plan in one place, you track work in another, and you spend enormous energy manually connecting them. That energy doesn’t scale. It doesn’t scale for humans, and it definitely doesn’t scale for agents.

When tasks live in the organizational graph, the connection is structural. You don’t have to remember why something exists — the graph knows. You don’t have to manually update status upward — completion propagates. You don’t have to write a context dump for every new agent session — the task inherits the context it needs.

The compounding benefit is that work teaches the graph. Every task that completes leaves behind learnings, decisions, and context that future tasks can use. The team gets smarter as it works — not as a side project, but as a natural consequence of how the system is designed.

What’s Available Today

Momental Tasks is live for all teams on Momental.

• Task creation within any Epic in your strategy tree
• Assignment to any human team member or active agent
• Acceptance criteria on every task
• The Todos view — real-time status across all your active solutions
• Agent task workflow — lock, checkpoint, complete, with full context at every step

If you’re already on Momental, Tasks is in your sidebar now. If you’re not, join the waitlist and we’ll get you in.

---

We built Momental Tasks because we needed it. Our agents have been running on it for months — the work you’re reading about was coordinated through the same system. We think that’s the right test for whether something is worth shipping.