Ideas

Most apps treat ideas like notes: a title, a body, you write something down, you come back to it later. That works for the first ten seconds and stops working as soon as the idea is interesting enough to actually pursue.

Jootle treats ideas differently. An idea in Jootle is a thinking surface: a place where you and your AI sketch, expand, compare, and stress-test something before deciding whether to turn it into work.

What an idea is

An idea has:

A title and a short summary. What’s the thing.
A notes area. Free-form prose that grows over time.
A set of lenses. Optional structured views your AI can produce on demand.
Lists. Attached lists for sub-questions, alternatives, risks, references.
Artifacts. Documents the idea has spawned (comparison charts, risk analyses, briefs).
Links. Connections to related ideas, projects, or contacts.
A status. seedling, growing, dormant, graduated, dropped.

You don’t have to fill any of this in. Most ideas start as just a title and a sentence. The structure shows up only when it’s earning its keep.

How an idea grows

The lifecycle is something like this:

Seedling. You capture something. “I wonder if we should offer a yearly subscription tier.” Two sentences. Save and move on.

Growing. Over a few days or weeks, you come back to it. Your AI helps you add structure. You might run a comparison lens to see this idea against alternatives. A risk lens to surface what could go wrong. You attach a list of questions you want answered before deciding.

Dormant. Some ideas sit. They aren’t dropped, just not yet. Dormant is not a failure state; it’s an honest one.

Graduated. Eventually an idea matures into work. You ask your AI to graduate it. The idea becomes a project, the lists become initial tasks, the artifacts move with it, and the idea is marked graduated with a link to the resulting project.

Dropped. Sometimes an idea ages out. You drop it. It stays in the archive in case you want to revisit, but it stops cluttering the active list.

Lenses

A lens is a small, focused playbook that takes the current state of an idea and produces an artifact for it. Each lens has a button on the idea’s page.

The built-in lenses on every idea include:

Comparison chart. Side-by-side against alternatives you specify, or alternatives your AI proposes.
Risk analysis. What could go wrong, scored by likelihood and impact.
Pros and cons. The simple one. Sometimes still the right one.
Stakeholder map. Who needs to weigh in, and what each one cares about.
Cost / effort estimate. Order of magnitude. Honest about uncertainty.
Argument against. The strongest case you can build for not doing this. Useful before you decide.

Each lens produces an artifact attached to the idea. You can run them more than once as the idea evolves. The previous artifacts stay in the history.

Toolkits you install can add their own lenses. If you’ve installed the Forge toolkit, ideas about content also get a launch outline lens. If you’ve installed Finance, financial ideas get a monte-carlo budget lens. The catalog grows with what you’ve installed.

Lists inside ideas

Most ideas grow into needing a few lists:

Open questions that need answers before you can decide.
Alternatives you considered but want to remember.
References (links, articles, people who’ve done this, prior art).
Risks as a working list, separate from the formal risk analysis lens.

You don’t have to create these lists by hand. Ask your AI: “Make me a list of open questions for the subscription tier idea.” A list appears, attached to the idea.

Capturing without ceremony

The friction-killer for ideas is the inbox-style capture.

From any channel:

You (text from Telegram): New idea: subscription tier with a “founding member” pricing for the first 50 customers.

Your AI files it as a new idea, gives it a draft title, and asks if you want to expand on it. You can answer or ignore. Either way the idea is captured.

If you have a lot of half-formed thoughts in your head before bed, dictating them one at a time produces a workable inbox of seedlings to sort through in the morning.

When to graduate

A useful rule: graduate when you have enough structure that the question “what should I do next?” has a concrete answer.

That usually means:

The idea has at least one clear deliverable (something you’d ship, write, or hand off).
You’ve answered the open questions that were blocking commitment.
The work is bigger than a single task but bounded enough to scope as a project.

If those are true, ask your AI to graduate it. The idea becomes a project with the lists and artifacts attached. You keep momentum.

If they’re not true, the idea isn’t ready. That’s fine. The point of the idea surface is to hold these in a useful shape until they are.

Dropping cleanly

Dropping an idea is not the same as ignoring it. Ignored ideas pile up and crowd out the live ones. Dropped ideas are out of the active view and out of your mental tax base.

Ask your AI: “Drop the idea about a yearly tier. Keep the comparison chart artifact in case it’s useful later.”

It does the right thing. The artifact survives in the archive; the idea is gone from your active list.

Why this matters

Most ideas don’t become projects. Most ideas should not. The point of having a real thinking surface is that you can put more candidates through cheap evaluation before deciding which to invest in.

If you have a place to grow ideas without commitment, you can be less precious about what you capture and more brutal about what you graduate. That’s the trade-off Jootle’s Ideas toolkit is built around.