Passive talent

16 Jun 2020 - Rob Calvert Stage: Finding a problem worth solving --> Find a solution that people are willing to pay for Market: Internal talent acquisition managers at 20-100 employee tech startups Job: Recruiting passive candidates (specifically engineers) Value prop: ??? Solution: ???

Last Sprint: We found a problem worth solving

We entered this sprint with one main aim; doing further interviews to find a problem worth solving.

More specifically, we had a reasonable idea of the main jobs/pains our target market had, but couldn’t rank them.

Over 10+ inverviews we asked broad open questions such as:

  • “If you had a smart, switched on and hard-working intern, what one task would you delegate to them?”
  • And “How could a tool or service make you twice as good at your job? You can define “twice as good” however you like”

We also asked them to rank top pains/possible ‘gains’, using information from previous interviews to setup a card-sorting exercise as follows:

Card sorting exercise The card sorting exercise for ‘upsides’ (gains). We shared our screen, and asked interview participants to select 3 top-priority gains.

Following analysis of all these interviews, we were able to re-organise the RHS of our Value Proposition Canvas to accurately reflect the jobs/pains/gains of our target market:

Updated VPC The RHS of our updated value proposition canvas, with an accurate reflection of top-priority jobs/pains/gains for our target market. Here’s a link to our Miro board if you want to dig into the detail.

And score customer jobs against their importance, tangibility, the degree of unsatisfied pains/gain (‘Unsatisfied’ in the below), and size of market/willingness to pay (‘Lucrative’ in the below):

Jobs ranking Our ranking of high-level customer jobs, based on our research. Here’s a link to ur Miro board if you want to dig into the detail.

Before I continue it’s probably worth highlighting that ‘passive’ candidates are those that would move but aren’t actively hunting. (Candidates actively job hunting are ‘Active’ candidates).

Perhaps this ranking comes as no surprise. When it comes to recruiting software engineers, there aren’t enough quality active candidates to fill open roles - so companies either headhunt themselves, or use recruiters, or both.

For this market, the vast majority of 20+ (or at least 40+) startup companies have internal talent who actively source passive candidates. When you ask them what their pains (or unrealised gains) are, everything points to this.

We’re aware this isn’t a new problem, but it has problems with it. Response rates on LinkedIn are low, candidate data is often incomplete or out of data, market mapping takes weeks, and all-in-all it’s a lengthy, tedious process.

In short, it’s a big thing, and no-one’s cracked it yet. If they had, recruitment companies would be declining rapidly - and they’re not.

Next up; finding something people will pay for

First, a caveat; this is just the very start of this process. We’re not going to get the answer with one ‘ideation’ session, but we’ve got to start somewhere.

As such, we followed a classic process for generated ideas.

Throughout this process, we didn’t get too bogged down into the details of a solution. Instead, we’re trying to find a high-level promise (i.e. value proposition) that people will pay for.

It went as follows…

First, we did a quick customer journey map to pinpoint where there were most pains/unrealised gains:

Customer journey map Typical customer journey map for finding candidates. Here’s a link to ur Miro board if you want to dig into the detail.

Then generated and ranked ‘How might we’ statements:

Customer journey map Ranked HMW statements. Here’s a link to ur Miro board if you want to dig into the detail.

Looked at how products/services in analogous industries looked to solve the same problems (including Watford FC’s recruitment policy…!):

Customer journey map A snapshot of analogous products we looked at. Here’s a link to ur Miro board if you want to dig into the detail.

Then generated and ranked a bunch of ideas:

Customer journey map A few ideas we generated… Here’s a link to ur Miro board if you want to dig into the detail.

Before ranking them, and outlining how we’ll get initial signals for them:

Customer journey map Initial plans for testing Here’s a link to ur Miro board if you want to dig into the detail.

We ended up with three ideas that would be directly used by our market

  • A service that uses highly-targeted social media adverts to increase response rate
  • A service that scrapes all publicly available information (LinkedIn, Github, etc), and does a degree of pre-screening and information-filling to present passive candidates that are more likely to response to direct outreach
  • A ‘Lunchclub.ai’ for Europe’s ‘top 5%’ of tech talent

Stu also pointed out that it will be difficult to sustain a competitive advantage with any company unless you’ve got access to candidate data (e.g. willingness to move, salary expectations, true indicators of technical ability), so we’re beginning to investigate ideas down that route.

Next Sprint: Testing initial value propositions

Aaaand breath. There’s a lot there, I know, and there’s still a lot further to go.

Here’s what we know:

  • None of these ideas will stand the test of time
  • This was from one ideation session, and there could be plenty more ideas out there
  • We’ve loosely taken competition into account, but need to dig more deeply
  • We haven’t even scratched the surface candidate-side
  • Needless to say, we haven’t yet covered details of the solution, channels, pricing model, etc

