HN user

metalab

704 karma
Posts21
Comments25
View on HN
twitter.com 5y ago

What I Learned Losing $10M

metalab
9pts0
twitter.com 5y ago

Launching a Company in 5 Hours

metalab
10pts1
www.futurejobs.io 8y ago

Future Jobs

metalab
1pts0
medium.com 8y ago

Growth Shouldn't Hurt

metalab
1pts0
medium.com 9y ago

The Power of Anti-Goals

metalab
2pts0
www.youtube.com 9y ago

Charlie Munger: The Psychology of Human Misjudgement

metalab
2pts0
medium.com 9y ago

Tiny Buys Dribbble

metalab
2pts0
medium.com 9y ago

Skateboard, Bike, Car: Building Products the MetaLab Way

metalab
4pts0
medium.com 10y ago

Lazy Leadership: Why I only see my team a couple times a week

metalab
2pts0
medium.com 11y ago

We need to talk about startups

metalab
10pts0
medium.com 11y ago

Slack's $2.8 Billion Dollar Secret Sauce

metalab
33pts0
docs.google.com 11y ago

The Great Robocoin Rip-off: How We Lost $25,000 Buying a Robocoin ATM

metalab
575pts128
usepeak.com 12y ago

We just launched Peak. Quit distracting your team.

metalab
2pts0
medium.com 12y ago

How 5 minutes of work made us $50,000

metalab
1pts1
medium.com 12y ago

MetaLab is selling Ballpark

metalab
4pts1
www.getflow.com 13y ago

Introducing: The All-New Flow iPhone App

metalab
1pts0
www.getflow.com 15y ago

Flow changes pricing, makes it free to collaborate with anyone

metalab
18pts0
blog.metalabdesign.com 15y ago

What we've learned about hiring

metalab
8pts1
blog.metalabdesign.com 16y ago

The Fallacy of Hoop Jumping

metalab
1pts0
blogs.zappos.com 16y ago

Zappos responds to Andrew Wilkinson's "You're Killing Me Zappos" letter

metalab
32pts13
metalabdesign.com 16y ago

You're Killing Me, Zappos

metalab
67pts95
[dead] 9 years ago

Ack! Don't think there's any way to edit, either.

Hey Steve,

We view this as a business within a business. Nobody from the Flow development team is being distracted with Concierge, it's just another part of the MetaLab umbrella.

Also, I find it weird that you think us "focusing on monetization" is a bad thing. What's wrong with having a sustainable business?

-Andrew

My Comment to Joshua:

I appreciate what you're saying here, but I think you're mischaracterizing the point of both of our articles. Neither of us proposed our mockups as comprehensive redesigns or attempted to address anything past the basic visuals. I wanted to buy shoes, and I found it to be a really frustrating experience, so I said something.

If the door to a retail store is hard to open and you complain about it, does it make you an arrogant prick for failing to think through all the potential reasons for the problem? Maybe the company handyman only comes every two weeks. Maybe there's a mountain of paperwork required before any repairs can be made. Maybe the staff needs approval from management. Does that make your frustration with the door situation any less relevant? It definitely makes you empathize with the staff, and speaks volumes about the company's ineffective management, but that doesn't change the fact that the door is really hard to open, and this is a problem for you as well as other customers. Understanding the context is important, but it doesn't make our critiques any less relevant.

You argue that, "it’s easy to 'design' when you’re unencumbered by things like metrics, creative direction, business acumen, sales experience, actual functionality". Of course, but think about all the companies that manage to get it right. Huge, lumbering corporations like Amazon, JetBlue, and Virgin all manage to pull off great user experience despite facing the same challenges. Why shouldn't Zappos and American Airlines be held to the same standard?

I found the Zappos website insanely frustrating to use, so I spent an evening identifying some of the problems I spotted and added a mockup to clarify. Yes, I was a little inflammatory, but the overarching message was a positive one. I wasn't trying to tell them how to sell shoes or reinvent their business - my article was intended to show how a few simple changes overtop of the existing website could help make it easier to use. Blurry images have nothing to do with metrics, business acumen, or sales experience. If this helped push them towards making their website easier to use in any way, then I'm happy.

