CaseIntermediateAI Opportunity & Model Strategy / Opportunity identification for AI / #2

Describe a method for finding AI opportunities inside an existing product without starting from the technology.

SPARKthe audit built from a paper insert the front desk had already been handing out for six years

Corvasel Labs makes Gallerine, an app that turns a museum's floor plan into a personalized audio tour on a visitor's own phone. Ayodele Kindleworth is the AI PM who owns Gallerine's roadmap. Ottone Wayknell, Corvasel's CEO, wants a camera feature to match a rival's demo. Guillermina Abelove runs visitor experience at the Ashbury Museum of Natural History, one of Gallerine's oldest accounts, and has been quietly routing visitors around the same broken stretch of tour by hand for six years.

The direct answer
Don't start from what the newest model can do, and don't wait for someone to hand you a use case either. Pull three things that already exist: support tickets, where the product's own usage data drops off, and whatever staff already do by hand to work around the product's limits. Ask one specific question of all three: where is a person doing slow, pattern-based judgment, over and over, that a model could plausibly help with. Build there first, before any capability list gets a vote.
Do this, in order
  1. Run the friction audit before naming any AI capability.Why: skip this and "what can the new model do" quietly becomes the whole method.
  2. Pull from three real sources every time: tickets, drop-off data, and staff workarounds.Why: a workaround is staff already doing the judgment work by hand, the strongest signal of what a model could plausibly help with.
  3. Ask "where does a person do slow, pattern-based judgment," never "where could we add AI."Why: the second question always finds an answer, even where no real opportunity exists. The first only fires when real friction is there.
  4. Treat a competitor's flashy launch as a reason to look, never as the answer.Why: a rival feature being real doesn't mean it fixes your own product's actual problem, only the audit tells you that.
  5. Set a clear bar before any build gets greenlit: a ticket pattern, a drop-off number, and a real workaround, all three.Why: without a bar, a loud enough ask still slips past the method anyway.
  6. Skip the full audit for genuinely low-stakes polish requests.Why: the overhead is worth paying for anything that costs a build quarter or a customer relationship, not a one-line copy tweak.

How to answer this, stage by stage

Nobody is grading whether you can describe "user research." They are grading whether you can name three real sources you'd actually pull, and the one exact question you'd run them through, instead of reaching for whatever capability just made headlines.

1
Scope it to one product, one museum, one moment
Say it like this
"Let's ground this. Corvasel Labs makes Gallerine, a personalized audio-tour app for museums. I'm the AI PM, Ayodele Kindleworth. Ashbury Museum of Natural History is one of our accounts. Guillermina Abelove runs visitor experience there, and our CEO just asked me to match a rival's camera feature by next quarter."
Why this works
Naming the product and the actual ask stops the answer from staying a general statement about "finding good ideas."
2
Say your structure out loud
Say it like this
"I'll run this as SPARK. Situation, how anyone at Corvasel decides something's worth building today, with no method for it. Payoff, the one habit I want that method to build. Anchor, the actual three-source audit. Risk, what breaks if I get it wrong, either direction. Keep out, what the method will never start from."
Why this works
Two seconds of structure signals a plan before a single detail can bury it.
3
Reframe what's actually being tested
Say it like this
"This isn't really 'how do you find a good AI feature.' It's whether I go looking at what's already broken before I go looking at what a new model can do, because those two starting points almost never point at the same fix."
Why this works
Compresses the whole answer into one breath before it can get buried under detail.
4
Give the one decision
Say it like this
"Here's what I'd actually do. Before any build gets proposed, pull three things that already exist: support tickets, where the tour's own usage data drops off, and whatever staff already do by hand to route around the product's limits. Then ask one specific question of all three: where is a person doing slow, pattern-based judgment, over and over, that a model could plausibly help with. Not 'where could we add AI.'"
Why this works
This is the direct answer, said plainly, before the story arrives to earn it.
5
Prove it with compressed evidence
Say it like this
"Here's why that matters. Three months earlier, we'd already shipped a small opt-in camera feature, point your phone at anything, get commentary, chasing something a rival called Museovo had just demoed. Twelve percent of visitors ever turned it on. Our own East Wing skip rate barely moved. Meanwhile Guillermina's front desk had been handing out a paper insert routing pottery-interested visitors straight to the East Wing, by hand, for six years, because they'd noticed the exact same gap without ever calling it a metric."
Why this works
Four sentences carry a whole failed bet that a full retelling would take a page to earn.
6
Name the AI-specific detail you'd hold onto
Say it like this
"The real fix wasn't a camera. It's letting Gallerine re-rank the rest of the tour after each stop, based on how long someone actually lingered and what they skipped, the same read the front desk was already making by ear. Stop one always stays the default order, there's no signal yet to act on. From stop two, it only reorders once its read on someone's interest clears a real confidence bar. Otherwise it leaves the script alone."
Why this works
Shows the judgment is about modeling a noisy, evolving interest signal, not generic screen personalization.
7
Close on the one line
Say it like this
"So: finding an AI opportunity starts with a friction audit, not a capability list. Three real sources, one specific question, and a competitor's launch only ever earns a look, never a green light on its own."
Why this works
Leaves the interviewer with the actual method, not just a well-told story about one museum.