But we’re taking it step by step, as per our process.

Next up, we’re generating 4x landing pages for these ideas. (I know, more landing pages - sigh - but we did look at other methods so test them, promise!).

The three company-focussed value propositions contain a ‘high bar’ element, visitors will be asked to enter a lot of information to ‘get a demo’.

We’ve done this because internal talent acquisition managers will readily sign up for anything that might make their life easier, so a normal ‘Join the waiting list’ won’t be a good signal of intent. We can also use the form to fill in gaps about our knowledge. We’ll be driving traffic to these using LinkedIn ads.

Our one candidate-side idea is focussed on one pain point we know about without doing any research; constantly getting spammed by recruiters.

We have no idea yet how to solve this, so we’re doing a ‘vision/mission’-based landing page, and seeding it into appropriate forums (Reddit, Twitter) etc to see if it gets any traction.

Just the start, and a long way to go - but a good progress from 2-3 weeks ago.

Other Comments

  • We were previously looking for ‘quick flip’ tools, but our attitude has shifted a little, mainly because solving a 10x more valuable problem isn’t necessarily 10x harder.
  • With the help of a friend, we’re also looking at which other markets have an acute problem with finding quality passive candidates.
  • Using the Value Proposition Canvas also helped broaden our horizons beyond focussing on ‘pains’ alone. I used to struggle with the idea of ‘Gains’, but it’s simply ‘unrealised value’. Something that a potential customer really wants to do, but can’t achieve it with any tools/services out there (rather than it being promised by a tool/service but not realising itself, which is a pain)

First steps

25 May 2020 - Stu Bates Stage: Finding a problem worth solving Market: Internal talent acquisition managers at 20-100 employee tech startups Job: Vetting engineers for technical ability Value prop: ??? Solution: ???

Last Sprint: New product, quickly invalidated

The Quick Flip Rob mentioned in our first post came from a tool I built in 2016 called GitHawk. This allowed companies to find developers based on the code they’ve actually written on GitHub.

It was intended as a tool for finding candidates but the costs associated with downloading and storing all that data were prohibitive!

More recently, it occurred to me we might be able to re-purpose the same codebase as a screening tool to help recruiters who, in the main, are not technical.

Now this might not sound like the new and improved process we were talking about. It sounds a lot like we’re going solution first!

Fear not, our first step on this was to articulate the problem GitHawk was intending to solve. The assumption that:

Recruiters are not technical and therefore struggle to assess the quality of a potential candidate.

We reached out on LinkedIn to set up problem interviews with recruiters both internal and external to start talking and learning.

We wrote up a set of problem interview questions (using the Mom Test as a guide) to start getting an unbiased and truthful look at their problems.

After writing up the first 5 interviews we started work on a Value Prop Canvas - pulling out the jobs, pains and gains that our customers had described in our first conversations.

It quickly became apparent we had too many pains and gains to solve and not enough data on which ones are the most severe.

Next Sprint: Further discovery

Right now, we think the most important thing to do is to simply speak to more users.

We’re aiming to get a pipeline of interviews set up so we can keep momentum over the next few sprints.

We’ve refined the interview questions to focus on the most common areas that came up previously and also added a card sorting exercise where we force people to pick a limited number of pains and gains that matter to them most.

Hopefully, this will provide us with some confidence to zoom in a little and let us focus on solving the right problems when we move onto generating our first Value Props for testing.

Running in parallel we’re also starting to flesh out the business environment map with competitors, industry trends and market forces that should help us shape the value propositions in the next phase.

Hopefully, the next one of these updates will be Rob talking about how we came up with and started to test our first handful of value propositions!

New approach

04 May 2020 - Rob Calvert Stage: Finding a problem worth solving Market: Various Job: Various Value prop: ??? Solution: ???

This post is the first in a series, where we’ll post ever two weeks to chart our progress.

Why? We did a full retrospective on our process, and decided it needed a lot of improving.

Long story short, we spent the past 8 months on an idea we quickly wanted to test in 6 weeks. When we took a step back, we realised it was far too small a market to spent that much time on.

Learned two things:

  • It’s very easy to get sucked in. We had some nice signals and early paying customers, but remotely enough for the amount of time we spent
  • It’s very difficult to practice what you preach

So, we’ve begun to overhaul our process, and we’ve decided that:

  • We’re going to spend more time picking a problem to solve. Building any product is difficult. We need to make sure we’re doing the right one (i.e. one with enough payoff, and that we care about)
  • We’re going to put in more guardrails, and this is one of them. If we’re not proud of what we’re writing on this blog, that’s a bad sign

What next? We’re looking at three things:

  • A ‘Quick flip’ idea in the recruitment space
  • Pivoting Inquisitive to focus on sales outcome
  • An idea in the Talent Mapping space with a contact/good friend of ours