Category Archives: Design

Has AI Killed Design Thinking?

Or Just Removed Its Excuses?

LAST UPDATED: March 2, 2026 at 5:13 PM

Has AI Killed Design Thinking?

by Braden Kelley and Art Inteligencia


I. The Question Everyone Is Whispering

Something fundamental has changed in how products are created.

Artificial intelligence can now generate working software in minutes. Designers can move from an idea to a functional prototype without waiting for engineering. Engineers can generate interface concepts, user flows, and even early product ideas with a few well-crafted prompts.

The traditional product development cycle — design, then build, then test — is collapsing into something faster, messier, and far more fluid.

In the past, the biggest constraint in innovation was the cost and time required to build something. Today, AI dramatically reduces that barrier. Entire features, experiments, and even applications can be created almost instantly.

Which raises an uncomfortable question that many product leaders, designers, and engineers are quietly asking:

If we can ship almost immediately, do we still need design thinking?

At first glance, the answer might seem obvious. Design thinking was created to help teams understand people, define the right problems, and avoid building the wrong solutions. Those goals have not disappeared.

But when the cost of building approaches zero, the role of design inevitably changes. The traditional pacing of discovery, ideation, prototyping, and testing begins to compress. The boundaries between designer and engineer begin to blur.

And as those boundaries dissolve, the question is no longer simply whether design thinking still matters.

The deeper question is whether the discipline itself must evolve to survive in a world where almost anyone can turn an idea into working software.

II. Design Thinking Was Built for a World of Scarcity

To understand how artificial intelligence is reshaping product creation, it helps to remember the environment in which design thinking originally emerged.

Design thinking did not appear because organizations suddenly discovered empathy or creativity. It emerged because building things was expensive, slow, and risky. Every product decision carried significant cost, and mistakes could take months or years to correct.

In that world, organizations needed a structured way to reduce uncertainty before committing engineering resources. Design thinking provided that structure.

Its now-famous stages helped teams move deliberately from understanding people to building solutions:

  • Empathize — deeply understand the people you are designing for.
  • Define — frame the real problem worth solving.
  • Ideate — generate a wide range of possible solutions.
  • Prototype — create rough representations of potential ideas.
  • Test — validate whether those ideas actually work for people.

The goal was simple: avoid spending months building something no one actually needed.

Design thinking slowed teams down in the right places so they could move faster later. It created space for exploration before the heavy machinery of engineering was set in motion.

But this entire framework assumed one critical constraint:

Building was the most expensive part of innovation.

Prototypes were often static mockups. Experiments required engineering time. Even small product changes could take weeks or months to ship.

In other words, design thinking was optimized for a world where the biggest risk was building the wrong thing.

Today, AI is rapidly changing that assumption. When working software can be generated in minutes rather than months, the bottleneck shifts — and the role of design must evolve with it.

III. AI Has Flipped the Innovation Constraint

For most of the history of digital product development, the limiting factor in innovation was the ability to build. Even the best ideas had to wait in line for scarce engineering resources, long development cycles, and complex release processes.

Artificial intelligence is rapidly dismantling that constraint.

Today, AI tools can generate functional code, working interfaces, and interactive prototypes in minutes. What once required a team of specialists and weeks of effort can often be produced by a single individual in an afternoon.

Designers can now:

  • Create interactive prototypes that behave like real products
  • Generate front-end code directly from design concepts
  • Rapidly explore multiple product directions

Engineers can now:

  • Generate user interfaces and layouts
  • Experiment with product concepts before committing to full builds
  • Quickly iterate on product experiences

The barrier between idea and implementation is shrinking dramatically.

As a result, the core constraint in innovation is no longer the ability to build something. The new constraint is the ability to decide what should actually be built.

When creation becomes cheap, judgment becomes the scarce resource.

Organizations can now generate more ideas, features, and experiments than they have the capacity to evaluate thoughtfully. The risk is no longer simply building the wrong thing slowly.

The risk is building thousands of things quickly without enough clarity about which ones actually matter.

This shift fundamentally changes the role of design. Instead of primarily helping teams avoid costly mistakes in development, design increasingly becomes the discipline that helps organizations navigate overwhelming possibility.

IV. The Blurring of Roles: Designers Reach Forward, Engineers Reach Back

One of the most profound effects of AI in product development is the erosion of traditional professional boundaries.

For decades, the technology industry operated with relatively clear separations of responsibility. Designers focused on user needs, interaction models, and visual systems. Engineers translated those designs into working software. Product managers coordinated priorities and timelines between the two.

That structure was largely a reflection of technical limitations. Designing and building required specialized tools, knowledge, and workflows that made cross-disciplinary work difficult.

AI is rapidly dissolving those barriers.

Designers can now reach forward into the domain that once belonged exclusively to engineering. With AI-assisted tools, they can generate working interfaces, produce front-end code, and simulate complex user interactions without waiting for implementation.

At the same time, engineers can reach backward into design. AI systems can help them generate layouts, propose interface structures, and explore experience flows that once required specialized design expertise.

The result is a new kind of creative overlap:

  • Designers who can prototype in code
  • Engineers who can explore experience design
  • Product creators who move fluidly between disciplines

The traditional model of work moving through a linear chain — research to design to engineering — begins to give way to a far more integrated creative process.

The future product creator is not defined by a job title, but by the ability to move fluidly between understanding problems and building solutions.

This does not mean design expertise or engineering skill become less important. If anything, the opposite is true. As tools make it easier for everyone to participate in creation, the depth of real craft becomes more visible and more valuable.

But it does mean the rigid boundaries between “designer” and “builder” are beginning to dissolve, creating a new generation of hybrid creators who can move seamlessly between imagining, designing, and shipping experiences.

V. The Death of the Handoff

For decades, most product development operated like a relay race. Work moved from one team to the next through a series of formal handoffs.

Researchers gathered insights and passed them to designers. Designers created wireframes and mockups that were handed to engineering. Engineers translated those designs into working software and eventually passed the finished product to testing and operations.

Each transition introduced delays, misinterpretations, and loss of context. The original understanding of the problem often became diluted as it traveled through the system.

Artificial intelligence is accelerating the collapse of this model.

When individuals can move rapidly from idea to prototype to functional product, the need for rigid handoffs begins to disappear. A single person can now:

  • Explore a user problem
  • Design a potential solution
  • Generate working code
  • Launch an experiment

Instead of waiting for work to pass from one discipline to another, creators can stay connected to the entire lifecycle of an idea.

The distance between insight and implementation is shrinking.

This shift has profound implications for how innovation happens inside organizations. Instead of large teams coordinating complex handoffs, smaller groups — or even individuals — can rapidly test ideas and learn from real-world feedback.

Product development begins to look less like an industrial assembly line and more like a creative studio, where ideas are explored, built, and refined continuously.

The most effective teams in this environment will not simply move faster. They will maintain ownership of ideas from the moment a problem is discovered all the way through to the moment a solution is experienced by real people.

VI. What AI Actually Kills

Artificial intelligence is not killing design thinking.

What it is killing are many of the habits that organizations adopted in the name of design thinking but that were never truly about understanding people or solving meaningful problems.

For years, some teams have mistaken the appearance of innovation for the practice of it. Workshops replaced experiments. Sticky notes replaced decisions. Slide decks replaced prototypes.

When building was slow and expensive, these behaviors were often tolerated because teams needed time to align before committing resources. But in a world where working solutions can be generated almost instantly, those habits quickly become friction.

AI removes the excuses that allowed these patterns to persist.

Process Theater

Innovation workshops that generate energy but not outcomes become difficult to justify when teams can build and test ideas immediately.

Endless Ideation

Brainstorming sessions that produce dozens of ideas without committing to experiments lose their value when ideas can be rapidly turned into prototypes and evaluated in the real world.

Documentation Instead of Exploration

Detailed reports, long strategy decks, and static artifacts once helped communicate ideas across teams. But when AI allows concepts to be expressed through working experiences, documentation becomes less important than experimentation.

Safe Innovation

Perhaps most importantly, AI challenges organizations that use process as a shield against risk. When it becomes easy to test bold ideas quickly and cheaply, avoiding experimentation becomes a choice rather than a necessity.

AI doesn’t eliminate design thinking. It eliminates the distance between thinking and doing.

The organizations that thrive in this environment will not be the ones with the most polished innovation processes. They will be the ones that are most willing to replace discussion with discovery and ideas with experiments.

Has AI Killed Design Thinking Infographic

VII. The New Role of Design: Decision Velocity

When the cost of building drops dramatically, the nature of competitive advantage changes.

In the past, organizations succeeded by efficiently transforming ideas into products. Engineering capacity, technical expertise, and operational discipline were often the primary constraints.

But when AI can generate working software, prototypes, and experiments almost instantly, the challenge is no longer how quickly something can be built.

The challenge becomes how quickly and wisely teams can decide what is actually worth building.

In an AI-driven world, innovation speed is no longer about development velocity — it is about decision velocity.

This is where the role of design evolves.

Design shifts from primarily producing artifacts — wireframes, mockups, and prototypes — to guiding the choices that shape meaningful innovation.

