Personal Narrative | ~6 min read
I almost didn’t write this post.
Not because I didn’t have anything to say if anything, the problem was the opposite. Twenty years in technology leaves you with a lot of stories, a lot of lessons, and a long list of things you wish someone had told you earlier. The hesitation wasn’t about content. It was about something else.
Who am I to be writing about this?
I’m not a bestselling author. I don’t have a massive following. I haven’t founded a company or appeared on a conference stage in front of thousands of people. I’m someone who has spent two decades in the trenches keeping systems running, managing teams, navigating organizational complexity, and making more than my fair share of mistakes along the way.
And then I realized something: that’s exactly the reason to write.
Not in spite of the mistakes and the uncertainty, but because of them. Because the most useful things I’ve learned didn’t come from textbooks or certifications. They came from real situations, real failures, and real people who were generous enough to share what they knew even when what they knew was “I got this wrong and here’s what I’d do differently.”
This site is my version of that generosity.
Where I Started
I didn’t walk into technology with a clear plan. I found my way in the way a lot of people do through curiosity, opportunity, and a willingness to figure things out as they came.
Early on, the work was hands-on and technical. Servers, networks, infrastructure. The kind of work where you knew pretty quickly whether you’d done it right, because if you hadn’t, something stopped working and everyone knew about it. There was something I genuinely loved about that clarity. A problem existed. You found it. You fixed it. The system came back up.
Over time, the work grew. The scope expanded. The roles changed. What started as keeping systems running evolved into leading teams, shaping strategy, navigating security and governance, and trying to help organizations use technology in ways that actually served their mission rather than just adding complexity.
And somewhere in that progression, the problems stopped being as clean as they used to be.
The Problems Nobody Prepares You For
Here’s what I’ve learned about technology careers that I wish someone had told me at the beginning:
The technical part is actually the easier part.
That’s not meant to diminish technical skill it’s foundational, and it matters enormously. But most technical problems have a knowable answer. You can test, iterate, and arrive at a solution. The feedback loop is relatively short.
The harder problems are the human ones. How do you build a team that stays accountable without micromanaging them? How do you communicate risk to leadership in a way they’ll actually act on? How do you make a governance process that people follow because they understand why it matters — not just because they’re required to? How do you lead people through uncertainty when you’re uncertain yourself?
Nobody gives you a certification for those things. And in most organizations, nobody really prepares you for them either. You get promoted because you were good at the technical work, and then you’re expected to navigate a completely different set of challenges using instincts you haven’t had time to develop yet.
I’ve been in that position. I’ve watched a lot of other people be put in that position. And I’ve seen how much unnecessary difficulty comes from not having access to honest, experience-based guidance the kind that says “here’s what I tried, here’s what didn’t work, and here’s what I’d do differently.”
That’s the gap this site is trying to close, even just a little.
What You’ll Find Here
I’m not building a content machine. I’m not trying to post every day or optimize for search traffic or build a personal brand. That’s not what this is.
What this is — what I want it to be — is a place where real experience gets documented honestly. Where the lessons that usually only get shared in one-on-one conversations or hallway chats are written down in a way that’s accessible to more people.
Most of what I write will fall into a few areas that have shaped my own career:
Technology and operations — practical insights from real environments, focused on what actually works when resources are limited and the stakes are real.
Leadership and mentorship — what I’ve learned about developing people, building trust, and growing into leadership roles that nobody fully prepares you for.
Governance and risk — why the unsexy work of structure, process, and accountability matters more than most teams realize until it’s too late.
Modern tools and AI — how to think critically about new technology, adopt what genuinely helps, and avoid the hype cycles that waste time and erode credibility.
Lessons learned — the honest ones. Things that worked, things that didn’t, and the stories behind both.
The primary audience I have in mind is people who are newer to IT leadership team leads and managers who are figuring out a role that no one fully explained to them. But I also hope that more experienced practitioners find value here, and that people outside of technology find things they can apply in their own fields. Good leadership lessons and hard-earned operational wisdom tend to travel across industries.
A Note on How I Work
You’ll occasionally see references to “Sophia” my AI assistant. I use AI as a thinking partner: to help organize ideas, push on my reasoning, and sharpen how I communicate. But everything on this site reflects my own perspective, my own experience, and my own voice.
I mention this because I think transparency matters — especially right now, when AI is being used everywhere and not everyone is being upfront about it. I’m not outsourcing my thinking. I’m using a tool to do it better. There’s a meaningful difference, and it’s one I’ll probably write about at length in a future post.
What I Still Don’t Know
The title of this post includes a phrase I want to sit with for a moment, because it matters to me: what I still don’t know.
After twenty years, the list is long.
I don’t have all the answers on how to build the perfect team. I’m still learning how to communicate more effectively under pressure. There are areas of technology that move faster than my ability to keep up. There are leadership situations I’ve handled poorly and am still processing.
I think this is true for almost everyone who’s honest about it. Experience doesn’t eliminate uncertainty it just changes the shape of it. You get better at recognizing the type of problem you’re facing, better at drawing on what’s worked before, better at asking the right questions. But the learning doesn’t stop.
And I think that’s actually the right attitude to bring into any work especially leadership work. The moment you think you have it fully figured out is usually the moment you stop being as effective as you could be.
So this site isn’t positioned as a place where someone with all the answers shares them. It’s a place where someone still in the middle of learning shares what they’ve picked up honestly, practically, and with the hope that it’s useful to someone else on a similar journey.
Why Now
I’ve been meaning to do this for a while. The honest answer for why it’s happening now is that I finally stopped waiting until I felt ready.
There will always be a reason to wait. More experience to accumulate. More clarity to develop. More time to organize the thoughts properly. But waiting for perfect readiness is just a slower version of not starting.
If anything I write here helps someone think a little differently, avoid a mistake they didn’t have to make, or feel a little less alone in a challenge they’re navigating — then it’s done exactly what I’m hoping for.
That’s enough. That’s more than enough.
Thanks for being here at the beginning. I’m glad you found this.
— Jose, with the help of Sophia (AI assistant)
Clarity Through Experience 
Leave a comment