| name | developer-experience-survey |
| enabled | true |
| description | Use when performing developer experience survey — structures a comprehensive
developer experience survey covering tooling satisfaction, development
workflow friction, documentation quality, and overall developer productivity.
This template helps platform and engineering leadership teams identify pain
points and prioritize investments that improve developer velocity and
satisfaction.
|
| required_connections | [{"prefix":"collaboration","label":"Collaboration Tool"}] |
| config_fields | [{"key":"org_name","label":"Organization Name","required":true,"placeholder":"e.g., Engineering Department"},{"key":"survey_period","label":"Survey Period","required":true,"placeholder":"e.g., Q1 2026"}] |
| features | ["DEVELOPER_EXPERIENCE","PLATFORM_ENGINEERING","SURVEY"] |
Developer Experience Survey
Phase 1: Survey Design
Define survey scope and distribution plan.
Phase 2: Survey Sections
Section A: Development Environment (rate 1-5)
| Question | Rating | Comments |
|---|
| My local development setup is easy to configure | | |
| Build times are acceptable | | |
| Test execution speed is acceptable | | |
| IDE and tooling meet my needs | | |
| I can spin up a development environment quickly | | |
Section B: CI/CD and Deployment (rate 1-5)
| Question | Rating | Comments |
|---|
| CI pipeline is fast and reliable | | |
| I can deploy my changes to production confidently | | |
| Rollback process is straightforward | | |
| Feature flags are easy to use | | |
| I get timely feedback on build/test failures | | |
Section C: Documentation and Knowledge (rate 1-5)
| Question | Rating | Comments |
|---|
| Internal documentation is up to date | | |
| I can find the information I need quickly | | |
| Onboarding documentation is helpful | | |
| API documentation is accurate | | |
| Runbooks are useful during incidents | | |
Section D: Collaboration and Process (rate 1-5)
| Question | Rating | Comments |
|---|
| Code reviews are timely and constructive | | |
| I understand the team priorities and goals | | |
| Meetings are effective and well-structured | | |
| I feel comfortable asking for help | | |
| Cross-team collaboration is smooth | | |
Section E: Open-Ended Questions
- What is the single biggest thing slowing you down?
- What tool or process change would have the most impact?
- What do we do well that we should keep doing?
Phase 3: Results Analysis
| Section | Avg Score | Previous | Change |
|---|
| Development Environment | | | |
| CI/CD and Deployment | | | |
| Documentation and Knowledge | | | |
| Collaboration and Process | | | |
Phase 4: Action Planning
| Finding | Impact (H/M/L) | Effort (H/M/L) | Owner | Target Date |
|---|
| | | | |
Counter-Rationalizations
| Shortcut | Counter | Why |
|---|
| "We can skip some steps for this case" | Adapt the workflow steps, don't skip them | Skipped steps are where incidents and oversights originate |
| "The user seems to already know what to do" | Complete all workflow phases with the user | The workflow catches blind spots that experience alone misses |
| "This is a minor case, full process is overkill" | Scale the process down, don't turn it off | Minor cases become major when unstructured; the process scales, not disappears |
| "I'll fill in the details later" | Complete each section before moving on | Deferred details are forgotten; real-time capture is more accurate |
| "The template output isn't necessary" | Always produce the structured output format | Structured output enables comparison, audit trails, and handoff to other teams |
Output Format
Summary
- Organization: ___
- Response rate: % ( / ___ engineers)
- Overall DX score: ___ / 5.0
- Highest-rated area: ___
- Lowest-rated area: ___
- Top requested improvement: ___
Action Items
