Bratha

Part 1.0 — Why Understand Business Before Picking a Skill

18 min read

This is Part 1 of 13 in the Capabilities and Competency series, the targeting layer of the Rich section. Income 101 told you why income matters and how to position yourself. Multiplying Money 101 tells you what to do with the income once it lands. This series sits in between and answers the harder question: which specific skill is actually worth getting good at, for which kind of business, and who pays for it. The full path:

Table of Contents

Why start with "understand business" and not "pick a skill"

Because almost every “what skill should I learn” article is fighting over the second question while ignoring the first. You cannot choose what to get good at until you can see where a business makes and loses money. Without that lens, “skill” is just a list of certificates and YouTube tutorials, half of which the market doesn’t actually pay for. This series teaches the lens first, then points it at something real, then names the skill that drops out the other end.

Where this series sits

Income 101 was about why income matters (it buys optionality) and how to position yourself inside the labour market (cheap-and-capable, target the startup, stack three economies). It ended with a handoff: once you’ve decided income is the project, the next question is what capability is the income built on.

Multiplying Money 101 is downstream of that. It tells you what to do with the money once you’ve earned it (allocate, defend, multiply, then stop forcing it). It assumes the income exists.

This series fills the missing middle. Income 101 told you to bet on a living industry and to make yourself the cheap-and-capable hire. This series tells you which exact skill, inside that industry, is actually worth getting good at, and who inside the company you'll sell it to. It is the aim before the shot.

Three through-lines carry into every article that follows:

  • Profit is the root, and every skill plugs into it. Every paid skill in the world either helps a business bring more money in or cuts what goes out. If you can’t draw the line from a skill back to one of those two branches, the market won’t pay for it (or won’t pay much).
  • Value is local to the bottleneck. At any moment, a business has one main thing holding it back. Fixing that one thing is worth a lot. Polishing anything else is worth almost nothing. Skills are not generically valuable; they are valuable for businesses in a stage where the skill happens to be the constraint.
  • The 90/10 rule. From Income 101 and the Fit series and the Nutrition series: 90% of the result is the boring structural work, and 10% is the chemistry. In capability terms, the 90% is picking the right skill for the right stage of business in the right industry. The 10% is the polish (the side project, the certificate, the personal brand). Most people invert it: they over-polish a skill the market doesn’t need much of.

A note on what this series is not

This series is not “here is a list of trendy skills to learn.” Lists like that age out in 18 months. The lens here is older than that and will still work after another LLM cycle has come and gone, because it’s built on how businesses make money (which hasn’t changed in a long time) rather than on which tools are hot this year.

The thesis: skill is meaningless without a target

Here is the through-line for all 13 articles, and it is worth stating plainly:

A skill is not valuable in itself. A skill is valuable because it moves a specific number, in a specific kind of business, at a specific stage of that business's life, for a specific person inside the org who is paid to care about that number. Strip any one of those four conditions and the skill is worth a fraction of what it could be.

The standard mental model of “learn a high-income skill and the income follows” smuggles a hidden assumption: that the market pays for skills in general. It doesn’t. The market pays for outcomes, and skills are just the way outcomes get produced. The person who can write a beautiful blog post is paid much less than the person who can write a blog post that ranks for a keyword that drives RM 500 of revenue per visitor for a business that is currently bleeding cash from a customer-acquisition leak. Those are the same “skill” on paper. They are not the same offer.

Two consequences fall out of this immediately:

  • A learner who picks a skill without knowing which business needs it, at which stage, will end up as a generalist competing with everyone else on price. The skill might be excellent; the positioning is broken.
  • A learner who studies a single business deeply (even just one, even just an internship), and then picks the skill that would have moved the needle there, walks out aimed at a specific buyer who would have paid for that exact help. Same effort, very different return.

If you only remember one sentence from this article

Skill without a target is a hobby. Skill with a target is an offer. Most of what makes income happen is the targeting, not the skill itself.

The “I need to learn X” trap

Walk into any career sub-Reddit, any TikTok feed about “skills for 2026,” any conversation among undergrads who’ve just decided they need a side hustle, and you’ll meet the same shape of question: should I learn Python, or video editing, or copywriting, or no-code, or AI prompt engineering, or trading?

The question is malformed. It has no business attached. No stage. No buyer. No number to move. The only honest answer to “should I learn X” is “for whom, doing what, at what stage of their business, to move which metric?” Without those, the question collapses into vibes, which is exactly why the answers in those threads are also vibes (“Python is hot,” “AI is the future,” “copywriting never dies”). All of which can be true and none of which tell you whether the skill will pay you anything.

