Azlan Nizam · Thinking

Operating Philosophy

Principles

How I actually make decisions. Every principle earns its place with a practical explanation — this is not a quotes page.

6 written · 10 in the pipeline

01

# Build systems, not hacks.

A hack solves today's instance of a problem. A system solves the entire class of it, then keeps solving it while you sleep. Hacks feel faster because the cost is deferred — you pay it every time the problem recurs and you patch it again. The test I use: if this exact situation happens ten more times, will I have to think about it ten more times? If yes, I haven't built a system yet, I've just postponed the work. Systems are more expensive up front and cheaper forever.

02

# Data beats opinions.

In most disagreements, the loudest or most senior opinion wins. That's a bug. The point of collecting data isn't to be scientific for its own sake — it's to give the quiet correct person a way to beat the confident wrong one. When someone says 'I think users want X,' the honest next question is 'what would we observe if that were true, and have we looked?' Opinions still matter for the questions data can't answer yet. But the moment a question becomes measurable, opinion should step aside.

03

# Simplicity scales.

Complexity has a carrying cost that grows with every person and year added to a company. A simple process survives being explained once and handed off. A clever one needs its inventor in the room. Every added option, exception, and special case is a tax the whole organisation pays forever. I treat simplicity as the default and make complexity earn its place — it has to solve a real, present problem, not a hypothetical future one. The hard part isn't adding; it's having the discipline to remove.

04

# Clarity beats cleverness.

Cleverness impresses; clarity moves people. A clever plan that the team half-understands produces confident action in slightly wrong directions — the most expensive kind. I'd rather have a plain plan everyone can repeat back accurately than an elegant one only I can hold in my head. This applies to writing, product, and strategy equally: if I can't explain it simply, I don't understand it well enough to ship it. Clarity is a gift you give everyone downstream of you.

05

# Ship. Measure. Improve.

Nothing you believe about a product is real until it meets users. Shipping isn't the finish line — it's the start of learning. The trap is treating launch as the goal, celebrating, and moving on before measuring whether it worked. The loop only compounds if all three steps happen: ship to learn, measure honestly (including when the number disappoints), improve based on what you saw. A team that ships without measuring is guessing loudly. A team that measures without shipping is stalling. You need the whole cycle, turning.

06

# Focus is leverage.

Doing more things divides your attention; doing fewer things multiplies it. Most underperformance I've seen isn't from working too little — it's from spreading effort across too many fronts so nothing reaches escape velocity. Saying no to a good opportunity is the price of saying yes to a great one with your full weight behind it. The uncomfortable truth is that focus means visibly neglecting things that matter, trusting that concentrated force on the few things that matter most will more than pay for it.

Still to be written