About the Role:
Our events division, Banana Bar Crawl and a growing portfolio of themed crawl events, currently runs on the deep operational knowledge of one person. Your mandate is to change that. You will extract, document, and systematize how this business operates, build the delivery infrastructure (Asana-based work management, SOPs, staffing playbooks), and then run it. Within 12 months, the business should be able to execute a full event cycle without escalating routine decisions to the Head of Events.
This is a build-and-run role. Roughly half of your first six months is systems construction; the balance shifts to steady-state operations management as the machine comes online.
What You'll Do
Build (months 1–6, ongoing thereafter)
- Work directly with the Head of Events to capture the full operating model, vendor relationships, venue logistics, staffing patterns, timelines, pricing mechanics, failure modes, and convert it into documented, repeatable processes.
- Design and implement the work management system in Asana (or equivalent): intake, project templates per event type, dependencies, staffing assignments, and delivery checklists.
- Create the SOP library: event run-books, staff onboarding materials, vendor coordination procedures, escalation paths, and post-event closeout processes.
- Establish the reporting cadence: pipeline status, delivery performance, staffing utilization, and per-event retrospectives delivered to the Head of Events on a fixed schedule.
- Run (ongoing) ● Own the intake pipeline: take direction, new events, and priorities from the Head of Events and translate them into structured, scheduled, resourced work.
- Manage day-to-day delivery across all events, schedules, task completion, blockers, and quality, ensuring everything ships on time.
- Directly manage event staff: daily direction, scheduling, performance feedback, and coordination. Staff answer to you on operational matters; the Head of Events sets priorities through you.
- Report delivery status, risks, and completions to the Head of Events; flag anything requiring strategic or commercial decisions early.
- Continuously improve the system: every event should make the playbook better.
What Success Looks Like
- 90 days: Asana pipeline live for all active events; first version of core event run-book documented; staff operating from the system rather than ad hoc direction.
- 6 months: A new event type can be stood up from templates without inventing a process from scratch; weekly reporting is routine; the Head of Events is out of day-to-day task management entirely.
- 12 months: A full event cycle, intake through closeout, runs without escalation of routine operational decisions. If you took two weeks off, the documentation would carry the team.
What You Bring
- 5–8 years of operations, delivery, or project management experience, including direct people management.
- Demonstrated experience building operational systems from scratch, not just working within them. You have stood up a PM tool for a team, written the SOP library, or systematized work that previously lived in one person's head. Be prepared to walk through a specific example.
- Fluency with modern work management platforms (Asana, Monday.com, ClickUp, or similar) at the level of designing workflows, templates, and automations, not just completing assigned tasks. ● Strong written documentation skills. The run-books you write are a core deliverable, not an afterthought.
- Comfort managing part-time and event-based staff, including scheduling around evening and weekend event delivery. Strong assets
- Events, hospitality, nightlife, or tourism operations experience.
- Experience taking over responsibilities from a founder or key operator.
- Familiarity with basic reporting/analytics (spreadsheet modelling, dashboard building).
