How to plan your project strategically and for a long-term. Presentation is based on mobile and web-services complex development examples.

1. Growth hack
development
Stanislav Azhotkin

2. Follow common sense
Prove and correct

3. Follow common sense
Prove and correct
NOTHING NEW

4. Strategic approach towards mobile
apps and web-services development
Stanislav Azhotkin

5. Команда

6. Birth of the project
Simple and brilliant idea comes to mind
The core idea gets additional functionality
Long development process
First release
PAIN

7. Sportlife
To create loyalty app that has no
analogues in fitness clubs’ industry
Challenge

8. First release
unique social network with gamification for club’ clients
huge block of functionality: schedule, trainers, clubs’
page, ratings, profiles, friends, messages, etc.
several developed ideas that were crossed out before
the actual release
two ideas that got no impact from the audience -
lessons’ filter and events
1 year 2 months - timeframe of first iteration development

9. What came next
analysis + public feedback from the audience + interviews
of the clients
constant product development via short iterations
delete irrelevant functions and add ones that are needed
by the audience

10. Result
every function is on demand
product became well known with a help of users
recommendations
application is a key argument to choose Sportilfe
instead of other fitness clubs

11. ZakaZaka
To create the most handy app for food
delivery from restaurants
Challenge

12. Result of first iteration
startup became one of major players on Russian
delivery market
appearance of their own loyal audience
new number of ideas

13. after one year we redeveloped an app with new
project and visual design
main focus on short terms and key functions based
on analysis
after 2nd release there were 10+ small updates
What came next

14. location is requested upon launch as a key
parameter
studied user behavior - added option to change
the location during processing your order
studied feedback - added option to change
your phone number
Spotlight and Google Now
we were first to integrate Apple Pay among
competitors

15. Way to survival
cut everything unnecessary - qualified review
of main hypothesis with minimal time span
HADI cycles and constant releases
audience reactions’ review ( with various tools )
and plan’ corrections

16. Thank you, cap
In general, all these ideas are obvious, but need
to be constantly reminded of when it comes
to your own product

17. Where the problem lays?
when it comes to your own project all ideas
seem necessary and crucial
your own view on features demand
“great product promotes itself”
“we need to be better than competitors
in every detail possible”

18. Cap on a way to survival
main idea is a core that is enough
for your project
short iterations and fail fast principle
analytics integration (but don’t overdo it!)
and feedback studies
HADI-cycles, constant evolution of the project
based on audience reactions

19. FOLLOW THE COMMON SENSE!

20. In the end
Never try to fit everything in first release
Be ready to constantly improve your product, its’ lifespan
doesn’t end with first release
10 small updates are better than 2 big ones
One iteration - to test one hypothesis

21. Thank you!
Stanislav Azhotkin
Operational director
+7 (977) 713-08-96
sa@handh.ru