Doubling response rates through service design

Hundreds of startup founders filled out this check-in every quarter, and most of them dreaded it. I redesigned the whole service to make it worth their time.

District 3’s quarterly check-in collected existentially important data. It fed reports to Concordia University, Quebec government agencies, federal agencies and partner nonprofits, and it directly affected 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.

Automating the old process would have preserved a bad experience at higher speed. The job was to redesign the service so people wanted to participate.

The service had four distinct types of user, each with different needs, pain points and touchpoints. Understanding that ecosystem came first.

The old process served none of them. Sixteen manual steps stretched across 7+ weeks, each handoff created a bottleneck, and founders mostly experienced the whole thing as being chased.

The founder matters most: if they don't submit, nothing else does. I redesigned their journey from first contact to follow-up.

The old approach was all taking: "fill this out because you agreed to in your contract." I rebuilt the service around a trade. Founders give us fifteen minutes of data, and we give them back a personalized report on their own startup.

Podio's webform builder is restrictive: no progressive disclosure, limited custom CSS, rigid field types. Within those limits, I first grouped the 25+ questions into eight categories that match founders' mental models, so they can batch their thinking.

Then I cut friction wherever Podio let me.

A new "Why This Matters" section at the top, which the old form lacked entirely, tells founders that their data stays confidential and is only viewed by the data team, helps summarize outcomes for stakeholder updates, highlights their successes within the Concordia community, and helps secure funding and improve D3's support.

The Nutrition Labels are the centerpiece of the "giving back" philosophy: automated analysis reports that turn founders' submitted data into something they can use. The hard part was the information design, starting with which metrics founders track.

The report has five charts.

The report is minimal black and white, directly inspired by real nutrition labels: a familiar format everyone knows how to read, just the facts presented clearly, a periodic check on the startup's "health", and the same format every time, so quarters are easy to compare. Each one carries the startup's name and quarter, the five charts with methodology explanations, a footer disclaimer about data limitations, and a subtle invitation to backfill past quarters.

Generating them took careful timing because of Podio's quirks.

Before building any of this, I gauged interest in the community Slack, and the response was enthusiastic. After the first round went out, two founders followed up specifically to share positive feedback, and in later user interviews founders described the new system as "an all-around upgrade" that made them "much happier to take the time."

The happy path was the easy half. I catalogued the ways submissions could go wrong and built automations to catch, clean, or flag problems before they corrupted our data.

Submissions also used to be a black hole: founders' website, address and legal numbers sat in a spreadsheet, never updating the central database. Now every submission enriches our primary Startup records without manual intervention. NEQ/BN numbers, changed website URLs and the headquarters address update the central Startup card, patent counts update IP tracking, and newsworthy highlights are forwarded to the Communications team.

I could also run the cleaning scripts retroactively on years of historical data, significantly improving data quality across the entire dataset.

I kept humans in the loop at key moments. Full automation was technically possible; I chose against it. The process emails hundreds of busy founders, and unnecessary emails damage the organization's reputation and train people to ignore future messages, so a quick IT review before triggering the email cascade is worth the extra step.

The two checkpoints cost the team minutes per cycle, and they prevent the expensive mistakes: emailing a founder whose startup already left, or triggering the sequence before stream leads have validated the list.

I left D3 in January 2026. 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 pass on Podio's quirks and the design decisions embedded in the system.

My employment ended in August 2025, and a follow-up contract carried me to January 2026. She ran the next two quarters of the quarterly system without a hitch, and it is still running exactly as designed.

This project taught me to design the entire journey: all four user types, failure modes included. The old check-in's technology worked fine; no one had designed the experience of participating in it.

The shift from taking to giving changed how I think about organizational processes: a process that asks people for their time should give something back. The Nutrition Labels cost me development hours and repaid them in response rate, as founders went from being chased to submitting on their own.

The accidental database deletion helped more than it hurt. It gave me a blank canvas and permission to rebuild with intention instead of patching what existed.

Keeping humans in the loop was a design decision I would make again. Where the stakes involve hundreds of founder relationships, a person should review before the system acts.

The Check In Suite has outlived my time at D3. For a service design, that is the result I care about most.