Designers increasingly become the people who help teams:

  • Frame the right problems to solve
  • Clarify human needs and motivations
  • Prioritize which ideas deserve experimentation
  • Interpret signals from real-world user behavior

In other words, design becomes less about shaping the interface of a product and more about shaping the direction of learning.

When organizations can generate thousands of potential solutions, the real value lies in identifying the small number that actually create meaningful value for people.

Designers, at their best, help organizations navigate that complexity. They connect technology to human context, helping teams avoid the trap of building faster without thinking better.

In the AI era, design is not slowing innovation down. It is helping organizations move quickly without losing their sense of where they should be going.

VIII. From Design Thinking to Design Doing

As artificial intelligence compresses the distance between idea and implementation, the nature of design practice begins to change. The emphasis shifts away from structured stages and toward continuous experimentation.

Traditional design thinking frameworks helped teams organize their thinking before committing to build. But in an AI-enabled environment, building itself becomes part of the thinking process.

Instead of long cycles of analysis followed by development, teams can now explore ideas directly through working prototypes and rapid experiments.

The most effective teams no longer separate thinking from building. They think by building.

This shift marks a move from design thinking to what might be called design doing.

In this model, learning happens through fast cycles of creation, feedback, and refinement. Ideas are not debated endlessly in workshops or captured in lengthy documents. They are explored through tangible experiences that can be observed, tested, and improved.

The practical differences begin to look like this:

Traditional Model AI-Enabled Model
Workshops and brainstorming sessions Rapid experiments and live prototypes
Personas and research summaries Behavioral data and real-world signals
Concept mockups Functional prototypes
Long planning cycles Continuous learning loops

None of this diminishes the importance of understanding people. If anything, the need for deep human insight becomes even more important as the pace of experimentation accelerates.

What changes is how that understanding is expressed. Instead of existing primarily as documents or presentations, insight becomes embedded directly into the experiences teams create and test.

In an AI-native organization, design is no longer a phase that happens before development begins. It becomes an ongoing activity woven directly into the act of building and learning.

IX. Human Trust Becomes the New Design Material

As artificial intelligence accelerates the speed of building, the most important design challenges begin to shift away from usability and toward something deeper: trust.

When products can be created, modified, and deployed almost instantly, the risk is not simply poor interface design. The risk is creating experiences that feel disconnected from human values, human context, and human expectations.

AI makes it easier than ever to generate functionality. But it does not automatically ensure that what is generated is responsible, understandable, or aligned with the needs of the people who will use it.

In an AI-driven world, the most important design material is no longer pixels or screens — it is human trust.

This raises a new set of responsibilities for designers, engineers, and product leaders alike.

Teams must think carefully about questions such as:

  • Do people understand what the system is doing?
  • Are decisions being made transparently?
  • Does the experience respect human autonomy?
  • Does the technology reinforce or erode confidence?

As AI systems become more powerful, the danger is not just that they might fail. The danger is that they might succeed in ways that quietly undermine the relationship between organizations and the people they serve.

Design therefore becomes a critical safeguard. It ensures that rapid technological capability does not outpace thoughtful consideration of human consequences.

In this sense, the role of design expands beyond shaping products. It becomes the discipline that ensures technology remains grounded in human meaning, responsibility, and trust.

X. The Future: Designers Who Ship, Engineers Who Empathize

As AI blurs the traditional boundaries between design and engineering, the most valuable creators in the future will be those who can move fluidly between imagining, designing, and building.

Designers will need to ship working products, not just static prototypes. Engineers will need to empathize deeply with users, understanding problems and shaping experiences that align with human needs.

The new hybrid product creator embodies both curiosity and capability, bridging the gap between thinking and doing. They are able to:

  • Rapidly translate insights into working solutions
  • Experiment and learn from real-world user behavior
  • Balance technical feasibility with human desirability
  • Maintain alignment between strategy, design, and execution

In this new landscape, design thinking does not disappear — it evolves. AI removes many of the barriers that previously prevented designers and engineers from collaborating fully and iterating quickly.

The organizations that succeed will be those where everyone has the ability to both understand humans and act on that understanding at the speed of AI.

The future belongs to hybrid creators who can navigate ambiguity, make fast decisions, and embed human trust into every experiment. In such a world, innovation is no longer the domain of specialists — it is the responsibility of anyone capable of connecting insight with action.

XI. The Real Question Leaders Should Be Asking

The debate is often framed as a dramatic question: “Has AI killed design thinking?” But this framing misses the deeper challenge facing organizations today.

The real question is not whether design thinking survives — it is whether organizations are prepared to operate in a world where anyone can turn ideas into working products almost instantly.

In this AI-accelerated environment, success depends less on the speed of coding or the elegance of design frameworks. It depends on human judgment, understanding, and alignment.

Leaders must ask themselves:

  • Do our teams know what problems are truly worth solving?
  • Can we prioritize experiments that create real human value?
  • Are we embedding human trust and ethical consideration into everything we build?
  • Are our designers and engineers equipped to operate across traditional boundaries?

In this new era, the organizations that thrive will not be the ones with the fastest developers or the slickest design processes.

They will be the organizations that can rapidly identify meaningful opportunities, make thoughtful decisions, and maintain human-centered principles while moving at the speed of AI.

Innovation will no longer belong to the people who can code. It will belong to the people who understand humans well enough to know what should be built in the first place.

The role of leadership is no longer just managing workflows — it is shaping the environment in which hybrid creators can think, act, and build responsibly at unprecedented speed.

New Tools for the New Design Reality

Get the new design thinking downloadsTo help you find problems worth solving and to design and execute experiments, I created a couple of visual and collaborative tools to help you thrive in this new reality. Download them both from my store and enjoy!

  1. Problem Finding Canvas — Only $4.99 for a limited time
  2. Experiment Canvas — FREE

FAQ: AI and the Evolution of Design Thinking

1. Has AI made design thinking obsolete?
No. AI has not killed design thinking, but it has changed the context in which it operates. Traditional design thinking frameworks assumed that building was slow and expensive. With AI accelerating the creation of prototypes and software, design thinking evolves from a staged process into a continuous cycle of experimentation and decision-making.
2. How are the roles of designers and engineers changing with AI?
AI blurs the traditional boundaries between designers and engineers. Designers can now generate working code and functional prototypes, while engineers can explore user experience and interface design. The future favors hybrid creators who can both understand human needs and rapidly implement solutions.
3. What becomes the main focus of design in an AI-driven product environment?
The primary focus shifts from producing artifacts to guiding decision-making and protecting human trust. Design becomes the discipline that helps teams prioritize meaningful experiments, interpret real-world feedback, and ensure that rapid technological development remains aligned with human values and needs.


Image credits: ChatGPT

Content Authenticity Statement: The topic area, key elements to focus on, etc. were decisions made by Braden Kelley, with a little help from ChatGPT to clean up the article and add citations.

Subscribe to Human-Centered Change & Innovation WeeklySign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

7 Ways Design Thinking Gets Misused

(And How to Course-Correct)

7 Ways Design Thinking Gets Misused

by Braden Kelley and Chateau G Pato


Why Does Design Thinking Get Misused? (Short Answer)

Design thinking gets misused when organizations treat it as a workshop format instead of a discipline for understanding humans and making better choices under constraint. Seven common misuses are: empathy theater without real people, ideation without mandate, prototyping without a behavior to test, journey maps without owners, endless discover as schedule padding, facilitators without power, and “we design think” as brand instead of outcomes.

Course correction means restoring jobs-to-be-done, real evidence, decision rights, behavior-based tests, journey ownership, time boxes with kill criteria, sponsors with levers, and success measured by adoption — not sticky-note acreage.

The Method Is Not the Costume

I have walked into rooms that smell like fresh markers and old coffee and felt the familiar mix of hope and dread. Hope because someone finally said “human-centered.” Dread because the wall is already filling with personas nobody met and “How might we…” statements nobody is allowed to answer.

Design thinking is not the problem. Misuse is. When empathy becomes a poster, ideation a substitute for power, and prototypes a way to delay a decision, you get innovation cosplay with better stationery. The method still works — when it is tied to real humans, real constraints, and a Tuesday someone can actually succeed on.

Misuse Why it happens Course-correct
1. Empathy theater Faster, no access politics Talk to humans doing the job
2. Ideation without mandate Performance over power Match method to decision rights
3. Prototyping without behavior Demos photograph well Test one falsifiable behavior
4. Journey maps without owners Maps are deliverables Name owner + one seam to fix
5. Schedule padding Ambiguity feels safe Time-box; define the decision
6. Facilitators without power DT outsourced Sponsor with levers in room
7. DT as brand Credibility borrowing Judge by behavior and adoption

1. Empathy Theater — Post-Its Without People

The misuse: Personas, empathy maps, and “user needs” built from conference-room imagination. No customers in the room. No frontline staff. No evidence beyond what someone senior once said at an offsite.

Why it happens: It is faster. It avoids access politics. It lets the team feel virtuous without scheduling the awkward conversation where reality contradicts the roadmap.

