Validate developer demand and priority for central reusable workflows

🧑‍💼 User Need

As a DevEx Team Member
I want to conduct some user research on reusable workflow needs
so that we can confirm demand, priority, and adoption criteria before delivery

💡 Value / Purpose

• Confirms whether this is a top developer pain point
• Reduces risk of building a low-adoption central service
• Informs scope, onboarding approach, and ownership model

🛠️ Description / Context

• Define 5–7 concise discovery questions (pain points, current workarounds, desired outcomes)
• Run a small sample of interviews/surveys across varied teams
• Summarise common themes, priority signals, and adoption barriers
• Propose a go/no-go recommendation and rough scope options

🧪 Testing steps

• Confirm research sample includes multiple team types (product, platform, service teams)
• Check recommendation maps clearly to evidence collected

✅ Definition of Done

• Document work completed in Developer Experience Team SharePoint
• Discovery questions and participant sample are documented
• Findings summary and recommendation are documented

❓ Additional Information

• Risk: Low response rate or skewed sample
• Mitigation: Time-boxed outreach via existing engineering channels and communities
• Constraint: Keep research lightweight and fast to avoid delaying decisions

📝 Notes (Optional)

• Use findings to define success metrics for any implementation phase

Start by drafting the 5–7 discovery questions and planning a sample spanning product, platform, and service teams. Record the questions, participant sample, findings, evidence-backed recommendation, and scope options in the Developer Experience Team SharePoint; done means the research and go/no-go recommendation are documented.