Re:Invent Work for the Asynchronous Era
Execution is already fast.
Decisions are what is slow.
AI made the doing of work parallel. Organizations still are not faster, because decision-making stayed synchronous — meetings, waiting for replies, approvals, confirmations. UTSUROI is infrastructure for lowering that synchronous share so decisions can scale.
01 — Amdahl's law
Your ceiling is set by the synchronous share.
No matter how much execution you parallelize, total performance is governed by the part that cannot be parallelized — Amdahl's law. In an organization that part is the synchronous region: meetings, waiting for replies, approvals that live in one person's head, confirmations. Now that execution is effectively free, this is the only thing setting your speed.
Maximum organizational performance ≒ 1 / synchronous share
UTSUROI aims to take that share from 40% down to 1%. The goal is not to work faster but to build a structure that keeps running without everyone being in sync.
02 — The bottleneck
"Stuck" comes from not being able to see.
Decisions pile up unmade not because people are lazy, but because the state of the work is invisible.
- Nobody knows whose ball it is right now.
- Nobody knows whether it is awaiting review or not started.
- No deadline was ever set.
- A decision is stalled inside someone's head.
UTSUROI turns requests in Slack and the movement of tasks into a visible state of work. Not for oversight — for spotting a stall and getting the work moving again.
03 — Built into the flow
Remove the drops instead of blaming them.
A flow that depends on human memory and attention accumulates a small error at every step. Turn a single reaction into the task — remove one step and the odds change by an order of magnitude.
The usual flow
- A makes a request5% B never reads it
- B copies it into a task tracker5% never entered · 15% no due date
- B checks their tasks10% missed
- B does the workIt falls through before it gets here
The UTSUROI flow
- A adds the reaction — it becomes a taskUnread no longer matters
- The copying step disappearsNothing forgotten · due date from the default
- Once set up, the due date is announced in the openSomeone else catches a miss
- B does the workWork arrives without stalling
Stop treating a dropped request as an individual failing and make it something the process detects and handles. Because the mechanism catches them, a team can move to asynchronous work without anxiety. The percentages are assumptions that illustrate the idea, not measurements.
04 — The screens
The state shows up on two screens.
The work that gets picked up comes back in two views: a Kanban board for whose ball it is right now, and a Timeline for when it lands. The same tasks, asked two different questions.
Improve sign-in Knowledge
Decision — Keep the existing auth flow
The new sign-in screen will preserve existing sessions, so the team does not need to set up access again.
Verified constraint
Expired invitation links need a clear explanation. Review cases are recorded in the task, and Tanaka now holds the ball.
05 — Product
Work as usual; the machinery runs underneath.
UTSUROI does not ask you to change how you work. Keep chatting and moving tasks as usual, and Slack conversations turn into tasks and stalls become visible.
From chat straight to tasks
The Slack integration turns a reaction or an unanswered mention into a task. Default assignees, due dates and labels can be applied.
Learn more →Estimates and velocity
Velocity is a record, not a target. Completed work shows the due date you get at your actual pace.
Learn more →Bottlenecks made visible
Which task, whose decision, how long. "We are stuck" becomes data rather than a feeling.
Learn more →MCP and AI integration
With the official plugin, decisions and findings from AI work can be saved to project knowledge. Source badges in history show where a change came from, and review goes back to a person.
Learn more →Skills — your team's know-how
Capture your team's way of working in a skill. Define the scope, decision rules and report format, then reuse it with your preferred AI.
Learn more →Public REST API
Slack is one way in. With a personal API token, your own scripts and existing systems can read and write tasks too.
Learn more →06 — Design principles
Assume people are imperfect.
People take time off.
People prioritize something else.
— and the work keeps flowing anyway.
We do not rely on the fantasy that everyone follows every notification and never misses a mention. Task management that does not depend on notifications. Accountability that does not depend on anyone's memory. Miss a mention, skim past Slack, and your task list still tells you everything you owe. That is the state UTSUROI is built for.
End the era of managing people.
With AI and portfolio careers now commonplace, what makes an organization faster is not more oversight but less synchronization. UTSUROI is the infrastructure for moving there.
UTSUROI — 移ろい. To keep changing without ever stagnating.