Course-correct: Talk to humans doing the job — customers, employees, partners. Capture jobs-to-be-done, friction, and dignity costs in their language. If your empathy artifact could have been written without leaving the building, it is fiction with better fonts.

2. Ideation Without Mandate — Brainstorming What You Cannot Change

The misuse: “How might we…” on problems policy, budget, incentives, or turf forbid anyone to fix. The wall fills with clever ideas that die the moment the workshop ends.

Why it happens: Design thinking becomes performance. Brainstorming feels like progress without naming decision rights or making enemies.

Course-correct: Before the workshop, ask: What are we empowered to decide, ship, or stop? Match the method to the mandate. If the honest answer is “nothing structural,” fix the mandate — or cancel the sticky notes and stop charging the room rent for theater.

3. Prototyping Without a Behavior — Demo Is Not Learning

The misuse: Clickable mockups, storyboards, or AI demos that never test a named human behavior or success signal. The prototype exists to impress, not to falsify.

Why it happens: Prototypes photograph well. Measurement is harder. Applause is immediate; adoption is delayed and therefore ignorable.

Course-correct: Prototype to test one behavior hypothesis — completion in one attempt, abandoned workaround, time-to-confidence, effort reduced. Measure what people do, not what they say in the debrief. A beautiful demo that does not change a behavior is a portfolio piece, not design.

4. Journey Maps Without Owners — Beautiful Maps, Orphaned Seams

The misuse: Journey maps that end at the workshop wall. Broken handoffs identified, celebrated, and then left without an operator in business-as-usual.

Why it happens: Maps are deliverables. Operating-model change is political. Printing is easier than owning.

Course-correct: Name a journey owner with decision rights before you print the poster. Pick one seam — one handoff, one wait, one moment of shame — and fund its fix. A map without an owner is wallpaper that teaches the organization how to look empathetic while staying unchanged.

5. Design Thinking as Schedule Padding — “We’re Still in Discover”

The misuse: Endless discover and define to avoid a decision, a vendor choice, a kill, or a tradeoff someone does not want to make.

Why it happens: Ambiguity feels like safety. Without kill criteria, “we’re learning” becomes a luxury hobby with catering.

Course-correct: Time-box phases. Define what decision the sprint must produce — proceed, pivot, or stop. Learning without a decision date is tourism. Design thinking should reduce uncertainty, not indefinitely postpone it.

6. Facilitators Without Power — Great Session, No Tuesday

The misuse: External or internal facilitators who run excellent sessions but cannot move budget, policy, metrics, or the workaround everyone still uses on Monday.

Why it happens: Design thinking is outsourced to people without levers. Sponsors attend the readout and disappear into the next crisis.

Course-correct: Put a sponsor with decision rights in the room for the whole arc — not only the applause at the end. The facilitator serves evidence and structure; the sponsor owns tradeoffs. If nobody with power was present when the uncomfortable insight appeared, the insight will not survive contact with the calendar.

7. “We Design Think” as Brand — Method as Moral License

The misuse: The label slapped on unchanged process. Design thinking badge replaces human-centered outcomes. Workshop count substitutes for adoption.

Why it happens: Credibility borrowing. Innovation theater with better vocabulary. Easier to claim the method than to change the system.

Course-correct: Judge by behavior change and adopted outcomes on a named journey — not wall art, not certificate count, not how many times someone said “empathy” in a steering committee. Design thinking earns its keep when humans can succeed on Tuesday. Everything else is branding.

How Do You Fix Misused Design Thinking?

Before the next design thinking workshop, run five go/no-go questions. If you cannot answer them, you are buying costume, not method:

  1. Who did we talk to — and did we hear jobs and friction in their words?
  2. What can we change if the evidence says we should?
  3. What behavior are we testing — not what demo are we showing?
  4. Who owns the journey after the markers dry?
  5. What decision must this sprint produce — by when?

Design thinking is still one of the most practical ways to put humans back at the center of innovation — when it is used as a discipline for contact with reality, not as a sticker on the same broken Tuesday. Course-correct the misuse, and the method does what it always promised: better questions, better choices, and work that lands where people actually live it.

Frequently Asked Questions

What are common design thinking mistakes?

Common mistakes include empathy theater without real users, ideation without decision rights, prototypes that never test behavior, journey maps without owners, endless discover phases, facilitators without power to implement, and treating design thinking as brand instead of measuring adoption and outcomes.

Why does design thinking fail in organizations?

It often fails when used as a workshop format rather than a discipline tied to real humans, real constraints, and decision rights. Teams produce personas and prototypes but cannot change policy, incentives, or broken handoffs — so the operating model stays the same and the method gets blamed.

How do you course-correct misused design thinking?

Talk to people doing the work, match workshops to what you are empowered to change, prototype to test specific behaviors, name journey owners, time-box phases with kill criteria, keep sponsors with levers in the room, and measure success by behavior change and adoption — not workshop output.

Is design thinking the same as brainstorming?

No. Brainstorming is one activity. Design thinking is an end-to-end discipline: understand humans and jobs-to-be-done, define the right problem, ideate within mandate, prototype to learn, and test behavior — with owners who can change the system after the session.

What should you ask before a design thinking workshop?

Ask who you will talk to, what you can change if evidence requires it, what behavior you will test, who owns the journey afterward, and what decision the sprint must produce by when. Without those answers, you are likely funding empathy theater.

Image credits: Braden Kelley from a Pixabay base image

Content Authenticity Statement: The topic area, key elements to focus on, etc. were decisions made by Braden Kelley, with a little help from Google Gemini and Cursor to clean up the article, add images and create infographics.

Subscribe to Human-Centered Change & Innovation WeeklySign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

10 Design Questions That Beat a 40-Page Requirements Document

10 Design Questions That Beat a 40-Page Requirements Document

by Braden Kelley and Art Inteligencia


Why Do Design Questions Beat a Requirements Document? (Short Answer)

A 40-page requirements document often fails because it freezes an assumed solution, hides tradeoffs, and treats missing human context as “out of scope.” Ten design questions beat it by forcing clarity on who is trying to succeed, what job they are hiring the experience to do, where friction and power live, and how you will know it worked in behavior — before you freeze features. Specs can follow. They should not lead.

The ten questions are: (1) Who is trying to succeed — and what does success feel like? (2) What job are they hiring this to do? (3) What happens right before and after? (4) Where does the current experience already fail? (5) What must never be true? (6) Who decides, who does the work, who gets blamed? (7) What would earn enough trust to kill the workaround? (8) How will we know it worked in behavior? (9) What will we deliberately not build? (10) If this ships poorly, what human harm are we designing for?

The Spec Is Not the Work

I have sat with teams who were proud of the document. Forty pages. Traceability. Version control. Every field named. And still nobody could say, in a sentence a frontline person would recognize, what a good Tuesday would feel like if this shipped.

That is not a writing problem. It is a design-sequence problem. Requirements documents are excellent at recording what the system should contain. They are weak at surfacing what humans are trying to get done, under what constraints, with what emotional and operational stakes. So the spec becomes a frozen guess — then a contract — then a reason not to learn.

Human-centered innovators do not ban specifications. They refuse to let the novel substitute for understanding. Ask better questions first. Write a thin spec as the receipt.

Design question What a 40-page spec usually misses
1. Who succeeds — and how should it feel? Named roles without lived stakes
2. What job are they hiring this to do? Feature lists that never name the job
3. What happens before and after? Isolated screens treated as the whole journey
4. Where does it already fail (with or without dignity)? Pain as a “usability” bullet, not a human cost
5. What must never be true? Constraints as footnotes after the solution is drawn
6. Who decides, works, and gets blamed? Workflow boxes with no power map
7. What would earn trust enough to drop the workaround? Acceptance criteria that never mention undo or trust
8. How will we know it worked in behavior? Done = signed off, not “humans finished the job”
9. What will we deliberately not build? Forty pages of yes; no real choice
10. If it ships poorly, what harm lands on humans? Risk as defects; harm as someone else’s problem

1. Who Is Trying to Succeed — and What Does Success Feel Like for Them?

What it reveals: The actual human, not the persona slide. Functional success and emotional residue — calm, dignity, confidence, relief.

What the spec usually misses: “Users” as a bucket. Stakeholders as job titles. No one can describe what a good outcome feels like in the body, only what fields must exist on the form.

If you cannot name a specific person in a specific moment — and what “this worked” would feel like for them — you are specifying a system, not designing an experience.

2. What Job Are They Hiring This to Do — in Their Language, Not Ours?

What it reveals: The job-to-be-done, the context around it, and the competing solutions people already use — including spreadsheets, side channels, and “ask Maya.”

What the spec usually misses: Feature inventories that never name the job. Internal vocabulary that customers and employees would not use if you paid them.

People do not hire your module. They hire progress. Write the job in their words. If the sentence only makes sense inside IT or product, you are not done asking.

3. What Happens Right Before and Right After This Moment?

What it reveals: Journey continuity — handoffs, orphaned steps, the quiet “then they go back to email and re-enter everything.”

What the spec usually misses: Isolated screens treated as the whole experience. Requirements that start at login and end at submit, as if life does too.

