It's easy to understand why it's still tempting to present a project's progress in phases like these:

• Requirements: 100%
• Development: 80%
• Testing: 30%
• Deployment: 0%

On paper, the project looks nearly finished. In reality, nothing usable has been delivered.
This is the trap of “% complete” reporting. It creates the illusion of progress without telling us the one thing that matters: when will value actually be available to customers?

"Every system is perfectly designed to get the result that it does." – W. Edwards Deming
​Why Systems Thinking MattersMost problems we face at work and in life aren’t isolated. They’re the result of many interconnected parts interacting over time. Yet we often try to solve them with quick fixes that treat symptoms instead of root causes.
Systems thinking is a way of seeing the whole instead of just the parts. It helps you understand how structure drives behavior and why well‑intentioned solutions sometimes make things worse.
This article discusses what systems thinking is and some examples of how to apply it in the real world.

Christopher Nolan’s Oppenheimer is, at its core, a story about building something unprecedented: the atomic bomb. While the ethical implications of the Manhattan Project are enormous (and should never be overlooked), the film also provides useful lessons in leadership, strategy, and execution that can still be applied today.
Here are some product management principles that stood out to me after reflecting on the movie:

In many teams I’ve worked with, when a challenge pops up there's often a rush to adopt specific tools, frameworks, or processes in hopes of improving productivity or alignment. This can be new apps for tracking work or communicating, new meetings or documentation practices. Sometimes this can help, but many times it feels like the issues that the team set out to solve haven't really gone away.
A big reason for this is that it is often easier to prioritize practices over principles.

I was a big fan of Rework and always felt the principles of that book were a great embodiment of the spirit of Agile (even though 37signals doesn't necessarily follow any of the frameworks that have been popularized alongside Agile). This made it particularly exciting when the book Shape Up was released which outlined their approach to product development.
When I started reading Shape Up, I knew there would be many great takeaways. I didn't, however, expect it to challenge so many assumptions I’ve internalized from years of working in Agile environments.
Below are a few of the ideas that really stood out to me:

Ever since I was in school, one thing I've always done first thing in the morning is make my bed. Since it seems like a relatively simple task I never really thought about the effect it had on the rest of of my day, over the years it’s become a popular example of how small actions can create flow and set the tone for the rest of the day. That single task delivers an early win, which gives a sense of order, accomplishment, and forward motion before you’ve even had your coffee.
That’s momentum in action.

n many organizations, there’s an unspoken belief that the most efficient system is one where everyone is operating at 100% capacity. On the surface, this seems logical (after all, idle time looks like waste) and if every person is busy all the time, surely the system is producing maximum output… right?
Unfortunately, reality doesn’t work that way. Optimizing for full utilization often creates hidden costs, slows the system as a whole, and erodes resilience.

I've always loved the idea of checklists, but was fairly skeptical on how well they worked in the real world based on how I had seen people using them. That all changed, however, when I read The Checklist Manifesto by Atul Gawande.

Whether you’re leading product strategy, closing a sales deal, resolving team conflicts, or simply trying to figure out where to eat with our spouse, you’re negotiating more often than you might realize.
Chris Voss, a former FBI hostage negotiator, wrote Never Split the Difference to show how high-stakes negotiation principles can be applied in everyday life. I've now read this several times (and watched Chris's MasterClass) and each time I revisit it I'm amazed with how applicable the principles are to almost any interaction and how easy it is to start bringing the book's tactics into my day to day.
I highly recommend reading the entire book, but I wanted to share some of the takeaways that I have continued to come back to year after year:

​Most teams I’ve worked with don’t struggle because of a lack of talent, effort, or ideas. The real issues are usually systemic (i.e. hidden constraints disrupt their flow). Teams often make fast progress at first, but momentum fades as bottlenecks emerge, handoffs stall, and priorities collide. Everyone’s busy, but the outcomes can often lag.
That’s where the Theory of Constraints (TOC) comes in.