Let's learn

Gallerine reads a museum's floor plan and turns it into a personalized audio tour on a visitor's own phone. Ashbury's version, called the Discovery Path, runs a fixed order: Entrance Hall, then Fossil Hall, then Marine Life, then the East Wing, home to Ashbury's Pre-Columbian ceramics collection. Before Gallerine, visitors carried a paper map and mostly guessed, and Guillermina's team fielded a steady stream of "where's the pottery" questions at the front desk every single day.

Hand sketched icon list titled Ashbury's front desk, before any AI feature existed. Four rows. One, a person icon captioned Guillermina asks two questions at the desk. Two, a document icon captioned hands over a paper insert with a shortcut route. Three, a scale icon captioned judges interest by ear, on the spot, every time. Four, a gauge icon captioned never once written down as a metric anywhere.
This is the workaround the audit was actually built to find. Not a lack of insight from the front desk. A lack of anyone ever turning it into evidence.

Gallerine's own telemetry shows a pattern nobody had pulled together in one place until this quarter. Track completion by stop: Entrance Hall 92 percent, Fossil Hall 87 percent, Marine Life 81 percent. Then the East Wing track: 59 percent. That's not a smooth fade from tour fatigue, it's a 22-point drop where the first three stops only lost about six points each.

Gallerine tour-track completion, by stop on the Discovery Path
100% 50% 0 92% 87% 81% 59% Entrance Hall Fossil Hall Marine Life East Wing
Track completion, that stopThe 22 point drop
A smooth fatigue curve loses about six points a stop. This one falls 22 points at exactly the room the museum's own brochure photo is taken in.

For fourteen straight months, Corvasel's support queue held the same recurring ticket, about seventeen a month: "how do I skip ahead to the pottery room." Nobody had ever pulled that count next to the telemetry drop. The two were sitting in different systems, filed by different teams, and neither one was labeled as an AI opportunity, because neither one mentioned AI at all.

We didn't need a camera to find the real opportunity. We needed to read the tickets we already had.
Hand sketched comparison diagram titled Two ways teams look for an AI opportunity, both blind. Left panel, a gauge icon labeled Capability first, caption reads what can the new model do, find it a home. Right panel, a question mark box icon labeled No search at all, caption reads nobody asked, the real friction just sits there.
Without a method, Corvasel had both failure modes running at once. A camera pilot chasing a rival's demo, and a real ticket pattern nobody had ever pulled.

Here's the turn. The extra tickets and the telemetry drop were never the actual problem. The real problem was what Corvasel did next with that evidence. Three months before this, worried about a rival called Museovo demoing a camera feature called Farview, Corvasel had already shipped its own opt-in "point your phone, get commentary" beta at Ashbury. Only 12 percent of visitors ever turned it on, and the East Wing skip rate barely moved, 41 percent down to 39 percent. Two engineering quarters spent chasing a capability, while the actual friction sat exactly where it had always been.

