#productcamp

[vivekkindrayan]

Pittsburgh Product Camp - the best gift I could get today at the amazing place that CMU is. @pghpcamp @teppercmu @carnegiemellon #pghpcamp #pittsburgh #productcamp #productmanagement #conference (at Tepper Quad) https://www.instagram.com/p/BoCgMwLnmWz/?utm_source=ig_tumblr_share&igshid=1hoohtfe2x0x2

[andreymelnichenko]

Конспект: Метрики наше всё!

Конспект выступления Ильи Забелина из Яндекса на ProductCamp. О метрика и почему они важны. 

Как в Яндексе выбирают метрики для проектов?

Выбрать главную (ту, которую хотим растить)  и дополнительные

Построить иерархию

За каждую метрику есть ответственный. На их основе оценивать фичи: как растут/падают. Если падают метрики верхнего уровня, а нижнего растут, всё плохо.. 

Иногда иерархию нужно пересматривать. Раз в полгода, например.

Как на их основе выбирают, какие продукты делать?

1. Набросать список проектов и оценить в размерах одежды

2. Оценить детально стоимость разработки и внедрения

3. Оценить уточнёно ожидания с учётом прошлого опыта, данных аналитики и мнений экспертов.

НО: даже если метрики растут, следить за качеством.

[andreymelnichenko]

Конспект: Как определить, понравится ли обновление

Конспект выступления на ProductCamp Светланы Половинкиной из Wargaming.

Планируйте исследования до начала разработки. Сбор фидбека — часть разработки и продвижения. 

Можно проводить на любой стадии: закрытое, открытое тестирование, релиз, но опрашивать один на один. Любой опрос запускать не в первый день.

Делать правку на то, насколько выборка репрезентативна  Также рассматривать аудиторию с разным опытом.

Люди обычно не дают резкие оценки, поэтому рассматривать обновление по частям, а не понравилось/нет вообще.

Перед опросом составить профиль респондентов: профиль (возраст, опыт) мотивы (почему участвуют), какую версию тестируют.

Закрытое тестирования для небольшой выборки.  В анкете — блоки открытых вопросов с полями для комментариев. Во время такого тестирования можно изучить:

что доработать

выбрать версию

найти баги

определить барьеры

какие возможности не предусмотрел разработчик

Открытое тестирование для всех. В анкете — закрытые и открытый вопросы с полями для комментариев.  Можно узнать:

как воспринимают обновление

какие есть серьёзные барьеры

какой контент неприемлем

В релизном опросе могут оказаться все, поэтому вопросы не должны быть слишком техническими. В анкете — закрытые вопросы с полями для комментариев.

[gabormolnar]

Impressions from Product Camp Berlin 2015

I attended a few sessions and I wanted to share a few notes for two of those sessions that resonated with me the most.

Keynote: Ship it!

Judith Andresen talked about reducing the complexity to ship faster and that a product should have a true north.

Measure your cycle time

The time between story creation and deployed should be measured (cycle time)

Goal: Keep the cycle time short!

Minimize your complexity costs

Wrong question: How long does it take to implement feature XY?

Right questions: How much complexity do we add?

Always focus on the simple solution

Simple Solution = Best Solution

Low complexity costs means you can ship faster (ultimate goal)

Find your true north!

The true north are 3-5 short action oriented statements that clarify for the whole team what the product ist about und where it should be heading

Session: Problem Roadmaps

Kadir Topal talked about a running experiment at Mozilla. They replaced feature roadmaps with problem roadmaps.

Have a roadmap with problems not features

Don't think in features or solutions. Think what problems for the customer should be solved.

List all problems and prioritize them

Problem need metrics to measure if the problem was really solved

A ticket in JIRA does not end with Done -> measure after deployment

Everybody wants to be data informed or data driven but feature roadmaps that extend over several months can't be data informed

Mozilla has problem finding meetings every 6 weeks and reevaluates the problem roadmap

[worklearnplay]

Make the most of your next unconference

Make the most of your next unconference - learn about this and more to supercharge your success at WorkLearnPlay.com

The “unconference” conference has been very popular especially for information workers. An unconference is a conference where the format is loosely structured. The idea is an informal exchange of ideas, interactions, and information rather than a tightly structured program. ProductCamps, BarCamps, CityCamps, WordCamps, and others are a popular type of unconferences and this year I have attended…

View On WordPress

[cindyfsolomon]

ProductCamp Bengaluru @PCampblr14 #PCampblr14

ProductCamp Bengaluru @PCampblr14 #PCampblr14

The Global Product Management Talk has been covering product events worldwide since 2011 using storify and twitter.  You can read the event by viewing the captured tweets in chronological order. Follow http://storify.com/prodmgmttalk for archives of product events worldwide.

[View the story "ProductCamp Bengaluru @PCampblr14 #PCampblr14" on Storify]

View On WordPress

[herttua]

Lean Product Management – talk at ProductCamp Helsinki 2014

Lean Product Management for me is about 1) understanding what is important in product management, 2) what is important in lean and 3) how the tools from lean and lean startup could be used in the context of product management.

