David Nelson

The Method

Human Problem → Enterprise System

A repeatable transformation system for moving from ambiguity to aligned, measurable execution.

(The method)

  1. Find the human problem
  2. Frame the enterprise opportunity
  3. Prototype the future
  4. Use evidence to sharpen decisions
  5. Align stakeholders
  6. Define how the work runs
  7. Scale the system
  8. Measure the outcome

Human problem Enterprise system

In short

What the work actually is.

I turn human problems into enterprise systems that scale.

My work follows a repeatable transformation system: find the human problem, frame the enterprise opportunity, prototype the future, use evidence to sharpen decisions, align stakeholders, define how the work runs, scale the system, and measure the outcome.

The result is not just better design. It is clearer strategy, stronger products, healthier teams, trusted platforms, and operating models that help organizations keep moving after the first launch.

The method

Eight steps, one repeatable system.

Each step does specific work, matters for a specific reason, and shows specific signals when it is working.

Find the human problem

Understand the people, friction, context, and unmet need behind the work.

Why it matters
Enterprise systems fail when they solve for structure instead of lived experience.
Signals it is working
  • Clear user problem
  • Named friction
  • Known business consequence
  • Better stakeholder questions

Frame the enterprise opportunity

Translate human need into business value, product strategy, and system-level ambition.

Why it matters
Human-centered work creates more value when it shapes strategy, not just interface decisions.
Signals it is working
  • Clear opportunity statement
  • Prioritized user and business outcomes
  • Explicit tradeoffs
  • Stronger decision criteria

Prototype the future

Make the direction tangible early so teams can align, test, and move.

Why it matters
Prototypes reveal misunderstanding faster than documents.
Signals it is working
  • Faster alignment
  • Clearer risks
  • Better stakeholder conversations
  • Less abstract debate

Use evidence to sharpen decisions

Bring data, research, experiments, and signals into the work before opinions harden.

Why it matters
Evidence should sharpen decisions without replacing product taste or human understanding.
Signals it is working
  • Fewer opinion loops
  • Better prioritization
  • Clearer success measures
  • Stronger confidence in direction

Align the system of stakeholders

Create shared language, decision clarity, and executive confidence across functions.

Why it matters
Transformation breaks when alignment is performative instead of operational.
Signals it is working
  • Named owners
  • Clear tradeoffs
  • Reduced rework
  • Decisions that stick

Define how the work runs

Clarify ownership, governance, rituals, standards, contribution paths, and decision rights.

Why it matters
Good work does not scale through heroics. This is where an operating model is the deliverable.
Signals it is working
  • Better team rhythm
  • Clear decision rights
  • Shared standards
  • Less dependency on individual intervention

Scale the system

Move from one product or team to reusable capabilities, platforms, patterns, and practices.

Why it matters
Enterprise value comes when good work compounds.
Signals it is working
  • Reusable patterns
  • Shared capabilities
  • Improved consistency
  • Higher adoption

Measure the outcome

Track adoption, quality, productivity, business impact, and experience health.

Why it matters
Work without measurement becomes theater.
Signals it is working
  • Clear outcome metrics
  • Adoption signals
  • Quality indicators
  • Business impact

Define how the work runs

Step six is where change sticks.

The operating model is the deliverable: ownership, decision rights, standards, contribution paths, and cadence - so good work scales without heroics.

How the work runs A governed loop: contribute, review, decide at a gate, release, then feed back into the next cycle. Contribute Review Decide Release feedback into the next cycle
  • Ownership & decision rights
  • Standards
  • Contribution paths
  • Release gates
  • Cadence

At Walmart, this is how Squiggly - the unified Associate AI Platform - holds together: shared components and interaction patterns paired with governance, contribution paths, release rituals, and a real operating cadence, so many teams build into one coherent system.

In context

The same method, different gravity.

The loop holds across very different environments. What changes is the constraint it has to respect.

Fortune 1

At extreme scale, the method holds coherence across fragmented systems, roles, and data environments so millions of people meet one trusted experience.

Startup

In zero-to-one work, the same loop compresses: find the problem, prototype, gather evidence, and ship a credible product before structure exists.

Regulated enterprise

In financial services and regulated work, governance, accessibility, and decision rights are designed in, not bolted on, so trust scales with the system.

Physical-digital

Where infrastructure, operations, and software meet, delivery discipline and end-to-end testability keep the experience dependable in the real world.

Why it matters

What this prevents.

A working method is the difference between change that ships and change that performs.

  • Technology theater
  • Strategy decks that do not ship
  • Feature factories
  • Fragmented platforms
  • Design systems without adoption
  • Change that never reaches how the work runs

What it produces

Outputs the organization can use.

The method ends in tangible deliverables – including, where the work needs to scale, an operating model.

  • North Star visions
  • Product strategies
  • Prototypes
  • Design systems
  • Governance models
  • Contribution models
  • Measurement frameworks
  • Enterprise operating models
  • Scaled platforms and experiences

What I bring

Capabilities across the loop.

  • Enterprise design strategy
  • AI-enabled product and platform vision
  • Experience architecture
  • Product and service incubation
  • Design-led operating discipline
  • Executive alignment and storytelling
  • Measurement and adoption systems

Proof

The method is reconstructed from the work, not invented for a deck.

Fortune 1 people experience, zero-to-one incubation, enterprise capability, climate tech, and physical-digital delivery.

Walmart

A unified, trusted Associate AI Platform at Fortune 1 scale

Squiggly · associate AI platform · multi-brand careers

Microsoft

Zero-to-one incubation before the structure existed

StaffHub, Office 365 frontline work, Xbox incubation

Northwestern Mutual

Enterprise capability for scalable transformation

CX transformation, design systems, org capability

Sustain.Life

Climate-tech product from ambiguity to market

Startup-to-acquisition, carbon accounting platform

Control Group

Digital experiences for physical places, at city scale

NYC subway · Talking Transition · Kennedy Institute

Adobe

Craft, experimentation, and product foundations

Product quality, evidence-based decisions

See the proof in full

Put it to work

Bring the right ambiguity.

For advisory, executive leadership, or a working session on bringing this method to your most important problem.

Start a conversation See the work