Operating a fully-remote founding team: Learnings

Even before this forced wave of work-from-home, I consciously built Workomo as a fully-remote, distributed US-India team from scratch, viewing it as a key competitive advantage. In fact, even today, most of my team have never met each other in-person :). Here’s my learning from operating a founding team of ‘strangers’:

  1. Reinforce — remote teams don’t have the luxury of office space, day-long huddles, and offsites to maintain focus and motivation. Founders need to reinforce the “Mission” 10x more than usual — why did we start this company? Why should we exist? Why did you join in the first place?
  2. Plan — this becomes especially crucial as people aren’t under the same roof. Each person having razor-sharp clarity on what the team needs to achieve and in what time frame, is super-important. The Plan needs to include Monthly KPIs (make it Quarterly for scaled companies), translated to Weekly Tasks. More on this next.
  3. Break it down — tracking, measuring & course-correcting becomes really challenging when people can’t be physically pulled into review sessions. I have found breaking down KPIs into really small, byte-sized tasks per member per week to be incredibly helpful. Small is beautiful!
  4. Communicate — remote teams need even more rigorous and frequent KPI communication. Both for Monthly KPIs and Weekly Tasks, ideally schedule a) kick-off session, 2) mid-period review and 3) end-review+retrospective. Just to re-emphasize, do these weekly even for tactical execution tracks.
  5. Clarify — remote teams have a big challenge in people not being able to walk up to their leaders/peers and ask clarifying questions. It’s hard anyway to ask questions in digital meetings, & time zone differences make it worse. Founders need to proactively clarify the “Why” behind each execution track, perhaps even multiple times especially during a crunch week where several priorities are getting worked on in parallel. Repetition of the “Why” is never enough. Clarifications are never enough.
  6. Cadence — set a cadence (daily/ weekly, as applicable) for huddles, standups, town halls, and 1:1s. Ensure they are respected and taken seriously. Founders need to personally drive discipline around attendance, starting on time, tight agendas & focused discussions.
  7. Empathy — effectiveness of remote WFH is deeply impacted by the personal environments of employees. Founders should make themselves aware of these surroundings, so the team’s operating style & cadence is empathetic to their situations. For instance, which team members have kids, and of what age? Do people have space to make a home office? Do the engineers prefer to code at night or during the day? Accounting for these elements can go a long way in driving both productivity and a caring environment.
  8. Observe — pay attention to everyone’s energy on the Zoom call. Who seems to be on top of their game? Whose shoulders are drooping? Who seems low on energy? Is anyone not feeling well? Follow-up accordingly — perhaps a quick 1:1 pep-talk. Some love. Some advice. Bit extra care!
  9. Mix it up — internal digital meetings with the same agenda every week can quickly get boring. Try mixing it up by say, together watching a YC video on getting first 1,000 users, getting a guest speaker for a product huddle or asking a team member to present something cool!
  10. Involve — unlike in-person, it’s really hard to observe body language, transmit energy & get everyone onboard in remote work. Extra-effort is needed towards getting everyone truly involved in digital meetings, energizing them, and making them partners in decisions. Some good ways to do this: a) function-specific huddles where members executing that function lead, manage and participate, and b) every member should routinely “present” their work to the entire team, even if it’s for 10 mins. Provide everyone with opportunities to earn & share respect.
  11. Celebrate — a big part of co-located teams is going out to celebrate mini-wins. Happy hours, brown bag lunches, etc. Like any solid sports team, celebrating wins together is important for creating bonds & reinforcing a shared mission. Don’t shy away from doing it even over video!
  12. Humor — it’s hard to have workplace banter when everyone is glued to a screen. Digital meetings anyway tend to become intense due to maintaining constant eye contact. So, while accomplishing work goals is important, don’t forget to have a few silly laughs with the team.

Ultimately, operating an effective & happy remote team involves going the extra mile to create a strong human quotient. Software like Zoom, Meet & Slack can only enable efficiency. In the end, it’s all about emotions, motivations & bonding over a common cause. Keep it real!

