Website Launch Delegation Challenge
Overview
Website launches and new environment creation currently sit with Mark, creating a bottleneck. Offloading this responsibility is a recognized need, but the role has specific constraints that make delegation non-trivial.
Requirements for the Role
A successful delegate needs:
- Technical proficiency — launches involve infrastructure-level work, not just website content
- Attention to detail — errors during a launch can cascade quickly
- Active availability during the launch window — this is not a "set it and forget it" task; the person must be present and monitoring in real time
- Timezone alignment — problems often surface hours after the initial launch, so the delegate must be reachable during business hours (US Central)
Candidates Considered
| Candidate | Notes |
|---|---|
| Chris | Most technically capable option; concern is timezone (roughly UTC+5/6), meaning if a launch happens at 8 AM CT, issues surfacing at midday CT would hit while Chris is asleep |
| Avoque | Possible, but same timezone concern applies |
| Paul | Same timezone concern |
| Eshock / Jeff | Mentioned briefly; not evaluated in depth |
| Sally | Floated as an option; likely not the right fit technically |
No decision was reached. The timezone issue is the primary blocker for the most technically qualified candidates.
Key Tension
"It's not like you flip some switch and then hope it's all going to be good. You've got to be right there watching it."
— Mark Hope
The role requires someone who can be on-call and reactive during a US business day window, which conflicts with the availability of the team's most technical offshore members.
Status
Unresolved. Mark acknowledged the need to delegate but wanted more time to think through the right candidate. No owner assigned as of this call.
Related
- [1] — current owner of website launches
- [2] — internal ops context
- [3] — parallel delegation work happening with new hire Jacob