The challenge with building products that people really love is identifying real behavior, not fictitious, manufactured, or fabricated behavior.
From another angle, it’s so easy to deceive ourselves into believing that what we are building really is the problem that most people are having when it’s actually not. I think many product builders and engineers are susceptible to these fallacies; I know that I am.
As I have done for the last few months (June and July) I wanted to continue to share a few more updated screenshots of what I’m putting together so you all can continue to get a sense of the momentum that’s being built behind-the-scenes.
And as I survey even the last few months it’s fascinating to review the changes myself as it becomes even more obvious how much work has been done and how much more exciting the project is becoming.
I’m not a super-fan of Facebook but the service and technology is impossible to ignore. It’s everywhere and it’s a daily (if not hourly) tool for many of the closest people in my life, like my wife.
For all that I don’t like about it I am reasonable to understand and appreciate all of the value that it does create for so many people, organizations, and businesses.
LinkedIn is almost impossible to ignore – it’s so big and so widely used in every circle, market, and industry that it’s essentially everywhere. And even more so with LinkedIn being acquired by Microsoft for an ungodly amount ($26B) it’s gotten as much attention that any company could ever ask (or pay) for.
But if you’re a technical (i.e. software engineer) person like me then you might have a bit of a love-hate relationship with LinkedIn and every time you see it you may even cringe a little (at least on the inside). It’s not that the network is completely without value, it’s just that it’s not all that entirely useful for software developers, engineers, and the more technically-inclined.
Every team and every project and every company, eventually, has to decide how to best represent and communicate their work to the world. Typically this is housed under the moniker of a “logo” but there’s something deep within my soul that is pretty averse to that word.
Perhaps it’s because I’ve seen so many terrible ones in my time, especially with the fly-by-night startups that popup (and then disappear) and that generally follow the soup-du-jour design mechanics and whatever is the culturally relevant design zeitgeist.
Keeping form with the new cadence of sharing screenshots of the project (a’la June Prototype Screenshots) I wanted to give you a snapshot of the next few iterations.
But, unlike last month, I wanted to give a bit more context around these screenshots so I can get a bit more exact feedback from our faithful readers and subscribers.
So, take a moment and dream with me for a bit, will you?
I took a week off from posting last week and that’s because I was on vacation – go figure.
But, if you’re like me, I got pretty angsty and the break just gave me more time to think through building a compelling and useful product for software developers and teams.
And, as I’ve mentioned before, I want to get as much feedback as humanly possible so I’ve put together the first (of many) quick surveys that I could use your help on. Mind giving me a few minutes of your time?