Getting Started

1. Get evidence in

You have two routes, and the fastest one depends on what you already have to hand.

If you already have feedback somewhere — a CSV export, interview notes, a support dump — paste or upload it. This takes about a minute and needs no setup at all, and it is the fastest way to see the product actually work.

If you want evidence to keep arriving on its own, connect a source:

Route	Best for	Setup
Ask your agent	Zendesk, Intercom, Jira, HubSpot, Slack — around a thousand tools	One link to approve
Email	Forwarding interview notes, support email, meeting transcripts	2 min
Signal webhook	Zapier, Make, n8n, your own scripts	5 min
GitHub	PRs, releases and deployments as operational context	10 min

2. Wait for Your First Claims

After connecting a source, Atisbo processes incoming signals:

1. Each piece of text is automatically classified (problem, idea, question)
2. Similar signals get grouped into a Claim — a confirmed pattern
3. Each Claim receives a PowerScore indicating how urgent it is

Email, webhook and uploaded sources typically appear in Triage within a few minutes. Polled sources like Notion and Granola run an import immediately after setup and then sync once per day; ask your agent for a sync now if you need one before the next run.

3. Triage Your Claims

In the Triage screen, review each Claim and decide:

• Real — Fixed: This is a real problem and you've already addressed it
• Real — Won't Fix: It's real but not a priority right now
• Real — Design Change: Requires a design decision
• Noise: Not a real signal — discard
• Need More: Not enough evidence yet — keep monitoring

4. Create a product decision on the Board

When you've confirmed a Claim is real, go to the Board and create a Solution:

1. Click + New Solution on any Claim
2. Review the problem evidence, contradictions, and strategic context
3. Describe the chosen response, constraints, and observable success criteria
4. Keep the suggested evidence-weighted priority or set a manual order/priority boost

The live priority combines urgency, evidence volume/recency, and strategy. Legacy RICE fields do not rank the backlog.

5. Use Atisbo from your existing agent work

Open Connect agents in the Atisbo sidebar, install the skills for Claude Code, Codex, Cursor, or another compatible client, and connect the workspace MCP URL.

Choose a skill that matches the interaction already in front of you:

• signal-intake for feedback, research, incidents, metrics, and documents;
• signal-review when captured evidence needs classification or Opportunity regrouping;
• product-review before a weekly or roadmap review;
• opportunity-decision when choosing a response to an Opportunity;
• backlog-brief before continuing a design, issue, branch, or SEN item;
• handoff when a design or PR is ready for In Review;
• outcome after a Done Solution has observable post-launch evidence.

The skill does not replace the designer's or engineer's process. It uses Atisbo's existing MCP tools to read or update Signals, Opportunities, Backlog, Decisions, Groups, Living Documents, and Outcomes.

6. Ask Questions in Chat

Use the Chat assistant for quick answers:

• "Why is the checkout Claim spiking?"
• "What's the most urgent opportunity in the Payments area?"
• "Summarize the evidence behind Claim #42"

The assistant has full context of your Claims, Solutions, and taxonomy — no copy-pasting needed.

7. Record what happened

After a Solution is launched and its observation window is complete, record the measured result as success, partial, miss, or unexpected. Atisbo keeps the intervention immutable and uses the outcome as memory for later decisions.