Sitemaps
How We Secretly Lose Control of Our Startups
Should Kids Follow in Our Founder Footsteps?
The Evolution of Entry Level Workers
Assume Everyone Will Leave in Year One
Stop Listening to Investors
Was Mortgaging My Life Worth it?
What's My Startup Worth in an Acquisition?
When Our Ambition is Our Enemy
Are Startups in a "Silent Recession"?
The 5 Types of Startup Funding
What Is Startup Funding?
Do Founders Deserve Their Profit?
Michelle Glauser on Diversity and Inclusion
The Utter STUPIDITY of "Risking it All"
Committees Are Where Progress Goes to Die
More Money (Really Means) More Problems
Why Most Founders Don't Get Rich
Investors will be Obsolete
Why is a Founder so Hard to Replace?
We Can't Grow by Saying "No"
Do People Really Want Me to Succeed?
Is the Problem the Player or the Coach?
Will Investors Bail Me Out?
The Value of Actually Getting Paid
Why do Founders Suck at Asking for Help?
Wait a Minute before Giving Away Equity
You Only Think You Work Hard
SMALL is the New Big — Embracing Efficiency in the Age of AI
The 9 Best Growth Agencies for Startups
This is BOOTSTRAPPED — 3 Strategies to Build Your Startup Without Funding
Never Share Your Net Worth
A Steady Hand in the Middle of the Storm
Risk it All vs Steady Paycheck
How About a Startup that Just Makes Money?
How to Recruit a Rockstar Advisor
Why Having Zero Experience is a Huge Asset
My Competitor Got Funded — Am I Screwed?
The Hidden Treasure of Failed Startups
If It Makes Money, It Makes Sense
Why do VCs Keep Giving Failed Founders Money?
$10K Per Month isn't Just Revenue — It's Life Support
The Ridiculous Spectrum of Investor Feedback
Startup CEOs Aren't Really CEOs
Series A, B, C, D, and E Funding: How It Works
Best Pitch Decks Ever: The Most Successful Fundraising Pitches You Need to Know
When to Raise Funds
Why Aren't Investors Responding to Me?
Should I Regret Not Raising Capital?
Unemployment Cases — Why I LOOOOOVE To Win Them So Much.
How Much to Pay Yourself
Heat-Seeking Missile: WePay’s Journey to Product-Market Fit — Interview with Rich Aberman, Co-Founder of Wepay
The R&D technique for startups: Rip off & Duplicate
Why Some Startups Win.
Chapter #1: First Steps To Validate Your Business Idea
Product Users, Not Ideas, Will Determine Your Startup’s Fate
Drop Your Free Tier
Your Advisors Are Probably Wrong
Growth Isn't Always Good
How to Shut Down Gracefully
How Does My Startup Get Acquired?
Can Entrepreneurship Be Taught?
How to Pick the Wrong Co-Founder
Staying Small While Going Big
Investors are NOT on Our Side of the Table
Who am I Really Competing Against?
Why Can't Founders Replace Themselves?
Actually, We Have Plenty of Time
Quitting vs Letting Go
How Startups Actually Get Bought
What if I'm Building the Wrong Product?
Are Founders Driven by Fear or Greed?
Why I'm Either Working or Feeling Guilty
Startup Financial Assumptions
Why Every Kid Should be a Startup Founder
We Only Have to be Right Once
If a Startup Sinks, Founders Go Down With it
Founder Success: We Need a Strict Definition of Personal Success
Is Quiet Quitting a Problem at Startup Companies?
Founder Exits are Hard Work and Good Fortune, Not "Good Luck"
Finalizing Startup Projections
All Founders are Beloved In Good Times
Our Startup Culture of Entitlement
The Bullshit Case for Raising Capital
How do We Manage Our Founder Flaws?
What If my plan for retirement is "never retire"?
Startup Failure is just One Chapter in Founder Life
6 Similarities between Startup Founders and Pro Athletes
All Founders Make Bad Decisions — and That's OK
Startup Board Negotiations: How do I tell the board I need a new deal?
Founder Sacrifice — At What Point Have I Gone Too Far?
Youth Entrepreneurship: Can Middle Schoolers be Founders?
Living the Founder Legend Isn't so Fun
Why Do VC Funded Startups Love "Fake Growth?"
How Should I Share My Wealth with Family?
How Many Deaths Can a Startup Survive?
This is Probably Your Last Success
Why Do We Still Have Full-Time Employees?
The Case Against Full Transparency
Should I Feel Guilty for Failing?
Always Take Money off the Table

