There may be mild bad language (such as ‘shit’ or ‘son of a bitch’)

We know how to build great products (even if we generally suck at using that knowledge effectively)

From fancy phones… (and the apps that run on them)

And cars

To simple, useful and beautiful software products

Some of the most valuable and engaging products are built iteratively to delightfully meet the needs of their users

What if we applied everything we now know works for product development, to teams?

Like…focus on customer value and user experience

Frequent releases and faster feedback

Validated learning

Team-As-A-Software-Product?!(Holy shit Mike!! That is just crazy talk!)

What is Your Team v1.0?

Who are your customers?!(and how well do you know what they want?)

What features do they consider valuable to them?!(vs what you offer)

Who are the users of your team-as-a-product?!(and how well do you know what they need you to help them do?)

What bugs are they experiencing with your product? !(and how well do you recognise and resolve them?)

Release a new version of your team regularly (fix your releases, vary your scope)

How will v2.0 be different from v1.0? (it only needs to be a little different)

Why oh why this craziness?

Continuous Improvement is a marathon, not a sprint (how do you stay the distance?)

You and your team will find more Joy!(or eventually you leave and find more joy)

You will gain better tools!

You stand a better chance of delighting your users!(and that ain’t a bad thing)

You will build better actual software products!(ok , this is getting a little surreal)

I tweet everyday @mhsutton I sometimes blog at mhsutton.me!

I offer joy and free coaching at www.theimprovementpartnership.com

Thank You!!Productising Teams.25x20 !Go try this and let me know how it goes.