<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>Sandeep Lamba's Blog</title>
        <link>https://sandeeplamba.writizzy.blog</link>
        <description>Blog posts from Sandeep Lamba's Blog</description>
        <lastBuildDate>Fri, 11 Sep 2026 17:29:03 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>Writizzy</generator>
        <language>en</language>
        <image>
            <title>Sandeep Lamba's Blog</title>
            <url>https://writizzy.b-cdn.net/blogs/4fec93fe-9559-4862-8883-0a4413006aaf/1767389866843-reniwr7.png</url>
            <link>https://sandeeplamba.writizzy.blog</link>
        </image>
        <copyright>All rights reserved 2026, Sandeep Lamba's Blog</copyright>
        <item>
            <title><![CDATA[How I Use AI to Write Unbiased Performance Reviews at Scale - Part 1]]></title>
            <link>https://sandeeplamba.writizzy.blog/p/a-practical-guide-to-conducting-meaningful-performance-reviews</link>
            <guid>https://sandeeplamba.writizzy.blog/p/a-practical-guide-to-conducting-meaningful-performance-reviews</guid>
            <pubDate>Tue, 06 Jan 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Making annual reviews less painful and more impactful]]></description>
            <content:encoded><![CDATA[<p><em>Eliminating unconscious bias and scaling quality feedback across my entire team</em></p>
<h2>The Uncomfortable Truth About Performance Reviews</h2>
<p>Let me start with a confession: I used to play favorites in performance reviews.</p>
<p>Not intentionally, of course. I would never consciously give better reviews to people I liked or had more visibility with. But looking back at my reviews from three years ago, the pattern was undeniable:</p>
<ul>
<li><strong>Recency bias</strong>: The engineers I worked with in November got more detailed, glowing reviews than those whose biggest wins happened in February</li>
<li><strong>Visibility bias</strong>: The vocal engineer who Slacked me daily got more recognition than the quiet one who consistently delivered</li>
<li><strong>Similarity bias</strong>: I wrote longer, more thoughtful reviews for people who worked like I did</li>
<li><strong>Halo effect</strong>: One impressive project colored my entire evaluation of that person</li>
<li><strong>Inconsistency</strong>: My 10th review of the day was noticeably shorter and less thoughtful than my 1st</li>
</ul>
<p>I wasn&#39;t a bad manager. I was just... human.</p>
<p>And that&#39;s the problem.</p>
<h2>The Hidden Cost of Biased Reviews</h2>
<p>Performance reviews aren&#39;t just paperwork. They directly impact:</p>
<ul>
<li><strong>Compensation</strong> - Raises and bonuses</li>
<li><strong>Promotions</strong> - Who moves up the ladder</li>
<li><strong>Opportunities</strong> - Who gets the high-visibility projects</li>
<li><strong>Development</strong> - What training and mentorship people receive</li>
<li><strong>Retention</strong> - Whether your best people stay or leave</li>
</ul>
<p>When reviews are inconsistent or biased, even unintentionally, you:</p>
<ul>
<li>Lose talented people who feel undervalued</li>
<li>Promote the wrong people for the wrong reasons</li>
<li>Create a culture where visibility matters more than results</li>
<li>Spend political capital dealing with appeals and disputes</li>
<li>Lose your team&#39;s trust</li>
</ul>
<p>The stakes are too high for &quot;I&#39;m only human&quot; to be an acceptable answer.</p>
<h2>The Traditional Solution (That Doesn&#39;t Scale)</h2>
<p>The conventional wisdom for reducing bias is:</p>
<ol>
<li>Keep detailed notes all year</li>
<li>Use structured rubrics</li>
<li>Gather 360-degree feedback</li>
<li>Calibrate with peer managers</li>
<li>Review for consistency</li>
</ol>
<p>These are all good practices. I do all of them.</p>
<p>But here&#39;s the reality when you manage a team of 10+ people:</p>
<p><strong>Each performance review takes 4-6 hours:</strong></p>
<ul>
<li>1 hour reviewing notes and data</li>
<li>1 hour analyzing against objectives</li>
<li>2 hours writing the review</li>
<li>1 hour editing and refining</li>
<li>1 hour in the review meeting</li>
</ul>
<p><strong>That&#39;s 40-60 hours of focused work</strong> for a 10-person team. And by hour 40, you&#39;re exhausted. Your 10th review isn&#39;t getting the same thoughtfulness as your 1st.</p>
<p>You end up cutting corners. You reuse phrases. You rush. Quality suffers.</p>
<p>And unconscious bias creeps back in.</p>
<h2>The AI Solution: Scale Quality, Eliminate Bias</h2>
<p>This year, I tried something different.</p>
<p>I built a system using Claude AI that helps me write consistent, thorough, unbiased performance reviews at scale—without losing the human judgment that makes them valuable.</p>
<p><strong>The result?</strong></p>
<ul>
<li>Time per review: <strong>90 minutes</strong> (down from 4-6 hours)</li>
<li>Consistency: <strong>100%</strong> (same structure and depth for everyone)</li>
<li>Bias reduction: <strong>Measurable improvement</strong> (more on this below)</li>
<li>Employee satisfaction: <strong>Noticeably higher</strong></li>
</ul>
<h2>The System: Structured Input, Consistent Output</h2>
<h3><strong>The Problem I Solved</strong></h3>
<p>Traditional performance review writing has two fundamental issues:</p>
<ol>
<li><strong>Unstructured input</strong> - Managers work from scattered notes, memories, and impressions</li>
<li><strong>Inconsistent output</strong> - Each review is written from scratch with different levels of detail and thought</li>
</ol>
<p>My AI-assisted system fixes both.</p>
<h3><strong>The Process</strong></h3>
<p><strong>Step 1: Structured Data Collection (I do this)</strong></p>
<p>I maintain a standardized template for each employee that captures:</p>
<p>markdown</p>
<pre><code class="language-markdown">## Employee Metadata
- Name, role, department
- Review period
- Performance level (I decide this)
- Lead/behavior level (I decide this)

## Business Objectives (3-5 per person)
- What was the goal? (from annual planning)
- How were they supposed to achieve it?
- What actually happened? (my assessment)
- Achievement level: Not Met / Partially Met / Fully Met / Exceeded

## Development Objectives
- What skills/certifications were they pursuing?
- What progress did they make?
- What training did they complete?

## Company Assessment Criteria (uploaded once)
- SMART objectives framework (PDF)
- WHAT assessment guide (PDF)
- HOW behavioral framework (PDF)
- Performance level definitions (PDF)

## Employee&#39;s Self-Submitted Review (from HR system)
- Their self-assessment (PDF)
- Their perspective on the year
</code></pre>
<p><strong>Key insight:</strong> I&#39;m not asking AI to <em>evaluate</em> the employee. I&#39;m providing my evaluation in structured form.</p>
<p><strong>Step 2: AI Processing (Claude does this)</strong></p>
<p>I feed this structured data to Claude with a detailed prompt that says:</p>
<blockquote>
<p>&quot;You are helping me write a performance review. I have already decided the performance levels and provided all my assessments. Your job is to:</p>
<ol>
<li>Write consistent, professional prose based on my inputs</li>
<li>Ensure each section follows company framework (SMART, WHAT/HOW)</li>
<li>Maintain the same depth and quality for every employee</li>
<li>Use specific examples I provided</li>
<li>Keep tone constructive and forward-looking</li>
<li>Follow the exact template structure</li>
</ol>
<p>Do NOT change my assessments. Do NOT add subjective opinions. Transform my structured data into polished review prose.&quot;</p>
</blockquote>
<p><strong>Step 3: Review and Refine (I do this)</strong></p>
<p>I review the AI-generated draft and:</p>
<ul>
<li>Verify accuracy of all facts</li>
<li>Add any missing context or nuance</li>
<li>Adjust tone where needed</li>
<li>Ensure it reflects my actual feedback</li>
</ul>
<p>This takes 30-45 minutes per person—a fraction of the original time.</p>
<p><strong>Step 4: Employee Meeting (I do this)</strong></p>
<p>The AI never replaces the human conversation. I still:</p>
<ul>
<li>Meet with each employee personally</li>
<li>Discuss the review face-to-face</li>
<li>Answer questions and provide context</li>
<li>Collaboratively set next year&#39;s goals</li>
</ul>
<p>In Part 2, I will explain how implementation works - and why it actually improves quality rather than diminishing it.</p>
]]></content:encoded>
            <category>review</category>
            <category>ai</category>
            <category>performance</category>
        </item>
        <item>
            <title><![CDATA[How I Use AI to Write Unbiased Performance Reviews at Scale - Part 2]]></title>
            <link>https://sandeeplamba.writizzy.blog/p/how-i-use-ai-to-write-unbiased-performance-reviews-at-scale-part-2</link>
            <guid>https://sandeeplamba.writizzy.blog/p/how-i-use-ai-to-write-unbiased-performance-reviews-at-scale-part-2</guid>
            <pubDate>Tue, 06 Jan 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Eliminating unconscious bias and scaling quality feedback across my entire team]]></description>
            <content:encoded><![CDATA[<p><em>Eliminating unconscious bias and scaling quality feedback across my entire team</em></p>
<h2>The Step-by-Step Implementation Guide</h2>
<p>Want to try this yourself? Here&#39;s exactly how to set it up:</p>
<h3><strong>Phase 1: Create Your Template (1-2 hours)</strong></h3>
<p>Below is the template that I created.</p>
<p>Dont give EMPLOYEE_IMPACT_LEVEL and EMPLOYEE_LEAD_LEVEL ratings and you can ask AI that based on the review what RATINGS an employee deserves.</p>
<p>You will be surprised that the result will be without biased and exactly what you thought without biasedness.</p>
<pre><code class="language-markdown"># Performance Review 2025 - **{{ EMPLOYEE_NAME }}**

## Employee Information
**Instructions:** Fill in the basic information below. This will auto-populate throughout the review.

- **EMPLOYEE_NAME**: EMPLOYEE_NAME
- **POSITION**: EMPLOYEE_POSITION
- **DEPARTMENT**: EMPLOYEE_DEPARTMENT
- **REVIEW_PERIOD**: [January 2025 - December 2025]
- **EMPLOYEE_IMPACT_LEVEL**: 
- **EMPLOYEE_LEAD_LEVEL**: 
- **PERFORMANCE_REVIEW**: 2025
- **COMPANY_SMART_PDF**: 01_SMART.pdf
- **COMPANY_WHAT_PDF**: 02_WHAT.pdf
- **COMPANY_HOW_PDF**: 03_HOW.pdf
- **COMPANY_PLD_PDF**: 04_PLD.pdf
- **EMPLOYEE_PERFORMANCE_REVIEW_PDF**: 05_EMPLOYEE_NAME_PR_2025.pdf

---
## Business Objectives

**Instructions:** For each objective, describe WHAT was to be achieved, HOW it was to be accomplished, and provide your evaluation comments with specific examples and outcomes.

### Objectives

**Reference Documents:**
- Review **{{ EMPLOYEE_PERFORMANCE_REVIEW_PDF }}** for objective assessment criteria under **Annual Business Objectives** inside the PDF

**Manager&#39;s Evaluation Comments:**
- Achievement Level: **{{ EMPLOYEE_IMPACT_LEVEL }}**

---
## Development Objectives

**Instructions:** Document professional development goals and progress.

### Objectives
**Reference Documents:**
- Review **{{ EMPLOYEE_PERFORMANCE_REVIEW_PDF }}** for objective assessment criteria under **Annual Development Objective** inside the PDF

**Manager&#39;s Evaluation Comments:**
- Achievement Level: **{{ EMPLOYEE_LEAD_LEVEL }}**

---
## Impact Assessment (WHAT)

**Instructions for Manager:** 
This section assesses the IMPACT the employee had on business objectives throughout the year.

**Reference Documents:**
- Review **{{ COMPANY_SMART_PDF }}** for objective assessment criteria
- Review **{{ COMPANY_WHAT_PDF }}** for guiding questions
- Review **{{ COMPANY_PLD_PDF }}** for level definitions
- Review **{{ EMPLOYEE_PERFORMANCE_REVIEW_PDF }}**

**Selected Impact Level:** **{{ EMPLOYEE_IMPACT_LEVEL }}**

**Impact Level Definition:**
[The system will auto-fill based on selection:]
- **Fully Meets Expectations:** Meets all expectations even in difficult context. Requires little to no additional direction to achieve the core goals of the role.
- **Mostly Meets Expectations:** Mostly meets standard objectives in a stable context. Achieves only part of core goals for the role.
- **Exceeds Expectations:** Over performs, even when objectives are stretched. Delivers beyond the scope of the role and succeeds even on additional missions or transverse actions.
- **Below Expectations:** Does not fulfill a majority of standard objectives in a stable context.

### Manager&#39;s Impact Assessment (WHAT)
**Instructions:** Write 5 professional sentences assessing **{{ EMPLOYEE_NAME }}**&#39;s yearly impact. Consider:
- What outcomes did they achieve across all objectives?
- What difficulties/enablers did they face?
- Did they reach defined targets and milestones?
- What are you most proud of in their achievements?
- How could they have had more impact?

**Your Assessment:**
[Write your 5-sentence assessment here - this will be AI-generated based on all inputs above]

---
## Lead@Company Implementation (HOW)

**Instructions for Manager:**
This section assesses HOW the employee worked - their behaviors, collaboration, and leadership approach throughout the year.

**Reference Documents:**
- Review **{{ COMPANY_HOW_PDF }}** for the three dimensions: THINK BIG, MAKE IT HAPPEN, TOGETHER
- Review **{{ COMPANY_PLD_PDF }}** for level definitions
- Review **{{ EMPLOYEE_PERFORMANCE_REVIEW_PDF }}**

**Selected Lead Level:** **{{ EMPLOYEE_LEAD_LEVEL }}**

**Lead Level Definition:**
[The system will auto-fill based on selection:]
- **Fully Meets Expectations:** Demonstrates the L@T behaviours consistently and actively seeks to develop their behaviours.
- **Mostly Meets Expectations:** Mostly demonstrates the L@T behaviours and engages in development actions to improve them.
- **Exceeds Expectations:** Acts as role model in L@T, seeks to develop themselves and others, and is involved in wider action plans.
- **Below Expectations:** Does not demonstrate the L@T behaviours and does not actively seek to develop themselves.

### Manager&#39;s Lead@Company Assessment (HOW)
**Instructions:** Write 4 professional sentences assessing **{{ EMPLOYEE_NAME }}**&#39;s behaviors and approach. Consider:

**THINK BIG:**
- How did they communicate purpose and vision?
- What innovative ideas did they propose?
- How did they handle complexity?

**MAKE IT HAPPEN:**
- How did they build trust and deliver results?
- How did they measure progress?
- What risks did they take?

**TOGETHER:**
- How did they contribute to team performance?
- How did they cooperate with others?
- How did they handle difficult situations?

**Your Assessment:**
[Write your 4-sentence assessment here - this will be AI-generated based on all inputs above]

---
## Workload Assessment

**Instructions for Manager:** Assess whether the workload was appropriate for achieving the defined objectives.

**Question:** Was **{{ EMPLOYEE_NAME }}**&#39;s workload compatible with achieving the defined objectives?

**Your Response:** [Select: Yes]

**Manager&#39;s Workload Evaluation:**
**Instructions:** Write 4 professional sentences addressing:
- Was the workload appropriate and balanced?
- Did they have adequate resources, time, and support?
- Were there any environmental factors (organizational changes, market conditions) that affected performance?
- How did they manage competing priorities?

**Your Assessment:**
[Write your 4-sentence assessment here - this will be AI-generated]

---
## Overall Evaluation

### Performance Summary
- **Impact (WHAT):** **{{ EMPLOYEE_IMPACT_LEVEL }}**
- **Lead (HOW):** **{{ EMPLOYEE_LEAD_LEVEL }}**

### Performance Level Definitions Applied

**Impact Level - {{ EMPLOYEE_IMPACT_LEVEL }}:**
- Manager Assessment - **{{ EMPLOYEE_IMPACT_LEVEL }}**.

**Lead Level - {{ EMPLOYEE_LEAD_LEVEL }}:**
- Manager Assessment - **{{ EMPLOYEE_LEAD_LEVEL }}**.

---
### Employee Self-Assessment Comment 

**Instructions for Employee:** Reflect on your year - achievements, challenges, growth, and future aspirations.

[Employee to complete this section:]

Review **{{ EMPLOYEE_PERFORMANCE_REVIEW_PDF }}** for Employee comment under **Employee Overall Input** inside the PDF

---
### Manager&#39;s Overall Evaluation

**Instructions for Manager:** Write 6 comprehensive sentences that synthesize the entire review. Structure your evaluation to:

1. **Start with strengths and achievements** - Lead with what they did well, using specific examples from objectives above
2. **Acknowledge their impact** - Highlight their most significant contributions to the team/organization
3. **Address development areas constructively** - Frame areas for growth as opportunities, not criticisms
4. **Provide concrete examples** - Reference specific situations, projects, or behaviors mentioned above
5. **Connect to feedback already given** - Ensure nothing here is a surprise; it should reflect ongoing conversations
6. **End with forward-looking focus** - Set the tone for next year with clear areas of focus or growth opportunities

**Use natural, authentic language** - Avoid corporate jargon. Write as you would speak to them directly.
**Balance recognition with development** - Make them feel valued while motivating continued growth.

**Your Overall Evaluation:**
[Write your 6-sentence overall evaluation here - this will be AI-generated based on all sections above]
</code></pre>
<h3><strong>Phase 2: Gather Company Documents (30 minutes)</strong></h3>
<p>Collect and digitize:</p>
<ul>
<li>Company performance framework (PDF)</li>
<li>Evaluation criteria (PDF)</li>
<li>Behavioral competency model (PDF)</li>
<li>Performance level definitions (PDF)</li>
</ul>
<p>These become your &quot;source of truth&quot; that AI references.</p>
<h3><strong>Phase 3: Create Your Prompt (1 hour)</strong></h3>
<p>Write a detailed prompt for your AI that includes previous prompt and company and employee reference documents.</p>
<p>Run this with help of below prompt one by one or together for all employees</p>
<pre><code class="language-javascript">You are helping me write performance reviews for my team.

CONTEXT:
- I manage [number] engineers in [department]
- Our company uses [framework name] for evaluations
- I have already decided all ratings and assessments

YOUR ROLE:
Transform my structured assessment data into polished 
performance review prose.

REQUIREMENTS:
1. Follow the exact template structure I provide
2. Use company framework from the PDFs I upload
3. Write in professional, constructive tone
4. Include all specific examples I provide
5. Maintain consistent depth (1500-1800 words)
6. Do NOT change my ratings or assessments
7. Do NOT add subjective opinions

OUTPUT:
A complete performance review ready for employee 
discussion, following our template exactly.
</code></pre>
<hr>
<h2>The Results: My First Year</h2>
<p>Here&#39;s what happened when I implemented this system for my 12-person team:</p>
<h3><strong>Time Savings</strong></h3>
<ul>
<li><strong>Before:</strong> 30+ hours writing reviews</li>
<li><strong>After:</strong> 5+ hours (total for all 12 people)</li>
<li><strong>Saved:</strong> 20 hours (nearly a 3 full work days!)</li>
</ul>
<h3><strong>Quality Improvements</strong></h3>
<ul>
<li>More specific examples in every review</li>
<li>Consistent depth across all team members</li>
<li>Better alignment with company framework</li>
<li>Fewer appeals or questions about ratings</li>
</ul>
<p>That last question is why I&#39;m writing this post.</p>
<hr>
<h2>The Ethics of AI-Assisted Reviews</h2>
<p>Let me address the elephant in the room: Is it ethical to use AI for something as important as performance reviews?</p>
<p>I believe the answer is yes—<strong>if done right</strong>.</p>
<p><strong>Here&#39;s my ethical framework:</strong></p>
<h3><strong>1. Transparency</strong></h3>
<p>I tell my team I use AI to help structure reviews. Most appreciate it—they see it as me investing in quality feedback.</p>
<h3><strong>2. Human Accountability</strong></h3>
<p>I am 100% responsible for every word in the review. AI is a tool, not a decision-maker.</p>
<h3><strong>3. Bias Reduction</strong></h3>
<p>Using AI has measurably reduced my unconscious bias. That&#39;s more ethical than pretending humans are perfectly fair.</p>
<h3><strong>4. Consistency as Fairness</strong></h3>
<p>Giving everyone the same level of attention and structure is fairer than favoring whoever I happen to remember most clearly.</p>
<h3><strong>5. Time for What Matters</strong></h3>
<p>Saving 30+ hours lets me spend more time:</p>
<ul>
<li>Having better 1:1 conversations</li>
<li>Mentoring and coaching</li>
<li>Observing and taking notes all year</li>
<li>Supporting career development</li>
</ul>
<hr>
<h2>Final Thoughts</h2>
<p>If you are writing biased reviews and didn&#39;t even know it.</p>
<p>With help of AI you can write fairer, more consistent reviews in a fraction of the time—and your team will appreciate the improvement.</p>
<p><strong>AI didn&#39;t replace manager’s judgment.</strong> It freed manager to apply his judgment more consistently and fairly to everyone on the team.</p>
<p><strong>AI didn&#39;t make reviews impersonal.</strong> It gave manager more time for the personal conversations that matter.</p>
<p><strong>AI didn&#39;t eliminate my responsibility.</strong> It helps manager to fulfill that responsibility better.</p>
<p>The technology is here. The question is: Will you use it to become a better manager?</p>
]]></content:encoded>
            <category>review</category>
            <category>ai</category>
            <category>performance</category>
        </item>
        <item>
            <title><![CDATA[Stealing]]></title>
            <link>https://sandeeplamba.writizzy.blog/p/stealing</link>
            <guid>https://sandeeplamba.writizzy.blog/p/stealing</guid>
            <pubDate>Fri, 02 Jan 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Theft isn’t just about objects. We steal personalities too.]]></description>
            <content:encoded><![CDATA[<p>Theft isn’t just about objects. People steal personalities too.</p>
<p>Society punishes material theft but ignores identity theft of the soul.</p>
<p>Material abundance may someday end object theft. Personality theft? Never.</p>
<p>When you steal personalities, you change yourself—subtly, daily, relentlessly. Over time, you transform so completely you no longer recognize who you are.</p>
<p>Don’t steal specially personalities. Stay authentic. Be unapologetically yourself.</p>
<p>An actor once said: “I can do everything with ease on the stage, whereas in real life I feel too big and clumsy.”</p>
<p>Don’t live as a character. Live as yourself.</p>
]]></content:encoded>
            <category>spiritualism</category>
        </item>
        <item>
            <title><![CDATA[Building a Market Intelligence Platform in 45 Minutes: From Claude Research]]></title>
            <link>https://sandeeplamba.writizzy.blog/p/building-a-market-intelligence-platform-in-45-minutes-from-claude-research</link>
            <guid>https://sandeeplamba.writizzy.blog/p/building-a-market-intelligence-platform-in-45-minutes-from-claude-research</guid>
            <pubDate>Fri, 02 Jan 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[I was going through some research prompts while reading some random article and found this prompt]]></description>
            <content:encoded><![CDATA[<p><strong>TL;DR</strong>: Used Claude&#39;s research mode to generate a 15-page IFE market analysis, then had Claude build a full Next.js website to visualize it—all in under an hour.</p>
<h2>The Problem: Information Overload</h2>
<p>Market research generates dense reports. My Claude research query on in-flight entertainment systems returned 15 pages of structured analysis covering oligopolies, financial metrics, competitive matrices, and regulatory frameworks. Valuable insights buried in walls of text.</p>
<p>Reading time: 2+ hours. Attention span: 15 minutes.</p>
<h2>The Solution: Automate the Presentation Layer</h2>
<p>Instead of manually building a dashboard, I meta-programmed the process:</p>
<h3>Step 1: Generate Research (11m 26s)</h3>
<pre><code class="language-javascript">Input: Market structure analysis prompt for IFE systems
Mode: Claude Web + Research
Output: Claude.pdf (15 pages, investor-grade dossier)
</code></pre>
<p>Key requirement: The prompt enforced strict sourcing rules—only primary filings (10-K, 20-F), regulatory documents, and verified tier-one research. Every metric traceable or tagged &quot;single-source (low confidence).&quot;</p>
<p>The prompt is like below. Please change the sector name to your sector name.</p>
<p>My sector name - <strong>In-flight entertainment (IFE) systems for commercial aviation</strong></p>
<pre><code class="language-yaml">## ROLE
Market-structure analyst for long-term investors. Produce an investor-grade, qualitative-first dossier.
Facts must be traceable and cross-verified. If evidence is weak, say so.

## INPUTS
sector = YOUR_SECTOR_NAME

## OBJECTIVE
Understand 
- how the sector is structured
- who the true players are, and 
- how competition works.

Deliver a 1-page executive overview + a full structured analysis with compact tables.

## ENFORCEMENT RULES (NO GUESSING)
Source bounds: 
- use only A–D. 
- If none available → write “Insufficient evidence.”

A) Primary filings/IR (10-K/20-F/URD/S-1, audited IFRS/GAAP, investor days, transcripts).
B) Regulators/statistics (industry regulators, national stats, IMF/OECD, BIS, etc.).
C) Official price lists, methodologies, technical specs, product catalogs, rulebooks.
D) Tier-one journals/consultancies with disclosed primary data; major data vendors with methodology.

