Top Banner
6/2/15 1 Innovation for an Existing Software Product : An R&D Approach Aaron Barrett - Infusionsoft @twitterhandle #hashtag The Problem
16
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Innovation for Existing Software Product: An R&D Approach

6/2/15  

1  

Innovation for an Existing Software Product : An R&D Approach Aaron Barrett - Infusionsoft

@twitterhandle #hashtag

The Problem

Page 2: Innovation for Existing Software Product: An R&D Approach

6/2/15  

2  

@twitterhandle #hashtag

Successful Innovation with R&D – a Framework

•  Create R&D Team •  Send R&D Away •  Bring R&D Back •  Actively Engage “Regular” Developers •  Develop with Go-To-Market Strategy in Mind

@twitterhandle #hashtag

Create R&D Team

Page 3: Innovation for Existing Software Product: An R&D Approach

6/2/15  

3  

@twitterhandle #hashtag

Create R&D Team

•  Smaller is better

@twitterhandle #hashtag

Create R&D Team

•  Smaller is better •  Some Devs do well in R&D setting, some don’t

Page 4: Innovation for Existing Software Product: An R&D Approach

6/2/15  

4  

@twitterhandle #hashtag

Create R&D Team

•  Smaller is better •  Some Devs do well in R&D setting, some don’t •  Appropriate skillset mix

@twitterhandle #hashtag

Create R&D Team

•  Smaller is better •  Some Devs do well in R&D setting, some don’t •  Appropriate skillset mix •  Consider team leadership and oversight

Page 5: Innovation for Existing Software Product: An R&D Approach

6/2/15  

5  

@twitterhandle #hashtag

Send R&D Away

@twitterhandle #hashtag

Send R&D Away

•  Freedom is important

Page 6: Innovation for Existing Software Product: An R&D Approach

6/2/15  

6  

@twitterhandle #hashtag

Send R&D Away

•  Freedom is important •  Constraints are important

@twitterhandle #hashtag

Send R&D Away

•  Freedom is important •  Constraints are important •  Agree on clear problem statements

Page 7: Innovation for Existing Software Product: An R&D Approach

6/2/15  

7  

@twitterhandle #hashtag

Send R&D Away

•  Freedom is important •  Constraints are important •  Agree on clear problem statements •  Test, test, test

@twitterhandle #hashtag

Bring R&D Back

Page 8: Innovation for Existing Software Product: An R&D Approach

6/2/15  

8  

@twitterhandle #hashtag

Bring R&D Back

•  Prepare to get buy-in

@twitterhandle #hashtag

Bring R&D Back

•  Prepare to get buy-in •  Data is important

Page 9: Innovation for Existing Software Product: An R&D Approach

6/2/15  

9  

@twitterhandle #hashtag

Bring R&D Back

•  Prepare to get buy-in •  Data is important •  Don’t over promise

@twitterhandle #hashtag

Actively Engage “Regular”Devs

Page 10: Innovation for Existing Software Product: An R&D Approach

6/2/15  

10  

@twitterhandle #hashtag

Actively Engage “Regular” Devs

•  Don’t ever call them “regular devs”!

@twitterhandle #hashtag

Actively Engage “Regular” Devs

•  Don’t ever call them “regular devs”! •  Everyone will want to be on the new thing

Page 11: Innovation for Existing Software Product: An R&D Approach

6/2/15  

11  

@twitterhandle #hashtag

Actively Engage “Regular” Devs

•  Don’t ever call them “regular devs”! •  Everyone will want to be on the new thing •  Celebrate importance of revenue generating code work

@twitterhandle #hashtag

Actively Engage “Regular” Devs

•  Don’t ever call them “regular devs”! •  Everyone will want to be on the new thing •  Celebrate importance of revenue generating code work •  Clearly communicate roles and expectations to all devs

Page 12: Innovation for Existing Software Product: An R&D Approach

6/2/15  

12  

@twitterhandle #hashtag

Actively Engage “Regular” Devs

•  Don’t ever call them “regular devs”! •  Everyone will want to be on the new thing •  Celebrate importance of revenue generating code work •  Clearly communicate roles and expectations to all devs •  Prepare for everything to change

@twitterhandle #hashtag

Develop with Go-To-Market Strategy in Mind

Page 13: Innovation for Existing Software Product: An R&D Approach

6/2/15  

13  

@twitterhandle #hashtag

Develop with Go-To-Market Strategy in Mind

•  Get out of “prototype” mode

@twitterhandle #hashtag

Develop with Go-To-Market Strategy in Mind

•  Get out of “prototype” mode •  How are we going to sell this?

Page 14: Innovation for Existing Software Product: An R&D Approach

6/2/15  

14  

@twitterhandle #hashtag

Develop with Go-To-Market Strategy in Mind

•  Get out of “prototype” mode •  How are we going to sell this? •  Will existing users need to migrate?

@twitterhandle #hashtag

Develop with Go-To-Market Strategy in Mind

•  Get out of “prototype” mode •  How are we going to sell this? •  Will existing users need to migrate? •  How important is backwards compatibility?

Page 15: Innovation for Existing Software Product: An R&D Approach

6/2/15  

15  

@twitterhandle #hashtag

In Summary

@twitterhandle #hashtag

In Summary

•  Create R&D Team •  Send R&D Away •  Bring R&D Back •  Actively Engage “Regular” Developers •  Develop with Go-To-Market Strategy in Mind

Page 16: Innovation for Existing Software Product: An R&D Approach

6/2/15  

16  

@twitterhandle #hashtag

Questions?