IoT6P - From Problem to Product and beyond

name: inverse
class: center, middle, inverse
layout: true
.header[.floatleft[.teal[Christopher Biggs] — Problem to Product].floatright[.teal[@unixbigot] .logo[@accelerando_au]]] .footer[.floatleft[.hashtag[EBN] Sept 2017]]

---
name: callout
class: center, middle, italic, bulletul
layout: true
.header[.floatleft[.teal[Christopher Biggs] — Problem to Product].floatright[.teal[@unixbigot] .logo[@accelerando_au]]] .footer[.floatleft[.hashtag[EBN] Sept 2017]]

---
layout: true
template: callout
.header[.floatleft[.teal[Christopher Biggs] — Problem to Product].floatright[.teal[@unixbigot] .logo[@accelerando_au]]] .footer[.floatleft[.hashtag[EBN] Sept 2017]]

---
template: inverse
# From Problem to Product in the Internet Of Things
### or, IoTPPPPPP (catchy, eh?)

.bottom.right[
Christopher Biggs, .logo[Accelerando Consulting]
<br>@unixbigot .logo[@accelerando_au]
]

---
layout: true
template: callout
.crumb[
# Prelude
]

---

# Who am I?

## Christopher Biggs — .teal[@unixbigot] —  .logo[@accelerando_au]

* Brisbane, Australia
* Founder, .logo[Accelerando Consulting]
* 20+ years in IT as developer, architect, manager
* Accelerando is a "full service" consultancy - chips to cloud
* ***IoT, DevOps, Big Data***

---
# The "Six P" model
### (models P1-P5 were taken)

* .yellow[Problem] - I have identified something Wrong in the world
* .yellow[Proposal] - I intend to make the world a better place in this way
* .yellow[Players] - I understand the strategy of other entrants in the space
* .yellow[Proof-of-Concept] - I can demonstrate that a (better) solution is possible
* .yellow[Prototype] - I will test that **my** solution is attractive to the market
* .yellow[Product] - They like it.  Now I have to build (and support!) a million.

???
* Production Preparation Process

* Place Product Price Promotion

* Proper Planning Prevents Pisspoor Performance

---
layout: true
template: callout
.crumb[
# Prelude
# Problem
]

---
template:inverse

# 1. Problem

## *"I have a bad feeling about this"*

---

# IoT: solving problems so common we don't even notice them

## Tiny, Cheap, Connected devices open a new class of solutions

---

# How many people are affected?
## Can I lead them to a solution?
## How much will they pay for it?

---
layout: true
template: callout
.crumb[
# Prelude
# Problem
# Proposal
]

---
template:inverse
# 2. Proposal
## *"Wouldn't it be nice if..."*

---

# What kinds of solutions are possible?

---

# What are the pros, cons and costs of each?

---
layout: true
template: callout
.crumb[
# Prelude
# Problem
# Proposal
# Players
]

---
template:inverse
# 3. Players
## *"Surely someone thought of this before?"*

---

# Know your Competitors

* Who am I up against?
* What's been tried?
* What are my threats?

---

# Know your Customers

* How can I maximise my market?
* What is the lifetime of my opportunity?
* How do I ride the hype curve?

---
layout: true
template: callout
.crumb[
# Prelude
# Problem
# Proposal
# Players
# PoC
]

---
template:inverse
# 4. Proof-of-Concept
## *"That's so crazy it might just work!"*

---

# Exploring the problem space

* What are the attributes of a successful product?
* Can each of them be achieved?

---

# Stitching together some quick experiments

* A little bit of brain, a little bit of muscle
* Igor, fetch me the jar of.... **Blu Tack**

---
layout: true
template: callout
.crumb[
# Prelude
# Problem
# Proposal
# Players
# PoC
# Prototype
]

---
template:inverse
# 5. Prototype
## *"If I build **this**, will they come?"*

---
# Exploring the solution space

* Does it look like a duck?
* Does it quack like a duck?
* Is it actually Wabbit Season?

---
# Putting it all together

* Get customer validation ASAP
* Each prototype asks and answers a question

---
layout: true
template: callout
.crumb[
# Prelude
# Problem
# Proposal
# Players
# PoC
# Prototype
# Product
]

---
template:inverse
# 6. Product
## *"A gadget is for life, not just for Christmas"*

---

# Scaling up

* Design Matters.   I mean it *really* *really* matters.
* Production processes - Custom PCBs, Robot assembly, Injection Moulding

---

# The long run

* Component lifetime
* Software maintenance
* Customer support
* Learning from customer behaviour

---
layout: true
template: callout
.crumb[
# Prelude
# Problem
# Proposal
# Players
# PoC
# Prototype
# Product
# Peroration
]

---
.fig30[
![](keep-calm.jpg)
]

# Peroration
### (Yes, that's a word.  Look it up.)

.nolm[
* Choosing a .yellow[Problem] to solve
* .yellow[Proposing] a way to solve it
* Understanding the .yellow[Players] and the field
* Creating a .yellow[Proof-of-Concept]
* Using .yellow[Prototypes] to refine the value proposition
* Moving from prototype to .yellow[Production]
]

---

# Resources, Questions

## Related talks - [http://christopher.biggs.id.au/#talks](http://christopher.biggs.id.au/#talks)

## Me - Christopher Biggs

- Twitter: .blue[@unixbigot]
- Email: .blue[christopher@biggs.id.au]
- Slides, and getting my advice: http://christopher.biggs.id.au/
- Accelerando Consulting - IoT, DevOps, Big Data - https://accelerando.com.au/

???

Thanks for your time today, I'm happy to take questions in the few
moments remaining and I'm here all week if you want to have a longer
chat.   Over to you.