Sample site by ANotSoI — fictional person, AI-generated photo. Demo only: fictional person created by ANotSoI to show a personal brand site. Back to Hire Me

Evan Pritchard (fictional person, AI-generated photo)

Evan Pritchard

Columbus, Ohio

Product Operations Manager — Release Systems, Cross-Team Delivery & Operational Metrics

I run release operations for two product lines at Northline Software, including the handoff from a signed contract to a working account. Unowned launch items slip, blocked work sits unnamed, and the Monday number drifts off the database. I put the checklist, the owner, and the query in one place, then I count the misses.

Contact

Placeholder links. Not monitored.

Experience

Three seats. Same job: name the owner, the date, and the number.

Product operations manager

Northline Software

March 2023 – Present · Columbus, Ohio

  • Two product lines kept two calendars, and launch items with no owner slipped. I put both lines on one release calendar and one checklist in Jira. Missed handoff items fell from 11 a quarter to 2.
  • Blocked implementation work sat on the board with no name on it. I mark the blocked item in Linear and put the owner in the Monday note. Median days a blocked item sat untouched fell from 9 to 4.
  • The weekly launch count in the spreadsheet drifted from the operations database. I publish a SQL check through Looker and quote that table in the Monday note. The number the room reads now matches the database.
  • Sales and support asked for status in side threads. I cut the Monday note to owners, dates, and blockers, on one page. The Tuesday status thread stopped.
  • Jira
  • Linear
  • SQL
  • Looker
  • Release trains
  • Notion

Senior operations associate

Fieldnote Systems

June 2020 – February 2023 · Remote

  • Signed contracts waited on a kickoff nobody had written down. I ran the kickoff the day the contract closed: owners, dates, and the first month in Notion. Time from signature to a staffed account fell from 18 days to 6.
  • The account team rebuilt status by asking around on Friday. I sent a recap off the board: done, next, blocked. Open questions carried into Monday dropped by about half.
  • Three account setups got reinvented every time. I wrote those three playbooks and linked them from the kickoff. New associates stopped chasing the same steps from the same three people.
  • Notion
  • Jira
  • OKRs
  • SQL

Business operations analyst

Westmill Office Group

August 2018 – May 2020 · Dayton, Ohio

  • The operations director's weekly volume numbers arrived in a deck nobody could audit. I replaced it with a volume and exception report from the order export. Exceptions named in the report got closed inside the week.
  • The monthly order export and the invoice export disagreed. I reconciled them and wrote down the three mismatch rules behind most of the gap. Unexplained variance fell under 1% of monthly order dollars.
  • Opening a regional account lived in one person's head. I wrote the steps, named an owner for each, and left the page where the team already worked. A new region no longer waited on that person being in the office.
  • SQL
  • Looker
  • Spreadsheets
  • OKRs

B.S., Information Systems, Riverbend State University, 2018.

Featured projects

Case studies from the same work. The write-ups on this demo are placeholders.

One calendar for two product lines

Constraint

Northline shipped two product lines from separate launch lists. Items with no owner went out late or not at all.

Impact

One calendar, one checklist. Missed handoff items fell from 11 a quarter to 2.

  • Jira
  • Release trains
  • Notion

Sample write-up

Sample write-up. The checklist names an owner and an exit check for every launch item. That is the whole system.

Contract to working account

Constraint

Fieldnote closed deals, then waited on a kickoff that existed only as a meeting someone might schedule.

Impact

Signature to a staffed account went from 18 days to 6, with owners and the first month on one page.

  • Notion
  • Jira
  • OKRs

Sample write-up

Sample write-up. A signed contract is not an account. The account starts when a person owns the first month.

The Monday table

Constraint

The launch count in the spreadsheet did not match the operations database, and the meeting argued about which one to trust.

Impact

A SQL check lands in Looker before the note goes out. The Monday number matches the database. Airflow runs the extract on a schedule so nobody is pasting rows at 8 a.m.

  • SQL
  • Looker
  • Airflow

Sample write-up

Sample write-up. If the sheet and the database disagree, the sheet leaves the meeting.

Tech stack

Tools I will actually open. Not a logo wall.

Planning & delivery

  • Jira
  • Linear
  • Notion
  • Release trains
  • OKRs

Data & reporting

  • SQL
  • Looker
  • Spreadsheets

Ops tooling

  • Airflow
  • Shared boards
  • Checklists

Methods

  • Written kickoffs
  • One-page status
  • Named owners
  • Exception reports

Writing

Notes I would send to my own team. Links on this demo go nowhere.

The Monday note is a product

· 4 min

If product, sales, and support cannot finish it before the coffee cools, it is too long.