Paul Herrera

Agile delivery of value 🚀 | Achieving better and quicker results while ensuring customer, stakeholder, and team happiness. Scale-up cofounder.

[Paul Herrera @ctopaulh]

Legacy lies not in control, but in equilibrium. Protect people from systems—and systems from people—by valuing transparency, merit, dissent, compassion, and shared stewardship. Only then can organizations outlive their founders without outgrowing their humanity.

[Paul Herrera @ctopaulh]

The “system” threatens the people.

Conversely, individuals can destabilize organizations that have thrived for decades.

These are 3 non-negotiable principles for dealing with this dilemma if you want to create your legacy by building long-lasting and humane companies.

[Paul Herrera @ctopaulh]

Mandate dissent.

Allocate budgets for “red team” challenges, and celebrate employees who question outdated norms.

Constructive conflict prevents institutional inertia and individual complacency.

Friction, when channeled ethically, sparks innovation without combustion.

[Paul Herrera @ctopaulh]

@Itsdawuma @mikekarnj Instagram or LinkedIn. The platform is useless until you have a full network of people using it. But once you have it, boom! It becomes huge.

[Paul Herrera @ctopaulh]

@mikekarnj OKRs and 1-1s come from Intel at their golden age. So it is a proven method.

But why PMs? What's wrong about them?

[Paul Herrera @ctopaulh]

@ttorres I am reading the Bright Spots chapter of the Switch book these days. Bizarre coincidence!

[Paul Herrera @ctopaulh]

@tdd_fellow Why?

[Alex Fedorov | Fractional CTO | FinTech Expert @tdd_fellow]

💡 Quality and speed in software engineering are deeply interconnected. Cutting corners in quality for speed? You're setting up a boomerang of slowdowns in the future. #SoftwareQuality #DevOps

[Paul Herrera @ctopaulh]

@JTLonsdale Very good point. Founders also had the difficult task of communicating their vision to many employee and potential clients. That makes them very good at communicating complex ideas in a clear and effective way. That's what everyone wants from a good professor.

[Paul Herrera @ctopaulh]

@DavidJRicardo1 @victoruxui La mejor respuesta jajajaja

[Paul Herrera @ctopaulh]

@JuanCaMatiz @victoruxui Ese no sería el Arquitecto de Software?

[Paul Herrera @ctopaulh]

@victoruxui Reconocerlo y saber que a muchos les pasa ya es un gran comienzo!

Te recomiendo el libro Grit de Angela Duckworth. Ayuda a entender cómo se comporta una persona que es constante en sus propósitos.

[Paul Herrera @ctopaulh]

@1337hero @DorianDevelops Happy to know that you have had managers that do that for you. It doesn't have been the case for me.

[Paul Herrera @ctopaulh]

@tottinge I like the comparison of writing code with good literature. Every word and comma results from years of reading, practice and mastering when to use communication devices. Likewise, every line, abstraction and separation of functionality needs years of decision-making practice.

[Paul Herrera @ctopaulh]

@knunery But, to be fair, I also think Scrum has many good things.
https://t.co/jpizHHTddT

[Paul Herrera @ctopaulh]

What most people forget about Scrum is that it is a data-driven methodology. A team's data is statistically more significant than individual data.

Therefore, Scrum is a team-focused methodology. It measures team improvement, not individual improvements.

[Paul Herrera @ctopaulh]

@knunery I would say they have forgotten to think that they are in a business. And, in business, creating valuable outcomes is the golden rule. When you have a team that only one to "develop" for the sake of developing, you have to babysit them with canned methodologies like Scrum.

[Paul Herrera @ctopaulh]

@bukki_o I also recommend Project Management Institute's Agile Practice Guide https://t.co/oXE9nW7rY1
It does a good job at blending traditional PM and Agile methodologies.

[Paul Herrera @ctopaulh]

Yet, I have to admit, as a manager, not assessing individuals goes against everything we learned. That makes it difficult to really apply this part of the Scrum methodology.

[Paul Herrera @ctopaulh]

What most people forget about Scrum is that it is a data-driven methodology. A team's data is statistically more significant than individual data.

Therefore, Scrum is a team-focused methodology. It measures team improvement, not individual improvements.