HasanJaffal.com — Writing Guide

AI will not fix weak operations. It will expose them.

1. Website Purpose

The website exists to help professionals understand:

How AI changes operational work
How organizations fail to use AI correctly
How risk and analytics should drive action
How workers can adapt to survive and create value in the AI era

The website is NOT:

Generic AI news
Coding education
Startup advice
Productivity content
Motivational content
Consultant-style transformation content

Focus areas: AI, operations, risk, analytics, decision-making, organizational failure, and AI-era career adaptation.

2. Primary Audience

Primary readers:

Professionals worried AI may replace their work
Managers adopting AI into operations
Executives trying to understand operational AI risk
Analytics professionals
Operations leaders
Risk and fraud professionals

Audience sophistication mix:

Segment	%
Beginners	20%
AI-aware professionals	50%
Advanced operators	30%

Target geography: United States, Europe.

3. Reader Transformation

The reader should evolve: from passive information worker → to operational decision-maker in the AI era.

Readers should leave with: urgency, clarity, empowerment.

4. Content Priorities

Priority order (highest first):

Newsletter subscriptions
Backlinks
Traffic
Authority
Conversion
Shares
Engagement
Search ranking

The site optimizes primarily for search discoverability and newsletter growth.

5. Core Positions

AI-DECISION-OPERATIONS

Statement: AI exposes weak operations and slow decisions.

Description: AI increases the speed of signals, but weak organizations still fail to act. Detection without ownership, authority, and escalation creates faster chaos, not better execution.

RISK-INTELLIGENCE

Statement: Reporting explains the past. Intelligence changes what happens next.

Description: Most dashboards create visibility without intervention. If metrics do not trigger action, accountability, or escalation, they are operational decoration.

AI-JOB-RISK

Statement: AI is replacing low-judgment work and raising the value of decision ownership.

Description: The most exposed roles are built around reporting, routing, and repetitive information work. The safer path is judgment, trade-off management, escalation authority, and contextual decisions.

6. Layer 2 Topics

AI-DECISION-OPERATIONS Topics

AI Theater
Fake AI Transformation
Slow Decision Cultures
AI Accountability Vacuum
Automation Failure Loops
Human Bottleneck Myth
AI Governance Bureaucracy
Meeting-Driven Operations
Escalation Collapse
Operational Cowardice

Core conflict: AI exposes organizational weakness faster than humans ever did.

RISK-INTELLIGENCE Topics

Dashboard Addiction
KPI Theater
Reporting Bureaucracy
Alert Spam
Data Without Ownership
False Confidence Metrics
Vanity Analytics
Intelligence vs Reporting
Data Team Irrelevance
Metric Manipulation

Core conflict: Most analytics teams produce reporting, not intelligence.

AI-JOB-RISK Topics

White-Collar Automation
Fake AI Safety Advice
Productivity Trap
Middle Management Exposure
The Collapse of Busy Work
Prompt Engineer Hype
Knowledge Worker Oversupply
Credential Irrelevance
AI Career Delusion
The Death of Information Work

Core conflict: Most professionals are underestimating how exposed they are.

7. Article Archetypes

Every article must fit one archetype:

#	Archetype	Description	Example
1	Contrarian Opinion	Attack a common belief	“Most AI Transformations Are Expensive Theater”
2	Framework / How-To	Provide operational guidance	“How to Build AI Escalation Paths That Actually Work”
3	Operational Breakdown	Analyze a real or fictional operational failure	“The Dashboard Was Green. The Operation Was Failing.”
4	Prediction / Future Risk	Predict organizational or workforce shifts	“Middle Management Will Shrink Faster Than Most Executives Expect”

8. Article Structure

Length: 500–600 words

Qualities: Short paragraphs, highly scannable, conversational, emotionally provocative, strategically useful.

Structure:

Hook
Key takeaway
Tension
Consequence
Recommendation
Forced-position question
CTA

Example opening:

“The dashboard looked healthy. That was the problem.”

9. Conversational Writing Rules

Write like speaking naturally.

Rules:

Use contractions
Use simple language
Ask questions
Use “you”
Inject personality
Use dry sarcasm and dark workplace humor
Sound like an operator-strategist
Avoid sounding academic
Avoid sounding like polished corporate marketing

The writing should feel: human, direct, slightly imperfect, thoughtful, sharp.

10. Controlled Imperfection Rules

The content must not sound over-optimized.

Allowed:

Occasional repetition
Abrupt paragraphs
Incomplete transitions
Blunt statements
Asymmetry
Slightly messy conversational flow

Avoid:

Perfect rhythm everywhere
Over-structured prose
Excessive polish
Sounding like a professional ghostwriter
AI-generated “smoothness”

The writer is sharing operational thinking, not performing literature.

11. Writing Techniques

Use these frequently:

Contrast
Metaphors & Analogies
Imagery
Strong verbs
Repetition
Foreshadowing
Pattern interrupts
Narrative hooks
Open loops
Tension escalation
Short punch sentences
Counterintuitive claims
Story framing
Forced choice questions

The writing should contain: memorable lines, screenshot-worthy phrases, emotionally sharp statements.

12. Signature Beliefs

Recurring beliefs (repeat naturally across articles):

Visibility is not action.
AI exposes weak management.
Busy work is disappearing.
Dashboards delay accountability.
Reporting is not intelligence.
Automation scales weak processes.
AI increases signal speed faster than organizations can react.

13. Signature Metaphors

Use recurring operational metaphors:

Radar systems
Pressure leaks
Digital battlefields
Mission control
Tripwires
Chain reactions
Fault lines
Black boxes
Traffic jams
Wildfire spread