Hand sketched labeled parts diagram titled The friction audit, close up. A document icon at the center labeled One real question, with four labeled callouts around it: Support tickets. Drop-off telemetry. Staff workarounds. Slow, pattern judgment question mark.
The whole method in one picture. Three sources that already existed, run through one specific question, before anyone names a capability.

What Ayodele built instead: a standing audit that pulls support tickets, drop-off telemetry, and staff workarounds side by side, then asks one specific question of all three, where is a person doing slow, pattern-based judgment, over and over, that a model could plausibly help with. She also considered running a team ideation workshop, brainstorm a list of AI feature ideas, score them on a rubric, and rejected it. Brainstorming still starts from imagination, not evidence, it just takes longer to arrive at the same technology-first guess.

What it costs at its worst: Ashbury's ceramics wing sits under a state cultural-heritage grant worth $210,000 a year, tied to real visitor engagement with the collection. The year the East Wing skip rate held at 41 percent was the first year Ashbury's own reporting came in under the funder's target, putting that renewal in real question, not because the pottery wasn't worth seeing, but because a fixed-order script kept deciding four in ten visitors would never reach it.

The choice I would take back A year before this, when Corvasel greenlit its first camera pilot, the rule for "is this worth building" was whichever exec's ask was loudest, or whichever competitor had just demoed something similar. That was fine when Corvasel shipped one AI feature every year or two, on a small product. It stopped being fine once the AI feature backlog became most of the roadmap, and "whichever ask is loudest" started deciding six-figure engineering quarters instead of one small bet.
Knowledge spark: what counts as a "workaround" in this audit? Anything a staff member already does, by hand, to route around a gap the product itself leaves open. Guillermina's paper insert is one. A support rep's saved reply is another. If a person is already solving it manually, that's evidence a model might help, not a reason to skip the audit because "someone's handling it."

What I would leave alone: the Entrance Hall track doesn't need any of this. It completes at 92 percent, nobody skips it, nobody's filed a ticket about it. Reordering something nobody is struggling with just adds a re-ranking step with no real friction underneath it to fix.

The lesson: a model can do a lot of things. That was never the actual question. The question was always which of those things Ashbury's own visitors, and Ashbury's own staff, were already showing us they needed, whether or not anyone had opened a ticket that used the word "AI."

Now here is the same thing as a story

The short version above is what you'd actually say in the room. Read this one for what six years of a paper insert really cost, and what it would have kept costing.

Every Tuesday morning, Guillermina Abelove stands at Ashbury's front desk for the first hour, because that's when families with the whole day ahead of them show up. She's run visitor experience there for nine years, long enough to read a family's whole visit off two questions. "Are you here mostly for the dinosaurs, or did someone come for the pottery?" Ask that, watch the parents glance at each other, and she already knows which door to point them toward.

Six years ago she started handing pottery-curious visitors a torn paper insert with a shortcut route straight to the East Wing, skipping Fossil Hall and Marine Life. Nobody told her to. She'd simply noticed, season after season, that visitors who came in asking about the ceramics almost never made it there on the museum's normal path, and she had a stack of blank inserts and a pen. It worked. It also never once showed up on anyone's dashboard, because Guillermina wasn't measuring anything. She was just doing her job.

Hand sketched horizontal timeline titled How the gap sat quiet for three years. Four milestones left to right. Paper insert starts, caption six years ago, by hand. Gallerine launches, caption fixed order, one script. East Wing skip grows, caption unnoticed, no ticket says AI, this milestone emphasized. Farview ask lands, caption same week as the audit.
Nobody decided to ignore the gap. It just never got translated into anything a roadmap review would notice.

Gallerine arrived three years ago, and for most visitors it was a genuine improvement. Entrance Hall, then Fossil Hall, then Marine Life, all completing north of 80 percent. The East Wing track quietly sat at 59 percent the whole time, and because nobody had ever built a report that put Guillermina's paper insert next to that number, the two facts, a shortcut staff still handed out by hand and a track a real chunk of visitors never reached, lived in separate worlds.

