Skip to content

Latest commit

 

History

History
284 lines (223 loc) · 7.15 KB

slides.md

File metadata and controls

284 lines (223 loc) · 7.15 KB
Raw

How to make a tech choice

Tiny Rhino

Agenda

  • Who are we?
  • Today's goals
  • Product phases
  • Workshop
  • Q&A / Discussion

Who are we...

:::

Emil 🇩🇰

  • Back-end developer
  • Work with Python, servers and databases
  • Collect, store and make data useful

:::

Kyle 🇦🇺

  • Front-end developer
  • Work with user interaction
  • Make things look pretty on the web with JavaScript

:::

Together 🎟

  • Ticketbutler / BilletFix
  • Tiny Rhino development consulting
  • Work with a lot of startups
  • Hack on stuff

Today's goals

  • Understand tech "buzz-words" ⚠️
  • Make "CTO" decisions
  • Rapidly test & develop your idea

Workshop

:::

Oh shit, you actually have to do something

::: Write down 2 things that impacted your startup:

  • One (good) tech choice
  • One screw up

Product phases ⚠️

  • Idea / concept
  • Pretotype
  • Prototype
  • Minimum Viable Product (MVP)
  • First version

:::

Why do we use product phases?

  • Time to market
  • Money (or lack thereof 💸)
  • Resources (few people to get lots done - fast 🏃)
  • Derives a product that solves a specific problem
  • Prevents building a 🚀 before first building a 🚲
  • Assists making good tech decisions
  • Enables rapid development

Idea / Concept

Wants vs needs

::: What do you need to solve your problem?

vs.

What colour should your spaceship be?

::: 🍷🍻

  • Napkin idea
  • Prove your concept
  • Think about flying to moon 🚀

:::

Tech Hack - Know your market

  • Google Trends
  • Producthunt.com
  • USE and understand your competitors tech

::: Ask yourself: Are you solving a specific problem?

(or are you building a spaceship 😆)

Pretotype

Test the market

::: Pretotyping is using simple tools to collect preliminary data.

Create and validate your hypothesis ::: 👨‍👨‍👧‍👧

  • Is there a market for my product?
  • Who would use this product?

:::

Tech Hack 💆‍♂️🙋‍♂️

  • Typeform
  • Facebook poll
  • WIX landing page
  • ASK REAL PEOPLE 👋

::: Ask yourself: Is your audience engaging with your concept?

Prototype

Tests your solution

::: A prototype is a thing you can interact with that demonstrates your solution.

Think: What technology do I need to solve this problem? :::

Tech Hacks

  • Squarespace / WIX
  • Embed Google forms
  • InvisionApp
  • GitHub pages
  • POP - Prototyping on Paper (App)
  • Keynote
  • Static sites ⚠️
  • 3D printing
  • Wordpress

:::

DEMO

:::

::: Think: Should you throw your implementation in the bin?

Ask yourself: Should you throw your idea in the bin?

Minimum Viable Product (MVP)

Tests your product

::: An MVP is the simplest version of your product that solves your problem. :::

MVP corner cutters

  • Draw inspiration from (copy 😉) market leaders
  • Send an email for an order instead of building an ecommerce platform
  • Build a simple webpage with an integrated "Buy" button
  • Settle for less (🚲 not 🚀)

:::

Web Shops Toolbox

  • Wordpress
  • Magento
  • Shopify

:::

Service products (don't reinvent the wheel!)

  • Messenger/WhatsApp as a messaging platform
  • Intercom
  • fiverr.com
  • Upwork.com
  • 99designs.dk
  • Google apps + Analytics
  • Microsoft Azure

:::

But sometimes that's not quite enough

:::

I need an App

:::

Platforms

  • Web
  • Native App ⚠️
  • Responsive web app ⚠️
  • API ⚠️
  • SAAS ⚠️
  • Responsive API SAAS progressively native in the cloud ⚠️⚠️⚠️

:::

You get all excited

:::

Then realise you could've built that spaceship faster

::: Think: What one platform will test my product on the market

Because you probably don't need more than one. :::

We like web 🌏

  • Fast to develop
  • Fast to deploy ⚠️
  • Fast to update and iterate (⏫ features)
  • All devices have a browser
  • Heaps of resources to draw from :::

Remember: Your MVP is just a suggestion of a possible solution. This is your time to test and define the product you need to build.

Ask yourself: Does my MVP enable me to validate my hypothesis?

First version

The child of your MVP iterations

::: The first version is a product you can sell to your market

:::

Tech TODOs 🔥🚒

  • Implement tech that gives your product the edge
  • Hire CTO / developer
  • Choose a stack ⚠️
  • 🚶 > 🛴 > 🚲 > 🚗 > 🚀

Remember: This isn't necessarily your final product. You will iterate and improve based on learnings.

:::

⚠️ Tech Considerations ⚠️

  • Hosting
  • Security
  • Privacy
  • Programming language
  • Framework
  • Database

:::

Tech Hacks

  • Azure/AWS - free hosting
  • Let's Encrypt - free SSL certificate
  • MailJet - free newsletter sending [up to 20.000]
  • Zoho - free email hosting for your domain
  • GitLab/GitHub pages - free static sites

::: Ask yourself: Are your tech choices scaleable? Are you ready for success?

Remember: If you crash, it will cost you! Both 💰 and 😎

Get to work

Get in groups and identify how your startup was affected by your one screw up and one good tech choice.

  • Maybe you iterated on your prototype?
  • Maybe you built a 🚀 before picking up a pencil
  • Maybe you wasted a week on a feature you didn't need?
  • Maybe you could've used a $5 service instead of building your own product?

Where to get help

Grab us at the coffee machine OR shoot an email to [email protected]

Places to get inspiration:

  • Social platform for products [producthunt.com]
  • Tech meetups in Copenhagen [meetup.com]
  • Hire devs looking for startups [thehub.dk, ...]

Slides at:

_tiny-rhino.github.io/how-to-make-a-tech-choice/ _