JumpCloud Leadership & Management

What’s a quotable hallmark of good management on your team — and how is it reinforced weekly? 

The work itself gets visibility through a layered cadence: two design-only regional critical reviews for both the Asia-Pacific region and the United States, where designers bring in-progress artifacts for craft feedback, one large cross-functional design review that surfaces work across our product, engineering and experience teams, and a business checkpoint where upper leadership sees what’s heading to market. Managers are expected to coach craft in the regional crits, not just run the calendar. Growth plans are revisited monthly against the work shown in those forums, so feedback compounds instead of getting saved up for performance season. The result is two reinforcing loops — peer feedback on the work in crits and consistent performance tracking through one-on-ones — so designers always know where they stand on both craft and growth.

Which forum or artifact keeps priorities obvious?

Our Global Priority List is the single source of truth for current, upcoming and backlog initiatives across every feature team. It gives everyone clear visibility into what they’re working on, how it's prioritized, and how it ladders up to the larger picture so designers aren’t guessing where their work fits. For individual growth, designers maintain artifacts that feed directly into performance reviews. Those get reviewed regularly during goal progress check-ins, where managers give feedback on direction, milestones and whether things are tracking. It keeps priorities legible at both ends: the company’s bets and each designer’s path inside them.

What part of the strategy excites people—and what metric shows progress?

The most energizing bet is that designers don’t just spec the product; they help build it. We’ve invested heavily in AI-augmented workflows — Cursor/Claude Code, prompt-driven prototyping and local agents — so designers can take an idea from sketch to working artifact in a day. The clearest signal so far is how quickly a problem gets in front of a customer in a testable form, down significantly from where we started. But it’s clear that the systems and pace are evolving faster than our measurement, and the team is actively working on better metrics that capture craft, code contribution and customer impact together.