It's Ready When You Are: Shifting Feedback Left at SAMHSA.gov
Video Description
Speakers: Amber Matz and Ramakrishnan Parameswaran
Government teams know the long road to "yes." A feature gets built, then waits — for review, for sign-off, for someone with the authority to make time. And while it waits, it costs you: a staging server tied up, a demo VM someone might wipe, a prototype going stale. When a test environment is scarce, you guard it, and the iffy idea that might've been great never gets built at all.
The team behind SAMHSA.gov changed that by making one thing cheap: the environment. A full preview now builds on every merge request, wired into their pipeline — so QA, stakeholders, and the client see the running site before it merges, not after. The work moved off the developer's laptop and onto the branch, where anyone who can click a link can weigh in.
Ramakrishnan “Rama” Parameswaran, Drupal Lead at Alpha Omega, and Amber Matz, Developer Advocate at Tugboat, will follow that single shift as it pays off at three escalating levels, each drawn from real work at SAMHSA.gov:
- Shifting feedback on a change left — a preview on every merge request, so the team catches problems before a merge tangles them up.
- Shifting feedback on a feature left — a long-running feature branch parked on a preview for months, no staging server held hostage.
- Shifting feedback on a bet left — a high-risk AI proof-of-concept built and locked for the client to evaluate, with every hour going into the feature instead of the infrastructure.
The throughline: in government you can't make approvals faster — but you can make waiting for them nearly free. When an environment costs almost nothing and rebuilds itself on every push, you stop rationing experiments, reviewers can honestly send work back without it being expensive, and a finished feature can simply sit ready until the people with authority have the time. It's ready when they are.
Attendees will leave with:
- A bigger way to think about "shift left" — not just testing earlier, but moving review of changes, features, and risky bets onto the branch where the whole team can reach it.
- A working pattern for per-merge-request previews wired into CI, so clients and reviewers join QA instead of waiting for the merge.
- How disposable previews let a feature or a POC sit ready for months without tying up a server or a VM.
- A first step you can take on your own Drupal project this week.
Government teams know the long road to "yes." A feature gets built, then waits — for review, for sign-off, for someone with the authority to make time. And while it waits, it costs you: a staging server tied up, a demo VM someone might wipe, a prototype going stale. When a test environment is scarce, you guard it, and the iffy idea that might've been great never gets built at all.
The team behind SAMHSA.gov changed that by making one thing cheap: the environment. A full preview now builds on every merge request, wired into their pipeline — so QA, stakeholders, and the client see the running site before it merges, not after. The work moved off the developer's laptop and onto the branch, where anyone who can click a link can weigh in.
Ramakrishnan “Rama” Parameswaran, Drupal Lead at Alpha Omega, and Amber Matz, Developer Advocate at Tugboat, will follow that single shift as it pays off at three escalating levels, each drawn from real work at SAMHSA.gov:
- Shifting feedback on a change left — a preview on every merge request, so the team catches problems before a merge tangles them up.
- Shifting feedback on a feature left — a long-running feature branch parked on a preview for months, no staging server held hostage.
- Shifting feedback on a bet left — a high-risk AI proof-of-concept built and locked for the client to evaluate, with every hour going into the feature instead of the infrastructure.
The throughline: in government you can't make approvals faster — but you can make waiting for them nearly free. When an environment costs almost nothing and rebuilds itself on every push, you stop rationing experiments, reviewers can honestly send work back without it being expensive, and a finished feature can simply sit ready until the people with authority have the time. It's ready when they are.
Attendees will leave with:
- A bigger way to think about "shift left" — not just testing earlier, but moving review of changes, features, and risky bets onto the branch where the whole team can reach it.
- A working pattern for per-merge-request previews wired into CI, so clients and reviewers join QA instead of waiting for the merge.
- How disposable previews let a feature or a POC sit ready for months without tying up a server or a VM.
- A first step you can take on your own Drupal project this week.