There are four signs your idea has legs:People pay you money: Several people start to pay for your product, ideally people you don’t have a direct connection toContinued usage: People continue to use your prototype product, even if it’s hackyStrong emotion: You’re hearing hatred for the incumbents (i.e. pain) or a deep and strong emotional reaction to your idea (i.e. pull)Cold inbound interest: You’re seeing cold inbound interest in your product

Every prosumer collaboration product, including Figma, Notion, Coda, Airtable, Miro, and Slack, spent three to four years wandering in the dark until they stumbled on something that clicked.

When I first started meeting founders, I wanted to help with anything and everything. Unfortunately, that's neither realistic or possible. For example, I have many responsibilities at my day job that must come first. Over time, I have honed in my pitch to be explicit about how I can and can't help. See the notes above about ways to be helpful, and find your own unique combination of value to bring to the table.

My contract typically looks like this: We agree to meet ~X hours per quarter/half/year Multiply by Y contracting rate Y ⨉ X = some dollar amount Z Divide Z by the startup's latest price per share to arrive at a number of advisor shares to grant

Be founder-friendly! It's a big deal and a lot of paperwork to get a smaller check or advisor on the cap table (unless they already have a lot of operational infrastructure in place) – this usually means being relaxed about the commitment paperwork or helping out pro-bono for the first few hours while they work through the logistics.

Finding founders you work well with can be a numbers game; you won't be sure what you like doing until you've met a handful of founders, done several advisory meetings, and poked at different types of problems. It's okay to dip your toe and warm up to the process before committing a lot of time and energy to this. I started slow, and have been steadily sharpening my own intuition about what kinds of products and founders get me excited, and where I can add unique value

John Watson looks down at his screen, and we see the message he’s reading on our screen as well. Now, we’re used to seeing extradiegetic text appear on screen with the characters: titles like “Three Years Earlier” or “Lisbon” serve to orient us in a scene. Those titles even can help set the tone of the narrative - think of the snarky humor of the character introduction chyrons on Burn Notice. But this is different: this is capturing the viewer’s screen as part of the narrative itself [1] It’s a remarkably elegant solution from director Paul McGuigan. And it works because we, the viewing audience, have been trained to understand it by the last several years of service-driven, multi-platform, multi-screen applications.

The connection between Sherlock’s intellect and a computer’s becomes more explicit in one of my favorite scenes, later in the episode. Sherlock is called to the scene of the murder from which the episode takes its title.[3] We watch him process the clues from the scene and as he takes them in, that same titling style appears, now employed in a more conventional-seeming expositional mode

But then the shot reverses, and it’s not quite so conventional after all. The titling isn’t just what Sherlock is understanding, it’s what he’s seeing. In the same way that text-message titling can take over our screens because whatever we’re watching TV on is just another screen in a multiplatform computing system, this scene tells us that Sherlock views the whole world through the head-up display of his own genius.

However the most controversial step I’ll be taking is removing a few of the functions. This usually gets pushback from most product managers as for them “features == sales”. The problem with this thinking is that it assumes a) all features are used and b) extra features has no negative impact.