Product Managment

Where can I find the latest product roadmap?
- The roadmap is maintained in [Notion/Jira/Confluence] and updated quarterly. It includes major epics, milestones, and OKR alignment.
What’s the typical timeline for a new feature (MVP to GA)?
- MVPs typically go from discovery to release within 1–2 sprints. Enhancements or complex features may span 2–3 quarters.
How do product initiatives tie into company OKRs?
- All roadmap items are tagged against OKRs in our planning tool to ensure alignment with revenue, engagement, or scalability goals.
How do I know if something is in discovery or in delivery?
- Each roadmap card is labeled with status: Discovery, Validated, In Development, QA, Shipped.
What criteria do we use for prioritizing features?
- We follow a RICE scoring model—Reach, Impact, Confidence, Effort. Customer demand, revenue potential, and technical feasibility are key factors.

How can a customer or team member request a feature?
- Internal: Submit via Jira → Product Request board.
- External: Requests are tracked via CSM inputs, Intercom tags, or Productboard customer portal.
What are the top requested features currently?
- Top 3 features this quarter include:
- 1. Offline mode in mobile app (Fieldforce)
  2. Exportable dashboards
  3. Auto-sync with 3rd party tools (e.g., Salesforce, Zoho)
How do we track the status of a request?
- All feature requests are assigned a status: Pending, Backlog, Planned, In Dev, Released.
Can I vote on a feature?
- Yes, Productboard and our internal Slack #product-feedback channel allow for voting and emoji reactions.

Where is customer feedback collected and stored?
- Centralized in Productboard, with sources from Intercom, NPS surveys, CSAT, and CRM notes from CSMs.
How often do we run user interviews or surveys?
- Bi-monthly for high-impact personas. Surveys are sent quarterly via email and in-app.
How is feedback analyzed and actioned?
- PMs tag feedback by theme (e.g., mobile UX, performance issues) and prioritize via impact score. Insights are shared in the monthly Product Pulse deck.

Where can I find competitor comparisons?
- A maintained Competitor Matrix is in Confluence, with head-to-head feature comparisons, SWOT analyses, and pricing details.
Do we maintain customer personas?
- Yes. We have personas for Consumer, Fieldforce, Admin, and Backend Ops. Each persona has defined goals, pain points, and preferred workflows.
What sources do we use for market insights?
- Gartner reports, McKinsey trend dashboards, industry blogs, and customer interviews.

Where is our user-facing product documentation?
- Hosted at [docs.example.com] or integrated in the Angular frontend via a help widget.
Where are internal PRDs and specs stored?
- Stored in Confluence or Notion under Product > Specs. Each PRD includes problem statement, goals, user stories, wireframes, and dependencies.
Are there version histories?
- Yes, tracked via GitHub (for APIs) and Confluence update logs (for specs and guides).

What’s our release cadence?
- Web (Angular/Django) – every 2 weeks
  Mobile (iOS/Android) – monthly
  Backend services – Continuous Deployment with approval gates
How are stakeholders notified of new releases?
- Via Slack #release-updates, release notes on Notion, and customer-facing emails for major changes.
Is there a beta user program?
- Yes. Teams can nominate users via the Beta Feedback Form.

What’s the long-term product vision?
- To be the most intuitive, scalable, and field-optimized platform for utility management across geographies.
What’s our North Star metric?
- Monthly Active Fieldforce Users completing Jobs in under X minutes.
What are our current strategic themes?
1. Mobile-first experience
2. Intelligent automations
3. Seamless 3rd-party integrations
4. Self-serve analytics

Where can I view the current pricing plans?
- Located in the Sales Wiki and at [pricing.example.com].
Do we offer custom enterprise pricing?
- Yes. Sales and Product collaborate to define custom SLAs and pricing models based on volume and feature access.
Are there any upcoming pricing changes?
- A/B tests are being run for new field-based pricing bundles for Q3.

Where can I find common user journeys?
- Defined in our User Journey Map located in Miro and linked via Confluence.
Do we use standard templates for stories?
- Yes, we follow the Gherkin syntax: “As a [role], I want to [action], so that [benefit].”
Can I see real examples of customers succeeding with our product?
- Case studies are maintained by Marketing and accessible in the Sales toolkit folder.

What tools do we use for experimentation?
- Firebase Remote Config (mobile), LaunchDarkly (web), and Mixpanel Experiments (data analysis).
Where can I view test outcomes?
- In the Experiments Tracker sheet (shared monthly) or in the Mixpanel Dashboards under Product Experiments.
What was our last major test?
- Job assignment flow redesign (v2) → Increased completion rate by 12%.

How does product work with engineering and design?
- Each squad includes a PM, Tech Lead, Designer, and QA. Workflows include:
- - Weekly backlog grooming
  - Sprint planning
  - Daily standups
  - Post-mortems
What tools are used for collaboration?
- Jira, Figma, Slack, Miro, Notion, Loom.
How are PRDs reviewed?
- Each PRD requires peer reviews from Eng + Design before sprint inclusion.

What are our core KPIs?
- DAUs, MAUs, Feature Adoption %, Retention Rate, NPS, Time to First Value (TTFV)
What tools do we use for analytics?
- Mixpanel, Looker Studio, Amplitude, Segment
Can I request a new dashboard/report?
- Yes. Fill out the Analytics Request Form (linked in #product-data Slack channel).