Cease Constructing Streetlamp Fashions: The Determination-First Framework for AI Merchandise


As UX and product leads, we sit proper at the intersection of consumer wants, enterprise objectives, and technical constraints. This is precisely the place most AI merchandise fail.

I’ve seen this sample repeatedly whereas main UX for an AI studying platform: product groups have a number of concepts. AI groups have knowledge. The enterprise desires to ship quick.

And customers… properly, they’re left with an issue none of us are really fixing — as a result of all of us acquired somewhat too enthusiastic about what the AI may do as a substitute of what customers wanted it to do.

The end result? Forbes estimates that 85% of AI projects fail to deliver real business outcomes. And the frequent thread in these failures is easy: groups answered the fallacious query. Not a nasty query. Simply… the fallacious one.

Each AI undertaking begins with a query. Ensure that it’s your consumer’s query — not your knowledge scientist’s.

The Streetlamp Entice

In his guide, UX for AI: A Framework for Designing AI-Driven Products, Greg Nudelman describes a sample known as The Streetlight Entice:

A person searches for his keys underneath a streetlight.
“The place did you lose them?”
“Over there.”
“Then why are you wanting right here?”
“As a result of right here, I can see.”

Most AI groups do the identical — they construct the place the knowledge is vivid, not the place the downside really is.

The AI-Query Framework

The AI-Query Framework is a device for driving AI worth via choosing the proper query.

It consists of simply three questions:

  1. Is the prediction tied to a metric that issues?
  2. Do you might have historic knowledge examples?
  3. Are false positives and false negatives tolerable?

Right here’s what every one seems to be like in follow.

1. Is that this the metric that issues?

Think about this instance from an AI studying platform:

“How lengthy will it take this scholar to full the course?” Vs. “How probably is this scholar to stop before finishing the course?”

Each use the identical knowledge — course development logs – however they predict barely various things.

The primary simply predicts a timeline. Good to know, perhaps it creates a fairly graph that may encourage some portion of the college students.

Nevertheless, the second predicts a chance of a nasty consequence, one thing that immediately impacts scholar success and, subsequently, key enterprise metrics. It additionally provides you one thing you may act on: intervene, coach, nudge the scholar, and save them before they stop.

That tiny shift — asking a extra attention-grabbing business-critical query — is the distinction between a intelligent show and an AI product that basically strikes the needle for the enterprise.

In case your mannequin isn’t linked to a metric management cares about, it’s analytics theater: all highlight, no present.

And people metrics aren’t mysterious: Retention, effectivity, income — choose one.

If every learner represents $1,000 in income and a ten% dropout, even a 1% enchancment saves $10 per cohort. Multiply that by 1000’s of learners, and the ROI turns into unattainable to ignore.

A number of prediction fashions sound sensible (“When will this occur?”) however don’t really drive any enterprise selections.

No determination → no impression → no worth.

Sadly, most AI groups begin with the capabilities, not the query the mannequin shall be answering. They fall straight right into a streetlight lure.

Keep away from it by framing the proper query before your crew builds something.

2. Do you might have historic knowledge examples?

The fitting query isn’t only one that addresses an actual enterprise consequence — it’s one you even have the knowledge to reply. Too many AI concepts fail as a result of groups body questions that sound invaluable however don’t have any historic examples behind them.

Right here’s what this seems to be like in EdTech.

You need to enhance learner engagement. An information scientist suggests:

“When ought to this scholar examine subsequent?”

Sounds proactive… nevertheless it’s a basic streetlamp query. It assumes knowledge you don’t have — their schedule, motivation, consideration span, life context.

And even in the event you nailed it?

It ends in a push notification that the majority college students swipe away. Excessive modeling effort, low enterprise impression. 

Now do this query as a substitute:

“Which learners are liable to dropping out this week?”

Why this works:

  • You have already got the indicators: login frequency, completion charge, and task delays.
  • The actions are apparent: coach them, nudge them, provide help.
  • The ROI is actual: a 1% enchancment in retention scales throughout 1000’s of learners.
  • The UX is easy: a background mannequin that quietly surfaces threat instances.

This one shift turns AI from a “perhaps characteristic” right into a retention engine — and forces your crew to cease asking, “What can our AI do?” and begin asking “Which consumer determination are we attempting to help?”

3. Are false positives and false negatives tolerable?

Many fashions get issues fallacious: The query isn’t whether or not AI will make errors or not. The actual query is:

“Can your corporation afford the errors?”

Take a dropout-prediction mannequin:

  • False Positives: Flagging college students who gained’t drop out wastes teaching assets and overwhelms your help crew. 
  • False Negatives: Lacking college students who are in danger immediately harm retention and income. 

Completely different errors have completely different prices.

That value determines whether or not the mannequin is price constructing, how correct it wants to be, and the way a lot human evaluation you want in the workflow. 

Some use instances tolerate errors: In case your AI really useful an additional follow session {that a} scholar didn’t want, no hurt finished. 

Others don’t: Assume an necessary buyer is secure after they’re really planning to depart, and also you lose the probability to intervene — together with significant income.

This is the half most groups skip. They take a look at technical questions like:

  • What are AI’s precision, recall, and accuracy?

As a substitute of metrics that truly matter to your corporation, reminiscent of:

  • What does every form of error value us? 
  • Who pays the worth? 
  • Can we soak up it operationally?

When you perceive your error tolerance, you may determine:

  • Whether or not the mannequin is price constructing.
  • How correct does it want to be?
  • How a lot human evaluation to layer in?
  • …And the way to design the UX round uncertainty.

To be sure to systematically ask the proper query, use the AI-Query Framework.

A fast diagnostic

To make use of the AI-Query Framework to drive AI worth, ask these three questions:

  1. Is the prediction tied to a metric that issues?
  2. Do you might have historic knowledge examples?
  3. Are false positives and false negatives tolerable?

In case you get a “no” to any of those three questions, congratulations — you’ve discovered your streetlamp.

Getting your crew to assume AI-question-first

Selecting the proper query is nonetheless a human job. AI can assist, however groups should be taught to acknowledge after they’re optimizing for what’s straightforward as a substitute of what’s invaluable.

A couple of straightforward methods to make the mindset stick:

  • Begin dash planning with “What determination are we enabling?”
  • Kill any AI concept that may’t identify its goal metric in 10 seconds
  • Run a fast workshop: reframe three current initiatives utilizing the three questions from the AI-Query Framework on this article
  • Ask your crew repeatedly: “What’s the streetlamp model of this?”

Earlier than your subsequent AI undertaking kicks off, ask:

“What determination will this reply empower?”

In case you can’t identify a transparent decision-maker, a transparent motion, and a transparent metric — you’re not prepared to construct.

Cease optimizing the streetlamp. Discover the keys.

The article initially appeared on UX for AI.

Featured picture courtesy: Jr Korpa.




Disclaimer: This article is sourced from external platforms. OverBeta has not independently verified the information. Readers are advised to verify details before relying on them.

0
Show Comments (0) Hide Comments (0)
0 0 votes
Article Rating
Subscribe
Notify of
guest
0 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments

Stay Updated!

Subscribe to get the latest blog posts, news, and updates delivered straight to your inbox.