Processing Final: Twitter DataVis Application
I’m finishing up my class in computational media at NYU’s ITP program. I have to say, it’s been an awesome experience and it’s gotten me excited to learn Javascript as a next challenge. I’ll probably start at Code Academy and work my way into more advanced topics and lessons.
A few takeaways that I’ve gotten from the class:
- The web is an awesome place of infinite possibilities.
- Despite the current movement of learning everything for free online, having weekly assignments that I had to present in front of the class kept me on track and learning. ITP also offered an environment that was conducive to creating, a community that was phenomenally supportive and a professor who kept the conversation moving forward. I think educational solutions like Kahn Academy are helping to structure the online learning process, but nothing beats having to show up, sit down, turn your phone off and learn. I’m a huge believer in traditional classroom work and, while I think the Internet can definitely enhance the current model, it will never replace it.
- Basic coding skills should be an absolute must for anyone who hopes to found a web-startup. You don’t have to build your own site, but you need to understand the process. The same is true for developers learning business development and strategy. For example, I am better at excel models because of this class, and I can better communicate with technical teams. I plan to continue my investment in programming and I expect it to pay dividends in the future.
For my final we had to build something and present it. I wanted to build something that helped me visualize data in a new way, and based on my experience in social I wanted to play around with the Twitter API. So, I built an application that allows a user to put in a Twitter handle and then receive a sorted list of words used to @reply that handle, sorted by frequency. Here’s a walkthrough of the application using Charlie O’Donnell’s handle (@ceonyc):
Here’s another visualization of @replies to Gary Vaynerchuck:
As you can see, it needs a bunch of work before it presents real value. On the upside, I was able to dynamically access the Twitter API, pull and sort data, and display it. I’m looking forward to continuing to build on what I started at ITP!
Joining the team at K2
I’m very excited to announce that I’ll be joining the team at K2 Media Labs on a full-time basis in the coming weeks. K2 is an early stage private equity fund that invests in startups focused on the connected consumer.
The Company is a bit of a hybrid, in that it makes early-stage investments and also incubates companies in-house. My day-to-day job will include working with CEO Daniel Klaus and Chairman Kevin Wendle on due diligence, planning and implementing strategies around new startup investments, as well as working in a supporting role with the current portfolio companies. On the investing side I hope to build on what I’ve learned from Joe, Nikhil and the rest of the team at Softbank Capital, and from my time learning from Jerry Neumann at NEU VC. From an operations perspective, I’m hoping my time in business development, social marketing, product development, and my background in media & entertainment has given me a foundation of experience to be a value add to the incredibly talented group of entrepreneurs at K2. I’ve spent lots of time selling services to businesses, and building in mobile and on Facebook. While I still have limited knowledge and tons to learn, I hope that the skill set and network that I’ve built will be helpful to the entrepreneurs I will work with.
Aside from the in-house team at K2 , the fund has a phenomenal group of investors and advisors. Overall, I could not be more excited by the opportunity to learn from this team. There aren’t many opportunities to work on both the investment and operations sides of early stage businesses, so I feel incredibly lucky to be here and I can’t wait to hit the ground running.
I plan to invest more time and energy into this blog, posting more often on topics covering startup operations and early stage investing. If you ever want to connect, you can find me at christian[at]k2medialabs.com, or on twitter @nycsteady.
Learning Processing….and So Much More
When you finish up at Stern you’re allowed to take a ‘free’ class (I hesitate to say it’s free because you’ve already made a tremendous investment in the MBA, but you don’t pay specifically for the credits to one class). I took advantage of our ability to go outside of Stern and I signed up for the Introduction to Computational Media Course at the Interactive Telecommunications Program school in Tisch. To say it’s been enriching to spend Tuesday evenings in the ITP school would be an understatement. Learning new skills in a creative environment has really helped me in all aspects of my work. I don’t think that I could have identified what I would gain from being in the class before taking it, but looking back it’s very clear to me that this has been a immensely valuable experience.
There’s a mentality that I think a lot of upcoming business executives accept that is career-limiting. I believe that there’s an over-emphasis in our graduate level schools on gaining depth within a functional area, or only focusing on training and coursework that directly relates to your career path. While I agree that’s the primary purpose of a graduate degree, I think a lot of value can be unlocked by learning completely new things that at first glance appear unrelated to your current skill set and career goals, especially courses that are creative in nature. Intro to Comp Media has been that experience for me. For everyone outside of an academic program, I’d encourage you to check out a skillshare class.
Back to my rudimentary coding skills. Processing is a computer language that’s primarily used by visual artists. For our last assignment, we had to create a ‘chance composition’ using the object-oriented approach to development. I made a pretty ridiculous looking space ship that meanders it’s way through some random stars. Overall, nothing to write home about. However, re-learning some of the fundamentals of coding has really helped me communicate with the real developers that I work with on a daily basis, and it’s been a great experience to get outside of my comfort zone.
Connecting the Dots
A couple weeks ago when Steve Jobs announced his retirement, I did a little research to try to sum up my takeaways from his success. One of his stories was about taking a calligraphy class in college, and how that class gave him enough knowledge in the subject to create font sets in the first Apple products (which were later copied by Microsoft for Word). At the time when he took that class, he had no idea how or why that class would be useful. Only when Jobs looked backwards he was able to connect the dots.
Jobs’ belief that ‘you can only connect the dots looking backwards’ struck me when I heard it, probably for the same reasons that it resonates with all of us. We all like to believe that everything we do has a deeper meaning, that every experience is building to a purpose and therefore no time and energy is ever truly wasted. I like to think that way on a personal level, but I also think this can be applied to entrepreneurship and product development.
Businesses are products of several environmental inputs: the entrepreneurs behind them, the industry that they serve, the macro-economy, the trends at the time, customer needs, etc. I believe many budding entrepreneurs, especially in the MBA communities, spend a lot of time thinking about these inputs and putting them into their business plans. I think this is smart work to do. You want to make sure that the market exists and is big enough to make your effort worthwhile. With that said, there’s a limit to the value of doing this exercise and very few people seem capable or willing to take the next step, which I believe is creating a minimum viable product for early adopters to see and give you feedback on. There’s a limited amount of planning that can be done in the startup phase, and much of entrepreneurship is based on experience and a ‘hunch’ that there’s some white space where you’re attacking. 5% of your learning will happen in the business planning process, 95% of it will happen when you start building.
In software, this process is called iterative development, or the agile method. Here’s a quote from the wiki page:
The basic idea behind the agile method is to develop a system through repeated cycles (iterative) and in smaller portions at a time (incremental), allowing software developers to take advantage of what was learned during development of earlier parts or versions of the system. Learning comes from both the development and use of the system, where possible key steps in the process start with a simple implementation of a subset of the software requirements and iteratively enhance the evolving versions until the full system is implemented. At each iteration, design modifications are made and new functional capabilities are added.
Creating a feedback loop that includes early adopters will allow you test many of the assumptions that you’ve made in your business plan. It also allows you make changes to your business model based on what you’ve learned. When we built Crowdstream, we weren’t really sure what was going to resonate with artist managers or with fans. It took four iterations to get it closer to right and we’re still iterating. The product that we have today is vastly different from the product that we originally designed, but looking back its easy to connect the dots.
Using Narratives
Having worked in both business development and production, I feel like I’ve learned a lot about people. The importance of people in every job function can’t be over stated. It doesn’t really matter if you’re selling enterprise software, building a product or making a trade, you need to think about the person on the other side. People are the consistent thread no matter what desk you’re sitting at.
I had an experience the other day responding to a request for a technical document around a piece of software. The request was to write out a summary of something technical to an audience that was mostly non-technical, and then to discuss it at a meeting. As an experiment, instead of writing out a summary, describing the environment that the software lives in, and listing the functional components of the software, I wrote out a narrative. The narrative was a story about a person who I considered to be a typical user, going through a typical experience needing and using the software. I named the user John and told a story about him using the software: how he found it, why he wanted to use it, what he did when he started using it, how he interacted with it and what brought him back. It was highly effective and I think everyone appreciated the approach.
There are a few reasons that I think narratives rock:
- Narratives are familiar to everyone: When was life better than when you were getting stories read to you as a kid? When you start telling a story, your audience naturally falls into a more relaxed state. Everyone understands stories because they’re relatable. There’s no need to try to ‘keep up with the technical details’, so there’s very little anxiety about the complicated topic.
- They are visual: People love visuals. If you don’t have a designer nearby, a narrative is your next-best asset. Good visuals create memories by eliciting emotional connections. If your story explains a user and then the use case, everyone has a person in their head walking through a process. It helps complete the picture for the listener.
- They force the storyteller to think about use case: Storytelling can improve your product or idea. By creating stories to present, the storyteller is forced to think from a user or customer’s perspective. This sounds overly simplistic, but I found it to be incredibly productive and a creative way to understand the software.
- They offer a platform for deeper conversations: To me, this was the most interesting benfit. After the story ended, all of the followup questions came in the form of questions about the narrative’s main character. Instead of ‘How does X do Y?’, the question was “What happens if John…?” This made the followup creative and productive, and kept everyone thinking through the process using visuals. It was the most productive product overview conversation I’ve had in a long time.
Five Things I Learned From Steve Jobs
On the heels of Steve Jobs’ announcement that he’s retiring from Apple (okay, I’m a little late for the heels, but there was a pseudo-hurricane), I thought I’d reflect on the top five things I take from the single greatest entrepreneur in the history of consumer technology.
1. Know Your Customer: When you start a business or step into an existing enterprise, it becomes easy to focus on operational or strategic issues. It seems to me that having an almost religious obsession with the customer experience is the best bet you can make on where to expend your limited resources.
- Jobs understood that his customers want their computing experiences to be seamless, and that they’re not interested in working through compatibility issues between manufacturers and software developers. This understanding has allowed Apple to enjoy premium prices in a commoditized market for decades.
- Remember what everyone was saying about the iPad before it was released? Those who doubted the market demand for tablets spent months trying to catch up after the iPad’s initial success, only to release products that felt like cheap knockoffs months too late.
- An example from another successful tech company: when Google’s Page Rank algorithm was first created, the company’s first strategy was to license its search technology to existing search engine websites. The issue, as the story is told, is that Google’s technology was too fast and, if users left the search sites too quickly it would hurt display advertising revenues. Of course, users wanted fast search and that became the model that eventually won out.
There are a million other great examples of this approach paying off in big ways. Know your customer and understand their needs.
2. You Cannot Replicate Culture: One of the reasons that Apple’s stock didn’t take a big hit following Jobs’ announcement is that investors have bought into the idea that not much is going to change at Apple. The reason that nothing is going to change is because their culture is fully-baked. One of the advantages of being a first-mover is that you can spend more time developing your product than your fast followers can. Apple is a design firm first and that DNA shows in everything they release. That type of culture is almost impossible to replicate; it will give Apple a competitive advantage for years to come.
3. Do What You Love / Follow Intuition: Check out this quote from Jean-Louis Gassee. I think that doing what you love means accepting that fact that a lot of people will be sure that you’re doing it wrong. I’m finishing a behavioral finance class with a professor who spent all of 1999 shorting tech stocks. He said that he became physically ill every night as the market continued to rise– that he didn’t sleep for a year. But his intuition was right: doubling your market cap every month is unsustainable and it doesn’t make any sense. When I think about Steve Jobs, I think about how difficult it must have been to get fired from the company that you founded. The idea that ‘you’re doing it wrong’ can affect your decision-making if you let it and the contagion can eat you up, even if you were right in the first place. Doing what you truly love helps you mitigate those downsides and it helps you trust your intuitions.
4. Think Big and Small: Apple’s products are a collection of seamlessly integrated UX details. While Apple changed the world in a lot of ways, most of what they accomplished came through creating superior user experiences– the details. For example, while strategy played a roll with the iPod (iTunes music store), everyone bought an iPod because it was slick and it made digital music fun. I think that the importance of UX / design cannot be overstated, especially in web and mobile products.
5. Fail: As Jobs himself said in his commencement address at Stanford, ”you can only connect the dots looking backwards”. Creating and ideating are the only tools you have to build something great. Failing is, for most people, an inevitable outcome for the majority of your attempts. Don’t think Apple has had any failures? Check out these five epic Apple fails (granted, not all of them occurred on Steve Jobs’ watch). Aside from these more esoteric failures, think about the battle for industry standard when the PC first came out. Jobs and Apple lost in a glorious fashion to the Wintel model. As a result of that failure, Jobs learned the importance of available software applications on any system– which is why we have the App Store today and why the iPhone and iPad have been such a huge success. Early failures + great leaders = future successes.













