Quick start for operations leaders

Business Summary: Operations leaders use Nimbus to run repeatable, cross-functional workflows — supply chain reviews, process improvements, and incident response — with clear ownership, approvals, and a record of what changed.

This guide is for COOs, ops directors, and program leads who coordinate work across teams and systems.

What Nimbus means for operations

Your first week — daily playbooks

Day 1 — Learn the platform loop

1. Read Key concepts — workstream, agent, NTU, HITL (15 min).
2. Open Overview and scan stat pills and activity tabs.
3. Optional: follow Platform walkthrough steps 1–2.

Day 2 — Connect operational systems

1. Open Connectors → search WMS, ERP, or ticketing (Jira, ServiceNow, etc.).
2. Toggle on → Continue → complete OAuth.
3. For messaging Action connectors, click Configure and set channels.

Deep guide: Connecting a connector

Day 3 — Create a pilot workstream

1. Open Workstreams → New workstream.
2. Scope one initiative (for example Weekly ops review brief).
3. Assign an Operations-domain agent and bind Day 2 connectors.

Deep guide: Creating a workstream

Day 4 — Assign team and approvals

1. Open workstream Settings → add contributors and approvers.
2. Set HITL to Soft for drafts, Hard before external share.
3. Confirm Needs you routes to the ops lead.

Deep guide: Workstream teams

Day 5 — Run and review outputs

1. Open Plan mode → describe the weekly brief.
2. Confirm & run → monitor Runtime on the collaboration rail.
3. Review Deliverables and Activity after completion.

Deep guides: Workstream chat modes,

Operations use cases to try first

• Weekly ops review brief — Intelligence connectors + Operations agent summarize KPIs and exceptions
• Supplier risk assessment — Scoped workstream with wiki policies and connector data
• Process change proposal — Plan mode with Soft checkpoint for draft; Hard before sharing externally

How this fits in Nimbus

Operations work spans systems, teams, and approvals. Workstreams scope each initiative; connectors supply live data; Activity records accountability.

flowchart TB
  Goal[Ops goal]
  WS[Workstream]
  Data[Connectors]
  Agent[Operations agent]
  Check[Ops lead approval]
  Out[Outputs and Activity]

  Goal --> WS
  Data --> Agent
  WS --> Agent --> Check --> Out

Workflow overview

flowchart LR
  Scope[Scope workstream]
  Run[Agent run]
  Review[Checkpoint]
  Release[Release decision]

  Scope --> Run --> Review --> Release

Governance tips for ops

• Use one workstream per initiative — keeps spend, team, and outputs clean
• Set workstream teams early so the right approvers see Needs you items — Workstream teams and access
• Prefer Intelligence connectors first; add Action connectors only when write-back is required

Example scenario

An ops director scopes Supplier disruption review, connects WMS and ticketing data, and assigns the Operations agent. The team lead approves a remediation brief at a Soft checkpoint before sharing with procurement; Activity records the full trail for the quarterly ops review.

FAQs {#faqs}

Q: How is this different from automation tools like Zapier? A: Nimbus runs multi-step specialist work with human approvals and NTU-metered runs — not simple trigger-action chains.

Q: Can multiple agents work on one workstream? A: Yes, when the goal warrants it. Nimbus can bring multiple functional teams into a single workstream based on your Primary goal — for example Supply chain plus Finance on a cost review. Plan mode orchestrates cross-team runs. Split into separate workstreams only when outcomes are unrelated.

Q: Where do approved ops decisions land? A: Outputs tab, optional Action connector writes, and Activity history — see Where decisions land.

Q: We use initiative tracking in our PMO — is that the same? A: Nimbus Workstreams map to scoped business initiatives with a clear goal, team, and audit trail.

Q: How do we onboard multiple ops pods at once? A: Give each pod its own workstream with a distinct objective and team; share connectors at the org level.