JB
Menu

Technical Operations & Implementation

I create the operating backbone complex teams need to move: clear requirements, delivery rhythms, decision records, risk signals, onboarding materials, operating documentation, launch support, and durable handoffs.

Start with the decisions

These are the clearest public-safe traces of how I frame work, make it executable, verify what changed, and leave it maintainable.

Harry J. Epstein Company

How does recurring customer and team friction become a maintainable release?

Decision and action
Jamie translated the question into a bounded requirement, coordinated an incremental change, inspected the public customer path and available signals, then preserved ownership and next actions.
Inspectable artifact
Maintenance-to-handoff workflow specimen
What became usable
Repeatable patterns across product information, marketing, e-commerce operations, and customer follow-up.

FairRentNYC / Commercial Rent Stabilization

How can a coalition keep sensitive, shifting work recoverable without overexposing it?

Decision and action
Jamie separated public sources, protected context, open policy questions, decisions, and next actions across 30+ pages of shared campaign memory.
Inspectable artifact
Campaign-memory spine and source map
What became usable
Collaborators could recover decision context, review public evidence, and continue work across city and state strategy lanes.

CallNYC

How can administrative data become a pathway a resident can recognize and use?

Decision and action
Jamie organized constituent-services records around recognizable issues and possible next steps rather than requiring people to understand the source dataset first.
Inspectable artifact
Issue-page information architecture and public implementation
What became usable
A small, complete civic product with source data, issue pathways, public documentation, and explicit limits.

Capability evidence

Follow a capability to the project and public wording that support it. The links carry the case context, evidence, credits, and limits.

Delivery coordination

Turning unclear public-facing work into launchable plans, releases, and handoffs.

  • Cross-project operating patternJamie coordinates public-facing technical work from ambiguity to launch
  • Harry J. Epstein CompanyJamie led long-running e-commerce and operations improvements for a legacy industrial business
  • CallNYCJamie built an independent CouncilStat follow-on translating civic data into resident guidance
  • WOWListJamie co-founded and co-built WOW List as a natural-language community platform

Risk surfacing and decision clarity

Making open questions, public/private boundaries, and stakeholder next steps visible.

  • FairRentNYCJamie built and stewarded 30+ pages of campaign memory for shared decisions and next steps
  • FairRentNYCJamie mapped legislative source lineage so collaborators could review bill changes
  • KC Town HallSecured a $490,539 public funding award through a successful CCED proposal and presentation, then transitioned the project to a mission-aligned organization

Operating documentation people use

Converting meetings, source trails, and recurring practices into reusable working memory.

  • FairRentNYCJamie built and stewarded 30+ pages of campaign memory for shared decisions and next steps
  • 196 / Sunday DinnerJamie created participation systems supporting 300+ gatherings and 20+ resident artists
  • Source-Backed Team MemoryJamie is developing a bounded method for source-backed team memory

Public-facing launch and adoption

Shaping websites, prototypes, and community platforms so real audiences can act.

  • NYC Artist CoalitionJamie was a founding member and organizer who implemented and maintained campaign websites
  • NYC Artist CoalitionJamie built civic systems and coalition operations for NYC Artist Coalition
  • KC Spaces FundCross-channel identity and web infrastructure for KC Spaces Fund
  • CallNYCJamie built an independent CouncilStat follow-on translating civic data into resident guidance
  • WOWListJamie co-founded and co-built WOW List as a natural-language community platform
  • Harry J. Epstein CompanyJamie's e-commerce and operations improvements contributed to 2x revenue growth
Where the public evidence stops
Demonstrated here
Requirements framing, stakeholder translation, incremental implementation, public-facing systems, decision and source records, onboarding patterns, continuity, and handoffs.
Needs stronger public proof
An end-to-end bug and regression-test lifecycle, direct budget and resource authority, quantified Ops-to-Product prioritization, formal resident research, and product-level accessibility decisions.
Not claimed
Government employment, procurement authority, PMP certification, sole causation for collective outcomes, or any named leader's private view of this work.

Full operating practice

  • Coordinate delivery across concurrent projects and keep work moving from concept through public launch.
  • Track status, surface risks early, and name recurring blockers before they become patterns.
  • Build planning cycles, team rituals, decision frameworks, status reporting, and retrospectives.
  • Coordinate dependencies across product, engineering, security, legal, communications, contracts, and external stakeholders.
  • Onboard collaborators with handbooks, runbooks, operating documentation, source maps, and decision records.
  • Report team health, project status, and operational metrics with honesty about what is and is not working.
  • Improve working systems over time without overengineering.

Resume

Technical project management, product operations, implementation, documentation systems, civic technology, and public-facing tools.

Download resume PDF

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