Skip to content

Lesson 18 of 34 · Module 6 · Shark forward map

Bull, base, bear - business paths and weights

Weights are opinion on the shop’s path - never % chance the price moves.

Bull, base, and bear are stories about the business, not guesses about the share price. You write three paths for what the shop might do, then you weight them as opinion, for example 20, 50, and 30, and you write why. These numbers are never odds that the price will go up or down, and the lab refuses any wording that treats them that way.

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

Do now: Practice on LUCK Study Mode →

Bull, base, and bear are stories about the business, not guesses about the share price. You write three paths for what the shop might do, then you weight them as opinion, for example 20, 50, and 30, and you write why. These numbers are never odds that the price will go up or down, and the lab refuses any wording that treats them that way.

After this lesson, you can…

  • ✓Explain bull, base, bear - business paths and weights 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

    Weights are opinion on the shop’s path - never % chance the price moves.

  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

Business path
Story about volumes/costs/cash — not a target price line.
Weights
Opinion on paths summing to 100 — not up/down odds.

bull / base / bear — study, not tip

This lab trains bull / base / bear 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

Three business paths, not three price levels

A scenario is a coherent story about the business over a stated horizon. The bull path describes a stronger outcome for drivers, the base path describes what you consider most plausible given the evidence, and the bear path describes a weaker outcome. Each path must talk about volumes, costs, cash, asset quality, or leverage, which are the things the company controls or experiences, not about where the price will land.

If your three lines differ only by a target price, start over. A good test is whether each path could be checked against Books and Filings later. For example, a teaching bear path for a cement name might say 'local demand stays weak and coal costs stay high, so margins shrink and operating cash falls', which you could later see in the numbers. A path that only says 'price falls' contains no business information.

02

Weights as opinion, summing to 100

After writing the paths, you assign opinion weights that sum to 100, for instance 20 for bull, 50 for base, and 30 for bear. The weights express how much of your attention and caution each business path deserves given your evidence. They are not probabilities that the share price goes up or down, and they are not forecasts of returns. Think of them as a way to say 'I find the base case most plausible but I will not ignore the bear case'.

Write one line of rationale for the weights, for example 'bear weighted higher because Books show cash conversion falling'. Leave room for pain: a map with 0 weight on the bear path is usually a wish. Also avoid fake precision. Weights like 37.5 percent suggest measurement that does not exist. Round numbers are honest about the fuzziness of opinion.

Pause and predict · free

Getting check ready…

A forward map is…

03

Worked mini-example: LUCK in three paths

Take LUCK as a teaching example. Open the desk, check as_of, and read Books for sales, profit, and operating cash across periods. A teaching bull path: 'domestic and export volumes improve and energy costs ease, so margins widen and operating cash covers debt service comfortably.' A base path: 'volumes roughly flat, costs roughly stable, margins hold.' A bear path: 'demand softens and coal and freight costs rise, so margins shrink and leverage looks heavier.'

Now weights: perhaps 20, 50, and 30, with the rationale 'recent Books show stable margins, but cost pressure is a visible risk'. Note what is absent: there is no price in any of these lines. The map does not say LUCK will go up. It says what the business might experience and how seriously you take each path. If someone asks 'so is it a buy?', the honest answer is that the map is homework, and the decision may still be Wait.

04

Scoring yourself: do not grade against the print

It is tempting to judge a scenario weight later by what the price did: 'I said 20 percent bull and the price went up, so I was wrong'. That is the wrong test. The question is whether the business path matched the numbers that arrived, and whether your reasons were sound given the evidence at the time. A good process can have a bad outcome, and a bad process can have a lucky one.

Keep a short log: date, paths, weights, rationale, and later what the filings showed. Over months you will see which kinds of drivers you tend to over- or under-weight. That feedback is about your reasoning, not about the market's mood, and it is the real benefit of the exercise. The map is a thinking tool, so keep it honest rather than impressive.

05

Tip-culture trap: fake precision odds, and the fork

The scar is writing '70 percent up, 30 percent down'. Tip rooms love fake precision because a number sounds scientific, but nobody can honestly assign such odds, and a number with no method behind it is decoration. The lab refuses any up-or-down percentage control. If your own wording drifts into price odds, rewrite the line as a business path.

Wait means you cannot write three distinct business paths from the evidence, or weights have no rationale. Need evidence means the paths are written but some depend on Books or Filings you have not found. Broker talk requires a full forward map with drivers, catalysts, scenarios, falsifiers, and exit, and even then it remains a discussion, not a forecast. A good scenario page often ends in Wait, and that is fine.

Check your understanding · free

Getting check ready…

Scenario weights mean…

Scar · refuse this

Trap: Writing 70% up / 30% down.

Refuse: Refuse up/down percentage controls.

Tip rooms love fake precision odds.

Required lab

Do this on the desk now

  • On LUCK, write bull/base/bear business lines and weights summing to 100.

    Done when: Three paths + weights + rationale

    Open →

Lab · Forward map

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

Practice on LUCK Study Mode →

Loading forward map lab…

Or practice on live desk with Study ModeOpen LUCK Study Mode

Worked example

HBL BBB Scenarios: Provisions Drive the Paths

Step-by-step walkthrough on HBL. Open the desk alongside to follow.

Steps (4)▼

1. Start from the base driver

Base driver: 'Asset quality / provisions'. This is the swing factor for banks.

💡 Base case = normal provision cycle. Bull = clean. Bear = spike.

2. Write three DIFFERENT business paths

Bull: 'Provisions normalize, NPLs decline, NIM stable'. Base: 'Provisions at 5-yr avg, NIM steady'. Bear: 'Provision spike from corporate NPLs, NIM compression'.

💡 Paths must describe business outcomes, not price targets. No 'stock goes to 200'.

3. Weight as OPINION on paths

Bull 20%, Base 55%, Bear 25%. Rationale: 'Base until dated provision/governance shock. 5-yr avg provisions support base.'

💡 Weights = your opinion on business paths. Sum = 100. Not % chance price moves.

4. Check: no prophecy language

Scan for: 'will go up', 'target', 'guaranteed', '% up'. Remove all.

💡 Prophecy veto is automatic. Your rationale must be business-only.

Show completed forward map

Drivers: Net interest margin / deposits; Asset quality / provisions

Catalysts: Quarterly provision charge (quarterly); NPL classification update (quarterly)

Bull: Clean asset quality and stable deposits

Base: Normal bank cycle with provision noise

Bear: Provision spike or governance shock

Weights: Bull 20% / Base 55% / Bear 25%

Rationale: Base until dated provision/governance shock. Opinion on paths, not price odds.

Falsifiers: Sharp provision spike; Tip without filing date

Exit: Usually liquid — still write lot and costs

Decision: need_evidence

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 write bull/base/bear as business paths with opinion weights that sum to 100.
  • →Weights are not odds that the share price goes up or down.

Worth keeping

  • Veterans keep scars next to every step.
  • A complete map still is not a price call.
  • Many professionals treat scenarios as stress tests rather than predictions; the bear path is often the most informative one to write.
  • A map with three nearly identical paths usually means the evidence has not been read closely yet.

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.

Should the base case always get the highest weight?

Usually, but not always. If evidence is mixed or thin, you may spread weights more evenly and say so in the rationale.

Can weights change over time?

Yes. When new filings arrive, update the paths and weights, and note what changed your mind. That log is part of the learning.

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.