The 90-Day Framework for Designing in Complex Systems

When joining a new product team—especially in healthcare or enterprise AI—you’re often dropped into a system that’s already in motion. Data is fragmented, priorities are shifting, and every stakeholder has a different definition of “urgent.” My 30-60-90 day framework helps me find focus, build context, and deliver impact fast.

Why It Matters

The first three months define how a designer integrates into a complex environment. They’re your chance to build trust, learn the landscape, and identify leverage points where design can drive real business and user outcomes. I treat this process as a kind of “design diagnosis”—understanding the system before prescribing solutions.

30 Days: Observe and Diagnose

The first month is all about listening and mapping. I meet with cross-functional teams—clinical staff, engineers, product managers—to understand workflows, constraints, and what success looks like to each group.

Study the business model and user ecosystem.
Shadow real users to see friction firsthand.
Audit product data, user research, and design artifacts.
Document assumptions and quick wins in a shared 1-pager.

By the end of 30 days, the goal is clarity—what’s working, what’s not, and which problems matter most.

60 Days: Synthesize and Prioritize

With context established, the next step is synthesis. I identify recurring UX gaps—bottlenecks in data visualization, onboarding, or adherence workflows—and frame them as design opportunities.

Map system dependencies and user flows.
Run design workshops to validate priorities.
Prototype quick experiments to test assumptions.
Align with product leadership on measurable goals.

At this stage, it is less about shipping features and more about designing focus—narrowing down what will have the most impact.

90 Days: Execute and Influence

Once aligned, I move into high-velocity design sprints focused on outcomes. This includes delivering prototypes, defining design system components, and preparing a roadmap for scaling UX maturity.

Launch low-fidelity MVPs and track user feedback.
Document principles for scalability and governance.
Share early wins to reinforce trust across teams.

By day 90, success means more than a shipped prototype—it means the team sees design as a strategic engine, not a service.

Lessons Learned

Whether building clinical dashboards at Curie AI or data tools for wellness platforms, the same principle applies: clarity before speed. Entering complex systems with a structured learning mindset allows designers to make an impact quickly without losing sight of the bigger picture.

The 90-day framework isn’t a checklist—it’s a rhythm. Observe, align, and execute. Repeat with every new challenge.