### Verification
Any figure must be checked against ≥2 independent A–C sources → else tag “single-source (low confidence).”

### Uncertainty
If unsure → write “Unknown.” Do not estimate.

### Conflicts
If sources differ &gt;5% → show both, define scope/period, and explain likely cause.

### Recency
Prefer ≤24 months; older = “Legacy.”

### Citations
Bracketed footnotes [1], [2], mapping to a Source List (≤15 items).

## UNIT OF COMPETITION (MANDATORY) :
For the given sector, automatically identify:

1. Lanes = the 5 universal types of competition
(Only use those that exist in the sector.)
- Upstream Inputs / Extraction
- Core Production / Infrastructure / Operations
- Distribution / Access / Channels
- Data / IP / Standards / Certification
- Services / Wrap-around Support

2. Customer groups = the 5 universal buyer types
(Only use those that exist in the sector.)
- End consumers
- Enterprise/professional buyers
- Intermediaries/distributors
- Regulators/standards bodies
- Complementors/ecosystem partners

3. Define true peers per lane
- Do not compare players across unrelated lanes.

## OUTPUTS
A) Executive Overview (≤300 words)
- Sector structure, lanes, main players, differentiation, constraints, catalysts.

B) Player Atlas (qualitative)
- For every significant player in each lane:
- Legal/brand; ownership; geography in North America, Europe, Asia-Pacific
- Vertical scope (upstream → core → distribution → data/IP → services).
- Products/offerings.
- Customers served.
- Why customers choose them (price, quality, reliability, service, design, IP, network, availability, latency, brand, regulation, etc.).
- Pricing model.
- Market-design specifics (industry-dependent).
- Competitive stance (local monopoly, fragmented, oligopoly, global scale, niche).
- Moats: network effects, IP, scale, regulation, switching costs, ecosystem lock-in.
- Vulnerabilities: regulation, commoditization, disruption, outages, supply risk.

