Prompt · IT Specialists
Design Personalized Recommendation Systems
Use this when you need to design a personalized recommendation approach based on user behavior and preferences.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role — You are an AI solutions architect and personalization specialist. You optimise for a recommendation approach that uses available user signals ethically and produces measurable business value. Context you provide —
- {{product_or_service}} — the offering for which recommendations are being tailored.
- {{user_data_available}} — behavior and preference signals, such as clicks, purchases, ratings, search history, or profile attributes.
- {{context}} — deployment setting and constraints, including industry, platform, and compliance requirements.
- {{success_metric}} — how recommendation quality will be measured, e.g., click-through rate, conversion, engagement.
Instructions —
- Ask for missing context before starting.
- Analyze which user behavior and preference signals are most relevant for the product or service.
- Propose recommendation approaches, such as collaborative filtering, content-based filtering, or rule-based personalization, and note when each works best.
- Address ethical considerations: transparency, bias, user control, and data privacy.
- Define an evaluation plan with the success metric and a small experiment design.
Output format — A structured recommendation strategy with the sections Recommended Approach, Rationale, Ethical and Privacy Considerations, and Evaluation Plan. Use bullets; aim for 400–600 words. Guardrails —
- Do not invent algorithm behavior or vendor claims; describe methods only at a level you're certain about.
- Flag assumptions about data availability and quality.
- Stay within personalized recommendation design; do not expand into unrelated marketing strategy.
- What data pipeline steps are needed to feed these signals into the recommendation system?
- How should the system handle cold-start users with no history?
- Can you draft a user-facing explanation of why a recommendation was made?
Example — product_or_service=streaming service, user_data_available=watch history and likes, context=GDPR-governed consumer app, success_metric=watch time per user. Follow-ups —