Ship, Show, Ask
Not every change needs the same review. Ship, Show, Ask matches the process to the risk, without losing quality or collaboration.
Leading a team day to day: priorities, trust, and hard conversations.

Not every change needs the same review. Ship, Show, Ask matches the process to the risk, without losing quality or collaboration.

You have mastered the code, but technical skill alone will not carry you. If you cannot work with others, nobody wants to work with you.

Waterfall moves through fixed stages and gives no feedback until each one ends. Why that clashes with how software really evolves.

An impossible project, people playing politics, and endless quick patches, instead of anyone helping the business thrive.

Why Agile if you already do Scrum, Kanban or SAFe? How you manage an organization defines its quality, and what really kills it.

Kim Scott, former Google leader, on being a great manager: empathetic and results-oriented, where people can speak freely.

Most startups fail, and many of those failures are preventable. The approach that changed how companies build and launch.

Tuckman's five stages, and practical strategies for each one: forming, storming, norming, performing and adjourning.

The tools to handle life's hardest conversations: say what is on your mind and still reach the resolution you want.

An unhealthy working environment can have various symptoms that negatively impact both the physical and mental well-being of employees.

The Peter principle: people get promoted until they land in a role they are not competent for, and then stop being promoted.

Michael Abrashoff on how he transformed the performance and culture of the USS Benfold, and the leadership principles behind it.

From my talk at the WeAreDevelopers World Congress: my experience with Extreme Programming and the benefits of embracing change.

Waterfall projects ran over budget and shipped software nobody wanted to use. In 2001, a 68-word manifesto changed that.

An effective remote work environment is about treating everyone as remote, with everyone in mind having the same level, equality, and information.

Introducing a new tech stack affects everyone, so it needs a clear why and a strategy the whole team can get behind.

As organizations grow, leaders must shift focus from customers to employees. Key principles for scaling leadership effectively.

Told through the story of People First IT, this book lays out The Algorithm of Success for changing every part of an organization.

From the bestselling author of Start With Why and Leaders Eat Last, a bold framework for leadership in today's ever-changing world.

You apply the extreme programming values and practices. So how do you work with the teams around you that are not agile?

Twenty-six selections from Drucker on management in the organization, the individual and society. The principles that still hold.

Leadership is action, not a title. It has nothing to do with management or hierarchy. What it really means and how anyone can lead.

One of the most complicated challenges for everyone is avoiding misunderstandings and being aware that other people don't think the same way as you do.

Teresa Torres on a decision-making process that keeps product teams in touch with customers and improving what they ship.

How to scale from startup to company with a system of accountability, real problem solving and transparent feedback.

A triangle of time, quality and cost. it's an indicator that these three parameters are interconnected. You can fix one or two of them, but not three.

Cut off a spider's head and it dies. Cut off a starfish's leg and it grows back. How decentralized organizations change business.

Bikeshedding explains why teams waste time on trivial decisions while ignoring complex, important ones. Learn to recognize and avoid it.

Dunbar's number is a suggested cognitive limit to the number of people with whom one can maintain stable social relationships.

Team structures and interaction modes that let teams adapt quickly and keep software delivery both fast and safe.

Software demands non-stop learning. How to create the spaces your team needs to leave the comfort zone and embrace change.

Joel Beasley maps the jagged transition from developer to CTO: the challenges, the lessons and the things worth avoiding.

A company's real strength is never its products. It is its people, and their willingness to rally together when it gets hard.

A leadership fable about a tech company whose C level cannot agree on anything, and the new CEO who names the five dysfunctions.

Marquet dives into the sinking of the El Faro and surfaces with new ideas on how the language we use defines our leadership.

Blue Work and Red Work, the two modes David Marquet describes in Leadership is Language. Different mindsets, and different languages.

Marquet turned the submarine Santa Fe around by moving from leader-follower to leader-leader. On the limits of top-down hierarchy.

The Trident Career Model by Patrick Kua has three tracks. Each track represents where people spend most of their time or energy.

A solid compilation for engineering managers: 1:1s, performance reviews, hiring and firing, politics and remote work.

Software development is about people: when, how and where they work best together. Not about languages, tools or fast machines.

Leadership practices are small things done repetitively over time. Managers tell you where you are, leaders tell you where you're going.

As a manager your work is to create clarity, clarity, and more clarity.

Zombie Scrum Survival Guide reveals why Scrum runs aground and shows how to supercharge your Scrum outcomes, while having a lot more fun along the way.

Understanding the product owner’s role and envisioning the product.

Sutherland on Scrum: how to define what you are trying to achieve, set up the team for it, and track progress to done.

Andy Grove's Intel classic on managerial leverage, meetings, decisions and how to get the most output from a team.

Camille Fournier maps the path from engineer to CTO: 1:1s, mentoring, and what changes at each level of technical leadership.

A five-day formula for going from idea to prototype to decision, saving your team weeks of building the wrong thing.
Embracing change is not optional in software. How to create the spaces your team needs to leave the comfort zone and keep learning.