JB
Menu
Jamie Burkart at the East River shoreline beneath the Manhattan Bridge.

Technical Project Manager - Product Operations & Implementation

Jamie Burkart

I help emerging work become usable systems.

I work with public-facing teams to clarify requirements, build workflows and tools, carry context through implementation, and leave behind documentation people can use.

View selected workView resume

At the East River beneath the Manhattan Bridge, 2022.Photograph by Elana Gordon. From Jamie Burkart's photo archive.

Start here

Quick path through the portfolio

New to my work? These pages give the clearest route through the site for hiring managers, referrers, civic-tech peers, and collaborators.

Technical Operations & ImplementationThe fastest role-fit proof surface for public-sector technical operations, product operations, implementation, and delivery coordination.Harry J. Epstein CompanyLegacy e-commerce, analytics, content, marketing, and operations modernization.FairRentNYC / Commercial Rent StabilizationCampaign memory, source maps, public-data framing, and coalition operations.CallNYC.orgCivic open data translated into resident-facing guidance.ResumePDF for applications and hiring workflows.

Selected proof points

  1. 01

    14+ years creating operating structure

  2. 02

    Jamie's e-commerce and operations improvements contributed to 2x revenue growth

  3. 03

    Jamie built and stewarded 30+ pages of campaign memory for shared decisions and next steps

  4. 04

    Jamie co-founded and co-built WOW List as a natural-language community platform

  5. 05

    Jamie created participation systems supporting 300+ gatherings and 20+ resident artists

Capabilities

What becomes usable

  1. 01

    Technical project management

    Requirements, workflows, status rhythms, risk notes, implementation plans, quality assurance, user acceptance testing, and handoffs.

  2. 02

    Product operations

    Planning systems, decision logs, feedback loops, launch support, adoption materials, and operating memory.

  3. 03

    Knowledge systems & documentation

    Source maps, meeting synthesis, public guidance, resource libraries, templates, and reusable reference systems.

  4. 04

    Civic technology & open data

    Public-facing tools, data translation, policy explainers, campaign hubs, and resident/community guidance.

  5. 05

    Web systems & public-facing tools

    Maintainable websites, e-commerce workflows, community platforms, and low-cost public infrastructure.

  6. 06

    Community systems

    Onboarding, facilitation, hospitality, artist support, recurring gatherings, and continuity systems.

Selected systems

Proof across operating, civic, and community systems

These projects show a recurring pattern: emerging, high-context work becoming usable systems, public-facing tools, documentation, decision trails, and durable handoffs.

View all work
Harry J. Epstein Company storefront showing product search, editorial artwork, video, navigation, and commerce controls.
The maintained public storefront brings discovery, editorial voice, customer guidance, and ordering into one system. Public website capture, July 2026.

Operating Structure

2009-2015

Full case studypublic-safe

Harry J. Epstein Company

E-commerce and operations modernization

Led web, e-commerce, analytics, content, marketing, and operational improvements that helped an 80+ year-old industrial business modernize without losing its trusted voice.

What was emerging
A legacy business had public voice, customer trust, inventory knowledge, and operating habits that did not automatically translate into modern e-commerce workflows.
What became usable
Improved web, e-commerce, analytics, marketing, content, and operational systems that supported online growth while preserving the company's distinctive institutional voice.
Read case study
Organizers, artists, and public officials hold a hand-painted Save NYC Spaces and NYC Artist Coalition banner in front of a packed Market Hotel room.
A collective Save NYC Spaces town hall at Market Hotel, October 11, 2017. Photograph by Paul Mossine. From Jamie Burkart's photo archive.

Civic Systems

2017-Present

Full case studypublic-safe

NYC Artist Coalition / FairRentNYC

Cultural-space advocacy, coalition memory, and Commercial Rent Stabilization

As a founding member and organizer of NYC Artist Coalition, implemented and maintained campaign websites and helped build coalition memory, source maps, and coordination infrastructure for cultural-space advocacy, FairRentNYC, Commercial Rent Stabilization, and storefront stability.

What was emerging
The work involved many stakeholders, public/private source materials, legal and policy questions, city/state strategy lanes, shifting meetings, and sensitive coalition context that could easily become fragmented or overexposed.
What became usable
Recurring cultural-space meetings, public event pathways, practical safety and legal sessions, town halls, hearings, campaign actions, running minutes, action trackers, source maps, public campaign websites, and shared campaign memory.
Read case study
Archived CallNYC prototype showing issue navigation, resident guidance, and a Council member service profile.
The archived prototype translated civic data into issue pathways, district context, and resident guidance. Archived public prototype capture, July 2026.

Civic Prototype

2016 - archived

Full case studypublic-safe

CallNYC.org

Civic data to resident-facing guidance

Built an independent civic-data follow-on translating CouncilStat constituent-services records into resident-facing issue pathways and next-step guidance.

What was emerging
Constituent-services data existed, but residents needed a clearer public-facing pathway from issue to relevant civic office or next step.
What became usable
An archived civic-tech prototype that organized open data into issue pathways, district context, and resident-facing guidance.
Read case study
WOW List landing page over a photograph of people gathered around a table, with the words being there changes everything.
WOW List's current threshold pairs its returning interface with a photographic scene of people gathering. Public website capture, August 13, 2026.

Community Platform

2010s; public return in progress, 2026

Short proof pagepublic-safe

WOWList.org

Natural-language community infrastructure for arts and music organizers

Co-founded, co-built, and operated a natural-language community-calendar platform for DIY arts and music organizers. A July 2017 production snapshot records 1,846 users, 16,142 posts/events, and 35 city-region keys with at least 50 posts.

What was emerging
DIY organizers needed lightweight ways to distribute events and maintain community visibility across scenes without relying on one centralized editorial calendar.
What became usable
A natural-language, collaboratively editable event system that turned community vocabulary into followable keyword calendars and organizer-facing distribution workflows.
Read case study
A person stands at a crowded dinner table, raising one hand and holding up a sheet of paper as others laugh beside a hand-drawn map.
A Sunday Dinner gathering with a hand-drawn map and shared table, January 6, 2013. From Jamie Burkart's photo archive. Photographer not identified in the retained export.

Participation Infrastructure

2010s-present

Short proof pagesummary-only

196 Artists Residency / Sunday Dinner

Hosting, onboarding, facilitation, and continuity systems

Created repeatable hosting, onboarding, facilitation, documentation, and continuity systems across 300+ gatherings and 20+ resident artists.

What was emerging
A recurring cultural space needed trust-building routines, invitations, hospitality, artist support, and continuity without turning private community records into public spectacle.
What became usable
Repeatable participation infrastructure for gatherings, resident artists, onboarding, facilitation, and handoffs.
Read case study

Operating motif

Structure grows from the material

The projects differ, but the move is consistent: clarify what is known, protect what should stay private, and leave behind material people can act on.

  1. 01

    Emerging stakeholder context

    shared decision records

  2. 02

    Public data awaiting translation

    civic guidance and source maps

  3. 03

    Long-running operations

    maintainable e-commerce workflows

  4. 04

    Recurring community gatherings

    repeatable participation infrastructure

How I work

Listen. Map. Build. Document. Transfer.

I usually enter when the work is important but loosely defined. I listen across stakeholders, map what is known and unknown, create the workflows or documentation the team needs, support launch or adoption, and leave behind materials that make the work easier to maintain.

Next conversation

Looking for technical project management, product operations, implementation, or knowledge-systems support?

Email Jamie about roles, referrals, bounded consulting work, or collaboration.

View resumeEmail Jamie