The trap has a predictable life cycle:

  1. You hear that skill X is valuable.
  2. You spend six months learning skill X.
  3. You discover that the businesses that need skill X most are either already covered, or are in a stage where they’d rather get a senior, or are in an industry you have zero access to.
  4. You quietly let the skill rot, conclude that “the market is broken,” and start the cycle again with skill Y.

The fix is not “pick the right skill on the first try.” Nobody does that. The fix is to stop asking the question in the abstract and start asking it inside a specific business you know, even partially, even from the outside. The skill that drops out of that question is almost always more specific, more boring-sounding, and pays much better than whatever was trending on your feed.

The single biggest thing this series will teach you to do is slow that question down. Before “what skill should I learn,” ask “for which business” and “at what stage” and “which number.” The answers narrow the skill list by 90% before you ever open a tutorial.

Why theory is just noise before experience

Here’s the part this series has to say out loud, because it shapes how the next 12 articles are written.

Frameworks, before you've worked inside a real business, are just more noise.

The Business Model Canvas, the seven powers, the four jobs of a business, unit economics, OKR cascades, the phase × constraint matrix: all of these are tools that cut noise after you have terrain in your head. Without terrain, they are not tools. They are wallpaper. You can memorise the nine blocks of the BMC and still have no idea which block is currently the constraint at the cafe down the street, because you’ve never sat with the cafe owner while she’s reconciling the day’s takings against the bill she has to pay her supplier on Friday.

This is why most “business literacy” content fails. It teaches the frameworks first, with no terrain, in the hope that the terrain will arrive later. The terrain rarely arrives. The reader closes the tab feeling like they “understand business now,” and then makes career bets based on a model they have never actually pointed at a real situation.

The opposite mistake is just as bad: skipping the frameworks entirely, on the theory that experience is the only teacher. Pure experience without a lens to read it through is also noise. You can work inside a startup for a year and learn almost nothing about how the business works as a business, because you only ever saw your part of it. The lens is what lets you read a year of experience and pull a decade of lessons out of it.

The honest order is:

  1. A little terrain first. Get inside a business in any role (an internship, a part-time job, a first hire at a startup, even just close observation of a family-run kedai). Without this, no lens will land.
  2. Then a framework, introduced as a lens. “Here is one way to read what you’ve already half-seen.”
  3. Then apply the lens to the terrain you have. What does it show? What does it miss? Where does it confirm your gut, and where does it contradict it?
  4. Then more terrain, read through the lens. This is when the next year of work starts compounding properly, because you’re no longer just collecting impressions; you’re updating a model.

This series is built to interleave with experience, not replace it. If you have never been inside a business in any capacity, do not try to absorb 13 articles in a week and then "go apply them." Read one. Then go look at one business you can actually see. Then come back.

A predictable failure mode

Smart, ambitious readers tend to consume the whole series back-to-back and feel like they’ve understood it. Then they realise three months later that they can name the seven powers but can’t say which power the warung selling them lunch every day has, or doesn’t. The frameworks didn’t fail them. They just used them as theatre instead of as a lens.

The pain × reflection model

The way capability actually builds is not “read theory → apply theory.” It’s pain × reflection, compounded.

Pain alone doesn’t teach. People who only ever take pain become bitter, not skilled. The bitter ex-employee who quit their tenth job in two years has been through plenty of pain; what they didn’t do is reflect on what each one was actually trying to teach them. Pain without reflection is just damage.

Reflection alone is also useless. People who only reflect (without ever going into the arena to take a real hit) become the world’s best armchair strategists and the world’s worst operators. Their model of how things work is internally consistent and externally wrong, because no part of it has been bruised against reality.

The compound is pain multiplied by reflection. Every painful working experience, read through a lens, leaves you with a sharper read on what the lens was for and where it breaks. Every framework, pressure-tested against a real situation that hurt, becomes a real tool instead of a recited list.

The recurring move in this series, the one you’ll find at the end of every article, is built on this:

  1. Read the framework (this article does its teaching).
  2. Point it at a business you have personally touched. Your last job. Your current job. Your friend’s startup. The cafe you’ve been going to for five years. Pick one and apply the lens.
  3. Write down two things: what the lens revealed that you hadn’t noticed, and what the lens missed about the situation. Both are valuable. The second is more valuable than the first, because it’s how you start to see where the framework is incomplete.
  4. Sit with it for a week before reading the next article. The integration is the point. Reading 13 frameworks in a row, without integration, makes you fluent in vocabulary you can’t use.

This move is the price of admission. Skip it and the series will feel like “interesting reading” instead of training.

How every article in this series will be built

