⚠ Draft for Zain's pass. A starter manual assembled from how he actually works; he rewrites in his own voice before announcing.
How I think
- Systems first. I look for the underlying structure before touching screens: the IA, the tokens, the operating rhythm. Fixing the system beats polishing the symptom.
- Commit hard. When I take something on, I go all in. The same pattern since I was flashing my hundredth custom ROM at 2 AM.
- Evidence over opinion. Bring me a number, a recording, or a user quote and I'll change my mind in a minute.
How I communicate
- Direct, low-jargon, honest about uncertainty. If something is weak, I'll say so, and I want the same courtesy.
- Async-friendly by default; deep-work blocks are sacred, meetings earn their slot.
- I'd rather over-document than re-explain. Everything important becomes a written artifact.
What energizes me
Shipping. Teaching a tool to someone and watching their week get faster. Hard problems with a measurable "after." Fellow tech nerds.
What drains me
Process theatre. Decisions that reopen without new information. "That's how we've always done it" as an argument.
Feedback
Give it straight and early. I treat feedback as free QA on my thinking: the sooner it lands, the cheaper the fix.