SoJo has many exciting product development decisions to make. Based on early insights from the strategic planning process, SoJo needs to improve the navigation, usability and interface of the public site. In parallel to making these improvements, SoJo is building its first-ever enterprise-level software product. The stakes are much higher now, and decisions have greater implications. I was able to guide the team to building a content site using a Wordpress framework in its most basic functionality. This next phase of growth is much more complex, and beyond our current capacity.
SoJo has great development team. When given proper direction and structure, they are able to execute above and beyond. That being said, both developers are fairly junior and SoJo is the largest technical project either of them has worked on. Trial by fire has been our methodology thus far, however it can be a hindrance in moving SoJo forward. The entire organization needs to work at a more accelerated pace to achieve these next set of milestones.
When seeking advice, my challenges around the gap that exists between translating business requirements into functional requirements, the need for a CTO (Chief Technical Officer) came up quite often. Most successful technology companies are co-founded by a technical person, who becomes the CTO. Bringing on an external CTO at this stage of our development will be challenging. We have no intentions of selling SoJo for millions of dollars in the coming years, and the financial payout seems be to be a large motivator to attract good senior technical talent.
Technical recruitment has always been a challenge. Linus and Jesse joined SoJo right before major product launches. For the past 8 months, I've been keeping my eyes peeled for a technical partner. After 3 intense and focused months of searching for a technical team member, I've learned that effort will not always equal result. With the inability to offer a 6-digit salary and a highly competitive market, finding the right person will remain an ongoing challenge for us.
SoJo is in a conundrum where it needs a CTO to grow, however is unable to find one -- therefore the only logical solution is to create one. To fill its technical deficiencies, SoJo will be crowd-sourcing its CTO. This is highly experimental in nature. I have not found any successful case studies and I am still figuring out what it will look like.
Traditionally, crowd sourcing implies reaching out to the public for assistance. In this case, I will be reaching out to a closed network, seeking referrals to source individuals looking to commit their skills and experience to SoJo. Since SoJo is not building any unique technology, all development related activities can likely be covered by our existing development team. What we need instead is support in project management, information architecture, decision making and industry insights. Most of these skills come from experience, and so it makes sense to leverage the experience of many professionals, most of whom can complement one another. In addition to benefiting from the skills and expertise of experts in their respective fields, not having someone in the daily grind of the business can also provide fresh perspectives.
Product vision and business requirements will continue to come from me, so the crowd-sourced CTO will be used for technical guidance.
This approach is highly risky for many reasons:
Lack of ownership and accountability
SoJo will not the first priority of any of the individuals. Being a secondary activity, they may not dedicate the mental energy or time required for this role. A dedicated CTO invests in the company, both with their time and expected payoff. It will be difficult to hold a crowd-sourced CTO accountable to the advice that they provide, as the consequences of their advice may not directly impact them. Beyond goodwill and the opportunity to shape an organization with huge potential for impact, there is not much more that I can offer to our crowd-sourced CTOs in terms of compensation.
Effectively communicating the problem
A crowd-sourced CTO will not be able to get into the trenches or depth of problems. Only someone that works on a project day-in and day-out will understand all of the intricacies of certain technical issues and implementation problems. When only providing incomplete information, we risk getting incomplete or misleading advice.
With multiple brains giving out different pieces of advice, it is likely that we will receive conflicting and incomplete advice. Distinguishing between everyone's bias can result in a lot of inefficiencies or lead us down a wrong path. Similarly, the different features and technical elements to our products are all intrinsically linked. Each crowd-sourced CTO will likely look at their own issues in isolation. Without taking into account the technical inter-dependencies of each of the solutions, it is possible that solutions to one problem create bigger problems elsewhere.
Having a dedicated CTO will free me completely of all technical related activities. With less focus on the product, I'll be able to dedicate my time to equally important CEO-type activities, such as getting funding, building the brand and supporting other functions of the organization. In addition to coordinating the schedules of the CTOs I will still be primarily responsible for relaying that guidance to the technical team.
Risks considered, I'm quite excited about going ahead with crowd-sourcing SoJo's CTO. This could be an experiment gone wrong, in which case we know that we exhausted every option. On the other hand, this can potentially be a new model for what is possible, given limited resources.