As my wife and I use Genlighten day by day, we notice things it does well and things it’s not so good at yet.
On the Plus Side
One of the things Genlighten does well is handle the iterative back-and-forth communications between client and provider that lead to a successful lookup result. Short notes from each party to the research transaction are displayed together in chronological order on a summary tracking page for each lookup request, along with the documents and report that are eventually produced.
Discovering Providers, on the Other Hand…
But when we go looking for a specific lookup provider (say, one that specializes in Jewish research or one who can access a certain repository in California) Genlighten doesn’t have a well-designed way to do that yet.
There’s a reason we didn’t build that feature in initially. We view ourselves as an e-commerce site (like Amazon.com) for genealogy lookups — NOT a Yellow Pages-like directory of genealogy researchers-for-hire. The distinction is an important one, and it arises out of our focus on fixed-fee lookups rather than on open-ended hourly research.
Buying a Camera vs. Hiring a Photographer
I’m not sure about you, but when I go to buy a digital camera, I focus on the product first — the features, price point and customer ratings — and pay attention to the brand second. On the other hand, if I wanted to hire a photographer, I’d focus on referrals from friends, professional credentials, portfolio… and only then would I look at specific packages the photographer might offer.
The initial design of Genlighten has a distinctly product-oriented e-commerce mindset, where the “products” are lookups. If our products appeal to you, you can then check out the profile of the providers who offer them, and evaluate their background, experience, and customer ratings before deciding to submit a lookup request. We made the assumption that most potential clients would approach the site in that order, and our information architecture reflects that.
The Problem with Assumptions…
Four months in, it’s becoming apparent that some of our site visitors don’t use Genlighten like we thought they would. One piece of evidence showed up recently in our Google Analytics logs:
Notice the Google site search for the keyword “California”. It’s hard to tell exactly what the site visitor had in mind, but my guess is they wanted to see if we had any providers that could do lookups either in California (i.e., at California repositories) or for California records. Or they might have read Randy Seaver’s blog post about Genlighten the week before and tried to find out if we’d added any California providers. Either way, they didn’t find our UI sufficiently intuitive and decided to take a shortcut.
“Hidden” Lookup Providers
A second indication that users aren’t behaving as we expected showed up when I went to do a census of every registered user so I could count the number that were offering lookups. To my surprise (and dismay!) I discovered sixty-some users who had filled out a provider-oriented profile (listing their qualifications, repositories they could access, etc.) but who weren’t yet offering any lookups. Because of the design assumptions I mentioned above, these providers are effectively hidden from our users. They won’t show up in any lookup search results, and we don’t yet offer a purely provider-oriented search capability. That’s starting to look like a problem.
Now perhaps the hidden providers don’t want to bother with basic lookups, but instead are just interested in quoting on custom requests that clients post. We do offer that capability in addition to off-the-shelf lookups, and it’s seen a fair amount of use.
But our thinking on custom requests was that providers would first establish a reputation for reliable, high-quality service with their off-the-shelf lookup offerings, and then be more likely to have their custom lookup quotes accepted based on high ratings they’d received. I still think this is a sound approach, but it’s become clear that we’ve done a poor job of communicating the idea.
Unfortunately, I suspect that some of these hidden providers don’t know they’re hidden. They assumed we’d make it easy for users to find them, like the yellow pages does, even if they didn’t offer any products in our online marketplace. And we haven’t.
So What to Do?
As a result of the thought process I’ve described, we now plan to:
- Reach out to our hidden providers and explain the advantages of offering off-the-shelf lookups so they can gain credibility and exposure to potential clients
- Invite our users to participate in usability testing so we can get feedback on typical flows through the site
- Develop search tools that let users discover providers based on the contents of their profiles, not just on the lookups they offer.
Glass Half Full
I’ve decided to take a positive view of these discoveries about our users. If I’d followed Steve Blank’s Four Steps to the Epiphany when we were first building Genlighten, I might have uncovered these design issues during the Customer Development process. But now that I’m belatedly trying to adhere to Lean Startup principles, customer-centric iteration is a sign that we’re heading in the right direction. Now if we can just work on making those iterations “ferocious” and “rapid”!
Want to Help?
Are you interested in helping us make Genlighten easier to use? We’d love to have some 15-20 minute chats with clients and providers willing to talk with us over the phone while navigating the site and pursuing basic tasks. E-mail us at firstname.lastname@example.org if this sounds like your idea of fun!