Read below a summary of the points in my talk at ProductCamp Helsinki 2014 organized at the Aalto Design Factory, Saturday April 5th 2014 that was aimed at the nascent community of Finnish product managers.

#pcamphki @therttua keynotes about his lean #prodmgmt experience @Rovio video entertainment platform pic.twitter.com/xkHVAhSUeW

— Brainmates (@brainmates)

5. huhtikuuta 2014

What is product management? – I might sound like a silly question, but I haven't found a simple yet comprehensive answer for it. Typically the definitions are something like "combination of UX, tech and business" but they don't help you in becoming better at product management. Other sources have long lists of what qualities good or "rock star" product managers should have, which often aren't very actionable. I think the community would benefit from a coordinated effort to try to understand what behaviors make a great product manager and how you can learn to do them.

“Guns don’t kill startups. Features do.” - @therttua

— Ash Maurya (@ashmaurya)

5. helmikuuta 2014

"Guns don't kills startups – features do!" – chasing features, instead of having a very specific Unique Value Proposition (UVP), risks running out of resources (both in startups and big companies)

"Guns don't kill startups, features do!" @therttua at #pcamphki

— Kjell Lauren (@klauren69)

5. huhtikuuta 2014

What is Lean? – about reducing waste, sure, but only in order to increase flow. Read more about Taiichi Ohno's concept of Flow vs Waste. here: http://www.slideshare.net/EmielVanEst/did-toyota-fool-the-lean-community-for-decades

Flow != coding stuff, it is about creating value for the customer @therttua at #pcamphki

— Kjell Lauren (@klauren69)

5. huhtikuuta 2014

Flow != coding stuff – typically, especially in bigger companies, we're used to thinking about flow in terms of SW dev productivity .. however, the flow we should care about is the flow of value to the customer. After all, the flow of customer value is often directly associated with cash flows as well. Thus: flow of customer value keeps your project alive.

Flow is about creating true value between ur customer & ur company, NOT feature chasing or building products @therttua

— Brainmates (@brainmates)

5. huhtikuuta 2014

Eliminating waste is relevant only in the context of flow – this comes back to Taiichi Ohno's point about focusing on value and eliminating waste in order to increase flow.

Getting the value to flow – how do you do it? This is something that doesn't have the "right answer" but there are many approaches to this. Mine is:

Build something that your customer wants (in line with Paul Graham)

..and wants to pay for (or you're fighting an uphill battle)

..a product that's 10X more engaging than the competition (because as a startup you have much less resources for promotion and sales compared to your corporate competition, and

Focus!

So how do you know where to focus on? My short answer is: customer insight. Understanding your customer intimately helps you understand their model of the world and thus you can use your intuition to come up with solutions that resonate even if the customer herself cannot articulate it in advance.

Customer development (qualitative customer understanding, http://www.slideshare.net/venturehacks/customer-development-methodology-presentation) combined with Lean Startup (build-measure-learn, http://theleanstartup.com/) – my suggestion for a starting point in building customer understanding as a Lean Product Manager. My question to you is: "could you test if a product will resonate before building it?"

Tools discussed:

Business Model Canvas (http://www.businessmodelgeneration.com/canvas)

Lean Canvas (https://leanstack.com/)

The Customer Factory (https://www.youtube.com/watch?v=5iq3xDul0JY)

Startup Metrics for Pirates: "AARRR"(http://www.slideshare.net/dmc500hats/startup-metrics-for-pirates-long-version)

Cohort metrics & Innovation Accounting (https://www.youtube.com/watch?v=gU3MZXW3uXw)

Visualizing experiments: The Lean Stack (http://practicetrumpstheory.com/2012/06/the-lean-stack/) or the Lean Startup Machine Validation Board (https://www.leanstartupmachine.com/validationboard/)

The A3 thinking process / the A3 report (http://sloanreview.mit.edu/article/toyotas-secret-the-a3-report/)

..or Ash Maurya's version of it, the Experiment Report (http://practicetrumpstheory.com/2012/06/the-lean-stack-part-2/)

Models for self-organizing teams: Holacracy (http://www.forbes.com/sites/stevedenning/2014/01/15/making-sense-of-zappos-and-holacracy/) or Agile Squads (http://blog.crisp.se/2014/03/27/henrikkniberg/spotify-engineering-culture-part-1)

Lean is about thinking and culture, not about tools! @therttua #pcamphki

— Kjell Lauren (@klauren69)

5. huhtikuuta 2014

And finally: Lean is above all a philosophy, a way of thinking, and adopting lean is about culture, first and foremost. The associated tools might help, but they might also do harm if focused on in a too fundamentalistic manner. 

  <blockquote class="twitter-tweet" lang="fi"><p>Flow != coding stuff, it is about creating value for the customer <a href="https://twitter.com/therttua">@therttua</a> at <a href="https://twitter.com/search?q=%23pcamphki&src=hash">#pcamphki</a></p>— Kjell Lauren (@klauren69) <a href="https://twitter.com/klauren69/statuses/452339879490646016">5. huhtikuuta 2014</a></blockquote> <script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script>

"There is no right or wrong, there's continuous learning!" @therttua #pcamphki

— Kjell Lauren (@klauren69)

5. huhtikuuta 2014