About me
An engineering leader focused on product strategy, execution, resilient systems, and practical AI adoption.
I’m Tushar. I build products and teams.
My background spans engineering leadership, product execution, and systems built at scale. I’m interested in how technical decisions intersect with business outcomes and how leaders navigate ambiguity, tradeoffs, and growth.
This blog is a space to think in public about leadership, engineering, product strategy, and learning through execution and failure.
I write for people who sit close to the work: engineering leaders, senior engineers, product-minded builders, and teams trying to make better decisions under real constraints. The common thread is practical judgment. What worked? What failed? What signal did we miss? Which decision looked technical but was really organizational?
Outside of work, I play the drums - where rhythm, restraint, and iteration matter as much as they do in building teams.
If you run a growth-stage engineering org, or you are a mid to senior engineer looking for engineering discussions and practical tech strategy, start here: Ways I Can Help
You can also join Community Office Hours or explore my AI & Systems Notes.
What I Usually Write About
I prefer specific stories over universal rules. A lesson is more useful when the constraints around it are visible.
Areas I Focus On
- Engineering leadership for product teams
- Org and execution design for scaling teams
- Architecture and platform decisions with business constraints
- Coaching engineering managers and senior ICs
Learn More Through My Writing
Insights on Smooth Project Delivery covers how cross-functional collaboration improves execution.
The Leadership Pipeline explains my approach to developing leaders.
Build to Outlive is my framework for long-term engineering decisions.
How To Use This Site
If you are here to evaluate how I think, read one long-form post and one short mental model. The posts carry the messy context. The mental models show the heuristics I reuse when making decisions.
If you are here with a specific problem, the fastest path is usually Ways I Help or Community Office Hours.
Contact
If you’d like to discuss collaboration, email me at tm@whatworked.io.
You can also connect on LinkedIn, GitHub, or Medium.