Introduction
Product Management practitioners decide what a team should build next and why. They turn user needs, mission goals, and business constraints into a clear product strategy, then guide cross-functional teams to deliver it. They frame problems before reaching for solutions, prioritize outcomes over feature lists, and keep delivery moving toward measurable results for the people a service serves.
Core craft
Problem framing and product strategy
Defining the problem before the solution, and setting product direction, success measures, and a roadmap
Prioritization and delivery
Breaking work into shippable value, maintaining a prioritized backlog, and keeping the team delivering
User and evidence grounding
Grounding product decisions in user research, usage data, and discovery
Cross-functional team leadership
Leading a team of researchers, designers, and engineers without authority over them, and setting the team's working rhythm and tending to its health and practices
Associate
Develop foundational product skills while supporting a delivery team.
- Scope: what you decide and own
- Executes defined product tasks, with guidance — for example, writing user stories, prepping ceremonies, and maintaining the backlog
- Relationships: working with stakeholders
- Responds to stakeholder requests with guidance; contributes to shared product artifacts
- Reach: what changes because of you
- Completes product tasks reliably with little rework
- Calibration question
- Can they deliver defined product tasks reliably, with guidance?
What success looks like
- Maintains a clear, current backlog and writes clear, actionable user stories
- Preps and supports team ceremonies with reliable follow-through
- Grounds work in user value, participating in discovery and research sessions
- Communicates progress and priorities clearly to teammates
- Builds working relationships across disciplines and begins to understand how stakeholders are engaged
Example outcomes
- A backlog kept refined and current so iteration planning runs smoothly
- User stories that pass into development without major rework
- Interview notes synthesized into themes that help the team prioritize
- A first stakeholder demo delivered clearly and on schedule
Level I
Own a defined feature or backlog area and run it well.
- Scope: what you decide and own
- Decides the approach for well-scoped product work; owns a defined feature or backlog area within a larger product or initiative
- Relationships: working with stakeholders
- Builds solid working relationships with direct counterparts; communicates progress and priorities clearly
- Reach: what changes because of you
- The work they own is done well and on pace
- Calibration question
- Can they choose the right approach for well-scoped product work without close oversight?
What success looks like
- Decides the approach for well-scoped product work and owns a feature or backlog area
- Frames problems around user and mission outcomes, not just feature requests
- Maintains a prioritized backlog and defends prioritization rationale to the team
- Translates research and usage data into concrete product decisions
- Communicates progress, risks, and priorities clearly to direct counterparts
- Identifies and addresses team friction points that slow down delivery
Example outcomes
- A feature shipped to production that improves a user workflow
- A reprioritized backlog that moves the team toward higher-value work
- Research insights translated into backlog changes the team acts on
- A clearer release plan that reduces churn during delivery
- A risk surfaced early enough that the team adjusted course without missing a milestone
Level II
Own a product or major capability end-to-end.
- Scope: what you decide and own
- Decides the approach for ambiguous product problems; owns a feature, workstream, or capability end to end
- Relationships: working with stakeholders
- Proactively manages stakeholder expectations; facilitates planning, syncs, and reviews; produces client-ready product artifacts that land without heavy revision
- Reach: what changes because of you
- The product or capability they own delivers its intended outcome — such as a workflow that ships and improves task completion
- Calibration question
- Can they own ambiguous product work end to end and make the calls without escalating?
What success looks like
- Decides the approach for ambiguous product problems and owns a product or capability end-to-end
- Defines a product strategy with clear outcomes, success measures, and a roadmap
- Sequences delivery so the riskiest assumptions get tested first
- Produces client-ready artifacts — roadmaps, prioritization rationale, and release plans — that land without heavy revision
- Partners with research, design, and engineering to shape solutions, not just hand off requirements
- Evaluates whether shipped work actually improved the outcome
Example outcomes
- A capability shipped that delivers the improvement it was scoped to deliver — for example, higher task completion in a benefits or enrollment workflow
- An MVP defined and launched to users that validated a direction before heavy investment
- A roadmap that realigned the team's priorities toward a higher-impact part of the user journey
- Prioritization decisions defended to a skeptical agency stakeholder that held up under pressure
- A discovery effort that retired a planned feature the evidence didn't support
Senior
Own product strategy for a core area that others depend on.
- Scope: what you decide and own
- Makes the consequential product tradeoff calls; owns product strategy for a core area their operating context depends on
- Relationships: working with stakeholders
- Navigates competing priorities and turns messy situations in their area into clear choices for senior stakeholders; influences how the team approaches product questions
- Reach: what changes because of you
- Improves product outcomes in their area because of decisions they made, not just the work they delivered
- Calibration question
- If they stepped away, would the team lose product judgment, not just capacity?
What success looks like
- Sets product direction and strategy for a core area that other work depends on
- Makes consequential tradeoff decisions under real constraints — scope, timeline, technical debt, client or stakeholder pressure
- Connects user insight and mission goals into a coherent product strategy
- Aligns the delivery team and client stakeholders around prioritized outcomes
- Reframes problems for senior stakeholders and navigates competing priorities
- Leads the team through discovery, delivery, and learning across iterations
- Mentors junior and mid-level product managers through planning, reviews, and direct collaboration
- Strengthens the team's product judgment alongside their own work
Example outcomes
- A reprioritized roadmap for an eligibility or enrollment program that shifted investment toward the highest-impact work
- A consequential build-versus-defer decision that held up under client and delivery pressure
- A product strategy that aligned three stakeholder groups around a single prioritized backlog
- Improved task completion or reduced support burden after a Senior-led capability redesign
- Prioritization rituals or discovery practices the team adopted and kept using
Staff
Improve product outcomes across multiple teams or services.
- Scope: what you decide and own
- Sets product direction for their whole operating context; owns the operating models, prioritization frameworks, and standards it runs on
- Relationships: working with stakeholders
- Gets teams across their operating context pulling in the same direction on product priorities; clears blockers no single team can resolve
- Reach: what changes because of you
- Other product workstreams — and teams beyond their own — move faster or improve in quality because of the operating models, standards, or direction they put in place
- Calibration question
- If they stepped away, would the operating context lose direction, not just a strong contributor?
What success looks like
- Sets product direction across workstreams or teams
- Surfaces product issues that span teams and would otherwise go undetected
- Establishes operating models, prioritization frameworks, or standards that other teams adopt
- Resolves cross-team tradeoffs and organizational blockers
- Influences program-level strategy with client and Skylight leadership
- Mentors product managers across teams and strengthens cross-team product decision-making
- Maintains cross-team alignment on outcomes when delivery pressure, shifting priorities, or organizational friction threaten it
Example outcomes
- A product operating model adopted by multiple workstreams on a large engagement
- A shared prioritization framework that made cross-team roadmap decisions consistent
- A cross-team discovery effort that revealed a shared barrier and redirected several roadmaps
- A cross-team prioritization conflict resolved, unblocking stalled delivery and restoring momentum
- A reusable roadmap or intake process that other product managers adopted across the portfolio
- A product manager who developed cross-team product thinking after sustained coaching and mentorship
Principal
Shape product strategy across portfolios or mission areas.
- Scope: what you decide and own
- Decides, with client leadership, what the product should accomplish for part of the mission, cutting through the noise to diagnose the root problem; shares ownership of Skylight's own health and growth
- Relationships: working with stakeholders
- A trusted advisor to client leadership on product strategy who aligns stakeholders on the solution and earns their buy-in; a recognized voice in their field
- Reach: what changes because of you
- The client adopts a different approach to part of its mission because of their work, and Skylight is stronger for it
- Calibration question
- If they'd never been here, would the client's approach to its mission — or Skylight's growth trajectory — be on a different path?
What success looks like
- Reframes problems and influences how the client thinks about part of its mission
- Serves as a trusted product authority for client leadership and externally
- Identifies major opportunities to improve mission outcomes through product strategy
- Aligns client leadership around product outcomes and direction
- Guides major product tradeoffs across programs
- Contributes to Skylight's Product Management practice area through hiring, leveling, and craft standards
- Contributes to Skylight's growth through proposals, expanded scope with existing clients, or bringing in new opportunities
Example outcomes
- An agency program reorganized around a Principal's reframing of what the product should achieve
- A product operating model adopted across a portfolio that changed how multiple programs prioritize
- A winning proposal contribution or a new contract opened with an existing client
- Client leadership adopting a different approach to a mission outcome — for example, sequencing a phased rollout instead of a single launch — based on a Principal-led product strategy
- A Skylight-wide product craft standard, or a body of external work such as writing and speaking, that builds the practice area's reputation and pipeline