So you know what to expect, every article from Part 2.0 onward will follow the same shape:

  • A real situation to anchor the article. Not a hypothetical “imagine a startup”; a specific kind of business in a specific phase, often with Malaysian context (a kopitiam scaling to a second outlet, a SaaS startup at year two, a manufacturing SME deciding whether to automate the line).
  • The framework as a lens. Not “here is theory.” Here is the lens, named in plain words, explained in plain words, with the bombastic vocabulary kept out unless it earns its place.
  • Application: the lens pointed at the situation, with the working shown. What does the lens see? What does it grade?
  • Where the lens breaks. Every framework in this series will get its own pushback section. No tool is universal. Knowing the edges of a tool is part of using it.
  • The recurring closing move: what to point this article’s lens at, in your own life or work, this week.

The articles connect like rungs of a ladder. Part 2.0 introduces the engine. Part 2.1 checks whether the engine works. Part 2.2 shows you the structure around the engine. Part 2.3 names the jobs that the structure exists to do. Part 3 zooms further into where value lives and why the same skill is worth different amounts in different businesses. Part 4 goes deep on the two biggest levers. Part 5 connects all of it to who pays you. Part 6 runs the chain start-to-finish on a real example, and then turns it on you.

If you only want to read three articles in the whole series, read 2.0 (the bottleneck idea), 3.2 (the phase × constraint matrix), and 6.0 (the full chain). The rest is the connective tissue that makes those three load-bearing.

What you should walk away from this series with

The deliverable, by the end of Part 6.1, is concrete:

  • A named, specific, phase-appropriate skill you can credibly bet a year or two of compounding effort on.
  • A named kind of business (size, stage, industry) where that skill is currently the constraint.
  • A named role (founder, CMO, COO, head of growth, the operator) who owns the metric that skill moves, and who will therefore pay for it.
  • A clear handoff: the learning-and-practice series, which is downstream of this one, picks up “now go build it.” The sales mechanism inside Part 4.0 of this series, plus the positioning logic from Income 101 Part 2.0, picks up “now go sell it.”

If at the end of this series the answer to “which skill should I get good at” is still vague, the series has failed. The whole point is to walk out of it with a single sentence that names a skill, a kind of business, and a buyer. Everything between here and there is in service of that one sentence.

Part 1.0 takeaways

Key concepts to internalise

  • Skill without a target is a hobby. The market pays for outcomes inside specific businesses, not for skills in the abstract.
  • The “I need to learn X” question is malformed. Replace it with “for which business, at which stage, to move which number, for which person inside the org?”
  • Theory is just noise before experience. A framework only cuts noise once you have terrain in your head. Pair every lesson with a real business you can see.
  • Reflection without pain is theatre; pain without reflection is damage. Capability builds at the product of the two. The recurring closing move in this series is built around that.
  • The deliverable is one sentence. Skill × stage of business × industry × the person who owns the metric. Everything else is connective tissue.

Your baseline task list

Before Part 2.0 introduces the profit engine, get the targets set up. This week is observation, not skill-picking.

  1. Pick one business you have actually been inside, in any capacity. A current job, a past internship, a friend’s startup, a family business, even just a shop you have a window into. This is your “case business” for the whole series. You’ll point every framework at it.
  2. Write down, in two or three sentences, what you think the business actually sells. Not the marketing copy version. The honest, operator-level version. (You will revise this after Part 2.2.)
  3. List two or three current pains you saw inside that business. Things people complained about, problems nobody seemed to be solving, places where the work felt obviously broken. This is your raw signal for the bottleneck idea in Part 2.0.
  4. Read or re-read Income 101 Part 4.0 (Stacking Economies). This series picks up where that one ended.
  5. If you have never been inside a business in any role, treat the first few articles as orientation and prioritise getting into one (an internship, a part-time job, a first hire at a startup, a side project with a real customer). The series will keep working when you do.

Up next

You have the operating rule (skill needs a target; theory needs experience). Part 2.0 — The Profit Engine introduces the single idea that the next twelve articles will lean on: a business is a flow of money in minus money out, and at any moment, one thing in that flow is the bottleneck. That one idea is what makes the rest of this series usable.

Disclaimer

This article is career and business-literacy education, not personalised career advice. Local labour markets, industry, life stage, and risk tolerance all change what “the right skill” looks like for a given person. The frameworks here are starting points, not prescriptions.

Sources & references

The “skill is meaningless without a target” framing is a synthesis of a few overlapping arguments. Cedric Chin’s writing on business triads (the capital / operations / market split that Part 2.2 will use) is one of the clearest treatments of why the same skill behaves differently in different businesses. The theory of constraints (Eliyahu Goldratt’s The Goal, 1984) is the formal version of the bottleneck idea introduced in Part 2.0. The “pain × reflection” framing draws on the long tradition of deliberate-practice research (K. Anders Ericsson, Peak, 2016) and the related working-class wisdom that experience without reflection is just years of repeating the same mistake.

Graph View

Backlinks