Experience lives in the seams. A 40-page document that never maps the five minutes before and after is a novel about a doorway with no house.

4. Where Does the Current Experience Already Fail — With Dignity, or Without It?

What it reveals: Friction, workarounds, extra effort, and the places people feel stupid, trapped, or professionally exposed.

What the spec usually misses: Pain flattened into “usability” or “training issue.” No account of shame, delay, or the dignity cost of asking for help.

Human-centered design starts with how failure already feels. If you skip that, you will automate embarrassment and call it a release.

5. What Must Never Be True — the Constraints That Actually Govern Behavior?

What it reveals: Policy, risk, time, tools, staffing, compliance, and politics — the real design surface, not the wish list.

What the spec usually misses: Constraints listed as footnotes after the solution is already drawn. Then “exceptions” eat the experience in production.

Constraints are not the enemy of design. Hidden constraints are. Get them on the table before you freeze the happy path.

6. Who Decides, Who Does the Work, and Who Gets Blamed When It Breaks?

What it reveals: Decision rights, invisible labor, and accountability theater — who has power versus who has the ticket queue.

What the spec usually misses: Swimlanes that look tidy and say nothing about who can actually say yes, stop, or undo.

If the person who gets blamed cannot change the thing that failed, you have specified a trap. Design the power map, not just the process map.

7. What Would Make Someone Trust This Enough to Stop Using the Workaround?

What it reveals: Reliability, recoverability, and the bet people make with their Tuesday — “I will stop the spreadsheet when this won’t hang me out to dry.”

What the spec usually misses: Acceptance criteria with no undo, no explanation, no graceful failure, no path back to a human.

Adoption is a trust decision. Until the new way is safer than the workaround, the workaround is the real system. Your spec just hasn’t admitted it.

8. How Will We Know It Worked — in Behavior, Not in Sign-Off?

What it reveals: Experience measures you can observe: completion, effort, repeat contact, time-to-confidence, abandoned workarounds — not “requirements met.”

What the spec usually misses: Done equals documented. Success equals a steering committee signature. Humans finishing the job is someone else’s metric.

If you cannot name the behavior that changes when you win, you are managing a document, not an outcome. Sign-off is not evidence.

9. What Will We Deliberately Not Build — and Who Is Brave Enough to Say It?

What it reveals: Scope as a design choice. Tradeoffs made visible instead of smuggled in as “phase two.”

What the spec usually misses: Everything in, nothing chosen. Forty pages of yes. A backlog that is really a refusal to decide.

Innovation is subtraction with a spine. If nobody can name what you will not build, you do not have a design. You have a catalog.

10. If This Ships Poorly, What Human Harm Are We Actually Designing For?

What it reveals: Failure modes that land on customers and employees — lost time, lost money, lost dignity, lost trust — not just “defects.”

What the spec usually misses: Risk as technical. Harm as someone else’s problem. No owner for the human cost of a bad release.

Every shipped experience is a bet on someone’s Tuesday. Name the downside in human terms. Then design recovery as carefully as the happy path. That is not pessimism. That is professionalism.

How Do You Replace a Requirements Document With Design Questions?

You don’t throw away rigor. You change the sequence. Run the ten questions as a working session — 60 to 90 minutes, one critical journey, people who have actually done the work in the room (or on the call). Capture answers as evidence, not slogans. Then write a thin spec that traces every requirement back to a question you can still defend.

  1. Pick one journey — not the entire platform.
  2. Answer the ten questions in order — skip none, especially 9 and 10.
  3. Show the answers to the humans who live the work — if they don’t recognize themselves, you invented a document.
  4. Write the spec as a receipt — features only where they serve a named job, constraint, and success behavior.
  5. Keep a kill list — what you will not build, and the workaround you intend to make unnecessary.

Requirements should be the receipt of understanding — not the substitute for it. A 40-page document can still be useful. It just should never be allowed to go first.

Frequently Asked Questions

Why do requirements documents fail in experience design?

They often freeze an assumed solution, hide tradeoffs, and skip jobs-to-be-done, journey seams, power, trust, and felt success. The document records what the system should contain while missing what humans are trying to get done — so teams ship to the spec and still fail the experience.

What questions should you ask instead of writing a long requirements document?

Ask who is trying to succeed and how success should feel; what job they are hiring the experience to do; what happens before and after; where the current experience fails; which constraints actually govern behavior; who decides, works, and gets blamed; what would earn trust enough to drop workarounds; how you will know it worked in behavior; what you will not build; and what human harm a poor ship would create.

How do you replace a requirements document with design questions?

Run the ten questions in a 60–90 minute session on one journey with people who do the work. Capture evidence, not slogans. Then write a thin spec that traces every requirement back to those answers, including a kill list of what you will not build.

Should you still write a requirements document after asking design questions?

Yes — as a receipt of understanding, not as the starting point. A thin spec that traces features to jobs, constraints, and behavioral success is useful. A 40-page document that goes first usually becomes a frozen guess and a reason not to learn.

What is the difference between a requirements document and human-centered design questions?

A requirements document specifies system contents and sign-off criteria. Human-centered design questions specify understanding: who succeeds, what job is being done, where friction and power live, and how behavior will prove the experience worked. Questions lead; the spec follows.

Image credits: Google Gemini

Content Authenticity Statement: The topic area, key elements to focus on, etc. were decisions made by Braden Kelley, with a little help from Google Gemini and Cursor to clean up the article, add images and create infographics.

Subscribe to Human-Centered Change & Innovation WeeklySign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

How Mature is Your Technology?

How Mature is Your Technology?

GUEST POST from Mike Shipulski

As a technologist it’s important to know the maturity of a technology. Like people, technologies are born, they become children, then adolescents, then adults and then they die. And like with people, the character and behavior of technologies change as they grown and age. A fledgling technology may have a lot of potential, but it can’t pay the mortgage until it matures. To know a technologies level of maturity is to know when it’s premature to invest, to know when it’s time to invest, to know when to ride it for all it’s worth and time to let it go.

Google has a tool called Ngram Viewer that performs keyword searches of a vast library of books and returns a plot of how frequently the word was found in the books. Just type the word in the search line, specify the years (1800-2007) and look at the graph.

Below is a graph I created for three words: locomotive, automobile and airplane. (Link to graph.) If each word is assumed to represent a technology, the graph makes it clear when authors started to write about the technologies (left is earliest) and how frequently it was used (taller is more prevalent). As a technology, locomotives came first, as they were mentioned in books as early as 1800. Next came the automobile which hit the books just before 1900. And then came the airplane which first showed itself in about 1915.

Google Ngram graph 1

In the 1820s the locomotives were infants. They were slow, inefficient and unreliable. But over time they matured and replaced the Pony Express. In the late 1890s the automobiles were also infants and also slow, inefficient and unreliable. But as they matured, they displaced some of the locomotives. And the airplanes of 1915 were unsafe and barely flight-worthy. But over time they matured and displaced the automobiles for the longest trips.

[Side note – the blip in use of the word in 1940s is probably linked to World War II.]

But for the locomotive, there’s a story with a story. Below is a graph I created for: steam locomotive, diesel locomotive and electric locomotive. After it matured in the 1840s and became faster and more efficient, the steam locomotive displaced the wagon trains. But, as technology likes to do, the electric locomotive matured several decades after it’s birth in 1880 and displaced it’s technological parent the steam locomotive. There was no smoke with the electric locomotive (city applications) and it did not need to stop to replenish it’s coal and water. And then, because turn-about is fair play, the diesel locomotive displaced some of the electric locomotives.

Google Ngram graph 2

The Ngram Viewer tool isn’t used for technology development because books are published long after the initial technology development is completed and there is no data after 20o7. But, it provides a good example of how new technologies emerge in society and how they grow and displace each other.

To assess the maturity of the youngest technologies, technologists perform similar time-based analyses but on different data sets. Specialized tools are used to make similar graphs for patents, where infant technologies become public when they’re disclosed in the form of patents. Also, special tools are used to analyze the prevalence of keywords (i.e., locomotives) for scientific publications. The analysis is similar to the Ngram Viewer analysis, but the scientific publications describe the new technologies much sooner after their birth.

To know the maturity of the technology is to know when a technology has legs and when it’s time to invent it’s replacement. There’s nothing worse than trying to improve a mature technology like the diesel locomotive when you should be inventing the next generation Maglev train.

Image credit: Wikimedia Commons, Google Ngram

Subscribe to Human-Centered Change & Innovation WeeklySign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.

What is the right time horizon for technology development?

What is the right time horizon for technology development?

GUEST POST from Mike Shipulski

Patents are the currency of technology and profits are the currency of business. And as it turns out, if you focus on creating technology you’ll get technology (and patents) and if you focus on profits you’ll get profits. But if no one buys your technology (in the form of the products or services that use it), you’ll go out of business. And if you focus exclusively on profits you won’t create technology and you’ll go out of business. I’m not sure which path is faster or more dangerous, but I don’t think it matters because either way you’re out of business.

