Skip to content

Lesson 31 of 34 · Module 9 · Sector lenses

Same macro driver, different sector maps

One driver, two sectors, same map — compare the paths.

One macro driver can mean different things in different sectors. A rise in the policy rate can help or hurt bank margins in different ways and can slow cement demand. A weaker rupee can lift textile export income and raise fertilizer or fuel input costs. This lab compares how the same driver plays out in two sectors on the same SOP, without ever creating a second process.

About 20 min · desk walk + key terms · Shark methodology

Do now: Practice on HBL Study Mode →

One macro driver can mean different things in different sectors. A rise in the policy rate can help or hurt bank margins in different ways and can slow cement demand. A weaker rupee can lift textile export income and raise fertilizer or fuel input costs. This lab compares how the same driver plays out in two sectors on the same SOP, without ever creating a second process.

After this lesson, you can…

  • ✓Explain same macro driver, different sector maps in plain words
  • ✓Apply the idea to one real PSX company
  • ✓Recognise the most common beginner mistake

Visual mental model

A calm learning loop

  1. 1

    Understand

    One driver, two sectors, same map — compare the paths.

  2. 2

    Check

    What did this lesson train?

  3. 3

    Apply

    Use one real desk or calculator

Move from explanation to evidence, then practice.

Key knowledge

Terms you will use on the desk

Peer check
Same-sector desks — still not a ranking tip list.

sector compare — study, not tip

This lab trains sector compare on a live desk. Write dated evidence, refuse undated tip calendars, and keep scenario weights as business-path opinion — never as % chance the price moves.

In-depth teaching

5 sections

01

Pick one macro driver, then read it through two lenses

Choose a single macro driver such as the policy interest rate, the PKR to USD rate, coal or gas prices, or oil prices. Then choose two sectors from the lenses you have studied, for example banks and cement, or textile and fertilizer. The aim is to write how that one driver reaches each sector's drivers, not to predict where the driver goes.

Write it as two short chains. For banks and a rate rise: rate change, asset and liability repricing, net interest margin, plus possible stress on borrowers. For cement and a rate rise: higher borrowing cost, slower construction projects, lower volumes, and higher finance cost. Same driver, different chain, and the chains point at different lines in Books and Filings.

02

Compare the paths: where the maps diverge

With two sector maps in front of you, compare bull, base, and bear business paths side by side. Where does the same macro move help one sector and hurt the other? Where does it hit both, but through different lines? For example, a weaker rupee might lift export revenue for a textile mill, while raising imported coal or feedstock cost for a manufacturer in another sector.

Also compare falsifiers and exit. Falsifiers differ because the evidence lives in different places: provisions for banks, volumes and costs for cement, energy and working capital for textile, gas notes for fertilizer. Liquidity may differ too, as large banks are typically easier to exit than smaller industrial names. Write these differences in plain words rather than ranking sectors.

Pause and predict · free

Getting check ready…

A forward map is…

03

Worked mini-example: policy rate across HBL and LUCK

Open HBL and LUCK. For HBL, write: 'A rate rise may lift earning yields on assets, but deposit costs also move; the net effect depends on repricing; asset quality may be tested if borrowers struggle; evidence: interest income and expense lines, provisions.' For LUCK, write: 'A rate rise raises finance cost if debt is floating and may slow construction demand; evidence: finance cost, volumes, debt trend.'

Now add your own opinion weights for each map's bear path as a teaching exercise, with one sentence of rationale. You may find the same macro move deserves a higher bear weight in one sector than the other. You are not forecasting rates, and you are not saying one sector is better. You are showing that the macro driver has no single meaning until read through each business.

04

Second pair: PKR across NML and FFC

Repeat with a currency driver. For NML, a textile exporter, write: 'A weaker rupee may raise rupee value of export sales, but imported inputs and dollar-linked debt can cost more; evidence: export share, cost of sales, foreign currency borrowings in notes.' For FFC, a fertilizer producer, write: 'Gas is domestically priced under regulated arrangements, so currency effects may be indirect, through imported equipment, financing, or product price policy; evidence: notes and Filings.'

If you do not know how a driver reaches a company, write unknown and list where you would look. That is a legitimate result. The goal of this second pair is to catch the habit of reusing a slogan like 'weak rupee helps exporters' without checking the company's actual mix of revenue and costs.

05

Tip-culture trap, and the fork

The trap is the one-line macro slogan: 'rates up, banks win' or 'rupee down, exporters win'. These slogans are attractive because they feel like insider logic, but they skip the company's own balance sheet and notes. A single slogan applied to every name in a sector is the opposite of homework.

Wait means you cannot trace the driver to specific lines in each company's Books or Filings. Need evidence means the chain is plausible but a key note or number is missing. Broker talk still requires each company's own complete forward map; the comparison only highlights differences. No sector gets a free pass, and no macro driver replaces the company-level map.

Check your understanding · free

Getting check ready…

Scenario weights mean…

Scar · refuse this

Trap: Assuming one macro driver means the same thing for every sector.

