The document discusses strategies for minimizing the gap between product makers and users. It provides examples of Lego Universe and Minecraft, noting that Minecraft was more successful because it was developed through frequent releases that incorporated user feedback. The key strategies proposed include: releasing often to get early feedback; using public bug trackers and feedback tools; empowering autonomous teams; practicing radical transparency; slicing problems into smaller pieces; and prioritizing curiosity over pride.
BDSM⚡Call Girls in Sector 99 Noida Escorts >༒8448380779 Escort Service
Gde je nasa produkt zajednica u odnosu na Evropu
1. Gde je naša product zajednica u odnosu na
Evropu?
2. Certified Scrum Product Owner Training with
Roman Pichler
&
Minimise the Gap Between Maker and User by
Henrik Kniberg
Vojislav Mokric, Project Manager at
50. Minimise the Gap Between Maker and User by Henrik Kniberg
Big disclaimer: This talk contains
nothing new or revolutionary, just old
principles that kinda need repeating.
Generalization rarely reveals truth, but
does reveals patterns. And that pattern
is “Minimize the Gap”.
Building the right thing is about
understanding the customer (Lego vs
Minecraft).
51. Lego example
Lego Universe, first big digital product,
game like a WoW but Lego-like.
They just build the whole thing until it was
perfect in their own minds and then they
shipped it.
250 people over 4 years = 1000 man/years
invested.
Didn’t hit the market and was retired soon.
Lesson learned -> start using Agile!
52. Minecraft example
Happening at the same time, a digital
equivalent of Lego game: Minecraft
Build initially by 1-2 people and shipped in
just a 6 days with the announcement done
via the Twitter.
Feedback via the Twitter, author actually
listen, made updates and released over
100 releases in first year.
80M $ in first 15 months. Ultimately, game
was sold to MS for 2.5B $.
53. Steps to minimize the gap: Release Often
Release often (snapshot every
week, create buzz, get the early
feedback).
Spotify: there was never Big
Bang release, more like exploring
the hypothesis (prototyping, early
releases).
“People will never pay for music”.
Frequent Releases -> Easier
Planning & Less Frustration
54. Steps to minimize the gap: Get Real User Feedback
Minecraft: Public bug tracker -
yes, anyone can add Jira
tickets! Tool to minimize the
distance between the makers
and users.
6k+ bugs reported :)
Positive Feedback Loop:
Frequent Releases (Minecraft
Snapshots) -> Fast Feedback ->
Better Product -> Happier Users
and Makers!
55. Steps to minimize the gap: Get Real User Feedback
Source of insights & decision
making: Try to find the balance!
If one corner is telling something
that’s a signal, a hint.
If two corners are telling the
same message that’s a strong
signal and you should probably
do that.
If all three corners are
screaming, then it’s a no-brainer.
57. Steps to minimize the gap: Autonomous Teams
Teams should have almost scary
amount of autonomy.
People like that, that gets them
motivated when they have
responsibility to impact the end
product - at least in Minecraft.
Reduce handoffs, increase speed.
Discovery Weekly - feature at
Spotify: give the problem to
solve, but don’t tell how to solve.
60. Steps to minimize the gap: Radical Transparency
Loosely coupled but tightly
aligned teams.
Product Transparency - Demo or
die! Everyone reminded on the
big picture - forcing factor for
collaboration.
Everyone needs to see the big
picture. Where we are,
Blockers, Priorities...
Photo -> Send to Stakeholders.
61. Steps to minimize the gap: Curiosity > Pride
Great cultures are about the
mindset.
Be proud on what you make, but
not too proud (Lego Universe).
Curiosity brings us closer to the
users.
Inspire that attitude and you’ll be
closer to success.