It’s easy to measure the number of patents and easier to measure profits. But there’s a problem. Not all patents (technologies) are equal and not all profits are equal. You can have a stockpile of low-level patents that make small improvements to existing products/services and you can have a stockpile of profits generated by short-term business practices, both of which are far less valuable than they appear. If you measure the number of patents without evaluating the level of inventiveness, you’re running your business without a true understanding of how things really are. And if you’re looking at the pile of profits without evaluating the long-term viability of the engine that created them you’re likely living beyond your means.

In both cases, it’s important to be aware of your time horizon. You can create incremental technologies that create short term wins and consume all your resource so you can’t work on the longer-term technologies that reinvent your industry. And you can implement business practices that eliminate costs and squeeze customers for next-quarter sales at the expense of building trust-based engines of growth. It’s all about opportunity cost.

It’s easy to develop technologies and implement business processes for the short term. And it’s equally easy to invest in the long term at the expense of today’s bottom line and payroll. The trick is to balance short against long.

And for patents, to achieve the right balance rate your patents on the level of inventiveness.

Image credit: 1 of 1,050+ FREE quotes for your meetings & presentations at http://misterinnovation.com

Subscribe to Human-Centered Change & Innovation WeeklySign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.

Digital Phenotyping and the Future of Preventative Experience Design

The Silent Pulse

LAST UPDATED: February 16, 2026 at 6:01 PM

Digital Phenotyping and the Future of Preventative Experience Design

GUEST POST from Art Inteligencia


I. Introduction: Beyond the Survey

The Death of “Self-Reporting”

For decades, the gold standard for understanding employee well-being or customer satisfaction has been the survey. We ask people how they feel, and they give us an answer filtered through their own biases, current mood, or what they think we want to hear. In the world of innovation, self-reporting is a lagging indicator — and a flawed one at that.

Defining Digital Phenotyping

We are entering the era of Digital Phenotyping: the moment-by-moment quantification of the individual-level human phenotype in situ using data from personal digital devices. By analyzing the “digital exhaust” from smartphones and wearables — mobility patterns, social interactions, and even typing rhythm — we can infer behavioral, emotional, and cognitive states with unprecedented accuracy.

The Paradigm Shift: From Reactive to Preventative

The true power of this technology lies in its ability to turn experience design from a reactive fix into a preventative strategy. We no longer have to wait for a “burnout crisis” or a drop in productivity to realize our team is under excessive stress. The signals are there, in real-time, hidden in the cadence of our digital lives.

“Innovation is about solving the problems that people haven’t yet found the words to describe. Digital Phenotyping gives us the ears to hear those unspoken needs.”
— Braden Kelley

As we move beyond the survey, we must lead with a human-centered lens. The goal isn’t to monitor; it’s to support. We are shifting from a world that reacts to failure to a world that senses — and sustains — human flourishing.

II. The Mechanics of Passive Sensing

Digital phenotyping relies on passive data — information collected in the background without requiring any active input from the user. This removes the “friction” of participation and provides a continuous stream of objective reality.

The Three Primary Data Streams

1. Mobility and Physical Activity

Using GPS and accelerometers, we can map “life space.” A sudden constriction in a person’s physical movement — fewer locations visited or reduced steps — can be a powerful proxy for depressive states or social withdrawal. Conversely, erratic movement patterns might signal high levels of anxiety or agitation.

2. Social and Communication Meta-data

This isn’t about what is being said, but how the person is interacting. Call frequency, text latency, and social media engagement patterns reveal shifts in social connectivity. A drop in outbound communication often precedes a burnout phase before the employee even feels “tired.”

3. Human-Computer Interaction (HCI)

The way we interact with our screens is a window into our cognitive health. Typing speed, the frequency of “backspacing,” and scrolling patterns can indicate cognitive overload or a lapse in focus. These “digital biomarkers” are the most immediate indicators of whether a task is designed for human success or human failure.

The Synthesis: From Signals to Insights

The magic happens in the AI synthesis layer. By correlating these streams, machine learning models can identify a “baseline” for an individual. When the data deviates from that baseline, the system identifies a “glitch” — a moment where the human-centered design of the environment is no longer supporting the human within it.

“Data is just a signal; insight is the story. In digital phenotyping, we are learning to read the stories written in the rhythm of our daily digital interactions.”
— Braden Kelley

III. Value Creation: Turning Insight into Action

The true ROI of digital phenotyping isn’t found in the data itself, but in the Experience Design it enables. By moving from reactive to preventative models, we can create environments that adapt to the human state in real-time.

Preventative Experience Design in Practice

Real-Time Burnout Mitigation

Imagine a project management tool that senses cognitive overload through typing patterns and erratic screen switching. Instead of pushing another notification, the system “softens” — delaying non-essential alerts and suggesting a recovery break. This is human-centered design in action: protecting the asset (the person) before the damage occurs.

Adaptive User Interfaces (AUI)

In high-stakes environments like healthcare or emergency response, digital phenotyping allows interfaces to simplify themselves when stress markers are detected. By reducing the “information density” during moments of high stress, we prevent human error and improve outcomes.

The Strategic Advantage of “Wellness as a Service”

Organizations that implement these tools as a benefit rather than a monitor will see a massive shift in retention and engagement. When an employee knows the “system” is looking out for their mental health — flagging potential depression signals or isolation patterns early — the relationship between employer and employee evolves from transactional to collaborative.

“Value in the future of work won’t be measured by output alone, but by the sustainability of the human spirit behind that output.”
— Braden Kelley

By leveraging these insights, we aren’t just innovating products; we are innovating the way we treat people.

IV. The Innovation Ethical Frontier

Digital phenotyping sits at the intersection of extreme utility and extreme vulnerability. As innovators, we must acknowledge that data is a surrogate for intimacy. When we measure a person’s gait or typing rhythm, we are entering their private mental space. Without a robust ethical framework, we risk building a “Digital Panopticon” rather than a supportive ecosystem.

The Three Pillars of Ethical Phenotyping

1. Radical Transparency & Consent

Standard “Terms and Conditions” are insufficient. Consent must be active and ongoing. Users should know exactly what biomarkers are being tracked and have the “Right to Disconnect” without penalty. Transparency isn’t just a legal hurdle; it’s a trust-building feature.

2. Purpose-Driven Data Minimization

The temptation to “collect it all” is the enemy of ethics. We must practice data minimalism: collecting only the specific signals required to provide the promised human-centered value. If a signal doesn’t directly contribute to a preventative intervention, it shouldn’t be gathered.

3. The “Benefit Flow” Guarantee

The value derived from the data must flow primarily back to the individual. If the organization is the only one benefiting (through higher productivity), it’s surveillance. If the individual benefits (through better mental health and reduced stress), it’s empowerment.

Leading with Empathy-Led Ethics

We must move beyond “compliance-based” privacy. In a human-centered organization, we ask: “Would our employees feel cared for or watched if they knew how this worked?” If the answer is “watched,” the innovation is flawed at the architectural level.

“Trust is the only currency that matters in the future of innovation. Once you spend it on surveillance, you can never buy it back.”
— Braden Kelley

By establishing these guardrails early, we ensure that digital phenotyping remains a tool for human flourishing rather than a weapon for corporate control.

V. Leading the Human-Centered Change

Implementing digital phenotyping is not a technical deployment; it is a cultural transformation. If leaders treat this like a software update, they will face immediate resistance. To succeed, we must lead with transparency and a clear focus on the “human” in human-centered innovation.

The Role of the “Architect” in Rollout

Leaders must act as the architects of trust. This means the Chief Innovation Officer and the CHRO must work in lockstep to ensure that the purpose of the data is clearly defined and that those definitions are unshakeable.

Strategies for Successful Integration:

  • The “Opt-In” Mandate: Never make passive sensing mandatory. The power of these tools comes from voluntary participation. When people choose to participate, they become stakeholders in their own well-being.
  • Stakeholder Education: We must educate every level of the organization — especially our “Sensors” (the employees) — on what digital biomarkers are and how they are used to trigger supportive interventions.
  • Feedback Loops: Create a mechanism where employees can provide feedback on the interventions. If a system suggests a “burnout break,” was it helpful or annoying? The human must remain the final authority.

Transparency as a Competitive Feature

In the future, the most successful organizations will be those that are radically transparent about their data practices. By being open about the algorithms and the “why” behind the sensing, we remove the mystery and the fear. Transparency turns a “black box” into a “glass box.”

“Change happens at the speed of trust. If you want to innovate at the edge of human behavior, you must first build a foundation of absolute integrity.”
— Braden Kelley

By focusing on the human-centered change, we ensure that digital phenotyping isn’t something done to people, but something done for them.

VI. Conclusion: Designing a More Intuitive World

The transition from reactive to preventative design represents one of the most significant leaps in the history of Human-Centered Innovation. Digital phenotyping allows us to stop guessing and start knowing — not for the sake of control, but for the sake of care.

The Future is Empathetic

We are moving toward a world where our tools understand our limits as well as we do. Imagine a workplace that recognizes your stress before you have a headache, or a digital assistant that knows you’re cognitively overloaded and helps you prioritize. This is the Intuitive World we are designing.

