Case Study

ciro

A staffing ecosystem that evolved through three generations, from separate products to a unified workforce platform now serving 4,000+ healthcare facilities nationwide.

Role

Brand Strategy, Product Design Leadership, Design Systems

Industry

Healthcare Staffing, Enterprise SaaS

Context

Enterprise Workforce Management Platform

Audience

B2B, B2C

Platform

Web

Medical Solutions' staffing business began as a set of separate products: one for MSP and travel staffing, another for local and PRN work, more for affiliates and clinicians. ciro became the ecosystem that connected them, then evolved again as the business strategy matured into the enterprise workforce platform it is today.

Design System

ciro UI is the component-driven system that carried the product through each generation of the ecosystem: 10 foundational primitives, 19 reusable elements, and 27 application-level components, documented and maintained in a living Figma library so a change in business strategy meant a rebrand, not a rebuild.

ciro UI design system table of contents in Figma, showing Foundations, Elements, and Application Components sections

Impact

Medical Solutions' staffing business began as a set of separate products: one for MSP and travel staffing, another for local and PRN work, more for affiliates and clinicians. ciro became the ecosystem that connected them, then evolved again as the business strategy matured into the enterprise workforce platform it is today.

ciro isn't one product. It's three generations of one, each shaped by the strategy that came before it.

Medical Solutions' staffing business grew the way most healthcare staffing businesses do: one product at a time. Separate experiences supported MSP and travel staffing, local and PRN and shift-based work, the affiliate agencies supplying talent, and the clinicians and healthcare clients on either side of every placement. Each solved a real problem. None were built to talk to each other. As the business expanded digitally, the constraint stopped being inconsistent interfaces and became something bigger: a product strategy capable of holding an increasingly complex healthcare staffing ecosystem together.

ciro became that strategy: an umbrella product brand connecting four distinct experiences instead of four disconnected applications. ciro Clinician carried job discovery, applications, onboarding, assignments, pay, benefits, timekeeping, and career management. ciro Talent Management gave healthcare organizations a way to manage jobs, candidates, approvals, and placements. ciro Shift Management served local, PRN, gig, and shift-based staffing. ciro Affiliate supported the partners supplying and managing talent. One ecosystem never meant one generic experience: clinicians, healthcare organizations, and affiliates have fundamentally different goals, so the work was building the experience strategy, the shared design system, and the cross-functional governance that let four audience-specific products feel like one connected platform, backed by a design organization that grew from 3 people to 12 to support it.

The name carried the strategy. ciro (see-roh) takes its name from the Italian form of Cyrus, itself derived from Helios, the sun, a deliberate metaphor for a product built around its users rather than around any one of them: clinicians, healthcare organizations, affiliates, and internal teams each experiencing the same ecosystem through a different lens, all of it orbiting a shared center.

That architecture was tested when new executive leadership brought a different product and brand strategy. ciro didn't go away, but what it represented changed. The clinician experience moved back under the flagship Medical Solutions brand, and ciro refocused specifically on healthcare organizations and workforce management, its visual identity brought closer to the Medical Solutions master brand to strengthen the relationship between the enterprise product and the company behind it. The previous strategy wasn't wrong. It had simply done its job: the product and design architecture underneath it was resilient enough to evolve as the business itself did.

That refocus became the platform ciro is today. Rather than asking healthcare organizations to navigate separate tools for separate categories of labor, ciro increasingly runs MSP, travel, local, PRN, shift, and vendor-managed staffing through one environment: one workforce platform, multiple staffing models.

That platform now supports healthcare organizations across 4,000+ facilities nationwide, including the largest hospital network in the United States. Those numbers aren't the point on their own. They're evidence that the underlying product and design foundation can carry multiple staffing models, enterprise-scale workflows, and a business strategy that has already changed once, at the scale a platform like this demands.

Design System

Foundations

Ten core primitives, including colors, color tokens, utility tokens, typography, logo usage, a Lucide-based icon set, shadows, spacing, and border radius, give every generation of the ciro ecosystem the same visual DNA before a single component gets built.

Elements

Nineteen reusable building blocks, from buttons, inputs, and dropdowns to badges, toggles, and a WYSIWYG editor, cover the interaction patterns clinicians, clients, and affiliates all rely on, so a control behaves the same way across Talent Management, Shift Management, and Affiliate today, the same consistency it held across all four products before the strategy changed.

Application Components

Twenty-seven higher-order patterns, including the application shell, page headers, KPI cards, activity feeds, command menus, and multi-step wizards, give teams the structural pieces whole product workflows are built from, not just the individual controls inside them.

Cross-Segment Patterns

Navigation, data visualization, and notification patterns designed once during ciro's four-product era and still carried forward today across Talent Management, Shift Management, and Affiliate, proof the pattern library outlasted the product lineup it was built for.

Governance & Documentation

Design governance and competency frameworks put in place to keep a growing design team (scaled from 3 to 12 people) shipping consistently as the product surface expanded, documented in a living Figma library that designers and engineers both work from as the system's single source of truth.

Accessibility as a Default

Accessibility built into the component layer itself, not audited in after the fact, so every new screen inherits compliant color, contrast, and interaction patterns automatically.