The document provides an overview of product management including defining product management, the product development cycle, and key aspects of product strategy, design, development, and launch. It emphasizes the importance of user research, testing hypotheses with users, and aligning stakeholders while constantly measuring progress towards goals.

1. PRODUCT
MANAGEMENT
101
A prelude into creating
a great product that
doesn’t make you insane.
Dimas Satrio Hutomo / @dimassrio

2. DIMAS SATRIO HUTOMO | @dimassrio
- FULL STACK Developer - Yes doing end-to-end engineering.
- Product Manager @ NARASI.TV (https://narasi.tv) -
Leading Digital Product Team
- Advisor / Former Product Manager @ ORDENT (https://ordent.co) -
a human centered Digital product Development Studio
- Technological Associate @ SARASWATI (https://saraswati.global ) -
Saraswati is a private Indonesian company that promoting innovation
in development.
- City Manager @ GDG Bandung -
Google Supported Development Community
- Community Enhancer @ FOWAB (Forum Web Anak Bandung)
- APEC App Challenge 2017 Vietnam - Indonesia Finalist

4. Definition Product management connect
the user experience, the
technical requirements and
the business requirements
together.

7. 1. Product Strategy
2. Product Design
3. Product Development
4. Product Launch
Product Development Cycle

8. It’s called art because there’s no the right way
In a realistic (yet not so defined) constraint,
and of course far from ideal condition.
Product Management is an art to align all
stakeholders towards a set of outcomes,
and drive the execution.
You do that while also constantly
measuring progress, metrics and milestone
- with user as a sole focus.

9. Product Strategy

10. Research
Industry Identification
Problem Identification Competitor Identification
Market Identification
Vision
Insight
Persona KPI
Hypothesis
Validate
User Identification

13. PRODUCT

14. Tell us about your product
and its value, in only
1-5 sentences.
Shorter is better.

15. You can’t think outside the box, unless you understanding what inside the box.
1. Industries and Sector
2. User Behaviour
3. Regulation and Rules
4. Fundamental
5. Research and Insight

17. NEED TO HAVE > NICE TO HAVE
FIND THE DISEASE, NOT THE PAIN

22. ● For (target customer)
● Who (statement of the need or opportunity)
● The (product name) is a (product category)
● That (key benefit, compelling reason to buy)
● Unlike (primary competitive alternative)
● Our product (statement of primary differentiation)

23. Product Design

27. In the Understand phase, you will create a shared knowledge base across all
participants. Using the Lightning Talk method, knowledge experts across the
business are invited to articulate the problem space from business, user,
competitor, and technological angles.

28. In the Define phase, the team evaluates everything they learned in the Understand
phase to establish focus. This is done by defining specific context and desired
outcomes of potential solutions. The phase concludes by choosing a specific focus
for your Sprint, as well as goals, success metrics, and signals.
define

30. In the Sketch phase, the Design Sprint team generates and shares a broad range
of ideas as individuals. You will start by looking for inspiration, such as solutions in
alternative spaces. Then, each Design Sprint participant will individually generate
ideas for consideration. From there, the team will narrow down ideas as group to a
single, well-articulated Solution Sketch per person.

31. In the Decide phase, the Design Sprint team finalizes the direction or concept to be
prototyped. Each participant will share their Solution Sketch, and the team will find
consensus on a single idea through decision-making exercises. The final direction
will aim to address the Design Sprint focus.

32. In the Prototype phase, the Design Sprint team will work together to create a
prototype of your concept. This is when many decisions are made around what
exactly the concept is and includes. You will aim to create a prototype that is just
real enough to validate, and you will do it really fast!

33. In the Validate phase, the Design Sprint team will put your concept in front of users
- this is your moment of truth! You will gather feedback from users who interact with
your prototype, and if relevant, you will conduct stakeholder and technical
feasibility reviews. You’ll end your Sprint with a validated concept– or an
invalidated concept to improve on. Either way, you’ve made progress.
Flawed SUCCESS Epic WIN
Efficient FAILURE Validated INSIGHT

34. Product Requirement Document

35. A product requirements document (PRD) is a
document containing all the requirements to a
certain product. It is written to allow people to
understand what a product should do. A PRD
should, however, generally avoid anticipating or
defining how the product will do it in order to
later allow interface designers and engineers to
use their expertise to provide the optimal
solution to the requirements.
REQUIREMENT
IS NOT SAME AS
SPECIFICATION

37. https://bit.ly/PRDDocument
1. Define the Product Purpose
2. Describe the Product Features
3. Outline the Release Criteria
4. State the Constraints & Establish a Schedule