Designer — Redesigning a Process

Designer is where you take a documented process and design what it should look like. It shows the process on a diagram and can draft an AI-enabled future state next to it, which you refine, walk through, and export. It's visible to org admins, admins of the selected Initiative, and members granted To-Be access — the same people who see Architect's To-Be tabs.

Opening it

• Designer in the Agents group of the sidebar — opens a picker of every process that has a diagram to redesign, grouped by department: analyzed processes with an interview deliverable, and processes in the Processes library with a published diagram (marked library), whether or not an Architect analysis has run. Processes with nothing to open yet — a gap Architect found, or a process with only an SOP — are left off the list. An Architect run isn't required to design a future state; when one exists, its opportunities can be selected as targets for the redesign.
• The ⋯ menu on any process row in Architect → "Redesign with AI".
• Select several rows in Architect → "Redesign together" (merges them into one end-to-end map), or "Harmonize" in the Variants view.
• A process chain header in Architect's Chain view → "Redesign with AI".
• A variants comparison → "Generate standard process" (reconciles the variants into one harmonized standard).
• An opportunity page → "Design AI-enabled to-be", or the roadmap for a process marked Transform or Replace → "Redesign with AI".
• A process page in the Processes library → "Start a to-be" (shown when the process has a published diagram). This works for any process, including one imported from documentation that no one has been interviewed about and that no analysis has run over yet — Designer opens on its published diagram, and the future state is saved against the process itself.

Working in it

• Switch between As-Is (the process today) and To-Be (the AI-designed future state) with the toggle above the diagram. The To-Be tab shows how many steps differ once a future state exists.
• The As-Is you start from is the process's published version — the same one on the Processes page — so you're redesigning the agreed current state, not one contributor's recording. A version button next to the process name (e.g. "v3") lists every version; pick another to design from that baseline. Versions with no diagram are listed but can't be opened; if nothing has a diagram, the As-Is comes from the interview that documented the process.
• The main button on the right is always the next step: Generate to-be (or Regenerate to-be). For a chain or variants it first reads Combine chain / Harmonize variants — those must be merged into one current-state map before a future state can be designed. When greyed out, hovering explains why.
• The targets button lets you tick which improvement opportunities the future state should realize — available on both views, so you can choose before generating.
• While the future state is designed you can watch the agent's reasoning stream. It runs in the background — a slow one keeps going even if you close the tab.
• Once a to-be exists, the Change 1 of N arrows step through everything that differs; changed steps are outlined. A "To-be impact" strip summarizes the redesign: steps added and removed, automated steps before → after, and — with targets ticked — the estimated hours per week and annual savings.
• Click any step for its details in the right-hand panel: mark it manual or automated, mark it validated (both saved for everyone), or ask the Design Agent about it. For a single process, the panel also shows an Evidence section — chips for the interviews and documents it derives from.
• The Design Agent sits at the bottom of the canvas — ask it questions or instruct it to change the design.
• Export BPMN downloads whichever diagram you're viewing as a BPMN file for other process tools. The link button copies a link to this design (it carries the process and version you have selected).
• Opened on a chain or variant set, a count button in the header (e.g. "5 variants") lists everything on the canvas; for variants a compare icon reopens the variants comparison in a new tab so you can check why they differ while designing the standard that reconciles them.