A Little Slice of Humble Pie

John Saddington

A Little Slice of Humble Pie

As we build out our early-stage product (and find great folks to Alpha Test it) we’re naturally working on all of the things related to the back-end (e.g. data, modeling, etc.) as well as the front-end (e.g. design, UI/UX, etc.).

The exciting and yet challenging thing at this point is that we have a completely carte blanche environment and anything that we do initially isn’t inherently wrong or qualitatively bad.

Of course, on the flip-side, we can’t be sure that we’re doing anything right or well either. The only answer, of course, is the combination of rapid experimentation in conjunction with early customer interviews, which is what great startups will do naturally.

0-z4Hmqkv_ZH8cqk7v

Some of the most poignant and powerful lessons-learned so far have also been some of the most obvious. Or, at the very least, “obvious” in hindsight.

You see, the biggest challenge that a product team has especially in the beginning is essentially getting out of your own head. In other words, as a consequence of proximity (i.e. being so close to the product) you develop natural blindness to design elements that you feel are obvious and intuitive but are, in fact, not.

A great example of this is how we show data to the end-user. Take for instance this one screen of contributions:

0-GE46lq6eUIGOwcZk

The first thing you’ll see for this particular user is, well, nothing. The “obvious” thing that I would do is immediately move toward the drop-down menu over on the right and change the time band:

0-6_kkdwvl_GjjFitl

The problem is that many of our Alpha Testers missed this drop-down completely! I would literally sit there and watch them get to this part of app and they would pause and then move on.

And it takes everything within me to just watch and observe instead of yell into the mic (or if it’s a in-person walk-through I’d want to tap them on the shoulder…) and tell them to hit the drop-down!

But the reality is that the placement of the drop-down wasn’t obvious, it wasn’t intuitive, and it was just visually being overlooked and missed.

Why? We’re still not entirely sure scientifically but we have our hypotheses and we certainly have enough empirical evidence that it’s being overlooked and missed.

Which, of course, is super-depressing because the user completely misses out on all the rich data that we’ve pulled about their current team and development environment and all of the actionable insights about their EngOps universe:

0-a4q5_T2bra51vV2z (1)

Obviously, this is what we’d like them to see but they just never get there.

So, rethinking the UI for a more natural UX was in order and designing the interface in such a way where it would be both impossible to miss became an obvious opportunity for improvement.

0-LwcV5SvE-TwsQAQ5

Quite literally, we had a real Dilbert-moment and “moving the button” creates a significantly-improved user experience that results in the end-user getting the data that they came for.

It seems obvious, now, but it wasn’t when we were building it and that’s the point: Product design blindness is real, even for the most experienced product teams.

I feel like I’m beating a dead horse at this point but it’s just worth stating, one more time: What seems obvious isn’t guaranteed to be obvious in the real world, with real customers, when it counts the most.

So do your live-fire tests with real folks and prepared to get served some humble pie. It doesn’t always taste sweet but it’s good for the soul (and the product).


Also shared on Medium

Find this article helpful?

This is just a small sample! Register to unlock our in-depth courses, hundreds of video courses, and a library of playbooks and articles to grow your startup fast. Let us Let us show you!

Submission confirms agreement to our Terms of Service and Privacy Policy.

Already a member? Login

No comments yet.

Register to join the discussion.

Already a member? Login

Create Free Account