Heuristics

• No release goes more than a day before getting out.

  • this unblocks Eng with “no stale code”

• If staffing is short, tag in product (ptt and tim) to handle some testing scope.

  • we can take notes and simultaneously improve the ops testing by being focused on intuition and UX instead of just functionality.

• More heads up to prod when deploys to ephemeral environemtns are up.

  • E.g., “Hey Tim im heading to gome to test this ledger thing if you want to jam or check it out this evening, if not it goes live after i give go/no-go”

• proactive signal rather than siloed responsiblities

  • this is just a CC more often than not. @'s are good

• If there aren't any tickets, we can fall back on our rituals to check in on what we might be missing.

loose KPIs

• SLAs: support-to-eng handoff ticket within X hours; bug triage within 24h; P0 fix ETA posted within 2h
• OPs will always issue X polish ticket and X bug ticket every week
  • We shouldn't really hold ourselves to a standard like this but some loose number to shoot for implies a focus on quality.
• CC product on sign offs every time
• There should be at least one release that product gets tagged on or brought into per week. We're never gonna get this perfect, but it shouldn't feel like stepping on toes and it shouldn't feel like escalating beyond an engineer. It should really feel like "additional eyes needed", "heads up", or "hat tip".

workflow agreements

• Product will write release notes with testing, polish, and improvements from Ops. The ideal flow here Ops is more involved in the shape, the feel, the look, and status of the product and the product team thinks a little more ahead. as a result ENG has more well scoped work to build and iterate.
  • This also means that we're looking ahead to support and features together instead of siloed

rituals

• Already have our bi-weekly one-on-ones.
  • check in on support, not only themes but if there is any way to bring users in for interviews or get in touch
• I probably need to get a monthly one-on-one with Max. Check in on her goals, talk about user. flows she has noticced, teach her other tools, get her degen-ing with some fundus to see the landscape.
• BI monthly product ecosystem jams: e.g., we agree on a product to go test with. A protocol or a wallet feature or a new hype app to go mess with together. weds after leaderhsip might be a good timeslot.