Welcome to the Tech for Non-Techies podcast

Why do you keep checking your phone, even when you’re trying not to? It's because the apps on your phone use the Hook Model. described by Nir Eyal in his book Hooked: How to Build Habit-Forming Products.

To learn how apps like Instagram, LinkedIn and Vivino keep us coming back to our screens, listen to this episode.

Learning notes from this episode:

• Habits are behaviours done with little or no conscious thought
• If your product becomes a habit, people will use it more. You will spend less on advertising and make more money.
• The greatest return on investment generally comes from increasing the product's ease of use.
  • If you want to improve a product, first look at the design: where you can make it more simple to use. E.g. can you require less information from users when they first sign up?
• The Hook model consists of 4 steps 
  1. Trigger: you get a notification that someone commented on your post
  2. Action: you open LinkedIn / Instagram to see the comment
  3. Variable Reward: you...

Software updates can have weird unintended consequences that the company doesn't even know about. Existing features that worked perfectly can stop working, leading to lost revenues and annoyed customers.

Listen to this episode to learn why this happens and how non-technical leaders deal with it when it does.

Learning notes from this episode:

• A developer could write a line of code to affect one outcome, and there could be a completely different unintended outcome that they don’t even know about it.
  • When an app, site or algorithm gets complicated enough, these unintended consequences are more and more likely to happen.
• To prevent this, make sure that different people test the new version on different devices and browsers.
  • In tech teams, this function is called Quality Assurance.
• Remember that these unintended consequences are inevitable. The key is to catch them early and correct course.
  • Create a process for your users to quickly tell you if something goes...

To become SMART MONEY as an investor, founder or corporate innovator, you have to know what questions to ask about a product. This helps you spot signs of early success or early warning. 

Listen to this episode to learn what questions to ask and how to link product innovation to business strategy. 

Learning notes from this episode:

• The questions fall into three buckets:
  1. How do my best customers behave?
  2. What are the characteristics of my best customers?
  3. What has to happen for them to abandon the product?
• For bucket 1, you could ask:
  • What features do my most active users use?
  • What screens do they visit?
  • How often do they open the app?
  • What time of day do they open it and on which days?
• For bucket 2, you could ask:
  • Where did these customers come from?
  • What are their demographics? Are there any patterns?
• For bucket 3, you could ask:
  • What screens tend to be the last screen that people get to before they shut down the app?
  • What prices of other apps they use have?...

When an app has too many features and pop ups, most users get confused and frustrated. This is feature creep: when the product’s core functionality becomes hidden in too many options and things to do.

Feature creep happens when a team is determined to stay productive, but loses sight of its strategy. Sometimes stopping is better for the product than doing more.

Learning notes from this episode:

• Feature creep is problematic for two main reasons: it confuses users and it costs money. This is because product teams have to be paid to design and code, and you also have to pay cloud costs to store your pointless features.
• Feature creep happens when there is a pressure to produce, which is contrary to the ability to focus. It can be easier to present new features as productivity to investors and corporate bosses, rather than saying that the product team took time to review results and reflect.
• To prevent feature creep, go back to the fundamental product development questions...

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...

If you have an idea for a new product in a traditional business, you will probably have to work on an extensive plan before you do anything else.

This is not how it works in tech companies. When the likes of Airbnb and Slack bring new apps or features to market, they use the Sprint Method. It is a methodology developed by Google Ventures to bring new ideas to life and test them quickly and cheaply.

Learn how this works in this podcast.

Learning notes from this episode:

• The aim of a sprint is to test an idea for a new product to find out whether it is worth investing more money in. For example, you can use a sprint to test an idea for an app by creating a prototype. If users like what you’ve made, only then should you hire developers.
• Each sprint should focus on one idea to test. Do not try to test multiple ideas in one sprint.
• To figure out where the biggest risks in a new idea lie, ask yourself: if this time in a year, this project failed, why would it have done so?
• A sprint...

No code apps and outsourced product studios mean that there is more opportunity than ever for non-technical founders and traditional businesses to get into tech and succeed.

But, as more companies enter the market, they’ll be competing for a finite resource: our attention.

Listen to this episode how to make the most of this opportunity and avoid costly mistakes.

Learning notes:

• The prevalence of No Code apps and outsourced product studios is driving down the cost of building apps, sites and algorithms.
• As more tech products enter the market, marketing costs will increase. This means a boon for Facebook and Google, and also for professionals who know how to attract and engage new users.
• Jobs that will benefit from this boom include User Experience designers, who know how to make habit forming products, Community Managers and Strategic Partnerships experts. None of these roles require coding, but they all require an understanding of how tech products get built and who does what...

Every app and site is made up of lots of different tech tools and languages. Like a house, one part is built on top of another and they need each other to function. If one part of the structure breaks, the rest can fall down too. 

These are called dependencies. To keep a product working, all the dependencies need to work together. This is part of the invisible work that software engineers do.

Learning notes from this episode:

• A tech stack describes all the tools and programming languages used to build an app or a site. Some of those tools are custom made, some are rented as licences and others plug you into a bigger ecosystem.
• Examples of bigger eco-systems that many products depend on are the Apple App Store, Google Play and Amazon Web Services. If one of these ecosystems has a problem, the apps and sites they support will have issues too. An app on the Apple App Store depends on Apple, hence the term dependency.
• Product teams have to update...

Why do some products go viral and others die a quiet death? The answer lies in growth hacking. 

Growth hacking is a type of marketing that combines working on the product, which is an inside job, and working on promotion, which is an outside job. It is a new discipline born with the tech sector, and growing in popularity today.

Learning notes from this episode:

• The Dropbox growth hacking case study is still seen as the Holy Grail in the sector. The team created a double referral program to grow 3900% in just 15 months.

• A growth hacking effort is always done by a multi-disciplinary team, and will often involve a product manager, a designer, a community manager, engineers, someone with a marketing or PR background, and maybe a data scientist.

• Traditional marketing is outside facing: billboards, TV ads and articles in the press.  Growth hacking is different because it looks at the inside of the product, and adjusts it to grow users and revenue.

• PR...