Welcome to the Tech for Non-Techies podcast

Every company wants to be innovative, but how do you balance the risk of innovation with the need to keep the lights on? Listen to this interview with Kapil Kane, Head of Innovation at Intel China, to find out.

Learning notes from this episode:

• Most tech innovations die because they do not have a solid business case. As much as non-techies need to learn to speak tech, techies need to learn to speak business. “No matter how smart you are, if you are not able to get your idea across in the language of a lay person, you are missing out a lot,” says Kapil.
• To structure creativity within an organisation, Kapil advises learning from Apple, where teams often worked on projects that other teams did not know about. This meant that they could focus on their work, while upper management connected the dots.
• The innovation accelerator at Intel China Kapil set up brings in revenue, but that is not the only benefit. It serves as a training ground for ambitious people “If...

Design is often at the core for why products go viral or flop. But, how can you tell good design from bad right at the start? How do you hire the right people and avoid costly mistakes?

That’s what you’ll learn on this episode.

Learning notes:

• User experience designers, not developers, should be your first hire in the vast majority of cases.
• Learning how to use design software does not make you into a designer. Learning to use a kitchen knife does not turn you into a chef. This is the same logic.
• Great designers mix human psychology and the design process to make products that people want to use. The best designers are well versed in behavioural economics and human insight, not just tech tools.
• Great designers are partners, who question your assumptions and sometimes tell you that you are wrong. Someone who only agrees with you isn’t going to help make your product great.

Resources mentioned in this episode:

• Introduction to Design for Technology: Listen on Apple...

You've probably heard about network effects, but they aren't the only thing you need. Learning effects build the ultimate moat against your competition.

Learning notes from this episode:

• You get better at speaking a language the more you practice and correct your mistakes. It is the same with algorithms: they get better with time and training.
• The more time and data you have to train an algorithm the more accurate the algorithm’s output will be, and also, the more complex the problems it can solve.
• “Learning effects can either capture or add value to existing network effects or generate value in their own right.” – Competing in the Age of AI, by Marco Iansiti and Karim Lakhani
• Companies that have been training machine learning algorithms for longer are at a competitive advantage. Strong learning effects make it impossible for competitors to catch up.

Resources mentioned in this episode:

• Sophia Matveeva’s LinkedIn
• Listen to The Business of AI...

How do you get to the top of a tech company as a non-technical professional? How can you drive innovation, when you’re not building the technology yourself?

That’s what you’ll learn from this interview with David Wells, ex CFO of Netflix and chair of the board at Wise.

Learning notes from this episode:

• “It’s called tech, or working in tech, but the entire economy is going to be this. So calling it tech is a little bit apocryphal at this stage,” David says.
• “Tech jargon distances people from the actual understanding of the concepts.” Learning core technology concepts is not as hard as the jargon has many believe.
• Learning what data scientists do and how to work with them is the best skill set to develop for business people in tech. “Data science is the analysis of the lifeblood of the company and you have to ask fundamental insight questions against it. You do not have to build the models yourself, but you are at an advantage if...

On Airbnb, people stay at strangers' homes. On Twitter, people get trolled. Both are global tech platforms, but why do people treat strangers well on one, and badly on the other?

The answer lies in platform governance: the rules you make to encourage good interactions and punish the bad stuff. Learn how to set up platforms where people are nice to strangers with this week's podcast episode.

Learning notes from this episode.

• Platform governance touches product development, engineering and marketing. It isn't just a corporate mission statement nobody reads.
• The logic we apply to creating good offline environments also apply to platforms, but just on a bigger scale. Ask yourself: how do I want people to feel when they get here? What do I want them to do?
• The Art of Gathering: How We Meet and Why It Matters by Priya Parker is an excellent book on how to create offline environments. You can apply these lessons to the online world you are creating. 
• Community leaders and opinion...

How do you launch a dating app, if you have no men and no women on it? Or, how do you launch a market place with niether buyers nor sellers?

This is the chicken and egg problem that all platforms have to solve to succeed.

In this week's episode, you'll learn 6 methods for how to launch a platform when you have no users. Some are sneaky, some are fun and all are very clever.

Sophia's favourite book on how to build & grow platforms is Platform Revolution: How Networked Markets Are Transforming the Economy - And How to Make Them Work for You.

1. Pipeline to Platform conversion, e.g. Amazon to Amazon marketplace

2. Using a company that has the user base you want, e.g. Airbnb & Craigslist 

3. Seeding content, e.g. dating apps & Quora

4. Bringing influencers to your platform for an incentive, e.g. Joe Rogan

5. Producer Evangelism: e.g. Kickstarter, Indigogo, Partyslate

Listen to Sophia's interview with Partyslate CEO & Co-Founder Julie...

Facebook disrupted the media market forever. The Apple App Store created the app economy, valued at $6.3 trillion today. What makes platforms like these SO successful?

In this episode, you will learn the core concepts behind platform businesses, so you can identify platforms in the making or build them yourself.

This is the beginning of a mini-series on platform fundamentals at Tech for Non-Techies.

Learning notes from this episode:

• Platform businesses have been around for millennia. A market square is a platform business. Technology just allowed these businesses to reach more scale and make more money than ever before.
• Most traditional businesses are pipeline businesses. A pipeline business employs a step-by-step arrangement for creating and transferring value with producers at one end and consumers on the other. For example, Ford makes cars and sells them to consumers.
• Pipeline businesses grow and prosper if they have Supply Economies of Scale. If Ford makes lots of...

Does having $2 billion in the bank account and celebrity backing guarantee success for a consumer app? Not necessarily.

Listen to how one company burned through almost $2 billion and had to shut down their app after just 6 months. Learn what Quibi did wrong, so you can avoid their mistakes.

Learning notes from this episode:

• Success in one field does not necessarily translate into another, especially without training. Quibi's founders used lessons from launching Hollywood blockbusters to launching consumer apps. This did not work.
• Follow the product development process, no matter how much money you have. Focus on the user. Do your research. Build in stages. Track user reactions at each stage and pivot if necessary.
• Only invest in large budget marketing after you've proven user need at small scale. Focus on retention metrics first, then on growth. 

Listen here on Apple Podcasts. 

Listen here on Spotify.

Developers don't work in the same ways as non-technical professionals. If you don't know how to work with developers, you can waste thousands of dollars and get very frustrated, as you'll see from the story Sophia shares on this week's episode.

Learning notes from this episode:

• A feature cannot be released when it is not ready. It is either ready to release, or it is not. There is no half way line. A feature can't be half ready, just like you can't be half pregnant. 
• Developers usually work in two-week cycles, when they are focussed on a specific set of tasks. For example, in a two week period, developers may be working on a specific feature for an app. Then they release it, and start on another feature.
• Since what developers do affects the rest of what the product team does, this lesson is relevant if you want to work with other people in the product team, like designers, community managers and data scientists.
• Corporate accelerators for technology start-ups, which...

Success in tech consists of two parts: making great products and using them to build a business. No matter how brilliant an app or algorithm is, if people do not want to pay for it, it is unlikely to live for long.

This is why all tech innovators need to learn the core skills of commercialising innovation.

Listen to this episode to learn how Salesforce, Starbucks and Xero commercialise their tech products, and so you can apply their lessons too.

The top 3 questions you need to answer to ensure your tech product has business success are:

1. How will this product help people make more money?
2. How will this product improve customer experience?
3. How will this product improve efficiency?

Always focus on the benefits that the product will bring customers, not its features.

Tell Sophia what you’re working on and submit your questions to her on [email protected]

Or reach her on Facebook, Instagram and LinkedIn and Twitter.

Listen here...