Dayforce Studios - Marketplace and Application builder (HCM)

Dayforce Studios turning enterprise complexity into a system people could actually build with.

The real design win was transforming enterprise complexity into an intuitive, scalable experience where users could confidently create and build using AI prompts and low-code tools. The goal was simple: learn the system once, then apply that knowledge across the entire platform.

Key Skills & Tools

Lead Product Designer
User Research
Persona Development
Search & Discovery
Cross-functional Collaboration.
Claude Design

Inspect live solution

Dayforce customers wanted to do more than use what was already in the platform. They wanted to build their own experiences around the way their businesses actually worked. That sounds simple until you look at what sits behind even a basic employee request.

Thinking AI first changed how I approached the problem. Instead of designing each experience piece by piece, I started with what AI could assemble and configure, and designed the system around that. The job shifted from building screens to building the pieces and the rules that let customers and AI put them together in ways that fit how their business actually works.

The platform had plenty of power. The challenge was making that power easier to understand.

How it came together

Finding the structure inside the complexity

As Lead Product Designer, I helped shape the product model for Dayforce Studio, bringing clarity, structure, and an AI-first approach to an expanding ecosystem of capabilities. My contributions spanned product strategy, information architecture, interaction design, and systems thinking, with a focus on creating a scalable, intuitive platform that could evolve alongside emerging AI capabilities.

A key part of my work was establishing a clear purpose for each component of the platform. Pages enabled users to create forms, dashboards, documents, and other experiences. Templates supported reuse and consistency. Logic managed rules and conditions, while Widgets introduced modular functionality. Workflows supported approvals and multi-step processes, Plugins and Applications addressed specialized needs, and Integrations connected Dayforce to external systems.

Beyond defining these capabilities, I explored how AI first thinking could simplify complex interactions, accelerate creation, and reduce the effort required to build and manage experiences. The larger challenge was connecting these individual capabilities into a cohesive product experience—one that helped users understand how the pieces worked together and empowered them to move from ideas to functional solutions with greater confidence and efficiency.

Designing the relationships, not just the screens

A user might start with a Page, use a Template, add Logic, trigger a Workflow, and send information toanother system through an Integration. To the employee using it, that should feel like one smoothexperience. To the person building it, those relationships needed to be clear.

That shifted my focus from designing individual screens to designing the system around them.

I worked on ways to help users understand what they had created, what was connected, wheresomething was being used, what depended on it, and what might be affected if they made a change.The goal was to make the invisible structure of an application easier to see without exposing users tounnecessary technical complexity.

Designing for very different users

Studio also had to work for people with very different levels of technical expertise. Administrators andcontent creators needed simplicity. Developers needed flexibility. Employees and managers simplyneeded the final experience to work.

So the experience had to grow with the user. Someone could start with a simple Page, then add moreadvanced capabilities only when the problem required them. That idea of progressive complexitybecame an important part of how I approached the design.

Consistency mattered too. Creating a Page, setting up a Workflow, defining Logic, or configuring anIntegration should not feel like learning a different product every time. I helped establish reusablepatterns around setup, configuration, validation, dependencies, errors, previewing, and publishing.

The outcome

The result was a clearer foundation for Dayforce Studio - one that could support something as simple asa form or as complex as a connected enterprise application without making every user deal with all ofthat complexity at once.

The work helped turn a collection of powerful capabilities into a more coherent building experience:Pages gave users somewhere to start. Templates created reuse. Logic added intelligence. Workflowsmoved business processes forward. Plugins and Applications extended what customers could create.Integrations connected those experiences to the broader enterprise ecosystem.

For me, that was the real design challenge: translating how a complex platform technically works into amodel that makes sense to the person trying to build something with it.