Leading a High-Trust Public Memorial Platform
As Frontend Team Lead with engineering-manager responsibilities, I rebuilt team capacity, strengthened accessibility and quality, and helped steward a live veterans memorial platform—work later recognized in a ceremony by the VLM VA Director.
Most software helps people complete a task. The Veterans Legacy Memorial helps preserve lives, service, photographs, documents, and family memories so future generations can remember the people behind the records. That changes what good engineering means. Accessibility is not merely compliance, reliability is not merely uptime, and a regression can affect how a family experiences someone they never want forgotten. When I joined Keeper Memorials as Frontend Team Lead, I stepped into a role with engineering-manager responsibilities across people leadership, hiring, delivery, technical direction, quality, and stakeholder coordination. I inherited a live platform, an evolving architecture, and a small team rebuilding after the previous lead had departed. My job was not simply to deliver software; it was to help create an engineering team worthy of the trust the platform represented.
The transformation at a glance
Rebuilding capacity while protecting a live public platform
- 01Live platformPublic memorial experiences already serving families and communities
- 02Leadership transitionThe previous lead departed and two relatively new engineers remained
- 03Team rebuiltI onboarded another engineer while completing my own government onboarding and platform ramp-up
- 04Trust strengthenedPairing, mob sessions, 1:1s, retrospectives, planning, empathy, and patience
- 05Delivery improvedRegressions fell, administrative capabilities shipped, and collaboration became calmer
How trust grew
Trust is built through repetition
+ team cohesion
High-trust engineering
Principles that guided the work
- Accessibility is product quality
- Reliability protects trust
- Careful delivery matters
- Simplicity over unnecessary abstraction
- People deserve context, not just tickets
Accessibility journey
One memorial, accessible across devices and abilities
The goal was not merely to satisfy a checklist. The same memorial experience needed to remain understandable and usable across devices, keyboard navigation, assistive technology, and different generations of visitors.
The impact path
Inherited
The Veterans Legacy Memorial was already live and preserving veterans’ service histories, photographs, documents, and family-contributed memories when the previous technical lead departed.
Owned
I stepped into the technical-leadership gap, set direction and delivery priorities, and remained hands-on in implementation, architecture, accessibility, and quality decisions.
Changed
I first learned where the system and responsibilities lived, including the evolving architecture, government processes, frontend patterns, and cross-team dependencies.
Result
< 2 months — Administrative platform delivery
What I inherited
The problem and the reality around it
The problem
- The Veterans Legacy Memorial was already live and preserving veterans’ service histories, photographs, documents, and family-contributed memories when the previous technical lead departed.
- The platform was live, but the underlying architecture was still evolving, and only two Keeper developers remained; both had joined the project only a few months earlier.
- I needed to complete extensive government onboarding, learn an unfamiliar codebase and Chakra UI, establish technical credibility, rebuild team cohesion, and help another incoming engineer ramp up without slowing public-platform delivery.
The constraints
- Section 508 accessibility requirements and a visitor population spanning devices, generations, and abilities.
- Sensitive public-service context, emotionally significant content, and careful data handling.
- Cross-organization dependencies, government clearance and onboarding, and an established live codebase.
- A small, flat organization where my official Frontend Team Lead title carried people leadership, hiring, delivery, quality, technical direction, and stakeholder-coordination responsibilities.
What I owned
My responsibility in the work
I stepped into the technical-leadership gap, set direction and delivery priorities, and remained hands-on in implementation, architecture, accessibility, and quality decisions.
I onboarded another engineer while simultaneously ramping up on the platform myself, helping rebuild team capacity during a leadership transition.
I coordinated across engineering, product, design, the internal government team, and platform stakeholders while making delivery risks and technical decisions understandable.
I treated accessibility, reliability, and regression prevention as core product responsibilities because families and communities trusted the platform with veterans’ legacies.
How I approached it
Decisions, tradeoffs, and delivery
I began by understanding the system and the reality around it. I completed extensive government onboarding, learned the existing architecture and Chakra UI patterns, and evaluated technical choices based on the value they created rather than treating them as fixed. Chakra remained useful where it supported consistency, but I chose simpler implementations where the abstraction added complexity without benefit. At the same time, I strengthened testing expectations, clarified work, made risk visible, supported accessibility improvements, and helped the team deliver administrative capabilities in under two months. The guiding principle was care: simplify thoughtfully, protect the live experience, and remember that Section 508, quality, and reliability existed for real people—not for a checklist.
- I first learned where the system and responsibilities lived, including the evolving architecture, government processes, frontend patterns, and cross-team dependencies.
- I evaluated Chakra UI pragmatically, keeping it where it created consistency and choosing simpler approaches where the abstraction added complexity without corresponding value.
- I built trust gradually through pairing, mob sessions, regular 1:1s, retrospectives, collaborative planning, virtual team-building, humor, compassion, empathy, and patience.
- I strengthened testing expectations, clarified work, surfaced risk earlier, supported Section 508 improvements, and encouraged reusable frontend patterns without treating existing choices as unquestionable.
- I led delivery of new administrative capabilities in under two months while the team continued supporting the public memorial experience.
- I helped create a calmer and more collaborative relationship among groups that depended on one another to maintain and evolve the platform.
How I led
The team and stakeholder system
The greatest leadership challenge was trust. I arrived after a lead transition, joined a small team whose members were still learning the platform, and needed to establish credibility while one engineer had also hoped to lead. I did not try to solve that through authority. Trust accumulated through pairing, mob sessions, 1:1s, retrospectives, planning sessions, virtual team-building, humor, compassion, empathy, and patience. Even while completing my own extensive onboarding, I helped another newly arriving engineer get established on the project so the team could regain capacity more quickly. Over time, technical conversations became healthier, collaboration across Keeper and government stakeholders became calmer, and the engineers grew into a more confident group that could challenge ideas respectfully and share ownership of the platform.
Results
What changed
< 2 months
Administrative platform delivery
My team delivered the administrative platform in under two months while continuing to support the live public platform. · Team outcome
50%
Regression reduction
Regression volume fell by half during the first three months of the engagement. · Shared outcome
2 → 4
Engineering team growth
I helped rebuild and grow the Keeper engineering team from two to four contributors. · My contribution
Ceremonial coin
VLM VA Director recognition
During a ceremony, the VLM VA Director—a decorated veteran—presented me with a Medal of Honor coin and praised my leadership and accomplishments on the platform. · My contribution
Leadership evidence
How I moved the people system
- — I earned trust through consistent collaboration rather than relying on title or authority during a leadership transition.
- — I rebuilt team capacity through simultaneous self-onboarding, onboarding another engineer, coaching, and shared technical work while maintaining delivery.
- — I created structure without losing empathy, helping a small team become more cohesive, confident, and collaborative.
- — I led at engineering-manager scope in a flat organization while remaining close to the code, quality work, and user context.
- — During a formal ceremony, the VLM VA Director—a decorated veteran—presented me with a Medal of Honor coin and publicly praised my leadership and accomplishments.
Technical evidence
How I moved the product system
- — Accessible frontend delivery and Section 508 improvements for a public platform serving visitors across devices and abilities.
- — Pragmatic Chakra UI decisions that preserved useful consistency without accepting unnecessary abstraction.
- — Reusable component and frontend standardization work inside an evolving established codebase.
- — Administrative and content-ingestion workflows delivered alongside ongoing public-platform support.
- — Stronger testing expectations, regression reduction, and reliability practices for emotionally significant public content.
Technical footprint
Technologies and system areas
What I took from it
The lesson I carry forward
This experience reinforced that software is ultimately about people. Sometimes those people are customers or teammates; sometimes they are families preserving the story of someone they love. High-trust products require leaders to move carefully, listen first, reduce risk, and protect confidence without becoming paralyzed by the stakes. My official title was Frontend Team Lead, but the work required the full scope of engineering management: developing people, setting technical direction, maintaining quality, coordinating stakeholders, and staying accountable for delivery. Being presented with a Medal of Honor coin by the VLM VA Director, a decorated veteran, was especially meaningful because the recognition came from someone who understood both the mission and the responsibility behind the platform. The experience reminded me that when software becomes part of someone’s legacy, every detail matters.
Related work · Frontend