Breaking Free from the Request Ticket Trap

Why Engineers Need Product Thinking

Author

Matt Watson
December 03, 2024

I've noticed a dangerous pattern that's killing engineering productivity.

Most developers are stuck in a cycle of passively waiting for tickets, following requirements, and shipping features without understanding why they matter.

The Real Cost of Passive Development

During a recent Product Driven episode, my guest Nax and I discussed how this "ticket-driven" mindset creates serious problems. "What developers don't realize is that users don't care about the code – they care about accomplishing their jobs," I explained.

When engineers just sit around waiting to be told what to do, several problems emerge:

  • They get stuck more often because they lack context

  • They make poor technical decisions without seeing the bigger picture

  • They build overly complex solutions to simple problems

  • They miss opportunities for innovative solutions

Why Engineers Fall Into This Trap

The problem isn't your engineers – it's how we've structured software development.

As Nax pointed out during our discussion, "Product thinking helps engineers align their technical work with the overall goal of the product."

Unfortunately, most companies have created systems where engineers are completely separated from users:

  • They don't attend product planning meetings

  • They rarely talk to customers

  • They're excluded from strategic discussions

Breaking Free from the Trap

At Full Scale, we've helped hundreds of companies build better engineering teams.

Here's what we've learned about transforming ticket-followers into product thinkers:

Involve Engineers Early: Nax emphasized that "participating in meetings with product managers to grasp the product roadmap and strategic direction" is crucial. Don't just invite engineers to planning meetings – make their attendance mandatory.

Encourage Direct User Contact: Learning from stakeholders, talking with UX designers... would really help develop their product mindset," Nax shared. Engineers need to understand how their work impacts real people.

Build Product Ownership: Stop asking "What's the requirement?" and start asking "What problem are we solving?" Give engineers responsibility for outcomes, not just output.

The AI Factor

This shift becomes even more critical as AI transforms software development.

As I mentioned in our discussion, while AI might help with coding, it can't understand user needs or make product decisions. Engineers who can think beyond code and understand product impact will become increasingly valuable.

The Bottom Line

The best engineers I've worked with aren't the ones who write the prettiest code or close the most tickets. They're the ones who understand why they're building what they're building and how it helps users succeed.

At Full Scale, we train our developers to think this way from day one. That's why our clients consistently tell us our developers don't just write code – they contribute to product success.

Want to Learn More?

This article is based on my conversation with Nax on Product Driven. Watch the full episode where we dive deeper into:

  • How to develop product thinking in engineering teams

  • Practical ways to bridge the gap between engineering and product

  • The future of engineering in an AI-driven world

  • Real examples of successful product-focused development

Want to transform your team with a Product-Driven Mindset

Reply

or to participate.