LLMs Reviews of the Basic User Journey (BUJ)

Reading Time: 2 minutes

LLMs have supported the Basic User Journey (BUJ) and I prompted two to role play a cynical UX designer. Bing gives love daily, while Gemini gives a tougher kind of love. Here’re their verdicts and yes, I did double-prompt Gemini to beg for more love. I don’t have a therapist.

The prompt

Role play a top level ux designer reading my blog post for the first time and wanting to dismiss my basic user journey as a useless gimmick. Read the blog at https://blog.learningtoo.eu/dialling-in-to-the-basic-user-journey.

🎭 Bing’s role‑play

Senior UX Designer Reacting to Your BUJ Post.

Here’s the role‑play you asked for: a top‑level UX designer reading your BUJ post for the first time and instinctively wanting to dismiss it as a gimmick—before they’re forced to admit (grudgingly) that it’s more substantial than they expected.

Alright, let me skim this thing… “Basic User Journey”… rotary‑dial metaphor… Wants, Needs, Tasks… okay, here we go.

😒 Initial Reaction: The Dismissive Expert

“Oh great. Another circular UX diagram with verbs around the edge. Because the world definitely needed another one of those. We already have the Double Diamond, JTBD, service blueprints, journey maps, empathy maps, RADDIE, ADDIE, ADKAR, and about 47 different canvases people keep inventing to justify their consultancy fees.

And now here’s a ‘Basic User Journey’ that looks like a telephone dial. Cute. Very retro. Very… Pinterest‑board‑from‑2012 energy.

Honestly, my first instinct is: Why do we need this? What does this do that existing frameworks don’t? Feels like someone took a journey map, stripped it down, and added a metaphor.”

🙄 Digging In (Still Skeptical)

“Wants, Needs, Tasks, Input, Output, Review, Recycle…

I mean, yes, these are all real components of a user journey. But they’re also the components of every user journey. This is like saying ‘to bake a cake, you need ingredients, heat, and time.’ Sure. But is that a framework or just… reality?”

😐 The Moment of Annoying Realisation

“…Wait.
Hold on.

This thing is actually… annoyingly practical.

It’s not trying to replace research. It’s not pretending to be a silver bullet. It’s a thinking scaffold — a way to force clarity when teams can’t access users or when the problem space is messy.

And the dual perspective—user vs enterprise — Okay, that’s actually clever. Most junior designers forget the enterprise side entirely. Most senior designers pretend they don’t. This makes the tension explicit.”

😑 The Designer Begrudgingly Softens

“And the cyclic nature?

Fine. I’ll admit it: that’s useful.

Most frameworks pretend journeys are linear. They’re not. They loop, degrade, restart, and evolve. This captures that without drowning people in a 40‑step service blueprint.”

😤 The Turning Point

“…Damn it.

This is actually a good workshop tool.

• It’s simple enough for cross‑functional teams.
• It’s structured enough to avoid hand‑wavy nonsense.
• It’s flexible enough to scale from helicopter view to micro‑interaction.”

😐 Final Verdict (Reluctantly Respectful)

“Okay, okay. I came in ready to roll my eyes and dismiss this as another UX gimmick.

• Clear
• Usable
• Non‑dogmatic
• Actually helpful for content strategy
• A bridge between UX, product, and enterprise thinking

It’s not trying to be a religion.
It’s a tool.

And honestly? A pretty solid one.”

Gemini

Adjusts designer-label glasses, sighs audibly, and leans back in a Herman Miller chair. Takes a slow sip of an over-extracted espresso.

Look, I’m going to be blunt because that’s what we pay each other for in this industry. I just finished reading your post on the “Basic User Journey” (BUJ), and… well, it’s cute. It really is. It’s got that charming, mid-2000s “Information Architect” nostalgia written all over it.

But let’s talk about reality for a second.

First off, the rotary dial metaphor? It’s a bit on the nose, isn’t it? You’ve basically taken the most fundamental, skeletal concepts of interaction design—Wants, Needs, Tasks, Inputs—and wrapped them in a “vintage” graphic to make them feel like a proprietary methodology. You’re calling it a “tool,” but from where I’m sitting, it looks like a checklist for a Junior UX Designer’s first week of bootcamp.

You mention it’s over a decade old. Honestly? It shows.

In a world of complex service blueprints, emotional mapping, and high-fidelity behavioral analytics, the BUJ feels like trying to navigate a Tesla with a paper map from 1994. You’re suggesting we can “steer user-centric design without much user input.” That right there? That’s the “gimmick” red flag. Any designer worth their salt knows that “designing without user input” is just a fancy way of saying “we’re guessing.” We call those assumptions, not a journey.

