Escape the UX Guessing Game
Set the Strategy, Experiment Fast and Reach Measurable UX
Insights
Jan 23, 2026
Ever felt your UX efforts were just a meticulously crafted aesthetic add-on, admired, but unclear if they made a real difference? I have. It's like a Michelin-star chef creating a meal, only for the diner to ignore it and ask, "What's for dessert?"
A little over a year ago, NN/g's credit course "Becoming a UX Strategist" and Jamie Levy's "UX Strategy" handed me a new lens. This wasn't minor tweaks; it was a foundational shift in my approach to Experience Design. Spoiler: it's incredibly liberating and effective.
"A good business strategy is one centered around the customer."
— Jamie Levy, Author of UX Strategy
The Big Idea: “UX Strategy IS Business Strategy”
Let's be blunt: UX isn't about making things ‘pretty’; it's about making things perform. NN/g highlighted a truth that should be tattooed on every product roadmap: experience strategy is a coordinated set of actions moving you toward a future state (vision → strategic objectives → tactical projects). It translates ambiguous business goals into tangible, customer-centered outcomes that move the needle.
If your team treats UX like glorified screen decorators, you're missing an opportunity; you're handing the steering wheel of your product to chance. And chance is a notoriously bad driver.
Jamie Levy then offered the playbook for validating strategic bets: treat product changes as hypotheses, design MVPs to test them, and iterate based on cold, hard evidence. As she puts it: "Strategy without validation is wishful thinking; experiments without strategy are aimless tinkering." Put them together, and you get undeniable, measurable proof. No more hoping, just knowing.
"The role of a UX strategist is to ensure that user-centered “insights” are integrated into the business strategy and implemented successfully."
— UX Strategist Research Report, Dickenson LLC 2019
My "Aha!" Moments
Looking back, some early failures could have been successes with just a few small adjustments. These 3 practical shifts aren't just academic concepts; they're battle-tested strategies born from projects that once felt immeasurable and adrift.
Shift 1: Ditching Vague Praise for Pinpoint Goals.
What changed: I used to jump straight into wireframes, fueled by enthusiasm and a general sense of "making things better." Now I start with a one-line vision and a quantifiable strategic objective before sketching anything.
Vision: Where do you want to be in 2-5 years? (e.g., "Become the easiest platform for small businesses to manage their cash flow.")
Objective: What specific, measurable step do we expect in 6-12 months? (e.g., "Reduce average time for SMBs to reconcile invoices by 25% within 6 months.")
Why it matters (and why it saves you from "looks great!" purgatory): A clear objective transforms vague praise ("Looks great!") into a business conversation ("Did it reduce processing time?"). It makes your work a strategic asset, enabling prioritization and saying "no" to distracting features. Like a GPS, it keeps you on track.
Shift 2: Mapping the REAL Journey
What changed: Journey mapping used to be a nice-to-have workshop exercise. Now, it's my go-to first-week tool, mapping not just screens, but the entire ecosystem: jobs, handoffs, tools, emotions, and all relevant customer segments.
Why it matters (and why your UI might be just wallpaper): This is where the magic happens. Journeys reveal where real pain lives; often outside the UI. Fixing only the UI without addressing systemic issues is like painting a leaky roof. You get a prettier interface, not a better one. Users see right through a crumbling foundation.
Shift 3: Small Bets, Big Wins
What changed: Inspired by Levy, every strategic objective spawns 2-4 testable hypotheses. For each, we design an MVP or micro-experiment with a clear success metric and a defined cohort. These experiments are time-boxed, instrumented, and limited in scope. No more all-or-nothing launches based on gut feelings.
Why it matters (and how to win over skeptical stakeholders): Small bets are strategic. They reduce risk, accelerate learning, and build credibility. Experiments offer a smart way to deliver value fast and prove the approach works with data. It's moving from "I think this will work" to "We know this works, with evidence."
"What a good UX strategy entails is researching and recognizing constraints and concerns from all sides and painting a big red target on the wall so that everyone involved can make decisions that serve researched, vetted, and defined objectives."
— Robert Hoekman, Jr., The Field Guide to UX Strategy, UX Pin
Learning from Past Missteps
Hindsight is 20/20. In 2019, a project aimed to digitize a manual claims process via a new portal feature. We built and launched it. A year later, most smaller businesses stuck to paper, finding the change too much effort. The failure wasn't effort, but a lack of clear strategy and experimentation. We chased 'automation' ambiguously, building a feature without solving the actual problem.
"Just because your stakeholders (or you) really want your product doesn't mean anybody else will. Most start-ups fail because the market doesn't necessarily need the product."
— Jamie Levy, Author of UX Strategy
What if we’d applied "Strategy First, Experiments Fast"? We could have highlighted risks, pivoted, and delivered impactful change. It’s about smarter, smaller bets delivering big insights, even on tight timelines. Here’s how that project could have looked:
Vision: "Make claims painless for the 80% of customers who use the portal monthly.” (Ambitious, but clear!)
Objective: "Reduce average claim handling time by 25% for SMBs within 6 months.” (Measurable, time-bound.)
From this, we generate hypotheses with 2 if/then statements:
"IF we automate X backend check, THEN claims that meet criteria will be resolved without manual review, saving 40% time."
"IF we add inline guidance for common claim paths, THEN submission errors will fall by 30%."
Then, we design experiments to test the interface and whether our new automation works for one claim type:
Guidance UI: Conduct moderated testing of a new UI with 20 SMB users, followed by an A/B rollout to a broader cohort, measuring submission error rates.
Automation Pilot: Roll out automation for a single claim type with 100 representative SMB users.
Success looks like: A measurable change in handling time and support tickets.
The outcome? Learn, iterate, and then scale.
How This Transforms Stakeholder Conversations (and Your Sanity):
This isn't just about changing what you do; it's about fundamentally changing how you talk about it – building a compelling case for the Return on Investment (ROI) of thoughtful design. No more arguing for pixels; you're discussing profit, efficiency, customer loyalty, and strategic business growth.
From: "Can you build this?" → To: "Which hypothesis should we test first, and what metric will convince us to scale?"
From: "Ready to ship!" → To: "Ready to measure!"
From: Feature opinions → To: Shared accountability for outcomes.
"You need to ground your stakeholders and team in reality with empirical evidence. You must turn assumptions into facts."
— Jamie Levy, Author of UX Strategy
Two Pragmatic Traps to Avoid (Because We've All Stepped in Them):
1. Testing only the "influential" users:
If your user base is segmented, your test pool must reflect that diversity. Relying solely on feedback from biggest customers biases results, leading to unrepresentative rabbit holes.
2. Letting influence replace evidence:
Influence is gold for unlocking resources and buy-in, but it should never be the sole justification to ship. Data trumps anecdotes, every single time.
3. Falling into the "analysis paralysis" or "we don't have time" trap:
Yes, this framework involves strategic thinking and experimenting. The alternative (building something nobody needs, or endlessly debating without data) is far more time-consuming and expensive. For small-scale projects or tight deadlines, remember: micro-experiments are your superpower. A 2-week, clearly defined experiment with a specific hypothesis and success metric is infinitely more valuable than rushing to build the wrong thing.
It's about being lean and smart, not slow.
Small Mindset Tweaks That Pay Off Big-Time (My Personal Growth Journey):
Embrace the "failed" experiment:
It's not a failure if you learned something! Celebrate those experiments that taught you what doesn't work. That's progress, folks, and starting small saves you from building the wrong thing at scale.Keep experiments visible:
Execs love evidence; especially when it's quick, clear, and tied directly to business KPIs. Transparency builds trust.Document the "why," not just the "what":
A roadmap that's just a list of features is a wishlist. A strategy-backed roadmap is a plan.
Ready to Stop Guessing and Start Proving?
If you're staring down a feature that feels urgent, or a product roadmap that feels more like a wish list than a battle plan, pause. Ask yourself: What's the one-line strategic objective this should serve? Then, let's design a short, sharp experiment (2-6 weeks) that will prove or disprove its value.
Need a template for that experiment (Hypothesis → Metric → Cohort → MVP)? I’ve got one I'd be happy to work on with you!
Strategy gives you the destination; experiments show the path. Do both, and you stop guessing and start proving.
Escape the UX Guessing Game
Set the Strategy, Experiment Fast and Reach Measurable UX
Insights
Jan 23, 2026
Ever felt your UX efforts were just a meticulously crafted aesthetic add-on, admired, but unclear if they made a real difference? I have. It's like a Michelin-star chef creating a meal, only for the diner to ignore it and ask, "What's for dessert?"
A little over a year ago, NN/g's credit course "Becoming a UX Strategist" and Jamie Levy's "UX Strategy" handed me a new lens. This wasn't minor tweaks; it was a foundational shift in my approach to Experience Design. Spoiler: it's incredibly liberating and effective.
"A good business strategy is one centered around the customer."
— Jamie Levy, Author of UX Strategy
The Big Idea: “UX Strategy IS Business Strategy”
Let's be blunt: UX isn't about making things ‘pretty’; it's about making things perform. NN/g highlighted a truth that should be tattooed on every product roadmap: experience strategy is a coordinated set of actions moving you toward a future state (vision → strategic objectives → tactical projects). It translates ambiguous business goals into tangible, customer-centered outcomes that move the needle.
If your team treats UX like glorified screen decorators, you're missing an opportunity; you're handing the steering wheel of your product to chance. And chance is a notoriously bad driver.
Jamie Levy then offered the playbook for validating strategic bets: treat product changes as hypotheses, design MVPs to test them, and iterate based on cold, hard evidence. As she puts it: "Strategy without validation is wishful thinking; experiments without strategy are aimless tinkering." Put them together, and you get undeniable, measurable proof. No more hoping, just knowing.
"The role of a UX strategist is to ensure that user-centered “insights” are integrated into the business strategy and implemented successfully."
— UX Strategist Research Report, Dickenson LLC 2019
My "Aha!" Moments
Looking back, some early failures could have been successes with just a few small adjustments. These 3 practical shifts aren't just academic concepts; they're battle-tested strategies born from projects that once felt immeasurable and adrift.
Shift 1: Ditching Vague Praise for Pinpoint Goals.
What changed: I used to jump straight into wireframes, fueled by enthusiasm and a general sense of "making things better." Now I start with a one-line vision and a quantifiable strategic objective before sketching anything.
Vision: Where do you want to be in 2-5 years? (e.g., "Become the easiest platform for small businesses to manage their cash flow.")
Objective: What specific, measurable step do we expect in 6-12 months? (e.g., "Reduce average time for SMBs to reconcile invoices by 25% within 6 months.")
Why it matters (and why it saves you from "looks great!" purgatory): A clear objective transforms vague praise ("Looks great!") into a business conversation ("Did it reduce processing time?"). It makes your work a strategic asset, enabling prioritization and saying "no" to distracting features. Like a GPS, it keeps you on track.
Shift 2: Mapping the REAL Journey
What changed: Journey mapping used to be a nice-to-have workshop exercise. Now, it's my go-to first-week tool, mapping not just screens, but the entire ecosystem: jobs, handoffs, tools, emotions, and all relevant customer segments.
Why it matters (and why your UI might be just wallpaper): This is where the magic happens. Journeys reveal where real pain lives; often outside the UI. Fixing only the UI without addressing systemic issues is like painting a leaky roof. You get a prettier interface, not a better one. Users see right through a crumbling foundation.
Shift 3: Small Bets, Big Wins
What changed: Inspired by Levy, every strategic objective spawns 2-4 testable hypotheses. For each, we design an MVP or micro-experiment with a clear success metric and a defined cohort. These experiments are time-boxed, instrumented, and limited in scope. No more all-or-nothing launches based on gut feelings.
Why it matters (and how to win over skeptical stakeholders): Small bets are strategic. They reduce risk, accelerate learning, and build credibility. Experiments offer a smart way to deliver value fast and prove the approach works with data. It's moving from "I think this will work" to "We know this works, with evidence."
"What a good UX strategy entails is researching and recognizing constraints and concerns from all sides and painting a big red target on the wall so that everyone involved can make decisions that serve researched, vetted, and defined objectives."
— Robert Hoekman, Jr., The Field Guide to UX Strategy, UX Pin
Learning from Past Missteps
Hindsight is 20/20. In 2019, a project aimed to digitize a manual claims process via a new portal feature. We built and launched it. A year later, most smaller businesses stuck to paper, finding the change too much effort. The failure wasn't effort, but a lack of clear strategy and experimentation. We chased 'automation' ambiguously, building a feature without solving the actual problem.
"Just because your stakeholders (or you) really want your product doesn't mean anybody else will. Most start-ups fail because the market doesn't necessarily need the product."
— Jamie Levy, Author of UX Strategy
What if we’d applied "Strategy First, Experiments Fast"? We could have highlighted risks, pivoted, and delivered impactful change. It’s about smarter, smaller bets delivering big insights, even on tight timelines. Here’s how that project could have looked:
Vision: "Make claims painless for the 80% of customers who use the portal monthly.” (Ambitious, but clear!)
Objective: "Reduce average claim handling time by 25% for SMBs within 6 months.” (Measurable, time-bound.)
From this, we generate hypotheses with 2 if/then statements:
"IF we automate X backend check, THEN claims that meet criteria will be resolved without manual review, saving 40% time."
"IF we add inline guidance for common claim paths, THEN submission errors will fall by 30%."
Then, we design experiments to test the interface and whether our new automation works for one claim type:
Guidance UI: Conduct moderated testing of a new UI with 20 SMB users, followed by an A/B rollout to a broader cohort, measuring submission error rates.
Automation Pilot: Roll out automation for a single claim type with 100 representative SMB users.
Success looks like: A measurable change in handling time and support tickets.
The outcome? Learn, iterate, and then scale.
How This Transforms Stakeholder Conversations (and Your Sanity):
This isn't just about changing what you do; it's about fundamentally changing how you talk about it – building a compelling case for the Return on Investment (ROI) of thoughtful design. No more arguing for pixels; you're discussing profit, efficiency, customer loyalty, and strategic business growth.
From: "Can you build this?" → To: "Which hypothesis should we test first, and what metric will convince us to scale?"
From: "Ready to ship!" → To: "Ready to measure!"
From: Feature opinions → To: Shared accountability for outcomes.
"You need to ground your stakeholders and team in reality with empirical evidence. You must turn assumptions into facts."
— Jamie Levy, Author of UX Strategy
Two Pragmatic Traps to Avoid (Because We've All Stepped in Them):
1. Testing only the "influential" users:
If your user base is segmented, your test pool must reflect that diversity. Relying solely on feedback from biggest customers biases results, leading to unrepresentative rabbit holes.
2. Letting influence replace evidence:
Influence is gold for unlocking resources and buy-in, but it should never be the sole justification to ship. Data trumps anecdotes, every single time.
3. Falling into the "analysis paralysis" or "we don't have time" trap:
Yes, this framework involves strategic thinking and experimenting. The alternative (building something nobody needs, or endlessly debating without data) is far more time-consuming and expensive. For small-scale projects or tight deadlines, remember: micro-experiments are your superpower. A 2-week, clearly defined experiment with a specific hypothesis and success metric is infinitely more valuable than rushing to build the wrong thing.
It's about being lean and smart, not slow.
Small Mindset Tweaks That Pay Off Big-Time (My Personal Growth Journey):
Embrace the "failed" experiment:
It's not a failure if you learned something! Celebrate those experiments that taught you what doesn't work. That's progress, folks, and starting small saves you from building the wrong thing at scale.Keep experiments visible:
Execs love evidence; especially when it's quick, clear, and tied directly to business KPIs. Transparency builds trust.Document the "why," not just the "what":
A roadmap that's just a list of features is a wishlist. A strategy-backed roadmap is a plan.
Ready to Stop Guessing and Start Proving?
If you're staring down a feature that feels urgent, or a product roadmap that feels more like a wish list than a battle plan, pause. Ask yourself: What's the one-line strategic objective this should serve? Then, let's design a short, sharp experiment (2-6 weeks) that will prove or disprove its value.
Need a template for that experiment (Hypothesis → Metric → Cohort → MVP)? I’ve got one I'd be happy to work on with you!
Strategy gives you the destination; experiments show the path. Do both, and you stop guessing and start proving.
Escape the UX Guessing Game
Set the Strategy, Experiment Fast and Reach Measurable UX
Insights
Jan 23, 2026
Ever felt your UX efforts were just a meticulously crafted aesthetic add-on, admired, but unclear if they made a real difference? I have. It's like a Michelin-star chef creating a meal, only for the diner to ignore it and ask, "What's for dessert?"
A little over a year ago, NN/g's credit course "Becoming a UX Strategist" and Jamie Levy's "UX Strategy" handed me a new lens. This wasn't minor tweaks; it was a foundational shift in my approach to Experience Design. Spoiler: it's incredibly liberating and effective.
"A good business strategy is one centered around the customer."
— Jamie Levy, Author of UX Strategy
The Big Idea: “UX Strategy IS Business Strategy”
Let's be blunt: UX isn't about making things ‘pretty’; it's about making things perform. NN/g highlighted a truth that should be tattooed on every product roadmap: experience strategy is a coordinated set of actions moving you toward a future state (vision → strategic objectives → tactical projects). It translates ambiguous business goals into tangible, customer-centered outcomes that move the needle.
If your team treats UX like glorified screen decorators, you're missing an opportunity; you're handing the steering wheel of your product to chance. And chance is a notoriously bad driver.
Jamie Levy then offered the playbook for validating strategic bets: treat product changes as hypotheses, design MVPs to test them, and iterate based on cold, hard evidence. As she puts it: "Strategy without validation is wishful thinking; experiments without strategy are aimless tinkering." Put them together, and you get undeniable, measurable proof. No more hoping, just knowing.
"The role of a UX strategist is to ensure that user-centered “insights” are integrated into the business strategy and implemented successfully."
— UX Strategist Research Report, Dickenson LLC 2019
My "Aha!" Moments
Looking back, some early failures could have been successes with just a few small adjustments. These 3 practical shifts aren't just academic concepts; they're battle-tested strategies born from projects that once felt immeasurable and adrift.
Shift 1: Ditching Vague Praise for Pinpoint Goals.
What changed: I used to jump straight into wireframes, fueled by enthusiasm and a general sense of "making things better." Now I start with a one-line vision and a quantifiable strategic objective before sketching anything.
Vision: Where do you want to be in 2-5 years? (e.g., "Become the easiest platform for small businesses to manage their cash flow.")
Objective: What specific, measurable step do we expect in 6-12 months? (e.g., "Reduce average time for SMBs to reconcile invoices by 25% within 6 months.")
Why it matters (and why it saves you from "looks great!" purgatory): A clear objective transforms vague praise ("Looks great!") into a business conversation ("Did it reduce processing time?"). It makes your work a strategic asset, enabling prioritization and saying "no" to distracting features. Like a GPS, it keeps you on track.
Shift 2: Mapping the REAL Journey
What changed: Journey mapping used to be a nice-to-have workshop exercise. Now, it's my go-to first-week tool, mapping not just screens, but the entire ecosystem: jobs, handoffs, tools, emotions, and all relevant customer segments.
Why it matters (and why your UI might be just wallpaper): This is where the magic happens. Journeys reveal where real pain lives; often outside the UI. Fixing only the UI without addressing systemic issues is like painting a leaky roof. You get a prettier interface, not a better one. Users see right through a crumbling foundation.
Shift 3: Small Bets, Big Wins
What changed: Inspired by Levy, every strategic objective spawns 2-4 testable hypotheses. For each, we design an MVP or micro-experiment with a clear success metric and a defined cohort. These experiments are time-boxed, instrumented, and limited in scope. No more all-or-nothing launches based on gut feelings.
Why it matters (and how to win over skeptical stakeholders): Small bets are strategic. They reduce risk, accelerate learning, and build credibility. Experiments offer a smart way to deliver value fast and prove the approach works with data. It's moving from "I think this will work" to "We know this works, with evidence."
"What a good UX strategy entails is researching and recognizing constraints and concerns from all sides and painting a big red target on the wall so that everyone involved can make decisions that serve researched, vetted, and defined objectives."
— Robert Hoekman, Jr., The Field Guide to UX Strategy, UX Pin
Learning from Past Missteps
Hindsight is 20/20. In 2019, a project aimed to digitize a manual claims process via a new portal feature. We built and launched it. A year later, most smaller businesses stuck to paper, finding the change too much effort. The failure wasn't effort, but a lack of clear strategy and experimentation. We chased 'automation' ambiguously, building a feature without solving the actual problem.
"Just because your stakeholders (or you) really want your product doesn't mean anybody else will. Most start-ups fail because the market doesn't necessarily need the product."
— Jamie Levy, Author of UX Strategy
What if we’d applied "Strategy First, Experiments Fast"? We could have highlighted risks, pivoted, and delivered impactful change. It’s about smarter, smaller bets delivering big insights, even on tight timelines. Here’s how that project could have looked:
Vision: "Make claims painless for the 80% of customers who use the portal monthly.” (Ambitious, but clear!)
Objective: "Reduce average claim handling time by 25% for SMBs within 6 months.” (Measurable, time-bound.)
From this, we generate hypotheses with 2 if/then statements:
"IF we automate X backend check, THEN claims that meet criteria will be resolved without manual review, saving 40% time."
"IF we add inline guidance for common claim paths, THEN submission errors will fall by 30%."
Then, we design experiments to test the interface and whether our new automation works for one claim type:
Guidance UI: Conduct moderated testing of a new UI with 20 SMB users, followed by an A/B rollout to a broader cohort, measuring submission error rates.
Automation Pilot: Roll out automation for a single claim type with 100 representative SMB users.
Success looks like: A measurable change in handling time and support tickets.
The outcome? Learn, iterate, and then scale.
How This Transforms Stakeholder Conversations (and Your Sanity):
This isn't just about changing what you do; it's about fundamentally changing how you talk about it – building a compelling case for the Return on Investment (ROI) of thoughtful design. No more arguing for pixels; you're discussing profit, efficiency, customer loyalty, and strategic business growth.
From: "Can you build this?" → To: "Which hypothesis should we test first, and what metric will convince us to scale?"
From: "Ready to ship!" → To: "Ready to measure!"
From: Feature opinions → To: Shared accountability for outcomes.
"You need to ground your stakeholders and team in reality with empirical evidence. You must turn assumptions into facts."
— Jamie Levy, Author of UX Strategy
Two Pragmatic Traps to Avoid (Because We've All Stepped in Them):
1. Testing only the "influential" users:
If your user base is segmented, your test pool must reflect that diversity. Relying solely on feedback from biggest customers biases results, leading to unrepresentative rabbit holes.
2. Letting influence replace evidence:
Influence is gold for unlocking resources and buy-in, but it should never be the sole justification to ship. Data trumps anecdotes, every single time.
3. Falling into the "analysis paralysis" or "we don't have time" trap:
Yes, this framework involves strategic thinking and experimenting. The alternative (building something nobody needs, or endlessly debating without data) is far more time-consuming and expensive. For small-scale projects or tight deadlines, remember: micro-experiments are your superpower. A 2-week, clearly defined experiment with a specific hypothesis and success metric is infinitely more valuable than rushing to build the wrong thing.
It's about being lean and smart, not slow.
Small Mindset Tweaks That Pay Off Big-Time (My Personal Growth Journey):
Embrace the "failed" experiment:
It's not a failure if you learned something! Celebrate those experiments that taught you what doesn't work. That's progress, folks, and starting small saves you from building the wrong thing at scale.Keep experiments visible:
Execs love evidence; especially when it's quick, clear, and tied directly to business KPIs. Transparency builds trust.Document the "why," not just the "what":
A roadmap that's just a list of features is a wishlist. A strategy-backed roadmap is a plan.
Ready to Stop Guessing and Start Proving?
If you're staring down a feature that feels urgent, or a product roadmap that feels more like a wish list than a battle plan, pause. Ask yourself: What's the one-line strategic objective this should serve? Then, let's design a short, sharp experiment (2-6 weeks) that will prove or disprove its value.
Need a template for that experiment (Hypothesis → Metric → Cohort → MVP)? I’ve got one I'd be happy to work on with you!
Strategy gives you the destination; experiments show the path. Do both, and you stop guessing and start proving.