Product Designer Priorities and Capacity Management

Product Designers work as managers of one, sequencing their own capacity across trio work, platform initiatives, and broader Upstream Studios responsibilities. This page provides guidance on prioritizing work and planning capacity.

For Product Designers working in Product Design, part of Upstream Studios.

Planning and managing capacity

Product Designers are assigned to a group as an equal member of the trio. The following guidelines help you sequence work and protect capacity for both production work and the upstream judgment that’s core to the role.

Product Designers

• Ensure cross-functional peers know about Upstream Studios assignments, such as platform initiatives, and what you’ll need from them to succeed.
• When a request would crowd out research, exploration, or trio strategy work, raise it as a capacity trade-off with your manager directly.
• Account for time off (yours and others’) during milestone planning.
• If you think you won’t complete your committed work on time, tell your manager and your trio as soon as you know. Early notice keeps the trade-off conversation open.
• Optionally, use UX issue weights to better understand your capacity and facilitate conversations with your Product Manager.

Product Design Managers

• If requested, help Product Designers set a baseline capacity for group and platform-assigned work each milestone.
• Give production work clear time-to-complete (TTC) expectations and due dates. Give strategy work measurable goals and checkpoints, paced by what the team is learning.
• Resolve team questions, concerns, and blockers quickly.
• As AI absorbs more routine production work, redirect the freed capacity toward discovery and strategic work.
• Ensure cross-functional partners understand a designer’s capacity includes discovery and strategic work alongside production work items, and are aware of potential dependencies.

Priorities

The highest-leverage work happens before a line of code gets written: validating the problem, starting with the flow before jumping to a prototype, and setting success criteria early. When more than one thing wants the same hour, this is the order.

Must do:

• Committed trio work for the current milestone: issues assigned with labels workflow::problem validation, workflow::solution validation, or workflow::design, next-milestone planning, and sharing progress through Upstream Forum, Slack, and design critiques. This is what you’ve committed to; it comes first.
• Anything blocking someone else: peer feedback requests and merge request reviews, including community contributions, where automated coverage doesn’t exist yet. Push for automated coverage in your domain so this shrinks over time.
• Exploration and vision work for large, holistic roadmap efforts, ahead of a specific solution being scoped. It’s the easiest thing to cut because no one’s waiting on it. That’s exactly why it needs protecting.

Should do:

• Tasks that improve understanding of users and their workflows (e.g. UX Scorecards).
• Issues in the current release milestone labeled Stretch, and Pajamas design system contributions (pajamas::define, pajamas::design, pajamas::build, or pajamas::integrate, and open ToDo blocks in Pajamas). Fill remaining capacity here before reaching further out.

Nice to do:

• Future release or Backlog milestone issues, community-labeled low-hanging fruit, popular issues with no milestones, and sharing your work externally. Pick these up when nothing above needs you.

Supporting Product Management

As strategic partners in trios, Product Designers provide insights into user needs and help identify both quick wins and larger strategic initiatives. This collaborative approach keeps design involved upstream, shaping planning discussions from the start.

UX Issue Weights

Issue weights are optional but useful for planning. They help Product Designers understand their capacity, evaluate the impact of time off, facilitate trade-off discussions with Product Managers, and identify teams needing more UX support.

Using UX Issue Weighting

1. Review upcoming issues and break down the work
2. Assign an issue weight using the provided chart. Collaborate with the Product Manager for clarity if needed
3. Record your issue weight using your team’s preferred method
   • List issues and weights in Google docs
   • Create a linked issue for the UX work and add a weight (close it after completion).
   • Use design-weight labels
4. Communicate your capacity and total issue weights when planning iterations or milestones
5. Review weights post-milestone to improve future planning accuracy

Additional Notes:

• Most UX issues, including research and Pajamas related issues can be weighted, if desired
• Consider visual reviews, meetings, and other non-weighted responsibilities when determining capacity
• Do not weight very small issues (less than 1)
• A weight of 8 or 13 indicates that the issue may be too large
• Add weights to unplanned work during a milestone and discuss trade-offs with the Product Manager

Milestone Capacity Template:

• Total weights completed last milestone: 10
• Average capacity (average of weights completed last 3 months): 10
• Estimated capacity for current milestone: 7 (use your average capacity and subtract planned time off)
• Total current weights: 10

UX Weight Definitions

View page source - Edit this page - please contribute.