Enterprise Design Thinking: Guiding Principles for User‑Centric Product Development

Principles Guide Us

Enterprise Design Thinking is a human‑centered framework that treats problems and solutions as an ongoing conversation, focusing on delivering measurable user outcomes rather than feature lists.

Focus on User Results

Teams should prioritize user success, measuring success by how well they meet user needs—whether curing disease, accelerating reporting, or any other real‑world task.

Practice

As user demand becomes market demand, every aspect of work—from metrics to language—must be user‑centric. Managers align management style with real user identities; team members understand user roles and contribute accordingly.

Distinguish Users and Customers

Front‑line contacts are often buyers (e.g., CIO) rather than end users. Gather second‑hand user experience data, collaborate with buyers, and connect directly with true users.

Manage User Outcomes

Leadership must keep work aligned with user needs. Define success by discrete user outcomes (Hills) instead of feature lists, tell stories from the user’s perspective, and involve real users from the start.

Measure User‑Result Metrics

Beyond revenue and cost, use metrics like Net Promoter Score (NPS) to gauge user loyalty and predict growth.

Team Member Role

Empathy with Users

Recognize that users are real people with values, behaviors, hopes, and fears that shape how they interact with systems.

Understand Their Roles

Users operate within complex, interdependent teams and processes; understanding team needs is as important as understanding individual users.

Re‑shaping Uncertainty

Human needs stay constant; our solutions evolve. Continuously iterate, keep dialogue with users, and accept that no solution is perfect—everything is a prototype.

Diverse Empowered Teams

Better Together

Diverse teams bring varied perspectives, leading to richer problem‑solving and breakthrough ideas. Empowered teams have the authority to turn ideas into outcomes without excessive bottlenecks.

Practice Example

Collaboration between a design graduate in Atlanta and a seasoned software architect in Beijing illustrates the need for diverse, empowered teams to solve complex problems.

Team Manager Responsibilities

Assign core leadership from each discipline, grant authority for daily decisions, and ensure accountability for delivered results.

Building Independent Teams

Consider identity, experience, and expertise when forming teams; avoid homogeneity to maintain creative tension.

Give Them Space

Stakeholders must allow teams autonomy to define roles and make decisions, similar to how Kennedy let NASA focus on the moon mission.

Observation (Observe)

Immerse in the real world to understand user contexts, uncover hidden needs, and gather unbiased feedback.

Ask Each Other

Who are our users? What are their stories, experiences, and influences?

What is their background? Who do they work with, what processes are they part of, and what expectations do they have?

What are their needs? What problems do they solve, how do they define success, and what outcomes have they achieved?

What feedback do they provide? What works, what doesn’t, and what ideas do they have?

Reflect

Regularly bring the team together to sync, share insights, and adjust direction based on new information.

Understand Each Other

Build a shared identity, empathize with teammates, and leverage diverse viewpoints as strengths.

Adjust Intent

Re‑evaluate motivations and ensure work stays aligned with user goals.

Uncover New Insights

Combine known and unknown information to reveal hidden opportunities.

Plan Ahead

Decide next steps collectively, whether iterating another cycle or committing to a concrete action.

Make

Translate abstract ideas into tangible prototypes, share them early, and iterate quickly.

Explore Possibilities

Don’t wait for perfection; experiment, learn from failures, and incorporate others’ input.

Communicate Ideas

Show, don’t just tell—visuals convey intent more effectively than words.

Prototype Concepts

Use low‑fidelity prototypes to validate assumptions quickly and cost‑effectively.

Drive Outcomes

Commit to turning ideas into results, embracing early failure as a learning opportunity.

Consider These Questions

What is possible? What can we do, combine, or achieve?

What happened? What are the ideas, expected results, and presentations?

What is the concept? What form does it take, what parts, and how do they relate?

How do we deliver? How do we build, deploy, and maintain it?

Key Alignment

Key metrics keep teams focused on user‑centric outcomes.

Hills

Hills are intent statements written as meaningful user results, guiding teams without prescribing implementation.

Hill Anatomy

Who : Identify the target user.

What : Define the desired outcome.

Wow : Explain differentiation and success measurement.

Examples

“A sales leader can assemble an agile response team within 24 hours without managerial approval.”

Managing Hills

Product teams own Hills; service teams involve senior client stakeholders. Iterate early and often, keeping the number of Hills manageable (typically three).

Playbacks

Playbacks (Hills, Delivery, Client) bring stakeholders into a safe loop to share stories, gather feedback, and maintain alignment throughout the project lifecycle.

Sponsor Users

Sponsor users are real users who regularly contribute domain expertise, helping teams stay grounded in actual needs.

Working with Sponsor Users

Include them in product management and design processes, consult them for insights, and treat their input as a core part of solution refinement.

---

For more resources, join the community via WeChat, QQ groups, Knowledge Planet, or other channels listed at the end of the original document.