Positioning
From PRD users and problemGet trusted answers to onboarding questions without searching across multiple HR systems.
Audience: New employees in their first 90 days, plus HR operations teams who answer their questions.
Problem: New employees spend their first weeks hunting for basic answers — leave policy, payroll dates, IT access, who to ask — across an intranet, PDFs, Slack and HR email. HR answers the same questions repeatedly.
Key benefits
- Answers cite approved company sources.
- Fewer repetitive questions land on HR.
- New hires see exactly what is still outstanding.
- HR sees where onboarding knowledge is missing.
Customer pain points
- Information is spread across HR portals, PDFs and Slack.
- New hires hesitate to ask the same question twice.
- HR answers the same 20 questions every month.
Differentiators
Validate before use- Answers are restricted to approved sources with attribution.
- Escalation to a human is part of the product, not a fallback.
- Competitive validation required — no competitor claims in the PRD.
Messaging themes
Draft — PM review needed“Trusted answers, not guesses.”
“Onboarding that answers itself.”
“Every answer shows its source.”
Launch FAQs
- Where do answers come from?
- Only documents HR has uploaded and approved, with the source shown on every answer.
- What happens when the assistant does not know?
- It says so and offers to escalate the question to HR.
- Is my question visible to my manager?
- Not specified in the PRD — product decision required before launch messaging.
Launch risks
- Knowledge coverage at launch is unproven — pilot with one department first.
- Positioning depends on source freshness; an outdated answer is a trust event.
- Competitive validation required before any comparison claim.
What this brief will not claim
- Competitive validation required.
- PRD section "Acceptance Criteria" is empty — required before generation.
- Unresolved gap: Problem Evidence — You cited qualitative sources, but no numbers yet. Add frequency or cost so severity is arguable with data.
- Unresolved gap: Success Metrics — Define measurable outcomes that indicate whether the product solves the problem.
- Unresolved gap: Non-Goals — Clarify what this product will explicitly NOT solve.