What this category is about: stories about developing, course-correcting, and caring for the people on a team — distinct from the technical/operational scars of the previous category. This category comes from recognizing that not every leadership lesson is about a system that failed — some are about a person we needed to listen to better.
Why a category separate from Leadership & Operations?
Because course-correcting a platform and course-correcting a person are not the same skill. In operations, the answer is usually technical: a circuit breaker, an immutable variable, an architecture change. With people, the answer is never a patch — it's listening better, developing better, and caring for the relationship while correcting.
Who is this category for?
For those leading teams at a SaaS or fintech company — and recognize that their hardest work isn't the failing system, but the person who needs to be heard better.
Articles in this category
Articles in this topic
The 6-hour feature that should never have been built
A new manager was about to request a 6-8 hour feature the platform already handled. Showing the reports live avoided the build and built their mental model. Context: engineers spend 17.3 h/week on technical debt (Stripe).
Read full articleWhat the numbers didn't explain — until I asked
A team member's performance dropped for no apparent reason. Instead of watching them, I asked: it was a health issue, not a commitment issue. Adjusting their schedule restored their numbers. Context: 86% of employees value empathetic leadership (EY).
Read full articleWhy a talent development plan fails (and how to catch it early)
An impeccable plan on paper: defined courses, regular feedback, a clear destination. What was missing was the person's conviction. The training was never completed and they left for performance. Dated milestones and an honest conversation.
Read full articleThe overtime nobody sees: preventing burnout on a support team under pressure
A headcount reduction left us over capacity: 30–40% of cases were out-of-contract configurations. The risk wasn't the overtime — it was the overtime becoming part of the landscape. Compensation by choice, a visible plan, and automation.
Read full articleHow we built, from scratch, the team that later generated more than half our ARR
Four people built with no defined process, documenting while serving clients. Assigning responsibilities by each person's real strength and resolving disagreements with objective criteria — not hierarchy — held it together. That team generated more than 50% of ARR.
Read full articleWhy we took 30% longer to hire a DevOps engineer, and why it was worth it
We depended entirely on Jenkins with no internal expert and R&D was blocked. Pressure said "hire whoever keeps it running". We waited for someone who could truly modernize: they retired Jenkins, migrated to Azure DevOps, and mentored today's infrastructure leaders.
Read full articleWhen someone didn't choose the role they were asked to lead
A colleague became the CEO's Chief of Staff during a restructuring — a role she didn't choose. The support wasn't about process, but communication: bringing real concerns to the CEO without softening them. Commitment reliability improved by more than 25%.
Read full articleThe feedback that was hardest for me to accept, and how I turned it into a habit
Direct feedback that executive communication was a real area for improvement. Instead of getting defensive, a concrete plan and AI as a second pair of eyes when preparing executive summaries. Still working on it: continuous practice, not a checked box.
Read full articleAgreeing with the decision, disagreeing with how it was communicated
The CEO split the team into implementation and support. The assignment of people was never discussed with me first, and I was direct with my leader about disagreeing with the form — not the decision. The specialization accelerated onboarding and enabled expansion.
Read full articleNew lessons will be added as they are published
Coming soonWritten and reviewed by Rogelio Barajas González — certified Lead Auditor ISO 27001:2022 and ISO 9001:2015, with 15+ years leading technology operations across LATAM and the United States. Founder of Barajas Advisory.
Follow me on LinkedIn:linkedin.com/in/rogelio-barajas-gonzalezLast updated: August 2026