PS: Here’s what our team has been building over the last few months — Workomo is a Chrome extension that shows you everything important about people, just before you meet, right inside the browser. We are already in private beta — do check us out and sign-up to request access. #peopleinsights

LinkedIn Search is broken… and another Workomo use case

Workomo gives you actionable context on the people who truly matter!

I love the days when I organically encounter a solid use-case for Workomo (“Relationships Intelligence for Power Professionals”). Today, I was having a Whatsapp discussion with a good friend, who is also an ex-founder (I had invested in her last startup). As part of another early stage startup now, she is incubating a new micro-lending product in India, and wanted to check with me whether I could intro her to someone working in the space.

Now, being an active startup ecosystem stakeholder & connector, I really want to help her. Given my Alibaba/ Ant Financial/ Paytm background, finding someone with “lending” experience/ expertise should be fairly easy for me. Except it’s not. Barring 1–2 people who are top-of-mind for me right now, it’s extremely hard for me to know who among the people I already know/ have shared history or context with, will be relevant for a potential warm intro. I tried to do a LinkedIn search with keywords like “lending” and “fintech”, but got crappy results wherein I don’t even know any of the people in the first page search results. PS: I don’t even know why I am being shown “company results for fintech”, which btw, are also beyond crappy.

Actual search results page from my LinkedIn profile
Actual search results page from my LinkedIn profile

Compare this with how Workomo helped me solve for this pain point. Currently, the product is in early private beta stage, wherein for me personally, I am tracking about ~160 of my top-priority professional relationships. These are ex-colleagues, customers, batch-mates, investors etc. — essentially, people with whom I already have a shared history, context, modicum of trust and double opt-in.

I went into Workomo, clicked on the “Relationships” tab and ran a search with the keywords “fintech” and “lending” (at an MVP stage, these are few of the many manual tags I have been using to curate my relationships). I got 9 and 2 search results respectively, comprising founders, VCs and operators, all of whom I know well-enough to ping and check.

Actual Workomo screenshots
Actual Workomo screenshots

This is what Workomo is doing at such an early MVP stage. We are in process of building an AI-powered “context engine” that will ingest hundreds of signals and “auto-tag” your top-priority relationships. Imagine your own, personalized, contextual “LinkedIn Search”, working in the way it should, helping you search & curate a high-quality dataset comprising only of relationships that truly matter to you!

Intrigued? Sign-up to request a private beta invite today. We will be delighted to partner with you as an early adopter, in building Workomo out.

What can you learn from Superhuman’s product-market fit playbook?

[Update on Feb 26, 2020] Rahul Vohra has recently published a super cool interactive tool so people can use Superhuman’s PMF framework for themselves. Check it out here.

As I am building-out my startup Workomo (helping knowledge professionals supercharge their professional relationships), have already used so many ideas from this method. My detailed take in this article below.

One of the best articles I have read in recent times is How Superhuman Built an Engine to Find Product/Market Fit by Founder-CEO Rahul Vohra. As I have been building Workomo over last few months, the overarching goal for me as a founder continues to be — how to achieve PMF while minimizing time spent & capital utilized? Having read Marc Andreessen’s legendary essay on defining PMF (“Product/market fit means being in a good market with a product that can satisfy that market”), as well as all YC stuff on the topic, I had developed a playbook for it in my head:

  1. Make something people want
  2. Be lean (product development approach + capital)
  3. Launch simple & quick
  4. Organic demand generation (networks + communities + word-of-mouth)
  5. Identify early adopter persona
  6. Iterate based on their feedback
  7. Eventually “delight” & consequently, “retain” early adopters
  8. Test how much will they pay
  9. Get to 10, then 100, then 1000 “retained & paying” users
  10. Scale-up from there

As a founder dealing with so many unknowns, one is always looking for actionable insights, more than theoretical advice. Reading about the Superhuman experience just gave me so much execution color on this PMF playbook. I think every founder (and even venture investor!) should absorb these valuable insights so sharing my notes & key takeaways from this article.