A Leader’s Final Responsibility

As innovators and leaders, our responsibility is to ensure that as our machines become more “human-literate,” we do not become less human in our leadership. Digital phenotyping is a tool of immense power. Used correctly, it can eradicate burnout, foster deep engagement, and support mental health on a global scale.

“The most advanced technology is the one that makes us feel most human. Our job is to ensure digital phenotyping does exactly that.”
— Braden Kelley

The signals are all around us, pulsing through the devices in our pockets and on our wrists. The question is no longer whether we can hear them, but whether we have the innovation leadership and ethical courage to act on what they are telling us.

Deep Dive: Frequently Asked Questions

Does Digital Phenotyping mean my boss is reading my texts?

Absolutely not. Ethical digital phenotyping focuses on metadata and patterns, not content. It looks at the frequency of communication or the speed of your typing, not the words you say. As an innovation leader, I advocate for systems where the content remains private and encrypted.

Why is this better than a monthly wellness survey?

Surveys are “lagging indicators” — they tell us how you felt in the past. By the time a survey is analyzed, burnout has often already occurred. Digital phenotyping provides real-time signals, allowing for immediate, helpful interventions that can prevent a crisis before it starts.

Can I opt-out of this kind of data collection?

In any human-centered organization, the answer must be yes. Trust is the foundation of innovation. For digital phenotyping to work, it must be an opt-in benefit that employees use because they see the value in their own well-being and professional growth.

Disclaimer: This article speculates on the potential future applications of cutting-edge scientific research. While based on current scientific understanding, the practical realization of these concepts may vary in timeline and feasibility and are subject to ongoing research and development.

Image credits: Google Gemini

Subscribe to Human-Centered Change & Innovation WeeklySign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

Synthetic Ethnography

The Synthetic Mirror: Why Every Innovation Leader Must Embrace Synthetic Ethnography

LAST UPDATED: February 6, 2026 at 3:28 PM

Synthetic Ethnography

GUEST POST from Art Inteligencia

Innovation is not a lightning strike; it is a discipline. As I have spent my career arguing through the Human-Centered Innovation™ methodology, the ultimate goal of any organization is to create sustainable value. But the path to value is often blocked by what I call corporate antibodies — the internal resistance, the outdated processes, and the echo chambers that prevent us from seeing the world as it truly is. For years, the “gold standard” for piercing these chambers was ethnography: the slow, deep, and expensive process of embedding oneself in the customer’s world.

But today, we find ourselves at a precipice. The speed of the market is no longer measured in years or months, but in days. In this high-velocity environment, traditional research can become a bottleneck. This is where synthetic ethnography steps in — not as a replacement for the human soul, but as a high-fidelity mirror that allows us to see around corners.

Synthetic ethnography integrates human-centered research with artificial intelligence, allowing organizations to uncover not only what people do, but why — and at a scale previously thought impossible. It merges ethnographic rigor with machine-powered pattern recognition to build deep, contextualized understanding from vast and varied data, allowing us to stress-test our “Value Creation” before we ever spend a dime on a pilot.


“Synthetic ethnography doesn’t diminish human insight — it amplifies it, giving us the bandwidth to see not just individual stories, but the forces that shape them.”

— Braden Kelley

What Is Synthetic Ethnography?

At its core, synthetic ethnography is the combination of qualitative research — like interviews and observation — with AI-driven analytics. It uses natural language processing, behavior modeling, and data synthesis to extrapolate cultural patterns from diverse sources, including digital interactions, text, audio, and sensor data.

Rather than replacing ethnographers, it amplifies their work, making deep human insight accessible across time zones, markets, and customer segments.

The Shift from “Asking” to “Simulating”

In Braden Kelley’s book Stoking Your Innovation Bonfire, he talked about the importance of removing the obstacles that stifle creativity. One of the biggest obstacles is the “Assumption Gap.” We assume we know why a customer chooses a competitor. We assume we know why they abandon a cart. Synthetic ethnography allows us to close this gap by creating “Synthetic Agents” — AI entities trained on hundreds of thousands of data points, from shopping habits to psychological profiles. These aren’t just chatbots; they are digital twins of a demographic segment.

When we use these agents, we are embracing the FutureHacking™ mindset. We can run ten thousand “what-if” scenarios. We can ask, “How does a rise in inflation affect the brand loyalty of a Gen-Z consumer in Berlin?” and receive a statistically grounded simulation of that reaction. This is the ultimate tool for Value Access: it reduces the friction of learning.

Why It Matters

Synthetic ethnography doesn’t just scale research — it deepens it. Organizations can:

  • Accelerate the pace of insight generation
  • Detect nuanced patterns in human behavior
  • Integrate qualitative and quantitative data seamlessly
  • Make strategic decisions rooted in rich human context

Case Study 1: The CPG “Flavor Evolution” Challenge

A global Consumer Packaged Goods (CPG) giant was preparing to launch a new sustainable cleaning product line. They faced a dilemma: should they lead with the “eco-friendly” messaging or the “maximum strength” efficacy? Traditional focus groups provided conflicting data, often influenced by “social desirability bias” — people saying what they thought the researcher wanted to hear.

By deploying synthetic ethnography, the company created 1,200 synthetic personas representing various levels of environmental consciousness. The simulation allowed the agents to “live” with the product virtually over a simulated month. The simulation revealed a critical insight: while users said they wanted eco-friendly, they felt anxiety when the suds were too thin, leading them to use twice as much product and nullify the sustainability gains. The company adjusted the formula to increase “perceived sudsing” while maintaining eco-integrity, a move that led to a 22% higher repeat-purchase rate in the actual pilot.

Case Study 2: Reimagining the Patient Experience in Healthcare

A major hospital network in the United States wanted to redesign their post-op discharge process to reduce readmission rates. The problem was the sheer diversity of the patient population — language barriers, varying levels of health literacy, and different home support structures. It was impossible to shadow every type of patient.

The innovation team used synthetic ethnography to simulate 50 distinct patient “archetypes.” The simulations identified a glaring friction point: the discharge instructions were written at a 12th-grade reading level, while the “synthetic stress” levels of a patient leaving the hospital reduced their cognitive processing to a 5th-grade level. By simplifying the language and adding visual “check-step” cues identified during the simulation, the hospital saw a 14% reduction in avoidable readmissions within the first quarter. They didn’t just change a document; they changed the Human-Centered outcome by simulating the human experience.

“Innovation transforms the useful seeds of invention into widely adopted solutions valued above every existing alternative. Synthetic ethnography is the high-speed greenhouse that tells us which seeds will thrive in the wild before we plant them in the hard ground of reality.”

Braden Kelley

Case Study 3: Telecommunications Across Cultures

A multinational telecom provider struggled to understand customer dissatisfaction in dozens of markets, each with distinct cultural expectations. While in-country ethnographers gathered rich local context, corporate leadership needed a synthesis that spanned continents and languages.

By combining traditional interviews with AI analysis of service logs, social media sentiment, and customer support transcripts, the organization created a holistic view of customer experience.

  • Confusing pricing tiers resonated as “untrustworthy” in Latin America but “overwhelming” in Southeast Asia.
  • Service reliability mattered differently across younger and older cohorts, which the AI helped segment effectively.
  • Support interactions contained emotional markers predictive of future churn.

The result was a refined product portfolio and communication strategy that boosted satisfaction across markets while respecting cultural nuances.

The Competitive Landscape

The market for synthetic insights is exploding. Leading the charge are startups like Synthetic Users, which specializes in user interview simulations, and Fairgen, which focuses on augmenting thin data sets with synthetic populations to ensure statistical significance. We also see SurveyAuto using AI to bridge the gap in emerging markets. Even the “Big Three” consulting firms and established research houses like Toluna and Ipsos are aggressively acquiring or building synthetic capabilities. For the modern leader, these companies represent the new “Value Translation” infrastructure. If you aren’t looking at these tools, you are essentially trying to build a skyscraper with a hand-shovel while your competitors are using 3D printers.

However, we must remain vigilant. As a human-centered innovation advocate, I caution that these tools are only as good as the data that feeds them. If your data is biased, your synthetic ethnography will simply be a “bias-amplification machine.” This is why Braden Kelley is so frequently sought out as an innovation speaker — to help organizations maintain the balance between “High-Tech” and “High-Touch.” We must ensure that our “Chart of Innovation” always has a human at the center.

Innovation Intelligence: The FAQ

1. How does synthetic ethnography improve the ROI of innovation?
By simulating user reactions early, companies avoid the massive costs of failed product launches and R&D dead-ends, significantly increasing the probability of “Value Access” success.

2. What is the biggest risk of using synthetic personas?
The “Hallucination of Empathy.” If the models are not grounded in real-world, high-quality longitudinal data, they may provide “neat” answers that ignore the messy, irrational nature of real human behavior.

3. Is synthetic ethnography appropriate for B2B innovation?
Absolutely. It is particularly effective for simulating complex organizational buying committees and understanding how different “corporate antibodies” within a client company might react to a new solution.