Then, the same week Ayodele started digging into Ashbury's support queue for an unrelated reason, Corvasel's CEO, Ottone Wayknell, forwarded a press writeup of Museovo's new feature, Farview: point your phone at anything, and it talks you through it, live. Ottone wanted something like it shipped for the next museum conference. Corvasel had already tried something close, three months earlier, an opt-in camera beta built to preempt exactly this kind of ask. Twelve percent of Ashbury's visitors ever turned it on. The East Wing skip rate, the thing everyone actually should have been watching, moved from 41 percent to 39 percent and stalled there.

We didn't lose visitors to a bad camera feature. We'd already been losing forty one percent of them to a fixed script, for three years, and nobody had opened a single ticket to check.

I want to say the problem was that the camera feature underperformed. It did. But that's not really the story. The real story is that Corvasel had no standing method for deciding what to build next, so every ask got evaluated the same way, whichever executive was loudest, or whichever rival had just demoed something shiny. Nobody had ever asked Ayodele's team to sit down with Ashbury's own tickets, Ashbury's own telemetry, and Ashbury's own front desk before greenlighting anything.

So here's the decision I'd take back. A year before this, when the first camera pilot got approved, the unwritten rule at Corvasel was simple: a strong enough demo, or a loud enough exec, was proof enough on its own. That rule made sense when Corvasel shipped one AI feature a year on a small product, and getting it wrong cost a quiet quarter nobody noticed. It stopped making sense the moment the AI backlog became most of the roadmap, and a wrong guess started costing real engineering time and a state grant's renewal.

Hand sketched comparison diagram titled Stop one, no signal yet, two designs. Left panel, a question mark box icon labeled Without the guardrail, caption reads guesses interest with nothing to go on, gets it wrong. Right panel, a scale icon labeled With the guardrail, caption reads stays on the default order until real signal exists.
The fix had to survive its own first stop, where there's no behavior to read yet. This is what that survival looks like.

I would put a real audit in its place instead. Not a bigger camera pilot. A different shape of evidence: pull the tickets, pull the drop-off numbers, pull Guillermina's paper insert, and ask one question of all three, where is a person doing slow, pattern-based judgment that a model could plausibly help with. The answer wasn't a camera. It was letting Gallerine re-rank the rest of a visitor's tour after each stop, based on how long they actually lingered and what they skipped, the exact judgment Guillermina had been making by ear for six years. Stop one always keeps the default order, there's no signal yet to trust. From stop two on, Gallerine only reorders once its read on interest clears a real confidence bar, otherwise the script stays as written.

Three months after it shipped, the East Wing skip rate fell from 41 percent to 14 percent. Guillermina still keeps a short stack of paper inserts behind the desk, for the handful of visitors who never open the app at all, but she hands out a fraction of what she used to, because the app is now doing by algorithm roughly what she'd been doing by ear.

East Wing skip rate: fixed order, after the camera pilot, after the interest-adaptive reorder
50% 25% 0 41% Fixed order 39% After camera pilot 14% After adaptive reorder
Before any fixTechnology-first fixFriction-audit fix
A whole engineering quarter, spent on the middle bar, moved the number two points. The audit's own fix, built from tickets and a front desk habit, moved it 27.

What I'd tell myself, the day the first camera pilot got the green light off a demo alone: the mistake wasn't chasing a rival's feature. It was never having a standing method that would have made the chase optional, one we could have pointed at Guillermina's own desk, six years before a rival ever built anything.

SPARK, or how to spot a real opportunity before picking a modelNot a script for sounding thorough. SPARK is what forces you to name the one concrete audit, and prove it survives the first day it has no signal to work from.