14. Brand Voice

Voice identity: Strategist, operator, sharp observer.

Tone: Provocative, emotionally charged, conversational, direct, humorous at times, aggressive toward weak thinking.

Allowed criticism targets: Consultants, BI teams, reporting bureaucracy, AI theater, meeting culture.

15. SEO Rules

Every article must include:

1 primary keyword
2–3 secondary keywords

Optimization level: Moderate.

Target: High-volume discoverable topics that still fit positioning.

Example keywords:

AI replacing jobs
AI in operations
Dashboard failures
Operational risk analytics
AI automation risks

SEO formatting:

Many subheadings
Short paragraphs
Lists frequently
Strong title structure
Keyword in title, intro, and at least one subheading

Title structure: SEO + curiosity hybrid.

Example: “AI Is Replacing Reporting Jobs Faster Than Most Analysts Expect”

15A. AI-Agent Visibility & Citation Strategy

The website should be easy for AI agents, AI search systems, and language models to understand, summarize, and reference.

Goals:

Easy to parse
Easy to summarize
Easy to cite
Easy to trust
Structurally useful for AI-generated answers

15B. Answer-First Content Structure

Every article should include a concise answer block near the top.

Length: 40–60 words.

Purpose: Help AI systems extract a direct answer quickly.

Example:

“AI replaces work when tasks are repetitive, rules-based, and disconnected from judgment. The safest professionals move closer to decisions, escalation, business context, and operational ownership.”

Rules: Clear language, no fluff, directly answer the article topic, keyword naturally included.

Placement: After the hook, before deeper analysis.

15C. Concept Definitions

The website should repeatedly define core concepts clearly and consistently:

AI Decision Operations
Risk Intelligence
Dashboard Theater
Reporting Bureaucracy
Signal-to-Action Gap
AI Job Risk
Decision Ownership
KPI Theater

Rules: Definitions stay consistent across articles. Avoid changing terminology. Repeat key phrases naturally. Create recognizable intellectual frameworks.

15D. Structured Article Sections

Articles should use predictable structures:

What It Means
Why It Matters
Example
Common Mistake
What To Do
Related Concepts

Not every article needs all sections, but structure should remain recognizable.

15E. Structured Data & Metadata

Every article should implement:

Article Schema
FAQ Schema (when relevant)
Author metadata
Publish/update dates
Category metadata
Related article metadata

15F. External References & Credibility Signals

Every article should ideally include:

One external study, operational report, AI adoption reference, or public event/news source

Preferred sources: Workforce reports, AI adoption studies, operational failures, layoffs, governance failures, automation incidents, public company decisions.

The website should feel: Opinionated but evidence-aware.

15G. Source-Worthy Assets

Pages designed to become reference material:

AI Job Risk Index
Dashboard Failure Checklist
Reporting vs Intelligence Framework
AI Operations Failure Patterns
Decision Ownership Model
Operational Escalation Framework
AI Adoption Failure Checklist

These pages should: define concepts, include tables, use concise explanations, contain frameworks, be heavily internally linked.

15H. Tables & Comparison Blocks

Articles should regularly include concise comparison tables:

vs.
Reporting	Intelligence
Dashboard	Decision System
Automation	Ownership
Busy Work	Decision Work
AI Output	Human Judgment

Tables should be: short, scannable, operational, keyword-aligned.

15I. AI Crawlability Rules

Do not block:

OpenAI crawlers
AI search crawlers
Search engine AI indexing systems

Public articles should remain crawlable, indexable, and accessible.

15J. AI-Friendly Writing Rules

Define terms clearly
Avoid ambiguous wording
Use descriptive headings
Use concise summaries
Maintain consistent terminology
Use operational examples
Avoid excessive abstraction

Goal: Human clarity first, machine readability second.

15K. AI Citation Optimization Checklist

Before publishing:

16. Internal Linking Rules

Minimum: 2 internal links per article.

Recommended:

1 link to related article
1 link to relevant tool

Internal links should connect: same position, related topic, supporting framework.

17. External References

Every article should ideally include:

One external reference (study, news event, or credible quote)

Preferred sources: Operational AI failures, layoffs, workforce studies, AI adoption reports, organizational case studies.

18. Fictional Examples

Allowed: Fictional companies, managers, incidents, meetings, operational failures.

Do not repeat the same characters. Examples should feel realistic and operational.

19. Formatting Rules

Use:

Subheadings heavily
Pull quotes
Key takeaway boxes
Bullet lists
Short paragraphs

Avoid:

Dense text blocks
Giant paragraphs
Excessive bolding
Corporate formatting

Bold usage: Minimal.

20. CTA Rules

Preferred CTA: Newsletter subscription.

Newsletter promise:

“Weekly writing on AI, risk, and decisions. How to use AI in operations and risk — and how AI is reshaping the skills that matter at work.”

Secondary CTAs: Use a tool, read another article.

21. Content Mix

Type	%
High confrontation	20%
Practical insight	40%
Predictive	20%
Humor / light operational observations	20%

22. Duplication Prevention Rules

Do NOT publish if:

Same position already covered
Same topic already covered
Same keyword already targeted
Same argument already exists
Same angle already exists

If overlap exists: force a new angle. Do not create near-duplicate content.

23. Forbidden Content

Do not write:

Coding tutorials
Generic AI news
Generic productivity advice
Startup content
Motivational content
Generic leadership content
“AI will change everything” fluff
Buzzword-heavy corporate writing

Forbidden phrases:

leverage
unlock
digital transformation
revolutionary
synergize
game changer
AI-powered solution

24. Editorial Quality Checklist

Before publishing:

If not: Regenerate.