About
Tarik Kansal
I write about systems, execution, and how AI actually fits into real-world workflows.
What I actually do
I work at the intersection of technical delivery, systems, and operations, mostly in environments where things are already moving: campaigns running, systems live, teams under pressure. The challenge is rarely building something from scratch. It's making complex systems actually work.
How I think about problems
Most problems in technology get framed as technical. In practice, they're usually structural: unclear ownership, loose workflows, inconsistent inputs. Tools get blamed, but more often than not, the system around the tool is the real issue. That's the lens I default to.
What I focus on
- Designing systems that reduce ambiguity
- Improving how teams handle complexity at scale
- Applying AI where it actually adds value, not just where it sounds good
- Turning reactive processes into structured ones
The goal isn't more output. It's better systems that produce better outcomes.
Why I write
Writing forces clarity. Most of what ends up here comes from patterns I keep running into across delivery, operations, and technical work. Not theory, not trends, just what actually holds up in practice and what doesn't.
Outside of work
Outside of all this, life is a bit more chaotic, in a good way. Most of my time goes to my wife, our little one, and family who've shaped who I am.
It's a good reminder that not everything needs optimizing; some things just need to be experienced. I still enjoy building and experimenting where technology can simplify real problems, but the throughline is always the same: understanding how systems behave, and how they can be improved.