Doubling response rates through service design

This isn't a story about building an automation system. It's about redesigning a service that touched hundreds of startup founders every quarter, and transforming it from something they dreaded into something they valued.

District 3's quarterly check-in collected existentially important data. It fed reports to Concordia University, Quebec government agencies, federal agencies, and partner nonprofits. It directly impacted funding. But the experience of providing that data was broken for everyone involved: founders ignored emails, stream leads chased people through busy inboxes, and the data team drowned in manual processes.

The question wasn't "how do we automate this?" It was "how do we redesign this service so people actually want to participate?"

I made an intentional design choice to keep humans in the loop at key moments. Full automation would have been technically possible, but not everything should be optimized away.

This process emails hundreds of busy founders. Sending unnecessary emails damages the organization's reputation and trains people to ignore future messages. A quick IT review before triggering the email cascade is worth the extra step.

Six months ago, I left D3. Before I did, I trained my replacement by co-creating a parallel system: an annual check-in for alumni and graduated startups. Building something together was the best way to transfer knowledge of Podio's quirks and the design decisions embedded in the system.

Since then, she's run two full quarters of the quarterly system without a hitch. I wrapped up a follow-up contract with D3 last week, the system is still running exactly as designed.

This project taught me that service design isn't about any single touchpoint, it's about the entire journey, for every user type, including the failure modes. The quarterly check-in wasn't broken because of bad technology; it was broken because no one had designed theexperience of participating in it.

The philosophy shift from taking to giving changed how I think about all organizational processes. When you're asking people for their time, ask what you can give back. The Nutrition Labels cost me development hours, but they transformed compliance into engagement.

The accidental database deletion was a gift in disguise. It gave me a blank canvas and permission to rebuild with intention rather than incrementally patching what existed. Sometimes you need that forced reset.

Most importantly: keeping humans in the loop isn't a compromise, it's a design decision. Automation serves humans. It shouldn't replace human judgment where stakes are high and relationships matter.

The Check In Suite will outlive my time at D3. That's the goal of good service design: to create something that runs without you, serves the people who use it, and adapts as needs evolve.