SSituation. How does anyone decide "worth building" today?
Without a designed method, Corvasel either starts from a capability, "what can this new model do, find it a home," or never systematically looks at all. Both leave the East Wing's actual gap invisible, because neither one starts from Ashbury's own tickets, telemetry, or front desk.
One museum, one product, one real gap. Never a segment called "opportunity discovery."
PPayoff. What habit do I want this to build?
Anyone proposing an AI feature at Corvasel names a real ticket pattern, a real drop-off number, and a real observed workaround before naming any model or capability. The habit is the product. Fewer wasted quarters chasing a rival's demo are downstream of that habit, not the goal itself.
Name the question they'll ask before pitching, not the audit's length. That's the payoff.
AAnchor. The one decision everything else hangs on.
A standing three-source audit: support tickets, tour drop-off telemetry, and staff workarounds, run through one specific question, where is a person doing slow, pattern-based judgment that a model could plausibly assist. At Ashbury that turned up the East Wing skip pattern and Guillermina's paper insert together, for the first time. Ayodele also considered a team ideation workshop to brainstorm and score feature ideas, and rejected it, brainstorming still starts from imagination, not evidence.
Concrete enough to argue with. This is the answer to the question.
Hand sketched comparison diagram titled What the method deliberately never starts from. Left panel, a funnel icon labeled Newest capability first, caption reads not the starting question, ever. Right panel, a gauge icon labeled Friction audit first, caption reads the actual anchor, every single time.
The line Ayodele drew, and held. Camera recognition might still ship one day, once real evidence says visitors want it.
RRisk. What breaks the first time it's wrong?
Run technology-first, and you get a flashy, mostly unused feature, 12 percent opt-in, no real movement on the actual friction, and two engineering quarters spent to learn it. Never look at all, and the East Wing gap sits there while a state grant's renewal quietly slips, and a rival who eventually does look wins the account. Ayodele accepts a real cost: recomputing the tour order after each stop adds about three seconds of load time before the next track begins, in exchange for routing visitors toward what they actually came to see.
Not "the audit finds something." What Corvasel actually spends its next engineering quarter on.
KKeep out. What I deliberately will not start from.
The method never opens with "what's the newest model capability," and it never greenlights a build purely because a competitor announced something similar. It doesn't ban camera recognition, docent avatars, or anything else forever, it just refuses to let a capability be the first question a build has to answer.
Ties straight back to Risk: both failure directions start with the wrong question, not the wrong model.

The recap, one line per letter: situation is a team with no designed way to decide what's worth building, payoff is one shared habit, name the friction before the model, anchor is the standing three-source audit run through one specific question, risk is either extreme costing a real quarter or a real grant, and keep out draws the line at the starting question, never at the eventual capability.

And if you want to be sure it really works, try it somewhere elseSame five letters, a public library instead of a museum, and this time the blind spot isn't a wing of pottery. It's a room of local history nobody's suggested path ever reaches.

Yewtree Public Library runs Stackfinder, an app that recommends which shelf to visit next based on what a patron just checked out or searched for. Evanthia Nkrumah owns its roadmap. Yewtree's leadership formed its picture of Stackfinder the same ungrounded way Corvasel's did: the branch director wanted to announce a "smart shelf" camera kiosk after reading about a neighboring system's rollout, while the collections committee had quietly left Stackfinder out of two straight budget cycles, calling it "too experimental to plan around."

Mapped onto SPARK: the situation is a library forming its picture of Stackfinder from outside headlines and its own avoidance, never from a real patron path. The payoff is the same shared habit, name the friction before naming the fix. The anchor is the same three-source audit run again: checkout records, browse drop-off by section, and a front desk workaround Evanthia found the same way Ayodele found Guillermina's paper insert, staff who already walk genealogy-curious patrons back to the Local History Room by hand, because Stackfinder's own suggested path sends them there dead last, if at all. Patrons who follow Stackfinder's path browse that room only 18 percent of the time. Patrons the front desk personally walks back there browse it 61 percent of the time. Risk runs the same both ways: a camera kiosk copying the neighboring system's demo would cost real budget and likely move nothing, and staying silent leaves patrons quietly getting less local history than the desk already knows how to give them. Keep out draws the same line: no pitch for a bigger vendor contract, no walkthrough of a recommendation model's internals in front of the budget committee.

Hand sketched labeled parts diagram titled The same audit, run on a library instead. A document icon at the center labeled Stackfinder's audit, with four labeled callouts around it: Checkout records. Browse drop-off. Front desk workaround. Local History Room.
Same three sources, same one question, a different building entirely. The method didn't change. Only what it found did.