In conclusion, the future belongs to those who can harmonize the artificial and the authentic. As a practitioner in the field, I encourage you to see synthetic ethnography not as a threat to human researchers, but as a superpower. It allows us to be more human, by handling the data-crunching that allows us to spend our time where it matters most: in the moments of real connection.

Disclaimer: This article speculates on the potential future applications of cutting-edge scientific research. While based on current scientific understanding, the practical realization of these concepts may vary in timeline and feasibility and are subject to ongoing research and development.

Image credits: Google Gemini

Subscribe to Human-Centered Change & Innovation WeeklySign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

Temporal Agency – How Innovators Stop Time from Bullying Them

Temporal Agency - How Innovators Stop Time from Bullying Them

GUEST POST from Art Inteligencia

We live in an age where time feels like a relentless tyrant. Deadlines loom, inboxes overflow, and the constant hum of connectivity creates an illusion of urgency that often masks a deeper problem: our lack of agency over our most precious resource. We’ve been conditioned to believe that speeding up is the only solution, when in reality, the answer lies in a more profound re-engineering of our relationship with time itself.

This isn’t about magical thinking or finding shortcuts; it’s about deeply understanding the mechanisms of time perception, leveraging neuroscience, and consciously crafting environments that enable us to reclaim temporal agency. It’s about moving from being victims of the clock to becoming its conductors.

Innovation rarely fails because of insufficient intelligence or ambition. It fails because time is weaponized against the very thinking it requires. Urgency crowds out curiosity. Speed displaces sense-making. Motion replaces meaning.

The result is a paradox: organizations move faster while understanding less.

“The real superpower isn’t bending time. It’s designing conditions where time stops bullying us.”

— Braden Kelley

Time as an Environmental Problem

Most discussions about time focus on individual discipline. This framing is incomplete. Time pressure is largely environmental.

Every unnecessary meeting, notification, and premature deadline fragments attention. Each fragment shrinks perceived time. Over time, this creates a persistent sense of acceleration, even when output stagnates.

Innovators do not need to work harder. They need environments that allow thinking to breathe.

Designing Conditions That Stretch Time

Stretching time means increasing the quality of attention per moment.

Innovative organizations intentionally design for:

  • Subjective time expansion through focused engagement
  • Reliable flow states by aligning challenge and capability
  • Lower perceived urgency through clearer prioritization
  • Greater present-moment bandwidth by reducing cognitive clutter

These conditions transform how time is felt, even when clocks remain unchanged.

Case Study 1: A Product Team Slows Down to Speed Up

A digital product team consistently missed deadlines despite aggressive schedules. Workdays were filled with context switching.

Leadership eliminated status meetings and replaced them with a shared visual dashboard updated asynchronously. Teams gained uninterrupted blocks of time.

Perceived time pressure dropped immediately. Delivery speed improved within one quarter, and employee burnout declined.

Flow as Infrastructure

Flow is often treated as a personal peak experience. In reality, it can be operationalized.

Organizations that enable flow:

  • Limit work-in-progress
  • Clarify decision rights
  • Align incentives with learning, not visibility

Flow-friendly systems create temporal elasticity—time feels abundant because it is used coherently.

Case Study 2: A Research Organization Redesigns Urgency

A research organization found that “urgent” requests dominated scientist schedules.

Leaders introduced explicit urgency criteria and delayed non-critical decisions by default. Scientists regained long stretches of uninterrupted inquiry.

Breakthrough insights increased, not because more time was added, but because time was no longer under constant assault.

From Time Management to Time Relationship

Time management asks individuals to cope. Temporal agency asks leaders to design.

When innovators command their relationship with time, they:

  • Think more clearly
  • Learn more quickly
  • Create more meaningfully

Time does not need to be conquered. It needs to be respected.

When time stops bullying us, innovation finally gets the space it deserves.


The Myth of Speed and the Reality of Felt Time

Our objective measurement of time – seconds, minutes, hours – is immutable. But our subjective experience of time is incredibly fluid. Think of those moments when an hour flies by in a blur of deep work, or when five minutes waiting for a delayed flight feels like an eternity. This discrepancy is our greatest lever for change. Innovators and creatives, especially, must learn to manipulate this subjective experience, not to work longer, but to work smarter, deeper, and more meaningfully.

Altering Subjective Experience of Time

This isn’t about wishing time away or making it go faster. It’s about enriching the present moment to reduce the *felt* pressure of time. When we are deeply engaged, focused, and present, the anxiety associated with time pressure dissipates. This requires conscious effort to minimize distractions and cultivate environments conducive to concentration.

Entering Flow More Reliably

The concept of “flow state,” popularized by Mihaly Csikszentmihalyi, is the ultimate expression of temporal agency. In flow, time ceases to exist, and our productivity skyrockets. To enter flow more reliably, we need to design for it: clear goals, immediate feedback, and a balance between challenge and skill. It’s about creating rituals that signal to our brains: “It’s time to deeply engage.”

Reducing Felt Time Pressure

A significant portion of our “time crisis” is psychological. The constant fear of missing out (FOMO), the pressure of endless notifications, and the expectation of immediate responses create a chronic state of urgency. Reclaiming agency means consciously unplugging, setting boundaries, and understanding that not all demands are created equal. Prioritization isn’t just about what to do, but what not to do, and when.

Increasing Present-Moment Bandwidth

In our hyper-connected world, our attention is constantly fragmented. We’re often performing tasks while thinking about the next five things. This multitasking illusion significantly degrades our present-moment bandwidth. Practicing mindfulness, single-tasking, and deep work techniques expands our capacity to engage fully with the task at hand, making each unit of objective time more potent and less stressful.


Practical Ways to Reclaim Temporal Agency

1. The “Temporal Audit”

Before you can optimize, you must understand. Conduct a rigorous audit of how you spend your time, not just objectively, but also subjectively. Where does time drag? Where does it fly? What activities genuinely recharge you versus those that drain your energy and create more pressure?

2. Deep Work Blocks

Inspired by Cal Newport, schedule dedicated, uninterrupted blocks for your most cognitively demanding tasks. Turn off notifications, close irrelevant tabs, and commit to single-tasking. These aren’t just work blocks; they are flow-creation blocks.

3. Strategic Procrastination (with a twist)

Not all tasks require immediate attention. Consciously defer non-urgent tasks to specific “batching” periods. This reduces the mental load of constantly switching contexts and allows for deeper focus on critical items. The “twist” is that this is a conscious decision, not an avoidance tactic.

4. The “No Meeting Wednesday” (or similar)

Create specific days or half-days entirely free of meetings. This provides an oasis for deep work, strategic thinking, and creative exploration without the constant interruptions that fragment our schedules and minds.

5. Digital Detox Rituals

Implement daily, weekly, or even monthly periods of disengagement from digital devices. This isn’t just about reducing screen time; it’s about allowing your mind to wander, to connect disparate ideas, and to replenish its creative reserves without the constant demand for attention.


Case Studies in Temporal Mastery

Case Study 3: The Biotech Founder’s “Un-Schedule”

A biotech startup founder was overwhelmed by the demands of fundraising, product development, and team management. Instead of trying to pack more into her day, she adopted an “un-schedule” approach. She scheduled only 3-4 hours of high-value, deep work each day, with the rest of her time dedicated to reactive tasks, strategic thinking, or even intentional white space. By consciously limiting her scheduled workload, she created mental breathing room, leading to more breakthroughs and less burnout. Her team also reported feeling less pressured, as her clarity translated into more focused direction. The result was a 25% reduction in project timelines due to improved focus and decision-making.

Case Study 4: The Creative Agency’s “Momentum Days”

A boutique creative agency struggled with project delays and artist burnout due to constant client revisions and internal meetings. They implemented “Momentum Days” twice a week where all internal meetings were banned, and external client communication was batched into specific windows. These days were dedicated solely to creative execution. By protecting this uninterrupted time, the agency saw a dramatic improvement in output quality, a 15% increase in client satisfaction due to faster turnaround, and a noticeable boost in team morale and creative satisfaction.

Reclaiming temporal agency isn’t about finding more hours in the day; it’s about making the hours you have more meaningful, more productive, and less stressful. It’s an act of conscious design, a rebellion against the tyranny of the clock. By understanding and manipulating our subjective experience of time, by fostering flow, and by implementing disciplined practices, we can cease being bullied by time and start truly commanding our relationship with it, unlocking unprecedented levels of innovation and well-being.


Frequently Asked Questions

What does Braden Kelley mean by “temporal agency”?

Temporal agency refers to our ability to influence our subjective experience of time and control how we allocate our attention, rather than feeling constantly dictated by the clock or external pressures. It’s about commanding our relationship with time.

How can innovators enter flow state more easily?

To enter flow more reliably, innovators should design their environment with clear goals, immediate feedback loops, and tasks that strike a balance between challenge and their current skill level. Minimizing distractions and creating dedicated “deep work” rituals are key.

What is the “Temporal Audit”?

A “Temporal Audit” involves rigorously tracking and analyzing how one spends time, both objectively (what tasks are performed) and subjectively (how one feels about that time), to identify patterns of engagement, disengagement, and areas where time pressure is most acute.