Refuse: Refuse 'rates up = all banks win' or 'PKR weak = all exporters win'.

Rate hike: banks (NIM path) vs cement (demand path). PKR weak: textile (export) vs fertilizer (gas cost).

Required lab

Do this on the desk now

  • Pick policy rate. Compare HBL (banks) vs LUCK (cement) on NIM vs demand path.

    Done when: Two sector maps with same driver, different paths written

    Open →
  • Pick PKR/USD. Compare NML (textile export) vs FFC (fertilizer gas cost).

    Done when: Two sector maps with same driver, different paths written

    Open →

Lab · Forward map

Build your map: drivers, catalysts, BBB, falsifiers, exit, decision.

Practice on HBL Study Mode →

Loading forward map lab…

Or practice on live desk with Study ModeOpen HBL Study Mode

Failed map examples — learn from scars

Real mistakes that fail the validator. See the error, understand the fix.

These are real beginner mistakes that the MapValidator catches. Study them so you don't repeat them.

PROPHECY

Prophecy Language in Rationale

HBL · 5 error(s)

▼

❌ Failed map — 5 validation errors

drivers: [ "Net interest margin", "Asset quality" ]
catalysts: [ { "event": "Q3 results", "whenOrUnknown": "2024-10-24" } ]
scenarios: { "bull": "Stock will go up 20% after clean results", "base": "Price will stay range-bound", "bear": "Will drop 15% if provisions spike" }
scenarioWeights: { "bull": 60, "base": 30, "bear": 10 }
weightsRationale: HBL will go up because provisions are normalizing and NIM is strong. Target 200.
falsifiers: [ "Market crashes", "Bad news" ]
liquidityExit: HBL is liquid
decision: broker_talk
  • Rationale contains prophecy: 'will go up', 'target 200'
  • Scenarios describe price targets, not business paths
  • Weights reflect price odds (60/30/10), not business path opinions
  • Falsifiers are vague ('market crashes')
  • Decision 'broker_talk' without completing evidence steps
💡 Teaching note

Prophecy veto is automatic. Every field must describe business paths, not price predictions. Weights are your opinion on business outcomes — not % chance price moves.

VAGUE-FALSIFIER

Vague Falsifiers

FFC · 4 error(s)

▼

❌ Failed map — 4 validation errors

drivers: [ "Gas cost", "Volumes" ]
catalysts: [ { "event": "Gas price notification", "whenOrUnknown": "unknown" } ]
scenarios: { "bull": "Gas manageable, volumes hold", "base": "Normal agri cycle", "bear": "Things go wrong" }
scenarioWeights: { "bull": 30, "base": 50, "bear": 20 }
weightsRationale: Base case until something changes
falsifiers: [ "Market crashes", "Economy gets bad", "Bad news" ]
liquidityExit: FFC is liquid
decision: need_evidence
  • Falsifiers are generic ('market crashes', 'economy gets bad') — not checkable
  • Bear scenario 'things go wrong' is not a business path
  • Weights rationale 'until something changes' is not a working case explanation
  • Catalyst 'unknown' without falsifier for 'no gas notification in 90 days'
💡 Teaching note

Falsifiers must be specific, dated, and checkable: filing events, book lines, governance signals. 'Market crashes' is lazy — name the filing or book line that kills your base case.

WEIGHT-ERROR

Weights Don't Sum to 100

LUCK · 3 error(s)

▼

❌ Failed map — 3 validation errors

drivers: [ "Cement demand", "Coal cost" ]
catalysts: [ { "event": "APCMA dispatch data", "whenOrUnknown": "monthly" } ]
scenarios: { "bull": "Demand up, coal stable", "base": "Normal cycle", "bear": "Cost shock" }
scenarioWeights: { "bull": 40, "base": 40, "bear": 30 }
weightsRationale: Bullish on demand
falsifiers: [ "Coal spike", "Demand drop" ]
liquidityExit: LUCK liquid
decision: broker_talk
  • Weights sum to 110 (40+40+30), not 100
  • Decision 'broker_talk' with invalid weights
  • Rationale 'bullish on demand' doesn't explain base/bear weights
💡 Teaching note

Weights must sum to exactly 100. The validator catches this automatically. Your rationale must explain why base is the working case, not just 'bullish on X'.

MISSING-DRIVER

Missing Key Driver (Circular Debt)

OGDC · 4 error(s)

▼

❌ Failed map — 4 validation errors

drivers: [ "Oil price", "Production volumes" ]
catalysts: [ { "event": "Monthly production data", "whenOrUnknown": "monthly" } ]
scenarios: { "bull": "Oil up, production up", "base": "Stable", "bear": "Oil down" }
scenarioWeights: { "bull": 30, "base": 50, "bear": 20 }
weightsRationale: Oil price drives everything
falsifiers: [ "Oil crash", "Production drop" ]
liquidityExit: OGDC liquid
decision: need_evidence
  • Missing critical driver: circular debt receivables / cash collection
  • OGDC is an E&P — cash collection from refineries is the real driver, not just oil price
  • Falsifiers don't mention receivables aging or government payment delays
  • Liquidity exit ignores that OGDC shares can be thin in panic