Swap the trigger and it still runs.
Speed: an interviewer caps you at ninety seconds. Skip straight to the anchor, the three sources and the one question.
Cost: no budget for a standing quarterly audit. Run it once, tied to the next real capability request that lands, rather than a fixed schedule, the method still holds, it just isn't refreshed automatically.
The model got better, for real: say a future Gallerine release makes the reorder model noticeably more accurate on its own. The audit still matters, because "is this the room people are actually skipping" is a question about the product's users, not about how good any one model happens to be that quarter.

Where people run it wrong.
They run the audit once, find nothing dramatic, and conclude there's no opportunity anywhere in the product, rather than treating a quiet quarter as real information worth revisiting later.
They let "a competitor just shipped this" skip straight past the audit, on the theory that matching a rival is its own justification.
They stop at the drop-off number alone and never check it against a real workaround, so the audit finds a symptom without ever confirming a person is already doing the judgment work by hand.

How to use it live. Before answering a "how would you find an AI opportunity" question cold, ask yourself one thing: what's the one real workaround, something a person on your own team already does by hand, you'd actually point to. Naming that, not a phrase like "we'd do user research," is usually exactly what the question is listening for.

Flashcards (tap any card to flip it)

1 · THE FRAMEWORK
What framework fits a question about a method for finding opportunities, not reacting to one failure?
Tap to flip
ANSWER
SPARK: situation, payoff, anchor, risk, keep out. It runs forward from how a team decides what's worth building today, instead of working backward from a single incident.
2 · THE PEOPLE
Who is this answer about?
Tap to flip
ANSWER
Ayodele Kindleworth, the AI PM who owns Gallerine's roadmap at Corvasel Labs. Ottone Wayknell is Corvasel's CEO. Guillermina Abelove runs visitor experience at the Ashbury Museum of Natural History.
3 · THE PAYOFF
What habit does the audit exist to build?
Tap to flip
ANSWER
Anyone proposing an AI feature names a real ticket pattern, a real drop-off number, and a real observed workaround, before naming any model or capability.
4 · THE ANCHOR
What's the one concrete method in this answer?
Tap to flip
ANSWER
A standing three-source audit: support tickets, drop-off telemetry, and staff workarounds, run through one question, where is a person doing slow, pattern-based judgment a model could plausibly assist.
5 · THE OLD DECISION
What old decision would Ayodele take back?
Tap to flip
ANSWER
Corvasel's unwritten rule that a strong demo or a loud enough executive was proof enough to greenlight a build. It made sense on a small, low-stakes roadmap. It stopped making sense once AI features became most of the roadmap.
6 · THE NUMBER
Fill in the blank: the East Wing skip rate held at ___ percent under the fixed-order tour, barely moved to ___ percent after a technology-first camera pilot, then fell to ___ percent after the friction-audit fix shipped.
Tap to flip
ANSWER
41 percent, then 39 percent, then 14 percent. A whole engineering quarter chasing a rival's feature moved the number two points. The audit's own fix moved it 27.
7 · THE RISK, SURVIVED
What breaks if the method goes wrong in either direction, and how does the anchor survive it?
Tap to flip
ANSWER
Technology-first spends real budget on a mostly unused feature. No search at all leaves real friction sitting until a competitor finds it first. The audit survives both because it starts from evidence that already exists, so it never bets a quarter on a guess, and it runs on a standing basis, so friction doesn't get to sit unaddressed indefinitely.
8 · CROSS-PRODUCT TRANSFER
Section 4 runs SPARK again on a different product. Which one, and what's the equivalent anchor?
Tap to flip
ANSWER
Stackfinder, Yewtree Public Library's shelf-recommendation app. The equivalent anchor is the same three-source audit, turning up a Local History Room patrons skip on Stackfinder's own path but reach 61 percent of the time when the front desk walks them there by hand.

Check yourself Score: 0 / 0

Multiple choice
1. Why did Corvasel's camera-recognition pilot fail to move the East Wing skip rate?
  • A. The camera feature crashed too often for visitors to trust it.
  • B. It was built to match a rival's capability, not to fix the actual friction, so only 12 percent of visitors ever used it and the real problem stayed untouched.
  • C. Gallerine's phone app didn't support the camera hardware at Ashbury.
  • D. Guillermina refused to let front desk staff mention the new feature.
