Product Management Process

PM Work Process:

● Identify Pain Points

● Derive solution ( Sometimes require competitive analysis)
● High-level Document
○ Annexure
○ Wireframes (with the help of designers)
○ Verify copywriting with the Tech writer team
○ Review with the tech team at a high level
● Approval (Peer / PO / Cross team / PM)
● Detailed Design from UX team (Sometimes requires Behavior Document)
● Detailed Design document for tech Engineers

Writing Document:

Write a document based on a business/ user point of view

● Users should be able to
● System should support

Know tech feasibility but don't worry about implementation.

No specific UI/UX needs to be specified.
Make the requirements clear - no ambiguous wordings should be involved.

PM - makes PRD - sync with the designer - PM shares thoughts with the designer - Designer
comes up with updated UI/UX - PM updates PRD if any modifications are required.

Template:
● PM detailed Spec
● Kickoff - when clarification is needed with other teams - Specify the need on the
document

While updating PRD, Make a copy of the old PRD with updating ‘It has updated Version’ link
and update the PRD on the new copy

PRD Other Headings:

Mobile - Your UX/UI mobile view if required

Streams - NA
Notifications - Does it require any notifications
Search - Does your element need to be listed in Global Search of Kissflow
Integration - Does any integration required
API - Do you have to expose any API to the Public
Security and Compliance - Security & Compliance requirements any
Audit - Process created by, modified by - any
Billing -
Filter Framework - Simple, Advanced Filter requirements in KF any
Formula implication
Delegation Behaviour
Documentation requirements
Event instrumentation(product dash) - KF analytics Purpose - logs any ( currently using Google
Big data)
Tours/Onboarding

Making Decisions:
● Refer competitor apps
● Think also for no-code perspective as well
● Think of internal other teams' dependency
● Think of future roadmap components. How do they leverage/ affect the current decided
approach
● Technical limitations - Don't think of it

Design Inspiration:
● Envato
● Dribble
● Behance

How to become a Great PM:

● Learning own Product (100%) In & Out

● Customer Feedback - knowing what our customers need by extracting info from
analytics tools, support team tickets, and Partner community discussions. Interacting with
the sales team on why they lost a lead due to a lack of features.
● Understanding Competitor Products better - What they offer better and what they lack
To score better in KF, it is evaluated by how much you contribute outside of your work like
helping the sales and marketing team.