Summary of Superhuman’s deconstructed product-market fit playbook:

#1 PMF takes time

#2 Quantify PMF via a single, North Star metric

#3 Structure & execute the user survey process well

#4 Create a highly detailed user persona of the High-Expectation Customer

#5 Focus on delighting a small number of users first

#6 To convert users that are “one-the-fence”, focus on what your fanatic users love the most about your product

#7 Two-pronged product planning approach to move towards PMF — focus on core strengths + address core concerns

#8 For feature prioritization, stack-rank to get to “lowest cost, highest impact” features

#9 Rinse, and repeat…

Let’s dive into these elements in detail.

  1. PMF takes time

Superhuman team first started coding in 2015 and it’s only in last few months that they have attained a critical mass of vocal adopters, who are in-turn, making the product viral. A reality check for all of us in terms of how much time it truly takes to make something people want, and therefore, the value of patience in founding teams (& investors).

2. Quantify PMF via a single, North Star metric

A big challenge in working towards PMF is that it appears “fluffy”, especially when as a founder, you are trying to align your engineering & product teams around it and even more so, when you are trying to set an actionable & trackable process roadmap for it.

The best way recommended is to quantify PMF in terms of a North Star “leading” metric.

The Superhuman team used the following leading metric to quantify PMF (originally articulated by Sean Ellis in this article) — just ask users “how would you feel if you could no longer use the product?” and measure the percent who answer “very disappointed”. The threshold for having achieved PMF is 40%.

3. Structure & execute the user survey process well

Perhaps the most refreshing info in this article are the details Rahul shares about the user survey process they ran, to gather data on the PMF North Star metric:

a) Identify users who used the product at least twice in the last two weeks

b) Exact survey that was sent out given below (just the minimum number of critical questions were included, amazingly succinct yet effective!)

PS: I loved the 2nd question, where existing users are prompted in a way, to describe their own persona. Makes it so much easier to clearly identify who your real early adopters are. More on this later.

c) Classified the responses into 3 buckets — 1) Very Disappointed, 2) Somewhat Disappointed, and 3) Not Disappointed.

d) Assigned a persona to each bucket, to identify the “Very Disappointed” user persona (the actual early adopter)

To me, this entire user survey process is the core of the PMF playbook, and something I found exceptionally insightful.

As has been my learning doing Workomo’s customer development process, at this really early stage of the company, the number of respondents matter much less than you think. Some data is better than no data, especially coming from actual, retained users. Superhuman mentions anything more than 40 responses as an adequate sample size (at the time, their universal sample set was only ~100–200 users that could be polled!!)

4. Create a highly detailed user persona of the High-Expectation Customer

I think the most clever trick in the above user survey structure is Q #2 — “what type of people do you think would benefit most from Superhuman?” ‘Cos, people tend to describe their own personas as a response. Analyze responses to this question only for the “Very Disappointed” bucket, and you end up with detailed personas that users themselves have pretty much self-created for you!

Going from this 1st level user persona…

1st Level User Persona

…to the 2nd level user persona.

2nd Level User Persona

PS: have been searching for what an optimally-sized user persona should be like for a really early stage startup. This is a great example — ~200 words, 2 paras; captures both professional & personal behavior, motivations, quantified behavioral characteristics, relevant life goals and desired outcomes/ end-state.

5. Focus on delighting a small number of users first

Paul Graham always says it; Superhuman case study just confirms it — define a narrow market, delight, dominate & then grow out from there.

Reproducing this quote by PG, just to drive home this point:

“When a startup launches, there have to be at least some users who really need what they’re making — not just people who could see themselves using it one day, but who want it urgently. Usually this initial group of users is small, for the simple reason that if there were something that large numbers of people urgently needed and that could be built with the amount of effort a startup usually puts into a version one, it would probably already exist. Which means you have to compromise on one dimension: you can either build something a large number of people want a small amount, or something a small number of people want a large amount. Choose the latter. Not all ideas of that type are good startup ideas, but nearly all good startup ideas are of that type.”

