Today, I participated in the Juneteeneth 4.0 Celebration that was hosted by OHUB, ThePlug, and Living Cities and led by Rodney Sampson. In addition to being part of a panel, I made several commitments as part of the #RacialEquityEcosystemPledge. Here’s the fact sheet released by OHUB today.
I’ve agreed to:
- Do a monthly podcast called Equity.District with Rodney on racial equity in entrepreneurial ecosystems and other issues around racial equity in entrepreneurship.
- Help organize and co-host a Racial Equity conference inclusive of Rodney’s network, my network, and anyone else who wants to participate.
- Make a meaningful financial contribution to the OHUB Foundation from the Anchor Point Foundation. If you are able, I encourage you to donate as well.
- Make a meaningful financial contribution to at least two more Black-led ecosystem building organizations recommended by OHUB.
- Work with Rodney and the OHUB team on an ongoing campaign to raise money for Black ecosystem builders, funds, and founders.
The entire event is below. There’s a lot of awesome stuff in it.
In addition to the awesomeness, I made a mistake. Right after I spoke, I got a text from a White friend who is an entrepreneur I’ve invested in who watched the event live.
I immediately sent Rodney an email under the heading “I apologize for the microaggression.”
Apparently in my closing comments I said that you were “articulate” (I wasn’t aware that I used the word.) While I hadn’t seen this NY Times article I know that “articulate” is viewed as a microaggression.
So, regardless of whether it was intended, or you heard it, or anything else, I want to simply apologize.
You are incredible. You inspire me.
Rodney quickly responded:
Thanks for this. Tell your friend they are right. Apology accepted. However, in this case, I know that you meant “vocal in my leadership”. 🙂
We’ve got a lot of work to do. I’m up for it.
When I make a mistake, I try to own it, apologize, and learn from it. I’m far from perfect here, but Rodney’s response, by acknowledging my mistaking, quickly accepting my apology, and getting back to work with me motivates me even more to work with him!
I participated in a one hour Crowdcast yesterday with Techstars and 43 North about How to Build a Successful Startup Ecosystem in your City. Some of the thoughts from my upcoming book The Startup Community Way are in the hour, along with a bunch of things Techstars is doing around this initiative.powered by Crowdcast
If you are in a city somewhere in the world working on developing your Startup Community and are interested in learning about the new Techstars Startup Ecosystem Development product, drop me an email.
Recently my partners and I spent some time discussing three of our recent investments – Spanning, Yesware, and Attachments – which are each applications built on top of Google Apps. Specifically, they are built for Google Apps and available in the Google Apps Marketplace or the Chrome Web Store.
Each company is going after something very different. Spanning is all about cloud backup. Attachments is all about getting control of your email attachments. And Yesware is “email for salespeople.” However, they have one very significant thing in common – they are all deeply integrated into Google Apps. In our thematic definition, they are in the Protocol theme.
The Google Apps ecosystem snuck up on us. We have all been hardcore Google Apps users for the past year and are psyched and amazed about all the easy integration points – both into the browser and the various Google Apps. In the past, we would have been more focused on “email as a datastore”, which would have resulted in multiple platforms, including of course Outlook / Exchange and IMAP. However, the pace of iteration on top of Google Apps, and the ease of integration is spectacular when compared to other platforms.
Notably, when the choice of building for Outlook vs. Google Apps comes up, many people who I know comes down strongly on the side of building for Google Apps. Their mindshare for cloud based business apps far outpaces Microsoft. A decade ago, Microsoft made a huge push with Visual Basic for Applications and the idea of “Office as a Platform” and – while plenty of interesting tech was built, something happened along the way and the notion of Office as a Platform lost a lot of visibility.
Theoretically Microsoft’s huge installed base of Outlook / Exchange users should drive real ISV integration interest, but the friction associated with working with Microsoft seems to mute the benefit. And – if you’ve ever built and tried to deploy an enterprise wide (say – 100,000, or even 1,000 seat) Outlook plug-in – well, I feel your pain. It’s possible that with Office 365, Microsoft will re-energize focus on Office as a Platform, but I haven’t seen much yet.
While Google has been building this all very quietly, I’m extremely impressed with what they’ve done. Companies like Yesware are able to release a new version of their app to all users on a weekly basis. For an early stage company that is deep in iterating on product features with its customers, this is a huge advantage. And it massively simplifies the technology complexity to chose one platform, focus all your energy on it, and then roll out other platforms after you’ve figured out the core of your product.
I expect to see versions of each of these products expand to work with Microsoft – and other – ecosystems. But for now, the companies are all doubled-down on Google Apps. And I find that very interesting.