Skip to content
Know Jaden.Say hello
← All work

HOME-START / PRODUCT + ENGINEERING

From seven spreadsheets to a clearer way to work.

Turning a nonprofit’s volunteer coordination needs into a focused portal, with a migration plan that respects decades of existing records.

MY ROLE

Product manager · Triton Software Engineering

WHEN

September 2026 — ongoing

STATUS

In development

HOME-START · PRODUCT THINKING

Seven spreadsheets.
One clear workflow.

People first. Then the portal.
7spreadsheets informing the portal
9,000+volunteer contacts to protect
20+ yearsof existing records

01 / THE PROCESS

Begin with the people doing the work

Home-Start’s volunteer coordination work was spread across seven spreadsheets. Before defining a new interface, I led user research and feasibility conversations with the Volunteer Coordinator to understand the workflow those spreadsheets were supporting.

I translated the findings into a status-driven portal specification, user stories, and acceptance criteria for engineering and design. The goal was a shared definition of what needed to work, before the team invested in building it.

02 / THE PROCESS

Choose a smaller first release

The team already had a React, Express, and MongoDB codebase. Extending it offered a more direct route to an MVP than starting again. I deferred shift-matrix visualizations and calendar integration to a second version.

That decision reduced the projected delivery timeline by two to three weeks. This is a planning estimate, not a claim of time saved after launch.

03 / THE PROCESS

Protect the history before changing the workflow

A simpler interface should not come at the cost of losing institutional memory. The project needed to account for more than 9,000 volunteer contacts and over 20 years of records.

I worked with the Engineering Manager to settle the events, assignments, and historical wage-rate model before development. Making those relationships explicit early reduced the risk of a database rewrite later.

04 / THE PROCESS

Treat release decisions as product decisions

I identified that the main branch automatically deployed to the client’s production environment. Establishing a separate release branch created a deliberate boundary between development and the live service.

The work also includes weekly progress reviews with engineering and design leads, milestone tracking, and surfacing blockers across the 13-person project team. Those coordination tasks are part of getting a useful product into people’s hands.

05 / THE PROCESS

Where it stands

As documented in my resume, this engagement is ongoing. The concrete outputs so far are the product specification, acceptance criteria, scope decisions, data-model agreement, and release process.

The portal’s adoption and operational outcomes still need to be measured after delivery. Client records and internal project material are intentionally not reproduced in this case study.

SOURCES & FURTHER READING

Experience documented in my resume ↗

Written from project documentation and my resume. Updated October 2026.

NEXT STORY

Inventory

A personal inventory system that helps you find what you own, remember where it lives, and ask useful questions about it.