After reducing incidents by 87% while maintaining 200 systems with just 2 people, I discovered the real problem:
Our obsession with velocity is destroying both our software and our people.
✓ Microsoft validated approach · ✓ Survived near-termination · ✓ Battle-tested in chaos
At a major bank: multiple directors competing for bonuses, 2 engineers drowning in 200 systems, dailies with 23 people lasting over an hour.Sound familiar? These aren't edge cases. They're symptoms.
"Bank's political structure became spaghetti code"
When organizational silos dictate architecture, both code and culture become unmaintainable
"Everyone wanted the bonus, nobody did the work"
Shared resources (developers) exploited until collapse when individual incentives misalign
"1h20 dailies with 23 people, velocity up, delivery down"
Copying rituals without understanding principles creates theater, not transformation
I was almost fired mid-transformation. Directors wanted their agile certifications and bonuses. Nobody wanted to do the actual work.
What saved me? Undeniable results. When Microsoft analyzed our approach, they validated what the metrics already showed.
The solution wasn't complex frameworks or expensive tools. It was common sense + respect for humans.
What they tell you vs. what I learned in the trenches
"We need to go faster"
Speed without direction is just chaos with velocity metrics
"More people = more output"
I maintained 200 systems with 1 other person. Quality > Quantity
"Technical debt is inevitable"
No. It's a choice made when velocity overrides sustainability
Battle-tested in one of Brazil's most politically complex corporate environments
Creator, Agile Reset Framework
📍 São Paulo, Brazil · Working Globally
I'm a fullstack engineer with 20+ years building scalable systems across financial markets, e-commerce, and insurance.
My expertise in React.js, Node.js, .NET, and microservices gave me the technical credibility. But my experience surviving one of Brazil's most politically complex corporate environments gave me the cultural insights that became the Agile Reset Framework.
When I reduced incidents by 87% managing 200 systems with one other person, I proved that the problem wasn't technical capacity. It was cultural chaos.
Microsoft validated the approach. But more importantly, the teams I worked with went from burned out and demoralized to engaged and high-performing.
I created Agile Reset because too many brilliant engineers are drowning in velocity theater while organizations wonder why innovation died.
This framework is for them. And for the leaders brave enough to challenge the status quo.
Organizations worldwide are optimizing for speed at the expense of sustainability, creating a compound crisis of technical debt and human burnout.
When velocity metrics override human capacity, both systems and people collapse. We prioritize sustainable pace over heroic sprints.
Each rushed sprint multiplies tomorrow's complexity. We value thoughtful design that prevents technical debt compounding.
Faster delivery often creates slower systems. We embrace incremental progress that compounds into sustainable growth.
A systematic approach to shifting from velocity-driven chaos to sustainable, high-performing development cultures.
Identify velocity-induced patterns causing systemic collapse
Build consensus around sustainable practices across teams
Apply incremental changes that compound into transformation
Expand sustainable practices across the organization
Your team is burning out. Your systems are collapsing. Your velocity metrics look great on slides.
But you know something's deeply wrong.
I've been there. I survived it. And I can help you transform it.
First consultation: Free reality check
No sales pitch · Just honest conversation · Based on real battle-tested experience