💡 Teaching note

Every sector has hidden drivers. For E&P: cash collection = production × price × collection rate. Missing receivables driver = incomplete map. Always ask: 'What kills cash flow even if price is good?'

NO-EXIT

No Exit Plan for Thin Name

THIN · 4 error(s)

▼

❌ Failed map — 4 validation errors

drivers: [ "Unknown — need filings" ]
catalysts: [ { "event": "None known", "whenOrUnknown": "unknown" } ]
scenarios: { "bull": "Could be anything", "base": "Wait and see", "bear": "Risks everywhere" }
scenarioWeights: { "bull": 10, "base": 20, "bear": 70 }
weightsRationale: Too many unknowns
falsifiers: [ "Any bad news" ]
liquidityExit: Will figure out later
decision: broker_talk
  • Liquidity exit 'will figure out later' is not a plan
  • Decision 'broker_talk' on thin data with no exit = dangerous
  • Drivers 'unknown' but decision not 'wait'
  • No lot size, volume, or free float analysis
💡 Teaching note

Thin data → Wait is the only valid decision. If you don't know lot size, volume, and free float, you cannot size a position. 'Broker talk' on unknown liquidity = gambling.

THIN-DATA-INVENTED

Inventing Numbers on Thin Coverage

THIN · 4 error(s)

▼

❌ Failed map — 4 validation errors

drivers: [ "Revenue growth 15%", "Margins expanding" ]
catalysts: [ { "event": "Next quarter results", "whenOrUnknown": "2024-12-15" } ]
scenarios: { "bull": "Growth continues", "base": "Stable", "bear": "Slowdown" }
scenarioWeights: { "bull": 40, "base": 40, "bear": 20 }
weightsRationale: Management guided growth
falsifiers: [ "Results miss" ]
liquidityExit: Assume liquid
decision: need_evidence
  • Drivers invented ('Revenue growth 15%') — Books are empty, no data to support
  • Catalyst date invented — no filing confirms Dec 15
  • Weights reflect optimism, not evidence
  • Liquidity exit 'assume liquid' on unknown name = dangerous
💡 Teaching note

Thin coverage → Wait. Honesty beats invented drivers. If Books are empty, write 'unknown — need filings/books'. Never invent numbers to make a map look complete.

What you can say now

Evaluation language — not a price call.

  • →I can brief this name: drivers, catalysts, business paths, falsifiers, exit, decision.
  • →I can evaluate a prediction claim: where is the evidence, and what would prove it wrong?
  • →I still refuse price targets and up/down odds — judgment, not prophecy.

Worth keeping

  • Veterans keep scars next to every step.
  • A complete map still is not a price call.
  • A floating-rate loan reacts to policy rate changes faster than a fixed-rate loan, so debt structure matters.
  • The same exchange rate move can raise revenue and cost at once, so net effects need both sides of the account.

Write Wait when evidence is thin — that is skill, not weakness.

Try it on a live desk

Practice · support fades as you go

Practice with support

Write Wait when evidence is thin — that is skill, not weakness.

Need a hint?

A scar-backed habit on the live desk — not a tip.

Done when: You can explain what you checked and what remains uncertain.

Now without hints

Try it independently

What did this lesson train?

A strong answer: A scar-backed habit on the live desk — not a tip.

Lesson FAQ

What did this lesson train?

A scar-backed habit on the live desk — not a tip.

Does a strong map mean buy?

No. It means homework. Decision may still be Wait.

Are weights price odds?

No. They are opinion on business paths only.

Is this lab telling me which sector to pick?

No. It shows that one macro driver can have different effects across sectors, and trains you to trace the driver to company-level evidence.

What if I cannot find how a driver reaches a company?

Write unknown and list where you would look, such as notes, Filings, or sector literacy pages. Unknown is a valid, honest entry.

Mark this lesson complete

What did this lesson train?

Show calm answer

A scar-backed habit on the live desk — not a tip.

A scar-backed habit on the live desk — not a tip.

Tick every required lab step above before you mark complete.

Sign in before completing lessons if you want them counted toward the certificate.

Optional: graded test (sign-in)

Member lesson tools

Full lesson test & member tools

Checking sign-in…

Ask coach

Locked

Ask: review my map gaps

Share drivers and falsifiers — coach checks process.

Sign in to unlock →

Stay on the course path

Follow the Shark Methodology path. How-tos and metrics are optional reference.

  • Shark Methodology course

    Main beginner path: evidence, forward maps, and evaluating claims — not competing starts.

  • Learn PSX hub

    Start Lesson 1, then optional guides and tools when you need them.

  • PSX today

    Pakistan stock market today in plain words - breadth, gainers, losers.

  • PSX companies list

    Browse all Pakistan Stock Exchange listed companies by name or sector.

  • KSE 100 index today

    Educational constituent board - not the official index level on psx.com.pk.

  • PSX gainers today

    Biggest % rises among ordinary listed shares - homework, not a buy list.