Big changes in the world create winners and losers. The talent game is in the midst of one right now.
The "old world" was linear and built upon familiar processes: post, recruit, screen, hire.
The "new world" is exponential, where network value eats your old process for lunch.
If you're a CTO/VP Eng struggling to hire local technical talent, telling you that outsourcing is a useful lever to increase velocity is about as useful as taking your watch and telling you the time.
What IS useful is giving you the tools to do it SUCCESSFULLY.
I don't know who needs to hear this, but...
Smart #outsourcing of your software dev isn't about giving up control.
It's about doubling down on your strengths.
Verifying a team's work history is critical when selecting an outsourcing team.
If the team you select doesn’t have domain experience in what you need to build, you’re literally paying them to learn.
Several mitigations including a “ramp clause” can help.
Brilliant piece by the smart folks at @McKinseyDigital on the role of the CEO in shaping the tech agenda.
#2: have ample talent, implement agile, and have targeted vendor relationships for commodity and/or niche skills.
Know a platform like that? 🤔😁
https://t.co/hfZ7yqyH1s
Leveraging the remote talent economy means getting an *entire team* in place and delivering code faster than finalizing 1 local full-time hire.
Yes, seriously.
If you're a #cto#coo#vpeng, one of the things you need to consider when you're looking at adding a remote team is: how will you manage cultural issues & challenges when you intermingle on-premise and remote?
When you add a remote team, you don't have what we call "lazy" connections - connections that exist primarily due to physical proximity.
But it's a solvable problem, especially with the plethora of connection tools available - it just requires some thinking, empathy, planning
#vc's: Imagine a world where your portfolio co's have access to all the technical talent they need, giving them the competitive advantage of releasing as many features as budget allows.
That world is @fuel_io.
We've been there. We know the pain. That's why we built it.
The old objections around remote teams (communication; project management; culture) don't apply anymore.
With more and more companies embracing remote as a value-driver, we're long-past the "early adopter" stage.
What are YOU waiting for?
Excited to announce the release of our Best Practices Guide for Working With Remote Teams, penned by our very own @rksaint, @fuel_io's CTO!
A great resource that gets down to brass tacks - absolute gold!
Check it out here: https://t.co/zq0oNKJGeZ
Such a great example of “remote but inclusive” - love it!
Shared experience is what creates bonds. Clients often worry about “contractor mentality” (build for the paycheck, not for quality) but if you treat them like teammates this is far less likely to occur.
Kudos!
One of my remote work hacks: when a team I did work with has a celebratory boba tea or whatever at HQ, I buy one of the same thing here in Tokyo and send them all a photo.
It helps both side engage in the shared ritual, and also gives coworkers a little glimpse into life here.