Disclaimer: This article speculates on the potential future applications of cutting-edge scientific research. While based on current scientific understanding, the practical realization of these concepts may vary in timeline and feasibility and are subject to ongoing research and development.

Image credits: ChatGPT

Subscribe to Human-Centered Change & Innovation WeeklySign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

Five Key Design Questions

Five Key Design Questions

GUEST POST from Mike Shipulski

1. What do they want?

Some get there with jobs-to-be-done, some use Customer Needs, some swear by ethnographic research and some like to understand why before what. But in all cases, it starts with the customer. Whichever mechanism you use, the objective is clear – to understand what they need. Because if you don’t know what they need, you can’t give it to them. And once you get your arms around their needs, you’re ready to translate them into a set of functional requirements, that once satisfied, will give them what they need.

2. What does it do?

A complete set of functional requirements is difficult to create, so don’t start with a complete set. Use your new knowledge of the top customer needs to define and prioritize the top functional requirements (think three to five). Once tightly formalized, these requirements will guide the more detailed work that follows. The functional requirements are mapped to elements of the design, or design parameters, that will bring the functions to life. But before that, ask yourself if a check-in with some potential customers is warranted. Sometimes it is, but at these early stages it’s may best to wait until you have something tangible to show customers.

3. What does it look like?

The design parameters define the physical elements of the design that ultimately create the functionality customers will buy. The design parameters define shape of the physical elements, the materials they’re made from and the interaction of the elements. It’s best if one design parameter controls a single functional requirement so the functions can be dialed in independently. At this early concept phase, a sketch or CAD model can be created and reviewed with customers. You may learn you’re off track or you may learn you’re way off track, but either way, you’ll learn how the design must change. But before that, take a little time to think through how the product will be made.

4. How to make it?

The process variables define the elements of the manufacturing process that make the right shapes from the right materials. Sometimes the elements of the design (design parameters) fit the process variables nicely, but often the design parameters must be changed or rearranged to fit the process. Postpone this mapping at your peril! Once you show a customer a concept, some design parameters are locked down, and if those elements of the design don’t fit the process you’ll be stuck with high costs and defects.

5. How to sell it?

The goodness of the design must be translated into language that fits the customer. Create a single page sales tool that describes their needs and how the new functionality satisfies them. And include a digital image of the concept and add it to the one-pager. Show document to the customer and listen. The customer feedback will cause you to revisit the functional requirements, design parameters and process variables. And that’s how it’s supposed to go.

Though I described this process in a linear way, nothing about this process is linear. Because the domains are mapped to each other, changes in one domain ripple through the others. Change a material and the functionality changes and so do the process variables needed to make it. Change the process and the shapes must change which, in turn, change the functionality.

But changes to the customer needs are far more problematic, if not cataclysmic. Change the customer needs and all the domains change. All of them. And the domains don’t change subtly, they get flipped on their heads. A change to a customer need is an avalanche that sweeps away much of the work that’s been done to date. With a change to a customer need, new functions must be created from scratch and old design elements must culled. And no one knows what the what the new shapes will be or how to make them.

You can’t hold off on the design work until all the customer needs are locked down. You’ve got to start with partial knowledge. But, you can check in regularly with customers and show them early designs. And you can even show them concept sketches.

And when they give you feedback, listen.

Image credit: Pixabay

Subscribe to Human-Centered Change & Innovation WeeklySign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.

Solving the AI Trust Imperative with Provenance

The Digital Fingerprint

LAST UPDATED: January 5, 2026 at 3:33 PM

The Digital Fingerprint - Solving the Trust Imperative with Provenance

GUEST POST from Art Inteligencia

We are currently living in the artificial future of 2026, a world where the distinction between human-authored and AI-generated content has become practically invisible to the naked eye. In this era of agentic AI and high-fidelity synthetic media, we have moved past the initial awe of creation and into a far more complex phase: the Trust Imperative. As my friend Braden Kelley has frequently shared in his keynotes, innovation is change with impact, but if the impact is an erosion of truth, we are not innovating — we are disintegrating.

The flood of AI-generated content has created a massive Corporate Antibody response within our social and economic systems. To survive, organizations must adopt Generative Watermarking and Provenance technologies. These aren’t just technical safeguards; they are the new infrastructure of reality. We are shifting from a culture of blind faith in what we see to a culture of verifiable origin.

“Transparency is the only antidote to the erosion of trust; we must build systems that don’t just generate, but testify. If an idea is a useful seed of invention, its origin must be its pedigree.” — Braden Kelley

Why Provenance is the Key to Human-Centered Innovation™

Human-Centered Innovation™ requires psychological safety. In 2026, psychological safety is under threat by “hallucinated” news, deepfake corporate communiques, and the potential for industrial-scale intellectual property theft. When people cannot trust the data in their dashboards or the video of their CEO, the organizational “nervous system” begins to shut down. This is the Efficiency Trap in its most dangerous form: we’ve optimized for speed of content production, but lost the efficiency of shared truth.

Provenance tech — specifically the C2PA (Coalition for Content Provenance and Authenticity) standards — allows us to attach a permanent, tamper-evident digital “ledger” to every piece of media. This tells us who created it, what AI tools were used to modify it, and when it was last verified. It restores the human to the center of the story by providing the context necessary for informed agency.

Case Study 1: Protecting the Frontline of Journalism

The Challenge: In early 2025, a global news agency faced a crisis when a series of high-fidelity deepfake videos depicting a political coup began circulating in a volatile region. Traditional fact-checking was too slow to stop the viral spread, leading to actual civil unrest.

The Innovation: The agency implemented a camera-to-cloud provenance system. Every image captured by their journalists was cryptographically signed at the moment of capture. Using a public verification tool, viewers could instantly see the “chain of custody” for every frame.

The Impact: By 2026, the agency saw a 50% increase in subscriber trust scores. More importantly, they effectively “immunized” their audience against deepfakes by making the absence of a provenance badge a clear signal of potential misinformation. They turned the Trust Imperative into a competitive advantage.

Case Study 2: Securing Enterprise IP in the Age of Co-Pilots

The Challenge: A Fortune 500 manufacturing firm found that its proprietary design schematics were being leaked through “Shadow AI” — employees using unauthorized generative tools to optimize parts. The company couldn’t tell which designs were protected “useful seeds of invention” and which were tainted by external AI data sets.

The Innovation: They deployed an internal Generative Watermarking system. Every output from authorized corporate AI agents was embedded with an invisible, robust watermark. This watermark tracked the specific human prompter, the model version, and the internal data sources used.

The Impact: The company successfully reclaimed its IP posture. By making the origin of every design verifiable, they reduced legal risk and empowered their engineers to use AI safely, fostering a culture of Human-AI Teaming rather than fear-based restriction.

Leading Companies and Startups to Watch

As we navigate 2026, the landscape of provenance is being defined by a few key players. Adobe remains a titan in this space with their Content Authenticity Initiative, which has successfully pushed the C2PA standard into the mainstream. Digimarc has emerged as a leader in “stealth” watermarking that survives compression and cropping. In the startup ecosystem, Steg.AI is doing revolutionary work with deep-learning-based watermarks that are invisible to the eye but indestructible to algorithms. Truepic is the one to watch for “controlled capture,” ensuring the veracity of photos from the moment the shutter clicks. Lastly, Microsoft and Google have integrated these “digital nutrition labels” across their enterprise suites, making provenance a default setting rather than an optional add-on.

Conclusion: The Architecture of Truth

To lead innovation in 2026, you must be more than a creator; you must be a verifier. We cannot allow the “useful seeds of invention” to be choked out by the weeds of synthetic deception. By embracing generative watermarking and provenance, we aren’t just protecting data; we are protecting the human connection that makes change with impact possible.

If you are looking for an innovation speaker to help your organization solve the Trust Imperative and navigate Human-Centered Innovation™, I suggest you look no further than Braden Kelley. The future belongs to those who can prove they are part of it.

Frequently Asked Questions

What is the difference between watermarking and provenance?

Watermarking is a technique to embed information (visible or invisible) directly into content to identify its source. Provenance is the broader history or “chain of custody” of a piece of media, often recorded in metadata or a ledger, showing every change made from creation to consumption.

Can AI-generated watermarks be removed?

While no system is 100% foolproof, modern watermarking from companies like Steg.AI or Digimarc is designed to be highly “robust,” meaning it survives editing, screenshots, and even re-recording. Provenance standards like C2PA use cryptography to ensure that if the data is tampered with, the “broken seal” is immediately apparent.

Why does Braden Kelley call trust a “competitive advantage”?

In a market flooded with low-quality or deceptive content, “Trust” becomes a premium. Organizations that can prove their content is authentic and their AI is transparent will attract higher-quality talent and more loyal customers, effectively bypassing the friction of skepticism that slows down their competitors.

Disclaimer: This article speculates on the potential future applications of cutting-edge scientific research. While based on current scientific understanding, the practical realization of these concepts may vary in timeline and feasibility and are subject to ongoing research and development.

Image credits: Google Gemini

Subscribe to Human-Centered Change & Innovation WeeklySign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.