> ## Documentation Index
> Fetch the complete documentation index at: https://docs.weaveos.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Developer experience surveys

> Run developer experience surveys, collect feedback, and review aggregated results

<Note>
  Developer experience surveys are available to every organization. Managers can view survey results, and admins can launch and manage survey cycles under **Reports** → **Surveys**.
</Note>

DevEx surveys measure tooling, workflows, and team health. Each launch creates a **survey cycle**; answers roll up by section. Respondents see **Quarterly check-in** in the product.

## Why not a form?

A generic form captures answers. Weave surveys turn them into signal:

* **Pre-built, validated question bank** — DORA/SPACE-style questions on tooling friction, build and review wait times, docs, focus time, and psychological safety. No guessing what to ask.
* **Qualitative meets quantitative** — survey answers sit next to your actual engineering data in Weave (PR review speed, build times, output), so you can see whether what developers *feel* matches what's actually happening.
* **Trends over time** — each cycle rolls up by section, so you catch drift early instead of relying on memory of who said what.
* **Scales with you** — direct feedback gets noisier as the team grows; surveys keep the signal structured without the manual lift of designing, sending, and aggregating forms by hand.

## Access and roles

| Action | Admin | Manager | Team lead / Member |
| - | - | - | - |
| View surveys and aggregate results | Yes | Yes | No |
| Launch, configure, close, delete | Yes | No | No |
| View individual responses | Yes\* | No | No |
| Complete a survey | Yes | Yes | Yes |

\*When identifiable mode is on for that cycle.

Admins and managers find surveys at **Reports → Surveys**. See [User roles](/features/user-roles) for details.

## Survey cycles

| Status | Meaning |
| - | - |
| **Draft** | Configured, not sent |
| **Open** | Accepting responses until close date |
| **Closed** | Results only |

* Admins launch manually
* One open cycle per org at a time
* Closes on schedule (daily job) or when an admin closes early
* Default window: **2 weeks** (1–12 in org settings or per survey)

## Default questions

Four sections, 12 preset questions (Likert, time/percentage/hours buckets, optional freeform). Admins can add custom questions and sections at launch.

| Section | Topics |
| - | - |
| Delivery speed & tooling friction | Local dev env, build/test wait times, PR review speed |
| Cognitive load & documentation | Internal docs, Slack-as-docs, codebase maintainability |
| Product specification & focus time | Requirement clarity, deep work hours, context switching |
| Culture & collaboration | Psychological safety, cross-team collaboration, open-ended friction |

## Launching (admins)

1. **Reports → Surveys** → enable **Survey enabled** in settings (gear) if first cycle
2. Click **+** — three steps: **Questions** (bank + custom, instruction message with `{{first_name}}`, `{{teams}}`, etc.) → **Recipients** (all members, or filter by role/team/person) → **Configuration** (title, close date, identifiable mode, draft or send)

Drafts need a title, questions, recipients, and a valid close date before send.

<Note>
  Reminders can be configured in the launch flow but **are not emailed yet** (detail page shows **None scheduled**).
</Note>

## Respondents

On send: email invite (from launching admin), home banner, and **Notifications** entry. Survey at `/feedback` — intro plus one step per section, auto-saves drafts, \~5 minutes.

## Results

* **Results by section** — answer distributions (managers and admins)
* **Individual responses** — admins only, when identifiable mode is on (statuses: not started, viewed, in progress, completed)

## Settings (gear icon)

| Setting | Default | Purpose |
| - | - | - |
| Survey enabled | Off | Turn on before first launch |
| Show individual responses | Off | Default identifiable mode for new surveys |
| Cycle length (weeks) | 2 | Response window (1–12) |

Identifiable mode removes anonymity but helps follow up with non-responders.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.