Book discovery
01

Capabilities

Diagnose, direct, make, and guide delivery.

Explore capabilitiesHow engagements work
02

EEM

A complete operating model for executable experience work.

Enter the EEM system
03

Work

Complete stories from complex product and service environments.

Explore workRecreation.gov
04

Thinking

Ideas about experience, organizations, AI, and decision-making.

Explore all thinking
About HellaHow engagements workBook discovery
Back to EEM Overview

08 Implementation

Implementing EEM

Start where you are. Scale only what the team can absorb.

Is Your Team Ready?

EEM isn't for everyone—yet. Assess your current state to determine the right starting point.

Design System Maturity

Do you have documented components, tokens, and patterns that AI can reference?

No system
Ad hoc
Documented
In Code
Storybook
Team AI Comfort

Are designers comfortable evaluating code output and prompting AI tools?

Unfamiliar
Skeptical
Curious
Experimenting
Proficient
Stakeholder Flexibility

Are stakeholders open to reviewing working prototypes instead of polished mockups?

Rigid
Traditional
Open
Eager
Demanding it
Decision Authority

Can your team make go/no-go decisions without excessive approvals?

Bureaucratic
Slow
Moderate
Agile
Autonomous

Reading Your Assessment

Mostly Green
You're ready. Start with Walk or even Run phase.
Mix of Yellow/Green
Start with Crawl. Build foundations first.
Mostly Red
Pre-work needed. Focus on design system and team training first.
01

Crawl

Foundation & Learning (Weeks 1-4)

Goal: Build foundational skills and validate the approach with a single, low-stakes pilot project.

Activities

  • Select a pilot project (internal tool, low-risk feature)
  • Set up Agent IDE (Cursor, Windsurf, or Bolt)
  • Document your design system (even if basic)
  • Run one complete EEM cycle (all 5 stages)
  • Document learnings and pain points

Success Metrics

Cycle Completed
One project through all 5 EEM stages, from Input to Production
Team Comfort
Designers can prompt Agent IDE and evaluate output
Stakeholder Buy-in
At least one stakeholder saw value in the approach

Pilot Project Criteria: Choose something with clear constraints, forgiving stakeholders, and low production risk. Internal tools, prototypes for user testing, or feature enhancements work well.

02

Walk

Expansion & Refinement (Weeks 5-12)

Goal: Expand to multiple projects, refine governance processes, and build organizational confidence.

Activities

  • Apply EEM to 2-3 concurrent projects
  • Establish formal governance process
  • Mature design system documentation
  • Train additional team members
  • Measure and compare velocity metrics
  • Refine based on what's working/not working

Success Metrics

Velocity Increase
Measurable reduction in time from Input to Production
Multiple Variants
Teams consistently producing 2-5 solution variants
Governance Rhythm
Regular, efficient governance sessions happening

Common Adjustment: Teams often discover their governance process is too heavy in Walk phase. Simplify: clear decision authority, time-boxed sessions, async when possible.

03

Run

Scale & Optimize (Months 4-12)

Goal: EEM becomes the default workflow. Scale across teams and continuously optimize.

Activities

  • All new projects use EEM by default
  • Onboard new team members to EEM workflow
  • Design system evolves through governance
  • Hire for EEM-native skills
  • Continuously optimize tools and processes
  • Share learnings externally (optional)

Success Metrics

Default Workflow
EEM is how your team works, not an experiment
System Evolution
Design system grows through execution, not theory
Competitive Advantage
Shipping faster than competitors using traditional methods

Common Implementation Pitfalls

01

Skipping Governance

"We're moving fast, we don't need review meetings." Speed without governance produces chaos. Governance is what makes speed sustainable.

02

No Design System Foundation

Trying EEM without documented components means AI has nothing to reference. Results will be inconsistent and off-brand.

03

Single Solution Mindset

Only building one solution defeats the purpose. EEM's power comes from comparing variants. Aim for 2-5 solutions minimum.

04

Designers Coding

Designers trying to write code themselves instead of directing agents. They should evaluate and prompt, not implement.

05

Skipping Stakeholder Engagement

Building in isolation then presenting "finished" work. Stakeholders should engage with working prototypes during Execute.

06

All-or-Nothing Adoption

Trying to transform everything at once. Start with one pilot, prove value, then expand gradually.

Getting Help

Self-Service

Explore our documentation, FAQ, and detailed guides to implement EEM on your own.

Advisory Call

Book a consultation to discuss your specific situation and get tailored recommendations.

Hands-On Support

We embed with your team to guide implementation, train designers, and establish governance.

Ready to Start Your EEM Journey?

Whether you're exploring or ready to implement, let's discuss how EEM fits your team's context and goals.

Let's Talk Back to EEM Overview

Continue exploring:

Tool Stack Team Structure Governance FAQ