Every product has a moment it’s really for. Not a persona, not a market segment — a moment. A specific point in someone’s day when they reach for your tool because something needs to happen right now.
For ganttchart.ai, that moment is the ten minutes before a meeting. You’re about to walk into a room (or a call) and someone is going to ask, “so what’s the plan?” You have the plan — it’s in your head, in plain English, maybe in a few bullet points. What you don’t have is the picture. And the meeting starts at half past.
Once we named that moment, every design decision got easier. Here’s what designing for ten minutes actually did to the product.
It set the input
With ten minutes on the clock, nobody is going to fill in a form with start dates, durations, and dependency dropdowns. The only input fast enough is the one you already have: the sentence in your head. So the input is a sentence. “Launch the bakery website in six weeks: design, build, taste-testing photos, then go live.” That’s a complete, valid project description.
It killed the account wall
Sign-up flows are where ten-minute tasks go to die. Verify your email, pick a workspace name, invite your team — the meeting is over before the onboarding is. So the chart comes first. You should be looking at a usable timeline before most tools would have finished asking who referred you.
It decided what “done” means
A tool for the ten-minute moment doesn’t need to be where the project lives. It needs to produce a thing you can walk into the room with: a chart that looks credible on a shared screen and travels as a link. Editable, because the AI’s first draft is a draft. Shareable by URL, because “let me email you the file” is another ten minutes you don’t have.
It made drafts disposable
Here’s the second-order effect we didn’t fully anticipate: when a chart costs seconds instead of an afternoon, people stop treating plans as precious. They generate a version, hate it, say so out loud, and generate another. The plan improves because iterating is cheaper than defending. Slow tools make people commit to their first idea; fast tools let them argue with it.
The general lesson
“Who is this for?” is a good question. “When is this for?” turned out to be a better one — it’s much harder to hand-wave. A moment has a clock on it, and the clock makes the trade-offs for you: what to build, what to cut, and what “fast enough” actually means.
Find the ten minutes your product is for, and design for the clock.