I feel awful for any designer who has to deal with Dilbertian management and bureaucracy, and I agree with the previous commenter - our frustration should have been primarily directed at the management team at either company. That still doesn't change the fact that there are designers responsible for crafting the pixels, and the pixels show a general lack of care. This might be due to the culture of the company, poor direction, or a myriad of other factors, but it doesn't make the work itself any less sloppy.

I'll be the first to admit that I'm a brash 23-year-old, but I'd rather say something and risk looking like an asshole than continue to patronize a company that doesn't care about their customer experience.

-Andrew

So when you glance at your car dashboard do you look for "DEFROST" or "RADIO POWER"? No, you look for cues based on positioning, size, and the icon on the button.

No, you're right. We shouldn't push the boundaries of what we can do on the web, we should always stick to the browser defaults.

Any competent front-end designer could easily figure out how to code this.

Hey Max,

I'm Andrew, the guy who did it. The key thing that I want to drive home is that their execution stinks. I figure they know how to sell their product - they did $1 billion in sales last year - but the site itself is incredibly sloppy.

-Andrew

This is Andrew from MetaLab. I just wanted to say thanks for all the compliments on the design. I hope that you guys will take it for a spin and let us know what you think.

Quoted from cominatchu: "The 'under 10k' price tag is misleading because it does not include the opportunity cost of the web designers time. In other words, one has to calculate (the hours spent by Metalab web designers * their normal hourly rate) and add this to 10k to arrive at a more accurate cost for building this site."

Yes, we really did build it for less than $10k. Our key expenses were: Rails development (1 developer a few hours a week), a SliceHost server, and some custom icons we hired out. We're planning to break it down in more detail on our blog in the next little while, but I'd like to debunk this a bit here. You're absolutely right about the cost being higher if you consider what it would normally cost at a full consulting rate, but I feel like that's kind of fallacious logic:

If you learnt how to woodwork, built a bookshelf, then told your friends that it cost you $15 (the price of the wood and a couple of screws), they aren't going to argue that the true cost was $500 (the hours spent learning woodworking or a carpenter's rate).

If a founder who was an incredible programmer paid himself $1,000/month during the early months of his startup, would you say that his time really cost the company $15,000 (what he would have charged at a consulting rate)?

The point isn't that someone with no technical skills can do this for 10k (after all, this is Hacker News, and I assume most of you are highly skilled in the field), we're just pointing out that we managed to create a business by pulling a few extra hours a week over 6 months. We didn't have to quit our day jobs, move to the valley, or build a board of advisors - we just went ahead and built it. This isn't to say that it's an especially complex app or that it is some sort of technical feat, just that a little bit of money went a long way.

I don't think taking funding is always bad or anything, especially small seed funding like YC. Sometimes advantageous ideas need money to make them happen. The point is that most of you already have many of the skills required to build things, so funding really shouldn't be a barrier to entry. If your idea requires more money than you have, boil it down to the bare minimum and build it within your budget. We could easily have decided that we wanted to build the best invoicing app ever, figured out that invoicing was a 1.3 kagillion dollar industry, secured some funding, built up the stakes, then gone crazy with features. We could have convinced ourselves that we needed to close down our consulting business, hire a full-time Rails developer, and move in together. Instead we took a simple idea that we felt wasn't being done right, boiled it down to its core, then built it when we had the time.

I think the key differentiation is the fact that Ballpark is built for teams. This might not resonate with freelancers (who might just use it because it works well and looks pretty), but, in most small businesses, more than one person is usually involved in the process. For example, we run a design firm (www.metalabdesign.com), and while I don't personally send out estimates or invoices, I can easily keep track of incoming payments via the dashboard, give sign off and comment, see what the numbers for the month were, etc.

Regarding PayPal: Nobody is required to use PayPal - it's totally optional. We're definitely planning on looking into offering payment gateway solutions, but at this point we are focused on polishing the core functionality and adding some really cool new features that will help differentiate us from the pack.