Research

A research campaign reads your connected sources, interviews the people who’d know, and drafts a proposal — outcomes, workflows, or memory — for you to review and publish.

Building a campaign

Cadence

• One-off — runs once
• Recurring — runs on a schedule, keeping proposals current

Scope

What the campaign may propose:

• Outcomes — company priorities
• People and Groups — who’s who, and how they’re organized
• Topics — what belongs in Memory
• Workflows — recurring work worth automating

Scope narrowly. A campaign scoped to “propose everything” produces a shallow draft; one scoped to “map our renewal process” produces something you can act on.

Sources

Which connections the campaign may read.

Note

Sources are opt-in. A campaign with no sources selected reads only the knowledge base and the public web.

Interviews

Who Alma should ask.

Each run creates an Ask routed to the people you pick. Their answers fold into the proposal.

Note

Interviews are opt-in too. No one is contacted unless you add them here.

Results

Everything a run proposes arrives as suggested — nothing is published automatically. Accept what’s right, correct what’s close, reject the rest. Rejections are signal: a campaign that keeps proposing the same wrong thing usually needs a narrower scope or different sources.

Accepted proposals become real outcomes, groups, topics, or workflow drafts. A proposed workflow arrives as a Proposed draft — still inert, still yours to enable or not.

Caution

Coming soon. The Campaigns tab on a campaign’s detail page — its run history and interview transcripts — always shows “No runs yet,” even after a run completes. The proposals a run produces are real and land in their sections normally.

Starting from research

Both Outcomes and Workflows offer research as the recommended starting point when empty. Correcting a draft of twenty proposals is faster than writing twenty from scratch.