I want to be honest about why I started writing this.
Twenty years of working with great people — at Amazon, BCG, ITC, Practo, InMobi, Pine Labs, and now Orange Health — taught me things I couldn't find in any book. Not theory. Operating systems. Ways of thinking about problems that held up under real pressure, in real organizations, with real people who were tired and under-resourced and trying to do their best.
My mentors didn't write it down. They showed me. I got lucky.
Most people don't.
So I started writing it down — not as an expert, but as a practitioner. Every issue is something I learned by doing it wrong first, or by watching someone do it right and reverse-engineering why. If it helps one person navigate a hard situation a little better, that's enough.
That's the mission. You're part of it now.
I committed to doing this for 2 years. We're six months in. I check every six months to make sure I'm still showing up — consider this the first checkpoint. The only metric I measure: did I show up and write. Outputs will follow or they won't. But inputs are mine to control.
What We've Built So Far
Some of you signed up last week. Some of you have been here from the first issue. Either way, here's the full archive — grouped by theme so you know where to start.
Operating Rhythms — how to run the day-to-day so nothing falls through the cracks
Meetings Are a Tax. — Jan 22
From Complaint Box to Improvement Engine — Mar 3 (scheduled)
Systems & Mechanisms — the difference between tools that die in two weeks and ones that outlast you
The System Under the System — Feb 7
You Can't "Do" Revenue — Feb 3
You're Learning AI Wrong — Feb 1
The FAQ as a Thinking Tool — Jan 20
AI as Confession — Jan 18
Keertimukha — Jan 18
Problem Diagnosis — how to find what's actually broken before you start fixing
The Three Buckets of Error — Feb 24
The Backlog Crisis Playbook — Jan 18
When Blockers Become Buffers — Jan 18
Career & Leadership — the things nobody tells you when the title changes
Your Function Programmed Your Clock — Feb 22
The Syllabus Changed — Jan 18
Specialist or Generalist? — Jan 18
The 5 Stages of Career Skill Levels — Jan 18
Why Life Lessons Are Rare — Jan 18
People & Management — how great managers actually operate
The Four Roles of a Great Manager — Jan 18
The Three Types of Managers — Jan 18
The Vulnerability Paradox — Jan 18
Shrink Mountains Into Molehills — Jan 18
Failures as Vaccinations — Jan 18
The Long Game — on career, consistency, and what it actually takes
The Area Under the Curve — Jan 18
One Ask — Three Ways to Help This Reach More People
I could run ads for this. I know how to grow an audience at scale — I've done it before.
I'm not doing that here. Not yet, maybe not ever.
This is a test. If what I'm writing is genuinely useful, it should spread on its own. People share things that helped them. They forward emails that made a colleague's problem click. They reshare posts that said something they'd been trying to articulate for months.
If this isn't spreading, one of two things is true: I haven't been clear enough about how you can act and pay it forward, or I'm simply not adding enough value. Either way, that's on me to fix — not on an ad budget to paper over.
So here's how you can help, if this has been useful to you:
Reshare on LinkedIn. Every issue has a LinkedIn post. Like it, comment, reshare it. That's how it reaches people outside this list.
Forward this email to a junior colleague who's navigating their first leadership role or stuck on an operational problem we've covered here.
Write to me. Suggest a topic. Share a framework that's worked for you. If you have battle-tested lessons from your own work, pitch yourself as a guest writer.
Not the only way. Probably not even the best way. Just one practitioner paying it forward.
~Discovering Turiya@work@life
