273 karma · joined October 24, 2012
What's worst is when offering free trials of an analytics product and then realizing that all freemium customers engage with a dashboard once, and then dropoff forever. Event tracking and various stages of a/b testing can be dangerous because they steer engineers to local minimums in designing a product.
Having a logical understanding of every element of the dashboard is the best way to approach the design.
Great post, we need more resources like this out there.
In consumer web, the product -> strategy -> business model approach makes complete sense, but I'm unsure if it carries over to most things in B2B.
Really hope that some sort of legal precedent is set so that us geeks and developers don't have to worry about distribution if we want to invest time/energy into building apps for Glass.
The Model S seems like a car from the future. Forget the fact that it's completely electric and charges via an alien-like, glowing plug. The interior with the large, beautiful touch screen, a voice-activated system (that, contrary to Siri, actually works) coupled with access to the internet, and the gorgeous trim and accents really make the Tesla a standout.
Moreover, it's every geek's dream. You can remotely control the car with a smartphone app, monitor the car's efficiency and performance via beautiful graphs, and even have presets for charging cycles.
Best of all, the pickup is like none other (as one would imagine). Flooring it in a Tesla has a completely different meaning. Pure acceleration and no roaring engine noise.
I think it goes without saying that I'm very excited about this company.
The reason Facebook and Twitter are popular platforms are not necessarily because of their particular features or user data but because of the massive networks they represent. By tying our products to their ecosystem, you're able to leverage their technologies and data while still having a large enough addressable market. This is definitely not the case with App.net (at least so far).
I think what App.net might have that's unique is an active developer community (as opposed to a mass of average users), so perhaps it can standalone as a developer-friendly social platform, but I'm questionable as to whether anything of mass market value can come out of it, especially on the B2C side.
This 'mishap' may have similar yet increased effects because of the impressive way they handled the situation. For example, I doubt Razer would have ever imagined their story landing on the frontpage of a high-traffic site like HN, but now that it has, I (and probably hundreds or thousands of others) have gone to their site to get more info.
Really shows that with smart and agile situation-response, you can turn an unpleasant circumstance into an opportunity.
Look at Ron Johnson, for example. His genius did wonders for Apple but the same concepts failed with a different industry in his tenure with JCPenney. There's no silver bullet, and what Mayer's doing with Yahoo may have some similarities with what was done early on with Google, but in order to cement Yahoo's independent identity, she's going to have to pursue some goals that aren't identical to things she's done before.
Ending WFH is perhaps a start. The externalities (noisy lashback from media, etc.) don't help, but she's going to have to face a lot more of that in order to institute long-lasting change.
This article brings up an interesting thought: back in the '60s and '70s when most rock bands extended improvisations into their concerts (Led Zep, Hendrix, Floyd, etc.), did none of them think of recording and distributing each live show as a standalone piece like Phish? Or were they perhaps already 'mainstream enough'?
Sometimes I think entrepreneurs err a bit too much on the side of being too 'okay' with failing and pivoting (buzz word), but I'm a big believer in planning, executing, reflecting, and repeating. Sure, for some things you just have to jump straight in, but I think caution, thought, and preparation all go a long way.
Turns out, a lot of what I spent time on was learning specific UX techniques from different places that looked pretty ugly when they were all smashed together. I think it's analogous to programming (when you learn a concept, you kind of want to force it into the project you're working on, even if there is little to no relevance).
All in all, I agree with the message. Becoming a great designer takes a lot of patience, hard work, and iteration. You have to be okay with throwing entire pieces away in pursuit of something better.
I think multitasking is very possible, but has to do more with optimizing for the various senses and developing a discipline and habit around repetition (code, push, read, repeat, etc. every 30 min).