簡
単
About Kantan

Simplicity is the ultimate sophistication.

かんたん (kantan) means simple. But it's more than that — it's the feeling when something just clicks. When the hard thing becomes easy. When you can finally exhale.

The problem

Writing specs shouldn't be the job.

Every PM knows the pain. You have a clear vision in your head, but turning it into a properly structured story with sharp AC, the right format, and a defensible priority score takes forever.

01
Inconsistent quality across your team — every PM writes stories differently, engineers interpret them differently, and QA tests them differently.
02
AC is an afterthought. Most user stories have success metrics where acceptance criteria should be — and nobody catches it until the sprint review.
03
Prioritization is gut feel dressed up as a framework. You know the formula, but applying it consistently to every story across a full roadmap takes hours.
04
Format tax is real. Jira, Linear, Notion, Confluence — every tool has a different structure, and you're the one reformatting everything by hand.
How it works

Four inputs. One complete story.

01
Describe your user and goal
Tell Kantan who the user is, what they want to do, and why it matters. No templates, no rigid forms — just a natural description.
→
02
Set your context
Platform, team size, effort level, and which metrics matter. Kantan uses this to calibrate the AC and prioritization score to your actual situation.
→
03
Define how you'll measure it
Select your metric type, cohort window, analytics platform, and guardrail. Kantan generates the full measurement plan — no freeform, no ambiguity.
→
04
Get a complete story
User story, definition-of-done AC, RICE priority score, measurement plan with event names, a shareable measurement blueprint, and export-ready output for Jira, Linear, or Notion.
簡単 · かんたん · easy
The best PMs don't write better specs.
They spend less time writing them.
— The Kantan philosophy
About Kantan

Why this exists

I've been a product leader for 20 years. I've written thousands of user stories. They take time and real effort to write: the format, the acceptance criteria, the prioritization score, and the measurement plan.

At 45 minutes per story, I figured it was the price to pay. But the reality is it took away time from strategy and thinking. What if those 45 minutes became 30 seconds?

Most tools either just organize your thinking, try to do everything, or cost too much for small teams. Kantan is the tool I always wished existed. It turns a rough idea into a complete, prioritized user story in under 30 seconds. Suddenly, those 45 minutes are back. 45 minutes to focus on your product vision, your next meeting, what you're going to eat that night or just life itself.

かんたん (kantan) means "easy." This tool embodies that philosophy in its simplicity and focus. It's the companion that helps anyone create best-in-class user stories, complete with acceptance criteria, priority scoring, measurement plans, and dashboards.

We're a small team focused on empowering everyone to build amazing things...easily. Welcome to Kantan Labs.