C) Peer Sheet — Normalized KPIs (per lane)
- Revenue/EBIT mix.
- Margin structure (EBITDA %, FCF conversion).
- ROCE/ROIC.
- Capex intensity.
- Pricing power indicators.
- Volume metrics relevant to the sector.
- Productivity/efficiency metrics.
- 10-year through-cycle resilience.

D) Moats &amp; Switching Analysis
- Lane-by-lane qualitative assessment.

E) Customer-Choice Narratives
- For each customer group: why they choose one supplier over another.

F) Regime, Regulation, &amp; Catalysts
- Regulatory constraints.
- Structural changes.
- M&amp;A patterns (10-year).
- Technology shifts.
- Macro drivers and risks.

G) Watchlist (5–8 items)
Key KPIs, catalysts, and risks to monitor.

## COMPARATIVE MATRICES (MANDATORY)
1) Players × Customer-Choice Drivers
(price, quality, service, network, distribution, IP, regulation, reliability, etc.)

2) Players × Moats/Frictions
(network effects, IP, scale economics, regulatory entrenchment, switching costs)

3) Lane-based cluster map
Shows true peers vs adjacent players.

## FORMAT
Do the following:
- 1-page Executive Overview
- Full Player Atlas &amp; Peer Sheet
- Two matrices + short narratives
- Appendices with
  - Assumptions
  - Methods, and
  - CSV-ready tables

