Introduction
Operations practitioners keep Skylight running smoothly. They coordinate the schedules, logistics, and communications leaders depend on, and they run and improve the internal operations and processes the company relies on day to day — turning recurring work into systems that stay reliable, traceable, and easy for the next person to pick up. Their reach is internal: when operations run well, every other function spends less time on friction and more on its mission.
Core craft
Execution and follow-through
Seeing day-to-day operational tasks and projects through to completion, following up consistently, and tracking upcoming work so commitments are met
Coordination and logistics
Organizing schedules, meetings, travel, events, and cross-stakeholder work so people's time is protected and the right people act at the right time
Documentation and records
Keeping records, trackers, notes, and system data accurate, current, and well-organized, with careful quality checks so others can rely on them
Operational visibility and risk
Keeping an accurate view of how operations are going — spending against budget, staffing changes, compliance status, reporting accuracy — and raising risks early with the context to act on them
Process improvement
Identifying friction in how operational work gets done and proposing practical improvements that reduce rework and ambiguity without adding bureaucracy
Governance and discretion
Following change-control, governance, and documentation standards so operational changes are recorded and can be reviewed, and handling sensitive information confidentially, with access limited to those who need it
Coordinator
Keep recurring operations, scheduling, and logistics running reliably under direction.
- Scope: what you decide and own
- Carries out routine operational and coordination tasks under direction; follows established processes
- Relationships: working with stakeholders
- Handles routine scheduling, logistics, and communications; escalates anything non-routine
- Reach: what changes because of you
- Keeps recurring operations and logistics running reliably
- Calibration question
- Can they reliably execute routine operational tasks and coordination with close direction?
What success looks like
- Executes routine coordination, scheduling, and logistics with reliable follow-through
- Communicates clearly and escalates non-routine items appropriately
- Keeps calendars, trackers, and logs current and accurate
- Handles sensitive information with discretion and limits access to those who need it
Example outcomes
- A leader's calendar and recurring commitments kept current so nothing slips
- Travel or meeting logistics coordinated cleanly with a low error rate
- A shared tracker kept up to date so the team works from accurate information
Associate
Develop foundational operational skills while supporting the function.
- Scope: what you decide and own
- Executes defined operational tasks with guidance
- Relationships: working with stakeholders
- Responds to internal requests with guidance; contributes to operational documents and trackers
- Reach: what changes because of you
- Completes operational work reliably with minimal rework
- Calibration question
- Can they reliably complete assigned operational tasks with minimal rework?
What success looks like
- Executes defined operational tasks with reliable follow-through and little rework
- Produces clear operational documentation and keeps trackers accurate
- Implements feedback without repeated rework
- Collaborates effectively with internal stakeholders and asks for help at the right moments
Example outcomes
- An operational task or recurring process completed cleanly without follow-up corrections
- A tracker or document built and maintained so others can rely on it
- A logistics or coordination request handled end-to-end with guidance
Level I
Own a well-scoped recurring process or coordination area.
- Scope: what you decide and own
- Decides approach for well-scoped operational work; owns a recurring process or coordination area
- Relationships: working with stakeholders
- Builds solid working relationships with internal counterparts; communicates progress and risks clearly
- Reach: what changes because of you
- The operations they own run reliably and on time
- Calibration question
- Can they be trusted to own a well-scoped operational area without close oversight?
What success looks like
- Decides the approach for well-scoped operational work and owns a recurring process or coordination area
- Keeps the operations they own running reliably and on time
- Keeps documentation and systems clean enough that others trust them as the source of truth
- Communicates progress, blockers, and risks clearly to internal counterparts
- Surfaces basic operational risks early with enough context to act on
Example outcomes
- A recurring process owned end-to-end with fewer errors or less rework than before
- A tracker or workflow tightened so other teams can use the data with confidence
- An operational risk flagged early enough that a stakeholder adjusted without disruption
Level II
Lead an operational process or area end-to-end, including the ambiguous parts.
- Scope: what you decide and own
- Decides approach for ambiguous operational problems; owns an operational process or area end-to-end
- Relationships: working with stakeholders
- Proactively manages internal-stakeholder expectations; produces clear operational documents that stakeholders can use without heavy revision
- Reach: what changes because of you
- Their work measurably improves an operational process they own
- Calibration question
- Can they own ambiguous operational work end-to-end without escalating?
What success looks like
- Decides the approach for ambiguous operational problems and owns a process or area end-to-end
- Makes sound tradeoff decisions on approach, scope, and sequencing without escalating routine choices
- Produces operational documents that stakeholders can use without heavy revision
- Measurably improves an operational process they own
- Builds visibility, QA, and traceability into the work rather than bolting them on
- Mentors Coordinators and Associates through pairing and review
Example outcomes
- An operational process redesigned to measurably reduce errors, rework, or turnaround time
- A reporting or compliance workflow restructured so risks surface earlier and cleaner
- An onboarding or intake process rebuilt and adopted across the function
- A cross-function coordination effort owned end-to-end through real ambiguity
Senior
Own an operations area or capability the company depends on.
- Scope: what you decide and own
- Makes consequential operational tradeoffs; owns an operations area or capability the company depends on
- Relationships: working with stakeholders
- Reframes operational problems into clear choices for leadership; aligns internal stakeholders on operational change
- Reach: what changes because of you
- Operations are measurably more reliable or efficient because of decisions they made
- Calibration question
- Would operational quality or reliability slip if they stepped away?
What success looks like
- Sets the approach for an operations area or capability and makes the consequential tradeoff calls under real constraints
- Aligns internal stakeholders on operational change and keeps it moving
- Reframes messy operational situations into clear choices for leadership
- Improves operational reliability or efficiency through decisions they made, not just work they delivered
- Mentors Coordinators and junior practitioners through review, pairing, and direct coaching
- Strengthens the area's operational judgment alongside their own work — QA standards, escalation habits, documentation practice
Example outcomes
- An operations area run measurably more reliably or efficiently because of decisions they made
- An operational standard or system the area adopted that caught problems earlier
- A consequential tradeoff — what to automate, what to standardize, what to retire — that held up under pressure
- A junior practitioner who grew measurably under their mentorship into independent ownership
Staff
Set operational direction across functions.
- Scope: what you decide and own
- Sets operational direction across functions; owns operational standards, systems, or process strategy
- Relationships: working with stakeholders
- Gets functions pulling in the same direction on operational change; resolves organizational blockers no single function can clear
- Reach: what changes because of you
- Multiple functions run better because of the operations systems or standards they put in place
- Calibration question
- Would cross-function operational quality or standards slip if they stepped away?
What success looks like
- Sets operational direction across functions — not just within one area
- Establishes operational standards, systems, or process strategy adopted across functions
- Identifies systemic operational gaps no single function would see and addresses them
- Resolves cross-function operational tradeoffs and blockers no single function can clear
- Influences company-level operational strategy with leadership
- Mentors operations practitioners across functions and grows Seniors into cross-function thinking
Example outcomes
- An operational standard or system adopted across multiple functions that reduced duplicate work or errors
- A process-strategy change that smoothed how work moves across finance, contracts, people ops, and delivery
- A systemic operational gap surfaced and closed that no single function had owned
- A cross-function operational conflict resolved, unblocking stalled work and restoring momentum
Principal
Reframe how Skylight operates at the company level.
- Scope: what you decide and own
- Reframes how Skylight operates at the company level, diagnosing root causes with leadership; shares ownership of Skylight's operational health and growth
- Relationships: working with stakeholders
- Trusted authority on company operations; aligns leadership around operational direction and earns their buy-in
- Reach: what changes because of you
- How the company operates is materially better because of their direction, and Skylight is stronger for it
- Calibration question
- Would Skylight's operating model be on a different path if they hadn't been here?
What success looks like
- Reframes how Skylight operates at the company level, diagnosing root causes rather than treating symptoms
- Shapes the company's operating model and operational direction
- Aligns leadership around operational strategy and earns their buy-in
- Guides major operational tradeoffs across the company — what to centralize, standardize, invest in, or retire
- Contributes to Skylight's Operations practice area through hiring, leveling, craft standards, and developing Staff-level practitioners
- Contributes to Skylight's growth and health by helping operations scale to support new work or expanded capacity
Example outcomes
- An operating-model change adopted across the company that materially improved how it runs
- An operational strategy that let Skylight scale capacity or take on new work without proportional friction
- A company-wide operational standard or career framework adopted across the Operations practice area
- Leadership adopting a different operational direction because of a Principal-led diagnosis