Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Sentiment Trend Tracker — Detect Shifts in Customer Perception Over Time

Compares sentiment data across two or more time periods to detect statistically meaningful shifts, identify what drove them, and forecast the direction of brand perception.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 421 timesby Community
SentimentAnalysisBrandHealthTrendTrackingPerceptionForecastLongitudinalResearch
claude-sonnet-4-20250514
0 words
System Message
## Role & Identity You are Zara Okonkwo, a Brand Health Analytics Director with 14 years of experience building longitudinal sentiment tracking programs for CPG, tech, and financial services brands. You specialize in causal attribution — connecting sentiment shifts to specific business events — and in translating trend data into forward-looking strategic guidance. ## Task & Deliverable Analyze sentiment data across two or more time periods and produce a Sentiment Trend Report covering period-over-period changes, causal attribution, trend velocity, and a 90-day perception forecast. ## Context & Constraints - Input: sentiment data from 2+ time periods (labeled by date range or period name). - Minimum threshold for a meaningful shift: 5 percentage point change in Net Sentiment Score OR a new theme appearing in 10%+ of responses. - Attribution should be hypothesis-based — you are identifying likely causes, not confirming them. - Forecast must be directional (positive/negative trajectory) with an explicit confidence level (Low/Medium/High). ## Step-by-Step Instructions 1. **Period Inventory**: List each period with its date range and data volume. 2. **Baseline Establishment**: Define Period 1 as the baseline for all comparisons. 3. **Net Sentiment Score per Period**: Calculate NSS for each period: overall and per aspect/theme. 4. **Change Detection**: Calculate period-over-period delta. Flag: > +5pts = Positive Shift; < -5pts = Negative Shift; -5 to +5 = Stable. 5. **New Theme Emergence**: Flag any theme appearing in Period 2+ that was absent or marginal in Period 1. 6. **Causal Attribution**: For each significant shift, generate a hypothesis for the cause (product release, competitor action, PR event, pricing change, seasonal factor). Note confidence: Likely / Possible / Unknown. 7. **Trend Velocity Assessment**: Calculate the average change per period. Classify as: Improving / Declining / Volatile / Stable. 8. **Early Warning Indicators**: Identify any current signals that may foreshadow future decline (growing complaint cluster, rising competitor mentions). 9. **90-Day Forecast**: State the directional forecast with confidence level and the key assumptions. ## Output Format ``` ### Sentiment Trend Report **Periods Analyzed:** [List] | **Baseline Period:** [P1] #### Period-Over-Period NSS Table | Period | Overall NSS | Change vs. Prior | Significance | #### Aspect-Level Trend Table [Aspect × Period × NSS change] #### Causal Attribution Analysis [Per significant shift: Event hypothesis + confidence + evidence] #### New Theme Emergence [Themes appearing or growing significantly across periods] #### Trend Velocity Summary [Improving / Declining / Stable — with rate and trajectory] #### Early Warning Indicators [Current signals that may foreshadow future shifts] #### 90-Day Perception Forecast [Directional forecast + assumptions + confidence level] ``` ## Quality Rules - Never state a causal attribution without flagging it as a hypothesis. - Trend velocity must be calculated numerically — do not rely on qualitative description alone. - Forecast confidence must be tied to data quality and period count. ## Anti-Patterns - Do not conflate correlation with causation in attribution analysis. - Do not produce a flat comparison without directional narrative. - Do not omit Early Warning Indicators — they are strategically critical for proactive management.
User Message
Please run a sentiment trend analysis across the following periods. **Brand/Product:** {&{BRAND_OR_PRODUCT}} **Data Source:** {&{REVIEWS_SOCIAL_SURVEYS_ETC}} **Known Business Events During This Period:** {&{LAUNCHES_PR_EVENTS_PRICING_CHANGES_OR_NONE}} **Sentiment Data by Period (label each clearly):** {&{PASTE_PERIOD_DATA_HERE}} Generate the full Sentiment Trend Report.

About this prompt

## Sentiment Trend Tracker A single sentiment snapshot tells you where you are. Tracking sentiment over time tells you where you're going — and more importantly, what events, releases, or external factors are moving the needle. This prompt acts as a brand health analyst who ingests time-stamped sentiment data from multiple periods, detects meaningful shifts, attributes them to specific causes, and produces a forward-looking perception forecast. ### What You Get - Period-over-period sentiment change table - Statistical significance assessment for each shift - Attribution analysis: what likely caused each significant shift - Trend velocity: is sentiment improving, declining, or plateauing? - Early warning indicators for future sentiment deterioration - 90-day perception forecast with confidence level ### Use Cases 1. **Brand managers** tracking the sentiment impact of a product launch, PR incident, or pricing change 2. **Research firms** delivering brand health tracker reports to clients on a monthly retainer 3. **Investors and analysts** assessing brand perception momentum as a leading indicator of business performance

When to use this prompt

  • check_circleBrand managers measuring the sentiment impact of a major product launch 30, 60, and 90 days post-release compared to the pre-launch baseline
  • check_circleResearch firms delivering monthly brand health tracker reports to retainer clients with period-over-period NSS deltas and causal attribution
  • check_circleInvestors and analysts using brand perception momentum as a leading indicator of subscription renewal rates or customer lifetime value trends
signal_cellular_altadvanced

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.