Senior Director, Head of Product Design.
Where design is going when people and agents ship together.
Family Man. Designer. Builder.
I’ve been shaped as both a designer and design leader by startups, agencies, and large enterprises, each one changing how I think about craft, product, and teams.








“I genuinely enjoy the process of learning, growing, and figuring things out. The greatest reward is seeing where that journey takes us and the opportunities it creates for all of us.”





Born in Terre Haute, IN. I grew up in Durango, CO and currently live just outside of Denver, CO.



































































A Grok bot and project context feed an Obsidian vault; Homebase turns it into my personal software.
Understand the customer, find the friction, and make an educated choice.













Create your personas from our data, per your new feature
Embed personas into your prototype
Iteratively launch persona reviews for feedback
A new PDLC where design, product, and engineering ship from the same prototypes.
It all starts with a rough idea or concept. From there you’ll create a PRD and attach it to a Jira ticket. Bring the Jira ticket into your IDE and it will begin building based on Circuit components, patterns, and page layouts.
I have a PRD for a new feature: Securing BYO Agents. Can you build a working prototype using our Circuit design system?
I'll build a prototype for Securing BYO Agents using Circuit components. Let me create the key flows: → Agent registration with certificate pinning → Policy assignment with compliance checks → Dashboard showing agent health & trust scores Using @jumpcloud/circuit for all UI. I'll start with the agent onboarding flow…
You’ve made enough progress on the concept and you want to share it out for an upcoming exec meeting, design review, or formal research study. Deploying to AWS is simple, and automatically puts the concept behind our company login. Only accessible for enabled customers, or internal employees.

Drop a prototype into a Userology study, let AI moderate the session, and get a synthesized read by end of day.
Try assigning admin access to a new teammate. Think aloud as you go.
Okay, I'd expect roles to be right here… yep, found it.
DiscoverabilityYou paused on the role dropdown. What were you expecting to see?
Honestly, I want to scope it by device group, not just pick a role.
Granular controlOn a scale of 1–5, how easy was that?
4.
Ease 4/5We have a confident view of the scope and level of effort associated with the initiative. Design starts to break apart the UI into components that Eng will implement and integrate the business logic. We’re also defining release milestones and GTM activities.
Covers the majority of our distinct component types — toasts, error messages, buttons, empty states, dialogs, modals, tooltips, placeholders, links, dropdowns, switches, radio buttons, status cards, etc. — each with its own dedicated reference file containing formulas and examples.
---name: ui-voice-and-tonedescription: Core UI voice & tone for JumpCloud product copy.--- # Voice- Clear over clever. Say the thing.- Active voice, present tense.- Sentence case everywhere, even buttons. # Tone by context- Empty states: helpful, never cute- Errors: own it, say what to do next- Success: confirm, then get out of the way # Words we avoid"simply" · "just" · "please" · "oops"
Design supports a mix of manual and automated tests and UI refinement.
Based on the launch type (Major, Minor, Critical) we’ll create and provide GTM materials for web pages, help documentation, and social channels. The project already holds the context: the PRD, the Jira epic, the prototype and the release notes. A docs agent turns that into the Knowledge Base article, ready for review.
Agents that run on a schedule or trigger.
Agents that run on a schedule or trigger.



Today the assistant answers. Ask for your users in a plain sentence and it runs the query, returns the table, and stops there. Everything past that — acting on a schedule, acting before anyone asks — is what we set out to design.


Two patterns, one platform. The Admin Bot takes a prompt and fans it out — Identity, Devices, SaaS Management, Reporting, Policy — each agent adding its vertical context before they converge on a single action. The JumpCloud Agent inverts it and runs on a trigger or a schedule instead of a prompt. It pulls a resource, acts, reports out to Slack, Jira, or email, and writes every run to an activity log.


Feedback on the Admin Bot release was very positive, so we were fairly sure our IT admins would also want extended agentic capabilities. To check that assumption, I led moderated customer interviews and used our research platform Optimal to send a 100-person survey to IT professionals who don’t use JumpCloud. Moderated sessions with admins, recorded and reviewed in Gong. The macOS lockout and password-reset workflow came up on its own.

A hundred IT professionals, none of them JumpCloud customers. They already use AI for writing and docs, troubleshooting, and product research. Most work somewhere with an approved list or no real policy at all. Sentiment skews positive and they say it has made them more productive.




Layout explorations for the Create Agent flow. The variations test how much structure the concept needs, from a full card layout down to a single natural-language prompt.




In Storybook’s left panel, the project is broken into consumable pieces for engineering. Engineers pull directly from this GitHub branch and build from those pieces.

Create an agent, set its triggers and schedule, review what it did.
It’s a great time to be a designer!




Jake Taylor · Senior Director, Head of Product Design