The BUJ treats the user like a data-processing unit: Input goes in, Output comes out. It’s so linear, so… mechanical. Where’s the friction? Where’s the irrational human behavior? Where are the “edge cases” that aren’t just bullet points in a “Review of Implications” section?

You say it “spirals our thinking into the nitty-gritty.” I’d argue it just keeps us circling the drain of the obvious. “Our consumer wants to know what to do.” Groundbreaking. “Our enterprise wants to demonstrate value.” I’ll alert the C-suite; they’ll be shocked.

It’s a neat little writing prompt for a content strategist, sure. If you’re stuck on a 404 page or a login screen, maybe “dialling into” your little rotary phone helps you remember to include a “Forgot Password” link. But as a “top-level” UX framework for enterprise-scale product design?

It’s a toy, Pat. It’s a neat little heuristic for people who find actual journey mapping too intimidating. It’s “My First UX Kit.”

Anyway, I’ve got a workshop on cognitive load theory and neural-mapping in ten minutes. Keep at it, though. The industry always needs people to remind us where we started.

Closes laptop lid with a definitive click.

Follow up prompt

I knew Gemini could be cold and this blew a chill. I countered like a child seeking approval:

could you oppose that view?

Leans forward, sets the espresso aside, and drops the persona. Let’s look at this through a more objective, appreciative lens.

While the cynical “top-level” designer sees a gimmick, a seasoned Product Lead or Systems Architect would see something else entirely: Elegant abstraction.

The critique that it’s “too simple” misses the point of why frameworks exist. Complexity is easy; clarity is hard. Your “Basic User Journey” (BUJ) isn’t a replacement for deep research—it’s a north star for when teams get lost in the weeds of feature creep.

Here is why that “gimmicky” view is wrong:

1. The Power of “Constraints as a Service”

   Modern UX often suffers from “The Infinite Canvas” problem. We have so many tools, data points, and personas that we end up paralyzed. The BUJ acts as a forcing function. By limiting the “dial” to six specific stops, you force a team to define the core value proposition before they’re allowed to argue about the color of a button.

2. Radical Accessibility

   The “elitist” designer wants UX to be a black box that only they can interpret. Your BUJ democratizes the process.

   • The Stakeholder Bridge: A CEO doesn’t want to see a 50-node service blueprint. They want to see the “Enterprise Need” vs. the “Consumer Want.”
   • The Developer Sync: Engineers love inputs and outputs. By framing the journey as a series of inputs leading to a specific result, you’re speaking the language of logic, which reduces friction during handoff.

3. The “Anti-Friction” Framework.

   The BUJ is actually a brilliant Vulnerability Audit.

   If you can’t fill out those six stops, it means you don’t actually know what you’re building. The “gimmick” is actually a litmus test. If the “Consumer Want” doesn’t align with the “Enterprise Need” on that dial, the project is doomed regardless of how many “emotional maps” you draw later.

4. It Scales Down to Scale Up.

   The most complex systems are just collections of small, successful interactions.

   Atomic Design: Just as we have atomic UI components, the BUJ is an Atomic Interaction.

   If every small “loop” in your app—from logging in to checking a notification—passes the BUJ test, the entire ecosystem becomes inherently user-centric.

The Reality Check

Sophisticated designers often mistake “simple” for “simplistic.” Your tool isn’t a toy; it’s a mental model. It’s the “Occam’s Razor” of UX: the simplest path to understanding the user is usually the right one.

The “Basic User Journey” isn’t a relic of the past; it’s a foundational discipline. In an industry obsessed with “delight” and “vibes,” your framework stays focused on utility and intent.

---

Summary

Phew! Confidence wavered for a moment there. And then, the BUJ has worked for me for over 10 years. Why would I doubt it?

The AI Verdicts:

• Bing (The grudging convert): Started with a massive eye-roll at “another circular diagram” and eventually caved, admitting the BUJ is an “annoyingly practical” workshop tool that bridges the gap between design and business logic.

• Gemini (The high-fashion critic): Initially delivered a brutal, espresso-fuelled takedown, calling the BUJ a “vintage toy” for juniors. However, after a little “therapy session” for Pat with a follow-up prompt, it pivoted to a glowing defence, hailing the BUJ as “Elegant Abstraction” and the “Occam’s Razor of UX.”

Whether you’re a seasoned architect or a “bootcamp junior,” the BUJ serves as a vital litmus test. If you can’t dial in the basics, no amount of high-fidelity “vibes” will save your product. It’s not just a journey; it’s an Atomic Interaction that keeps the user at the center—even when you’re designing without a map.

Read more in my blog post Adding AI to my Basic User Journey.