Working with Engineering
Teach AI like junior engineers, not magic tools
Cross-functional proximity beats process
Detail drives execution, not autonomy
B2B buyers need education, not pressure
Hire for what they've done, not where they've been
Product and sales tension signals healthy growth
Understaffing forces focus, overstaffing breeds politics
Platform teams need different validation cycles
Clear why beats detailed how
Code generation changes everything about velocity
Visual prototypes dissolve communication barriers
Hell yes or rework the request
True expertise comes from going all the way
Build redundancy before you need flexibility
Great developers self-organize around technical debt
Technology multiplies sales effectiveness
Network breadth determines execution capacity
Common Questions
How can I get engineers to provide accurate estimates on development timelines?
Engineers often underestimate the time needed to build features they advocate for, compared to features you request as a PM. Involving engineers directly in the design and planning process can help align their motivations and lead to more realistic timelines.
See what experts sayHow should I work with AI tools like Devin in my product development process? I'm worried they might not be as capable as I need them to be.
Treat AI tools like new junior engineers on your team. Give them specific, bite-sized tasks to work on, and provide guidance and support as they learn. Expect some trial and error, but focus on building up their capabilities over time rather than relying on them to be perfect from the start.
See what experts sayHow important is it to have a formal process for my team to collaborate across functions like engineering, design, and product management?
While formal processes are important, proximity and shared goals between cross-functional team members can be even more impactful. Aim to have your engineering, product, and design teams physically close together and aligned on common objectives. This allows for more spontaneous collaboration and a deeper shared understanding of customer needs.
See what experts sayHow much detail should I provide to my engineering team when working on a new feature?
Providing the right level of detail is crucial for successful execution. Focus on delivering clear, comprehensive specifications that give your engineers a solid understanding of what to build. The amount of detail you need may vary based on your team's experience, so communicate closely to find the right balance.
See what experts sayHow can I convince engineering to adopt the new product management tools and processes?
Resist the temptation to pressure engineering. Instead, focus on educating them about the market and how the new tools and processes can benefit their work. Involve the engineering "champion" in the decision-making process so they feel empowered to make the best choice for the team.
See what experts say