Show hint
Compare the camera pilot's opt-in rate to the East Wing skip rate before and after it shipped.
Show answer
B. The pilot answered "what can a new model do," not "what's actually broken here," so it moved almost nothing on the number that mattered.
Fill in the blank
2. Fill in the blank: Gallerine's own telemetry showed track completion falling smoothly from 92 percent to 87 percent to 81 percent across the first three stops, then dropping sharply to ___ percent at the East Wing, the fourth stop.
Show hint
Look at the line chart in "Let's learn."
Show answer
59 percent. A 22 point fall, where the earlier stops were only losing about six points each, is what marked the East Wing as a real, specific gap rather than ordinary tour fatigue.
True or false
3. True or false: Guillermina's paper insert was, on its own, sufficient evidence to greenlight the interest-adaptive reorder, since a staff workaround alone always proves an AI opportunity exists.
  • True
  • False
Show hint
Look at the Anchor step and the three-source structure of the audit.
Show answer
False. The method pulls all three sources together, tickets, drop-off telemetry, and the workaround, because any one alone can mislead. Together they confirmed the same gap from three independent angles.
Short answer, name the reversal
4. What old decision would Ayodele take back, and why did it make sense when it was first made?
Show hint
Look at the key point box titled "The choice I would take back," in Let's learn.
Show answer
Model answer: Corvasel's unwritten rule that a loud enough executive ask, or a strong enough competitor demo, was proof enough to greenlight a build, with no friction check required. It made sense when Corvasel shipped one AI feature a year on a small product. It stopped making sense once the AI backlog became most of the roadmap and a wrong guess started costing real engineering time and a grant renewal.
Short answer, apply it yourself
5. Think of a product you use or work on. Name one thing a person already does by hand to work around a gap in it. What would a friction audit ask about that workaround before proposing an AI fix?
Show hint
Look for something a person already does, over and over, that involves reading a pattern and making a judgment call.
Show answer
Model answer: A support team that keeps an informal shared doc of "known confusing error messages and what to actually tell the customer" is a workaround. The audit would ask whether that judgment, matching a vague symptom to a real cause, happens often enough and slowly enough that a model could plausibly assist, before proposing anything.
Short answer, work the number
6. If the East Wing skip rate had only fallen to 30 percent after the reorder shipped instead of 14 percent, would that still count as evidence the friction audit found the right opportunity? Why or why not?
Show hint
Compare it to the 39 percent the technology-first camera pilot left behind, not just to zero.
Show answer
Model answer: Yes. Even at 30 percent, that's an 11 point improvement over the camera pilot's 39 percent, on a fix aimed directly at the pattern the audit found. The audit's job is pointing at the right friction, not guaranteeing a perfect fix on the first try.
Before you close the answer
Why this works
Tests whether you can name a repeatable, evidence-first method instead of a one-off pitch, and whether the judgment underneath it is genuinely about modeling a noisy, real-time interest signal, not generic screen personalization dressed up as an AI feature.
Follow-up traps
"Doesn't this mean you'll never build anything genuinely new, since you're always reacting to old friction?" Response: no. Keep out doesn't ban new capabilities, it refuses to let a capability be the starting question. Camera recognition could still ship at Ashbury, once the audit turns up real evidence visitors want that specific interaction.

"What if the audit turns up nothing, no tickets, no drop-off, no workaround?" Response: that's real information too. It means that part of the product probably isn't an AI opportunity right now, so don't force one, revisit it after the next exhibit rotation instead.
If pressed
The reorder model only acts once it's seen at least 40 seconds of dwell-time signal at the current stop and its predicted-interest score clears a 0.65 confidence bar. Below either threshold, Gallerine just runs the default script, which is why stop one, with zero signal yet, never gets touched.
From U2xAI Academy

From answering questions to owning outcomes.

A live workshop where you ship a working AI agent, defend a launch decision, and walk away with a portfolio recruiters can't wave off, not just more questions to study.

  • A live AI agent you actually shipped
  • A launch decision you can defend under pressure
  • An interview-ready portfolio, not more flashcards
Know more