6. To convert users that are “one-the-fence”, focus on what your fanatic users love the most about your product

Key to converting more on-the-fence users into fanatic users is first identifying the core 1–2 strengths of your product. The reason being, non-fanatic users that fundamentally care about these strengths, are the ones most likely to convert into fanatics. However, this requires addressing their top 1–2 product concerns.

In Superhuman’s case:

Core strengths (as told by fanatic users)— speed, focus, keyboard shortcuts

% of “Somewhat Disappointed” bucket users, who care about “Speed” as the main benefit — 30%

For these 30% of “Somewhat Disappointed” users, what are their primary concerns (as told by them in the survey)— lack of mobile app (MAIN) + integrations, calendaring, better search etc.

7. Two-pronged product planning approach to move towards PMF — focus on core strengths + address core concerns

Boom! Post the above 6 steps, now you have a clear roadmap of features needed to convert on-the-fence users to fanatic users, and inch closer towards that elusive 40% PMF benchmark.

Your PMF product plan needs just the following 2 strategies — 1) doubling-down on core strengths that are loved by fanatic users+ 2) working to allay concerns & feature requests from on-the-fence users.

8. For feature prioritization, stack-rank to get to “lowest cost, highest impact” features

Use a combination of survey data and your qualitative product instinct to arrive at the low-hanging features (low cost + high impact) that can start delivering immediate value to users.

9. Rinse, and repeat…

…until you get to PMF!

Hope you find this deconstruction useful for your own journey towards PMF. Would love to hear any specific strategies that have worked for you.

Side Note: am currently building Workomo, a smart & simple professional relationships management hub for the new-age knowledge professional. If you would like to transform yourself from just a “networker”, to a deep “relationship builder”, do sign-up to receive private beta access. Also, check out this post on Workomo’s long-term Mission & product thesis.

How to think about building features at the beta stage?

It’s been an interesting journey for me as a product person, building Workomo over last few months. Having anchored the company mission on my personal pain point, the product roadmap for Workomo (at least for next 24 months) is quite clear in my head. Still, it’s not been easy to think through the order & prioritization of building features. This is a completely new “0-to-1” challenge for me as in my previous roles at Alibaba, Quixey and IDG Ventures, I was mostly used to evaluating, building & scaling products with at least some existing user traction.

As I work towards the private beta release of Workomo, the following frameworks have been really helpful for me in product planning:

  1. Running Lean by Ash Maurya — I really identify with the Lean way of building early stage products. While certain elements of the Lean process haven’t worked particularly well in my case (mockup based proto, hacking a solution without UI/ UX considerations), I have actively used the major core principles of Lean philosophy — iterative approach, user-pull over company-push, maniacally tracking return-on-effort, avoiding wastage, only focusing on 1–2 activities that matter at this stage of the startup. Though, it’s important to point out that I have found the need to adapt these approaches to my context by suitably modifying them.
  2. Focusing on the product’s “Atomic Unit” — I learned of this concept via a recent LinkedIn post by Pravin Jadhav. It was originally articulated by Fred Wilson in this 2012 post. What are the atomic units of popular products? Twitter — tweet, LinkedIn — resume, Instagram — picture, Gmail — email, Dropbox — file. It’s a lovely way to think about your product stack. For Workomo, the atomic unit is “a contact”. And that’s what I am building first for the private beta release.

I was on a Zoom call today morning — the moment I ended it, I received this version update pop-up, with following new features:

Zoom is releasing features like confirm starting video when joining a meeting, dropbox integration etc. ONLY AFTER going public!! Just proves that as early stage founders, we need to be much, much more disciplined about building additional features into our products.

Ultimately, there will be one, core UVP feature that will mainly drive user adoption. Our job as product founders is to discover & build it in an iterative manner while burning through minimum set of cycles.

PS: Workomo is your smart & simple professional relationships management hub. If you are sick of managing your networks on an excel sheet, do sign-up for free private beta access.