Actually, as a Software Engineer, I would embrace founder mode

Paul Graham’s “Founder Mode” essay has stirred up some important conversations about how companies grow and adapt. While it’s written for founders, there’s a lot here for software engineers too. Working closely with a founder isn’t about being micromanaged; it’s about learning different ways of thinking that can help us become better at what we do.

Welcoming Founders into Sprint Reviews

As software engineers, we often focus on the technical details and the immediate tasks at hand. But inviting a founder into our sprint reviews can offer a fresh perspective. Founders bring a deep understanding of the customer and the problem space. Their feedback can help us see beyond the code and think about the bigger picture—how what we’re building affects the customer’s experience.

Imagine having a founder in a sprint review, not to tell us what to do, but to share insights about the customer’s needs and how our work aligns with those needs. This isn’t about changing who we are as engineers; it’s about gaining exposure to new ways of thinking that might help us better understand the impact of our work.

Learning from Founders in Problem-Solving Discussions

Getting the chance to work directly with a founder in problem-solving sessions can be incredibly valuable. Founders often have a unique approach to thinking about problems and solutions, one that is shaped by their close relationship with the customer and their drive to solve real problems.

Welcoming founders into these discussions gives us a chance to learn how they approach challenges, how they weigh different options, and what they consider when making decisions. Why do they believe a certain solution will work? How do they prioritize customer needs over technical perfection? This isn’t about us adopting their mindset wholesale, but rather understanding the thought processes that have led them to success.

Exposure to Diverse Ways of Thinking

Being open to the founder’s involvement in our processes isn’t about becoming like them. It’s about getting exposure to different ways of thinking and problem-solving. As engineers, we often have a deep technical focus. Founders, however, might approach problems with a broader view, considering customer impact, speed of delivery, and long-term goals.

This exposure helps us build a more well-rounded perspective. We can adapt the elements that resonate with us and apply them to our own problem-solving processes. Maybe it means being more open to shipping a quick solution to learn faster, or maybe it’s about asking different questions when we’re faced with a new challenge.

Adapting and Learning

By welcoming founders into our sprint reviews and problem-solving sessions, we’re creating opportunities to learn from their experience and their approach. This collaboration can sharpen our skills and help us see our work through a different lens.

It’s about being curious, open to new ideas, and willing to adapt what works best for us. By doing so, we not only improve our technical skills but also our ability to create solutions that truly make a difference for the customer. This kind of growth mindset can make all the difference in our careers and the impact we have.