florianbonnet14/ThePowerOfAnalytics_ClaudeSkills / influential-factors-detective
influential-factors-detective
VerifiedIdentify and analyze qualitative factors that influence KPIs but can't be measured as numbers. Use when users need to find non-quantifiable drivers affecting metrics (like copy quality, design aesthetics, timing), plan A/B tests for subjective elements, bridge the gap between data and design/content decisions, understand why quantitative analysis is incomplete, optimize messaging or UX elements, or identify the actual levers to pull for improving KPIs at the leaf nodes of a KPI tree.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.6 KB |
| influential-factor-detective-tutorial.md | markdown | 2.3 KB |
| references/case-studies.md | markdown | 16.8 KB |
| references/common-factors.md | markdown | 10.3 KB |
| references/templates.md | markdown | 6.7 KB |
references/common-factors.md
View on GitHub# Common Influential Factors by Context
Comprehensive lists of frequently tested influential factors organized by business context.
## Email Marketing
### Subject Lines
- **Length:** Short (3-5 words) vs Medium (6-10) vs Long (11+)
- **Personalization:** Name, company, role, past behavior
- **Urgency:** Time-sensitive language vs evergreen
- **Curiosity:** Questions, incomplete thoughts, intrigue
- **Value proposition:** Benefit vs feature focused
- **Tone:** Formal vs casual vs playful
- **Numbers:** Including statistics vs avoiding them
- **Emojis:** Using vs not using, which ones
### From Name
- **Person vs company:** "John from Acme" vs "Acme Team"
- **Role clarity:** "CEO", "Support", generic
- **Personalization:** Sender name matching recipient relationship
### Preview Text
- **Relationship to subject:** Complementing vs repeating vs extending
- **Length:** Short vs utilizing full space
- **CTA inclusion:** Yes vs no
### Send Time
- **Time of day:** Early morning, mid-day, evening, night
- **Day of week:** Weekday patterns, weekend
- **Timezone:** Sender vs recipient timezone
- **Frequency:** Daily, weekly, monthly, triggered
### Email Body
- **Format:** Plain text vs HTML vs hybrid
- **Length:** Brief vs detailed
- **Image ratio:** Image-heavy vs text-heavy vs balanced
- **Personalization:** Dynamic content depth
- **CTA count:** Single vs multiple
- **CTA design:** Button vs link vs both
- **Social proof:** Customer logos, testimonials, statistics
---
## Landing Pages
### Headlines
- **Approach:** Benefit vs feature vs question vs statement
- **Length:** Short (5-7 words) vs long (10+)
- **Subheadline:** Present vs absent, approach
### Hero Section
- **Image type:** People, product, abstract, lifestyle
- **Media format:** Static image vs video vs animation
- **CTA prominence:** Size, color, position
- **Copy density:** Minimal vs comprehensive
### Social Proof
- **Type:** Testimonials, customer logos, statistics, ratings
- **Placement:** Top, middle, bottom, multiple locations
- **Credibility indicators:** Photos, names, companies, specifics
- **Format:** Quotes, carousel, grid, video
### Forms
- **Field count:** Minimal (2-3) vs standard (5-7) vs extensive (10+)
- **Field order:** Logical flow variations
- **Required indicators:** Asterisk, "(required)", none
- **Inline validation:** Real-time vs submit-time
- **Progressive disclosure:** All at once vs multi-step
- **Labels:** Above vs inline vs placeholder
### Trust Signals
- **Security badges:** SSL, payment processors, certifications
- **Guarantees:** Money-back, satisfaction, specific promises
- **Privacy statements:** Prominent vs standard
- **Third-party validation:** Awards, press mentions, associations
### Layout
- **Column structure:** Single vs multi-column
- **Visual hierarchy:** Primary CTA emphasis
- **White space:** Generous vs compact
- **Above-the-fold:** CTA visible vs scroll-required
---
## In-Product Experience
### Onboarding
- **Step count:** Minimal (1-3) vs standard (4-7) vs extensive (8+)
- **Information density:** Per step
- **Progress indication:** Steps, bar, percentage, none
- **Skip options:** Available vs required completion
- **Tutorial style:** Tooltips, modals, tours, video, none
- **Timing:** Immediate vs deferred vs just-in-time
### Empty States
- **Messaging tone:** Encouraging, informative, playful
- **Suggested actions:** Clear next steps vs exploration
- **Example content:** Show possibilities
- **Visual design:** Illustration vs text-only
### Feature Discovery
- **Method:** Tooltips, product tours, just-in-time, none
- **Trigger timing:** Immediate, after action, time-delayed
- **Dismissibility:** Permanent, temporary, persistent
- **Highlight style:** Overlay, pointer, subtle
### Navigation
- **Structure:** Hierarchical depth
- **Labels:** Feature names, benefit-focused, icons+text
- **Placement:** Top, side, hamburger
- **Search prominence:** Always visible vs hidden
### Notifications
- **Frequency:** Real-time, batched, digest
- **Tone:** Urgent vs informative vs friendly
- **Actionability:** Direct action vs informational
- **Channels:** In-app, email, push, SMS
- **Customization:** User control level
### Error Messages
- **Tone:** Technical vs plain language vs friendly
- **Specificity:** Generic vs detailed guidance
- **Resolution help:** How to fix prominently shown
- **Contact options:** Support visibility
---
## Checkout & Conversion Flows
### Form Design
- **Field count:** Minimize vs collect comprehensive data
- **Field labels:** Descriptive vs minimal
- **Error messages:** Inline vs summary vs both
- **Auto-fill support:** Address, payment, contact
- **Optional fields:** Clearly marked vs hidden
- **Field validation:** Real-time vs on submit
### Trust Elements
- **Security indicators:** Lock icons, SSL badge, secure checkout badge
- **Payment options:** Display all vs select-to-show
- **Return policy:** Prominent vs link vs hidden
- **Shipping information:** Upfront vs at checkout
- **Contact visibility:** Phone, chat, email prominence
### Friction Points
- **Account requirement:** Required vs optional vs guest
- **Guest checkout:** Prominent vs hidden
- **Registration timing:** Before vs after purchase
- **Save for later:** Available vs not
- **Coupon field:** Prominent vs collapsed vs hidden
### Progress Indication
- **Style:** Steps, bar, percentage, breadcrumbs
- **Detail level:** High-level (3 steps) vs granular (7+ steps)
- **Edit ability:** Can go back vs linear only
### Urgency & Scarcity
- **Stock indicators:** "Only X left", "Low stock", none
- **Time limits:** Countdown timers for offers
- **Social proof:** "X people viewing", "Y purchased today"
- **Abandoned cart:** Timing, discount inclusion, tone
### Payment Section
- **Order summary:** Always visible vs collapsible
- **Pricing breakdown:** Detailed vs simplified
- **Guarantee placement:** Near submit button
- **CTA text:** "Buy now" vs "Complete purchase" vs custom
---
## Content & Media
### Content Format
- **Primary medium:** Text, images, video, audio, interactive
- **Content depth:** Overview vs comprehensive vs deep-dive
- **Reading level:** Technical vs accessible vs beginner-friendly
- **Structure:** Linear vs modular vs choose-your-path
### Video Content
- **Length:** Short (<2 min) vs medium (2-5) vs long (5+)
- **Style:** Animated, live-action, screen recording, hybrid
- **Narration:** Voiceover, on-camera, text-only, none
- **Auto-play:** Yes vs no, muted vs audio
### Storytelling
- **Approach:** Data-driven, narrative, case study, comparison
- **Perspective:** First-person, third-person, customer voice
- **Examples:** Real companies, anonymized, hypothetical
### Personalization
- **Level:** Generic, name-only, role-based, behavior-based
- **Timing:** On visit, after action, time-based
- **Depth:** Surface-level vs deep customization
---
## Design Elements
### Typography
- **Font family:** Serif vs sans-serif vs monospace
- **Font size:** Hierarchical variations
- **Font weight:** Regular, medium, bold usage
- **Line height:** Tight vs comfortable vs spacious
- **Letter spacing:** Tight vs normal vs wide
### Color
- **Primary CTA color:** High contrast options
- **Color psychology:** Warm vs cool tones
- **Accessibility:** WCAG compliance level
- **Brand consistency:** Strict vs flexible
### Visual Hierarchy
- **Emphasis methods:** Size, color, weight, position
- **Contrast levels:** Subtle vs dramatic
- **Visual flow:** Z-pattern, F-pattern, custom
### Imagery
- **Type:** Photography, illustration, abstract, data viz
- **People:** Present vs absent, diverse representation
- **Style:** Realistic vs stylized vs minimalist
- **Relevance:** Product-focused vs lifestyle vs conceptual
### Buttons
- **Shape:** Rounded vs square vs pill
- **Size:** Small, medium, large, responsive
- **Text case:** Sentence case vs title case vs all caps
- **Icon inclusion:** Icon only, text only, both
### Spacing
- **Density:** Compact vs standard vs spacious
- **Section separation:** Clear breaks vs flowing
- **Margin/padding:** Proportional systems
---
## Timing & Sequencing
### Engagement Timing
- **First contact:** Immediate vs delayed vs behavior-triggered
- **Follow-up cadence:** Frequent vs spaced vs adaptive
- **Re-engagement:** After X days inactive
### Content Pacing
- **Information delivery:** All upfront vs progressive disclosure vs just-in-time
- **Tutorial length:** Compressed vs spread over time
- **Feature releases:** Big bang vs incremental
### Response Expectations
- **Support response time:** SLA display, expected wait time
- **Processing time:** For orders, requests, approvals
- **Loading states:** Estimated time, progress indication
---
## Positioning & Placement
### Page Placement
- **Above/below fold:** Critical elements visibility
- **Sidebar vs main:** Content prioritization
- **Header vs body vs footer:** Element placement
### Modal & Overlay Timing
- **Trigger:** Immediate, on action, exit intent, time-delay
- **Dismissibility:** Easy close vs required action
- **Frequency:** Every visit, once per session, once ever
### Navigation Placement
- **Primary nav:** Top, side, hidden hamburger
- **Search:** Always visible, in menu, prominent header
- **User menu:** Top right, dropdown, sidebar
### CTA Placement
- **Primary CTA:** Top only, bottom only, both, sticky
- **Secondary actions:** Prominence relative to primary
- **Multiple CTAs:** Same vs different actions
---
## Mobile-Specific
### Touch Targets
- **Size:** Minimum sizes, spacing
- **Placement:** Thumb-friendly zones
### Mobile Navigation
- **Style:** Hamburger, tab bar, hybrid
- **Depth:** Flat vs hierarchical
### Forms on Mobile
- **Input types:** Optimized keyboards
- **Field reduction:** Aggressive minimization
- **Auto-fill:** Mobile wallet integration
### Mobile Content
- **Image optimization:** File size vs quality
- **Video:** Auto-play policy, data warning
- **Reading experience:** Font size, line length
---
## Usage Notes
**Selecting Factors:**
- Start with factors specific to your business context
- Consider what you can realistically test given your traffic
- Prioritize factors that align with user feedback or data anomalies
**Combining Factors:**
- Test independently first to establish baselines
- Then test winning combinations
- Watch for interaction effects
**Context Matters:**
- What works in one context may not work in another
- Your audience, product, and brand all influence results
- Use these as starting points, not guarantees
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |