How to Run a 30-Day Automation Discovery Sprint: A Practitioner's Playbook

The organic approach to pipeline building - waiting for business users to submit ideas over time, handling each intake as it arrives - has a predictable output: a pipeline that's always 2–3 months out, always slightly undersized, always dependent on the volume and quality of whoever happens to be submitting this month. It's reactive, and reactive pipelines produce reactive programs.

The alternative is the discovery sprint - an intensive, structured period of active pipeline building where the CoE goes to the business rather than waiting for the business to come to the CoE. Done well, a 30-day sprint can generate 3–6 months of qualified pipeline, establish relationships with business stakeholders in new departments, and create a repeatable playbook for future sprint cycles. Here's how to run one.

Week 1: Stakeholder Mapping and Sprint Setup

Day 1–2: Identify Target Departments and Executive Sponsors

Before the sprint begins, identify the 3–5 departments or business units where the sprint will focus. Selection criteria: departments with high process volume and complexity (Operations, Finance, HR, Customer Service are almost always good choices), departments where executive sponsorship is available or can be obtained, and departments that haven't been active in the automation program previously (to expand the pipeline beyond existing strongholds).

Day 3–4: Brief Stakeholders on What to Expect

The sprint kickoff briefing is critical for setting expectations and motivating participation. Business users need to understand: what an automation opportunity looks like (and doesn't look like), why their input matters, how long the intake process takes, and what they'll receive in return (a qualification report, an ROI estimate, a clear recommended next step - not just a form acknowledgment that disappears into a queue).

Day 5: Configure and Test the Intake System

Ensure the intake platform is configured for the sprint: correct organizational mapping, relevant department options, appropriate technology catalog for each department's likely tool stack. Run a test intake with one of your own team members playing the business user role. Identify any questions or flows that are confusing and refine before opening to the business.

Week 2: Active Discovery

Day 6–10: Open Intake and Drive Submissions

The sprint's active phase opens with a direct ask to each department's stakeholder group: 'We'd like you to submit your three biggest process pain points in the next 5 days. Each intake takes 45–60 minutes. You'll receive a full qualification report and ROI estimate within 48 hours of submission.' The specific, time-bounded ask drives much higher completion rates than an open-ended invitation.

Don't wait for submissions to come in. Follow up with stakeholders who haven't submitted by Day 8. Offer to schedule 15-minute kickoff calls to answer questions. Remove every barrier to participation. In our experience, the conversion rate from 'briefed stakeholder' to 'completed intake' drops from 70% to 30% when there's no active follow-up during the submission window.

Week 3: Review and Qualification

Day 11–15: Review AI-Generated Qualification Reports

If you're using AI-powered intake, qualification reports will be available immediately after each submission completes. Review them for completeness and accuracy - flagging any intakes where the data seems inconsistent or where important questions weren't resolved. For flagged intakes, use the Deep Dive feature to request targeted follow-up questions rather than scheduling new workshops.

Day 16–18: Pattern Verification and Preliminary Prioritization

Validate the AI-recommended patterns against the intake data. For complex or ambiguous candidates, involve a senior technical resource in the pattern review. Begin preliminary prioritization using a consistent scoring framework: ROI potential, implementation complexity, strategic alignment, and time to value. Surface the preliminary prioritization to a CoE steering group for alignment.

Week 4: Handoff and Sprint Wrap-Up

Day 19–22: Create Development-Ready Briefs for Top Candidates

For the top 10–15 candidates from the sprint, prepare development-ready briefs that include: the qualification report summary, recommended pattern and rationale, ROI estimate and methodology, preliminary effort estimate, recommended builder profile (specialist or citizen developer), suggested next steps, and stakeholder contacts for follow-up. These briefs allow developers to pick up candidates from the sprint pipeline without any additional discovery work.

Day 23–25: Sprint Retrospective and Stakeholder Feedback

Conduct a retrospective with the CoE team: what worked, what didn't, what would improve the next sprint. Separately, gather feedback from business stakeholders on their intake experience - was the process clear, was the timing manageable, did the qualification report provide value? This feedback improves subsequent sprint designs and builds stakeholder trust.

Day 26–30: Documentation and Next Sprint Planning

Document the sprint output: number of candidates submitted, number qualified, pattern distribution, total ROI potential, departmental breakdown. Use this data to make the case for the next sprint (typically 90 days later) and to refine the targeting for the next cycle. The best programs run discovery sprints quarterly - building a structured pipeline cadence that keeps the CoE consistently supplied with qualified candidates.

Sprint Metrics: What Good Looks Like

• Target submission rate: 60–80% of briefed stakeholders complete at least one intake
• Qualification rate: 70–80% of submitted processes pass the root cause gate as genuine automation candidates
• Pattern distribution: expect 30–40% RPA, 20–30% API/Integration, 15–20% BPM, 10–15% IDP, 5–10% GenAI/ML
• Pipeline value: a well-run sprint in a large organization should generate $5–15M in qualified automation opportunity
• Time to first development start: top-priority candidates should enter the development queue within 2 weeks of sprint close