<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Product on Harlan D. Harris</title><link>https://harlanh.tech/tags/product/</link><description>Recent content in Product on Harlan D. Harris</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>harlan.harris@gmail.com (Harlan Harris)</managingEditor><webMaster>harlan.harris@gmail.com (Harlan Harris)</webMaster><lastBuildDate>Mon, 20 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://harlanh.tech/tags/product/index.xml" rel="self" type="application/rss+xml"/><item><title>Search Describes Solutions -- But What About Problems?</title><link>https://harlanh.tech/2026/07/search-describes-solutions-what-about-problems/</link><pubDate>Mon, 20 Jul 2026 00:00:00 +0000</pubDate><author>harlan.harris@gmail.com (Harlan Harris)</author><guid>https://harlanh.tech/2026/07/search-describes-solutions-what-about-problems/</guid><description>
&lt;p&gt;In a &lt;a href="https://harlanh.tech/2026/02/ize-revisiting-hierarchical-search-technology-pc-era/"&gt;previous post&lt;/a&gt; I said
that Search User Interfaces (UI) have two jobs -- helping people find things and educating them about the catalog's structure. (I'll use &amp;quot;catalog&amp;quot; here under the assumption that I'm
describing an e-commerce search system, but much of this post is relevant for
other search domains.)
The search results, facets, and other elements describe the catalog: the
solutions and products available.&lt;/p&gt;
&lt;p&gt;But there's a third job that's often not addressed and not always well defined: &lt;em&gt;helping users understand their problem&lt;/em&gt;, before they're ready to evaluate solutions.
Standard search UI patterns assume the user is already in the right mental state to evaluate what's on offer.
The design challenge that I want to discuss, then, is to figure out how best to support &lt;em&gt;problem education&lt;/em&gt; in search interfaces.&lt;/p&gt;</description></item><item><title>Design Decisions for a New Search Results Page</title><link>https://harlanh.tech/2026/05/design-decisions-new-search-results-page/</link><pubDate>Fri, 08 May 2026 00:00:00 +0000</pubDate><author>harlan.harris@gmail.com (Harlan Harris)</author><guid>https://harlanh.tech/2026/05/design-decisions-new-search-results-page/</guid><description>
&lt;p&gt;One of my specialties as a freelance consultant is discovery systems for e-commerce
-- web pages and backend systems for helping users search for and find what they want or need. For
the last year and a half,
I've been working as a consultant for &lt;a href="https://designshop.com"&gt;DesignShop&lt;/a&gt;, a
company that sells materials samples for home renovations. Want to find
a countertop, cabinet, paint, and tile combo for your kitchen reno that looks great,
with samples shipped overnight? Check 'em out.&lt;/p&gt;</description></item><item><title>You Don't Need a Search Engineer; You Need a Search Scientist</title><link>https://harlanh.tech/2026/04/you-dont-need-a-search-engineer-you-need-a-search-scientist/</link><pubDate>Mon, 13 Apr 2026 00:00:00 +0000</pubDate><author>harlan.harris@gmail.com (Harlan Harris)</author><guid>https://harlanh.tech/2026/04/you-dont-need-a-search-engineer-you-need-a-search-scientist/</guid><description>
&lt;p&gt;Say you're an Engineering Manager or a Product Manager, responsible for a business-critical
search system on a website. Maybe e-commerce, maybe a marketplace, maybe something else.
Search is sort of working, it doesn't crash, and it's fast, but there's a
feeling that &amp;quot;search isn't great&amp;quot;, and you've been tasked with finding someone to help.
Your first instinct, or that of your VP, might be some version of: “we need to hire a search engineer.”&lt;/p&gt;</description></item><item><title>A Collaborative Template for A/B Tests</title><link>https://harlanh.tech/2023/10/a-collaborative-template-for-a-b-tests/</link><pubDate>Thu, 12 Oct 2023 00:00:00 +0000</pubDate><author>harlan.harris@gmail.com (Harlan Harris)</author><guid>https://harlanh.tech/2023/10/a-collaborative-template-for-a-b-tests/</guid><description>
&lt;p&gt;As I've &lt;a href="https://harlanh.tech/2022/08/communicating-a-b-test-results-for-conversion-rates-with-ratios-and-uncertainty-intervals/"&gt;written about before&lt;/a&gt;, as a data scientist supporting a product or marketing team with A/B testing, the job is &lt;em&gt;communication&lt;/em&gt; -- helping to translate between business requirements and what we can learn from statistics. I (&lt;a href="https://www.google.com/search?q=a%2Fb+testing+document+template"&gt;and many, many others&lt;/a&gt;) have found that there is a lot of value in having a document, shared among the team that is running the test. Some A/B testing tools include some limited workflow for collaboration on testing (e.g., &lt;a href="https://amplitude.com/amplitude-experiment"&gt;Amplitude Experiments&lt;/a&gt; has pre-test, monitoring, and results tabs with useful graphs and summary statistics), but I think the most important thing is to have a tool that helps the team &lt;em&gt;get aligned&lt;/em&gt; by forcing them to &lt;em&gt;write things down&lt;/em&gt;.&lt;/p&gt;</description></item><item><title>Are LLMs a simple solution? And if so, for what problems?</title><link>https://harlanh.tech/2023/09/are-llms-a-simple-solution/</link><pubDate>Thu, 14 Sep 2023 00:00:00 +0000</pubDate><author>harlan.harris@gmail.com (Harlan Harris)</author><guid>https://harlanh.tech/2023/09/are-llms-a-simple-solution/</guid><description>
&lt;p&gt;The other day, I was reading a
&lt;a href="https://studio.ribbonfarm.com/p/my-climate-posture"&gt;post by Venkatash Rao&lt;/a&gt;
(thousands of words of under-edited brilliance, as usual), and was struck by
this note about the complexity of climate solutions:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;I tend to take as an article of faith the systems science rule of thumb that
the complexity of solutions generally matches the complexity of the problems.
If it doesn’t, then you either got lucky, or there are negative externalities
you’re ignoring.&lt;/p&gt;</description></item></channel></rss>