MethodMade

Studio

← Back to experience

Public service systems

Supporting a veteran memorial platform where reliability and care mattered

A public-service platform where technical work supported remembrance, family history, and legacy.

One of the most meaningful projects I worked on was the Veterans Legacy Memorial, a public web application that allows family members, loved ones, and communities to honor veterans by sharing resting place information, photos, documents, military history, and memorial content.

This was not just another web application. The platform carried emotional weight. The people using it were often interacting with memories, grief, family history, military service, and legacy. That meant the work needed to be technically sound, but also thoughtful. Reliability mattered. Usability mattered. Clear collaboration mattered.

I led a team of engineers responsible for maintaining the existing codebase, implementing new features, integrating new technologies, and working alongside an internal VA team. My role was both hands-on and leadership-focused: helping guide technical decisions, supporting the team, coordinating priorities, and keeping the work moving in a way that respected both the product and the people it served.

The project reinforced something I already believed: digital systems are not just tools. Sometimes they become part of how people remember, communicate, access information, or navigate important life moments. When that is true, the technical work has to be grounded in care.

How this applies

The same pattern shows up in smaller business systems too.

The scale may change, but the work still starts the same way: understand what is really happening, organize the moving parts, then build the next useful thing.

MethodMade translation

For a small business, that might mean clearer service pages, cleaner intake, better follow-up, usable documentation, or one practical automation.

1

Understand the real situation

Start by separating the visible problem from the actual workflow, people, tools, constraints, and risks underneath it.

2

Organize the moving parts

Turn the scattered pieces into a clearer map: what exists, what matters, what is missing, and what should happen next.

3

Build the next useful system

Create the practical next layer: a page, process, automation, document, or tool that can be understood and maintained.

Use this thinking for

  • Platform support
  • Careful feature development

Helpful when you need

  • Stakeholder coordination
  • Public-facing web applications

Often connected to

  • Accessibility-conscious thinking
  • Documentation and maintenance

Proof notes

Public-service contextVeteran-focused platformLeadership and collaboration

Next step

Want this kind of practical systems thinking on your project?

Start with a free Discovery Call or a paid Tech Checkup if you want help choosing the right next move.