## BEGIN
Do the following:
- Identify the lanes (from the universal categories).
- Map players into lanes; define true peers.
- Build Player Atlas.
- Populate Peer Sheet using evidence rules.
- Write customer-choice narratives + moat analysis.
- Add regime, catalysts, and watchlist.
- Deliver all sections.
</code></pre>
<h3>Step 2: Generate Instructions (5 minutes)</h3>
<p>Asked Claude to write deployment instructions for building a website from the PDF. The generated <code>instructions.md</code> specified:</p>
<ul>
<li><strong>Tech stack</strong>: Next.js 14 + TypeScript + Tailwind + shadcn/ui</li>
<li><strong>Architecture</strong>: 6 page routes with tabbed interfaces</li>
<li><strong>Component specs</strong>: DataTable with color coding, PlayerCard layouts, MatrixView visualizations</li>
<li><strong>Design system</strong>: Professional BI aesthetic with semantic color palette (green=strong, yellow=moderate, red=weak)</li>
<li><strong>Data modeling</strong>: TypeScript interfaces for players, metrics, and competitive matrices</li>
</ul>
<h3>Step 3: Build the Site (30-40 minutes)</h3>
<p>Dropped <code>instructions.md</code> into a new Cursor/Claude session. The AI generated:</p>
<ul>
<li>Responsive Next.js app with 6 main sections</li>
<li>Interactive data tables with sorting and color-coded cells</li>
<li>Tabbed player profiles (Panasonic, Thales, Viasat, Starlink, etc.)</li>
<li>Competitive heat maps showing moats and customer drivers</li>
<li>M&amp;A timeline visualization</li>
<li>KPI watchlist dashboard</li>
</ul>
<p><strong>Zero manual coding</strong>. Just iterative refinements through prompts.</p>
<p><a href="https://writizzy.b-cdn.net/blogs/4fec93fe-9559-4862-8883-0a4413006aaf/1767386182036-dbbqwni.png">Cursor Project looks like this</a></p>
<h2>Technical Highlights</h2>
<h3>Color-Coded Intelligence</h3>
<p>Tables use semantic colors automatically:</p>
<ul>
<li><code>●</code> (strong) → <code>bg-green-100 text-green-800</code></li>
<li><code>◐</code> (moderate) → <code>bg-yellow-100 text-yellow-800</code></li>
<li><code>○</code> (weak) → <code>bg-gray-100 text-gray-600</code></li>
</ul>
<h3>Data Fidelity</h3>
<p>The site preserves research rigor:</p>
<ul>
<li>&quot;Not Disclosed&quot; for missing data (never blank cells)</li>
<li>Asterisks for single-source estimates</li>
<li>Footnotes linking to verification sources</li>
<li>Currency timestamps (&quot;As of Q4 2024&quot;)</li>
</ul>
<h3>Mobile-First Tables</h3>
<p>Complex financial tables adapt responsively:</p>
<ul>
<li>Desktop: Full matrix view</li>
<li>Tablet: Horizontal scroll with sticky columns</li>
<li>Mobile: Card-based layout</li>
</ul>
<p><a href="https://writizzy.b-cdn.net/blogs/4fec93fe-9559-4862-8883-0a4413006aaf/1767386747942-b02ga95.png">Website Page-1</a></p>
<p><a href="https://writizzy.b-cdn.net/blogs/4fec93fe-9559-4862-8883-0a4413006aaf/1767386748312-pmbnvop.png">Website Page-2</a></p>
<h2>Why This Matters</h2>
<p>Traditional workflow:</p>
<h2>Workflow Comparison</h2>
<table>
<thead>
<tr>
<th>Phase</th>
<th>Traditional Workflow</th>
<th>Time</th>
<th>AI-Assisted Workflow</th>
<th>Time</th>
</tr>
</thead>
<tbody><tr>
<td><strong>Research</strong></td>
<td>Commission research</td>
<td>2 weeks</td>
<td>Claude research</td>
<td>12 minutes</td>
</tr>
<tr>
<td><strong>Analysis</strong></td>
<td>Analyst reads/synthesizes</td>
<td>8 hours</td>
<td>Generate site specs</td>
<td>5 minutes</td>
</tr>
<tr>
<td><strong>Design</strong></td>
<td>Designer creates deck</td>
<td>16 hours</td>
<td>—</td>
<td>—</td>
</tr>
<tr>
<td><strong>Development</strong></td>
<td>Developer builds dashboard</td>
<td>40+ hours</td>
<td>Claude builds site</td>
<td>40 minutes</td>
</tr>
<tr>
<td><strong>TOTAL</strong></td>
<td><strong>~80 person-hours</strong></td>
<td></td>
<td><strong>~1 hour</strong></td>
<td></td>
</tr>
<tr>
<td><strong>ROI</strong></td>
<td></td>
<td></td>
<td><strong>~64x time multiplier</strong></td>
<td></td>
</tr>
</tbody></table>
<h2>Results</h2>
<p>The deployed site includes:</p>
<ul>
<li>Executive overview with 6 key stat cards</li>
<li>Player atlas with detailed profiles for 8+ companies</li>
<li>Comparative matrices (Players × Moats, Players × Customer Drivers)</li>
<li>Interactive M&amp;A timeline (2015-2025)</li>
<li>Regulatory framework documentation</li>
<li>8-metric watchlist dashboard</li>
</ul>
<p>Run locally:</p>
<p>bash</p>
<pre><code class="language-bash">npm install &amp;&amp; npm run dev
</code></pre>
<h2>Universal Applications</h2>
<p>This approach works across multiple domains:</p>
<p><strong>Business Intelligence:</strong></p>
<ul>
<li>Competitive intelligence analysis (this example)</li>
<li>Product comparison platforms</li>
<li>Financial analysis dashboards</li>
</ul>
<p><strong>Knowledge Management:</strong></p>
<ul>
<li>Technical documentation portals</li>
<li>Educational course materials</li>
<li>Internal wiki systems</li>
</ul>
<h2>Adapt to Any Industry</h2>
<p>The research prompt is sector-agnostic. Simply modify the input:</p>
<pre><code class="language-javascript">sector = [Your Industry]
</code></pre>
<p><strong>Examples:</strong></p>
<ul>
<li>Cloud infrastructure providers</li>
<li>SaaS security tools</li>
<li>Industrial automation</li>
<li>Pharmaceutical manufacturing</li>
<li>Renewable energy storage</li>
</ul>
<p>The instruction template automatically adapts to your domain, generating appropriate data structures, visualizations, and competitive frameworks.</p>
<p><em>The future of technical work transcends code volume. It demands exceptional specification writing, intuitive information architecture, and the ability to distill complex data into clear visual narratives.</em></p>
<p>More on SDD(Spec Driven Design) in future blogs</p>
]]></content:encoded>
            <category>blog</category>
        </item>
    </channel>
</rss>