Main takeaways:
- Introduction to cryptocurrencies (from a Product perspective)
- Why are unexplored industries challenging?
- Output VS Outcome
- Agile VS Long term Roadmaps- Real-life challenges & case studies
7. INTRO TO CRYPTOCURRENCIES
CHALLENGES OF A NEW INDUSTRY
OUTPUT VS OUTCOME
How do cryptocurrencies work? Are they anonymous?
What’s different from a product management perspective?
Are we doing the right things?
AGENDA
01
02
03
What should we build next?
04 PRIORITISATION AND LONG TERM PLANNING
10. 10
CRYPTOCURRENCIES
Bitcoin created in 2009
Decentralised
Another way to buy illicit
products and services
Minimum regulation worldwide
Highly complex architecture
Future of Open Banking (?)
19. SETTING THE SCENECracking down on
cryptocurrencies by applying
very similar concepts as fiat
BUSINESSES
Have to interpret and apply
the rules of the regulators
Different jurisdictions have
different rules
REGULATORS
20. GATHERING REQUIREMENTS
CHALLENGES
● There’s no industry standard and requirements change
depending on the appetite for risk and jurisdiction
● Industry changes incredibly fast
● Users often times want the solution and don’t want to dive
into the details of the product.
RECOMMENDATIONS
● Educate the internal stakeholders on the importance of
gathering feedback and feature requests
● Gather feedback from different
channels/personas/demographics and build one source of
truth
● Fake features/buttons - “Thank you for your feedback”
21. SHIPPING
BOLDLY VS GRADUALLY
Which approach is right for my project?
● What could go wrong? What are the risks?
● What is our confidence level? Are we looking for feedback?
Are we willing to iterate the product based on feedback?
BOLDLY
● Changes are small; No disruption
● We are highly confident and have done extensive user
research
● We are going to make the changes regardless of the feedback
GRADUALLY
● Changes are likely to surprise, disrupt, confuse or negatively
impact users
● You want to iterate the product further based on feedback
● We are going to make the changes regardless of the feedback
SHIP GRADUALLY AND BE BOLD
28. HIGH LEVEL
PLANNING
Ideas gathered from all
stakeholders (internal and
external)
High level delivery plan
slotted into our
development process.
After a stable launch the
feature is monitored and
maintained (e.g. fix bugs
and small features)
INNOVATE EXPLORE
MAINTAIN PRODUCTISE
Run by a cross functional
team to identify high level
market opportunity and
technical cost.
1 2
34
29. 29
EXPLORE PHASE
OUTCOME
LEGAL COMMITMENT
Do we have a legal
commitment,
contract or liability?
FINANCIAL RETURN
What’s the
estimated financial
return in the next 2
years?
SCALABILITY
Will this feature
allow us to scale
COMPETITIVE ADVANTAGE
By not doing this,
will we lose market
share? Are we
letting competition
in?
CRITICAL FOR CUSTOMERS
Do our customers
see this as critical
for their business?
TECHNICAL RISK
Is this a low
technical risk
project?
30. Does anyone have any
questions?
andre@elliptic.co
andre.reina.pt
THANKS!