cesnimda
143 lines
4.3 KiB
Markdown
143 lines
4.3 KiB
Markdown
# Product Vision
|
|
|
|
## Vision
|
|
|
|
Jobjakt should be a modern career operating system for job seekers in Norway: a professional, supportive and highly usable SaaS product that combines job tracking, career profile management, CV creation, application support, interview preparation, analytics and contextual AI.
|
|
|
|
It should feel clean and easy to understand while still being information-rich enough that users can understand their job search at a glance.
|
|
|
|
The product should be suitable for everyone, not only technical users or experienced professionals.
|
|
|
|
## Market focus
|
|
|
|
Primary market: Norway.
|
|
|
|
The product should use terminology, workflows and defaults that make sense for Norwegian job seekers. The architecture and design should not unnecessarily prevent international expansion, but Norway is the product's primary focus.
|
|
|
|
English and Norwegian localisation should remain first-class product capabilities.
|
|
|
|
## Product positioning
|
|
|
|
Jobjakt should feel like:
|
|
|
|
- a professional career dashboard,
|
|
- a job-search command centre,
|
|
- a document and application workspace,
|
|
- an AI-assisted career tool,
|
|
- a personal analytics platform for the job-search process.
|
|
|
|
It should not feel like:
|
|
|
|
- a spreadsheet with a nicer UI,
|
|
- an AI chatbot with some job features,
|
|
- a cluttered ATS,
|
|
- an over-customisable design editor,
|
|
- a collection of unrelated pages.
|
|
|
|
## Design inspiration
|
|
|
|
Useful reference products include:
|
|
|
|
- Huntr
|
|
- FlowCV
|
|
- Teal
|
|
- Prentus
|
|
|
|
The redesign should learn from their clarity, workflow organisation and SaaS polish without copying their visual identity.
|
|
|
|
## Brand personality
|
|
|
|
The brand should be:
|
|
|
|
- professional,
|
|
- supportive,
|
|
- trustworthy,
|
|
- modern,
|
|
- calm,
|
|
- capable,
|
|
- encouraging without being childish or gamified.
|
|
|
|
AI should be visible as a capability, but it should not dominate the brand identity.
|
|
|
|
## Core user promise
|
|
|
|
A user should be able to open Jobjakt and immediately understand:
|
|
|
|
- what they are currently applying for,
|
|
- what needs attention,
|
|
- what is happening next,
|
|
- how their job search is performing,
|
|
- which opportunities are the strongest matches,
|
|
- which CV/application materials are attached to each job,
|
|
- what Jobjakt recommends they do next.
|
|
|
|
## Core product principles
|
|
|
|
### 1. Guide instead of overwhelm
|
|
|
|
The application should guide users toward sensible next actions rather than exposing every feature at once.
|
|
|
|
### 2. One source of truth
|
|
|
|
The Career Profile is the canonical source for the user's career information.
|
|
|
|
CVs, applications, cover letters and AI outputs should derive from it while allowing document-specific overrides.
|
|
|
|
### 3. Preserve user trust
|
|
|
|
User data must never be silently changed by AI.
|
|
|
|
### 4. Explainability over magic
|
|
|
|
AI recommendations should explain why they are being made and what source information they are based on.
|
|
|
|
### 5. High information value, low visual noise
|
|
|
|
The interface may be data-rich, but hierarchy, spacing, typography and grouping should keep it readable.
|
|
|
|
### 6. Customisable where it adds value
|
|
|
|
Users should be able to customise dashboards, density and relevant preferences.
|
|
|
|
The product should avoid offering unlimited styling controls that make the experience inconsistent or difficult to support.
|
|
|
|
### 7. Responsive by design
|
|
|
|
Mobile should be treated as a first-class experience, not merely a compressed desktop layout.
|
|
|
|
### 8. Existing functionality is protected
|
|
|
|
The redesign may restructure workflows, routes and UI components, but should not silently remove existing functionality.
|
|
|
|
## Primary user journey
|
|
|
|
The intended default flow is:
|
|
|
|
Find/import job
|
|
→ Analyse job
|
|
→ Match against Career Profile
|
|
→ Tailor CV
|
|
→ Create/tailor application
|
|
→ Apply
|
|
→ Track progress
|
|
→ Prepare for interview
|
|
→ Record outcome
|
|
→ Learn from analytics
|
|
|
|
The product should surface the next logical action at each stage.
|
|
|
|
## Success criteria
|
|
|
|
The redesign should be considered successful when:
|
|
|
|
- users can understand the main application structure without training,
|
|
- job details are clear rather than confusing,
|
|
- the CV builder is significantly easier to use,
|
|
- the application feels alive and polished without becoming visually noisy,
|
|
- users can scan meaningful job-search statistics quickly,
|
|
- AI feels native to the workflow,
|
|
- mobile workflows remain practical,
|
|
- existing functionality continues to work,
|
|
- light and dark modes both feel intentionally designed,
|
|
- spacing and component behaviour are consistent across the application.
|