Sidebar Grouping Concepts

Reorganizing the navigation around workflow stages — what engineers do when they're working a ticket vs building flows vs reviewing results. Also explores splitting AI Assistant into two distinct tools with clearer purpose.

Concept A — Resolve / Build / Insights

Three clear workflow stages. "Resolve" is front and center because that's what engineers spend most time doing. AI is split: copilot lives in Resolve, builder lives in Build.

Concept A1
With Section Labels
Explicit uppercase labels separate each group. Clear visual hierarchy.
Concept A2
With Dividers Only
Same grouping but uses subtle divider lines instead of text labels. Cleaner, less visual noise. Groups are implied by proximity.
Concept A3
Dashboard First
Dashboard stays at the top as the "home" landing, then workflow groups follow. Some engineers want the overview first before diving into work.

Concept B — Work / Build (Simpler Split)

Only two groups instead of three. Dashboard top, then "Work" (active troubleshooting) and "Build" (authoring + review). Exports and Analytics move into Build since they're about improving process, not resolving tickets.

Concept B1
Two Groups + Dashboard
Fewer sections = less cognitive load. "Work" is what you do when tickets come in. "Build" is everything else.

AI Assistant Split — Naming Options

Troubleshooting AI (Copilot)

Used during active sessions. Suggests next steps, explains errors, provides context from ticket data and knowledge base.

AI Copilot Current robot icon — generic but clear purpose
Resolve AI Sparkle icon — ties to the "Resolve" section name

Flow Builder AI (Authoring)

Used when building new flows from scratch. Conversational interface to generate decision trees, procedural steps, and intake forms.

AI Builder Robot icon — explicit "builder" label
Flow Forge Wrench icon — "forge" = crafting/building